The city is standing up NSX-T for civic datacenter security. How should NSX-T Manager be deployed for production?
Select an answer to reveal the explanation.
Short Explanation
One nested lab Manager is a folding table; production needs a three-legged desk. Stand up a three-node NSX-T Manager cluster with a VIP so DFW policy still has a control plane if a node dies.
Full Explanation
Production civic NSX-T security needs a resilient control plane: deploy a three-node NSX-T Manager cluster with a cluster virtual IP so administrators and API clients keep a stable management endpoint while Distributed Firewall and related security services survive a Manager node loss. For a city datacenter, that cluster-plus-VIP design is the production pattern, not a temporary lab footprint.
A single nested lab Manager lacks high availability and is unsuitable as the municipal production control plane. Installing Manager only from a workstation ISO without clustering likewise leaves a single point of failure for all security policy. Using vCenter HA as a substitute does not replace NSX Manager clustering—the NSX control plane has its own cluster and VIP requirements independent of vCenter HA.
Exam caveat: production design questions expect three Managers plus cluster VIP; lab-sized single Managers or “vCenter HA covers NSX” answers are distractors.
Operational check: verify three Managers healthy, confirm the cluster VIP answers for administrators, document Manager configuration backup and restore, and capture cluster membership in the city datacenter security build record so operations can recover the fabric after node loss.