Harborview operations need the SDN plane that stores user configuration and hosts the NSX UI and API. Which plane is that?
Select an answer to reveal the explanation.
Short Explanation
The management plane is city hall: the UI, the API, and the file cabinet of desired config. Host forwarding tables do the street work, but they are not where operators save the design. vSAN witness is a storage construct, not NSX city hall.
Full Explanation
The management plane, provided by NSX Manager, is the SDN plane that stores user configuration and hosts the UI and API for Harborview operations. Desired state is entered and stored there. The data plane on each ESXi host forwards packets; it is not the configuration store. The vSAN witness does not persist NSX objects. Local control alone without a central manager is not how NSX-T presents UI/API configuration storage. Exam caveat: NSX Manager clusters also participate in central control functions, but exam identification of UI/API/config store maps to management plane. Operational check: make a segment change in the NSX UI/API and confirm it is recorded as manager configuration before checking host realization. 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.