The municipal NSX deployment uses a cluster of three appliances that host the UI, API, and central control. Which SDN building block is that cluster?
Select an answer to reveal the explanation.
Short Explanation
Those three appliances are the NSX Manager cluster—the civic trio that keeps the UI, API, and central control standing. Edges forward services at the boundary; they do not replace Manager. Horizon Connection Servers and vSAN witnesses are different clusters.
Full Explanation
The NSX Manager cluster is the SDN building block of three appliances that host UI, API, and central control with high availability for the municipal deployment. It merges management and central control roles in NSX-T architecture. Three standalone Edge nodes do not replace NSX Manager. A three-node vSAN witness cluster does not store Geneve keys as the NSX control plane. A three-node Horizon Connection Server cluster is not the NSX control plane. Exam caveat: Edge clusters are separate and handle services/north-south; do not conflate Manager HA with Edge services HA. Operational check: verify the civic NSX Manager cluster shows three members healthy and VIP/UI access survives a single manager outage test. 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. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems.