A new city API gateway is delayed because the hardware firewall's licensed feature set does not include the needed function. Which traditional challenge do software-defined network services address?
Select an answer to reveal the explanation.
Short Explanation
Waiting on a firewall SKU is like the city holding a new bus route until a particular vendor ships a bolt-on. Software-defined services add the function in NSX without that hardware queue. The API gateway should not sit idle on a license dongle.
Full Explanation
Hardware-feature lock-in delays a city API gateway when the physical firewall's licensed feature set lacks a needed function. Software-defined network services can add functions without waiting on an appliance SKU or license upgrade cycle. NSX-T is not required to wait until the hardware firewall licenses the same feature. Horizon True SSO licenses do not solve network-service feature gaps. Carbon Black container scanning licenses are not the gating item for network services here. Exam caveat: edge integration and compliance reviews may still involve physical firewalls; the exam contrast is agility of software services versus appliance feature locks. Operational check: deliver the needed network function (for example load balancing or gateway firewall policy) as an NSX service for a non-prod API gateway without a hardware feature license change. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems. Record realization state and underlay health in the runbook used by on-call city operators. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent.