The 311 team wants repeatable network and security builds driven from the NSX API instead of one-off GUI clicks. Which NSX Data Center benefit matches that use case?
Select an answer to reveal the explanation.
Short Explanation
If 311 environments are a recipe, the API is the mixer that makes the same cake every time. NSX Manager exposes that automation. Recabling, host CLI, and Horizon Client are not the NSX automation benefit.
Full Explanation
Repeatable network and security builds for 311 driven from the NSX API match the automation benefit of NSX Manager API control over network and security objects. Desired-state creation of segments, groups, and DFW rules can be scripted or orchestrated instead of relying on one-off GUI clicks after each application release. Manual recabling of every 311 VLAN after each release is the traditional anti-pattern automation replaces. Handwritten switch configs on each ESXi host are not an NSX API model and do not scale as Policy objects. Horizon Client is an end-user client, not a network-provisioning API for 311. Exam caveat: API automation still requires RBAC, change control, and validation—automation is not a license to skip civic CAB process. Operational check: create a segment and a DFW group via the NSX Policy API in a lab project, compare the realized objects to a GUI-built twin, and store the call sequence in the municipal infrastructure-as-code repository with the same peer review the city uses for other platforms. In municipal operations, record the chosen control and the rejected distractors in the change ticket so future on-call staff understand which failure modes would affect city services. Re-validate after the next maintenance window that the same design still holds for the current NSX build and the agency workloads that depend on it.