City-clerk operators need the component that hosts the NSX graphical user interface and the API for civic network objects. Which high-level component has that role?
Select an answer to reveal the explanation.
Short Explanation
NSX Manager is the clerk's front counter: the GUI, the API, and the management-plane books. Hosts forward packets, vSAN watches disks, and Horizon is a desktop broker. None of those is the NSX console.
Full Explanation
NSX Manager hosts the NSX graphical user interface and API for civic network objects. It is the management plane, and a three-node Manager cluster also provides the central control plane—the clerk's front counter for the GUI, the API, and the management-plane books that define segments, gateways, and security. A host transport node data plane forwards tenant packets and enforces distributed services; it is not the operator UI for creating city-wide objects. The vSAN health service reports storage health and capacity issues, not NSX configuration state. Horizon Connection Server is an EUC broker for desktops and applications and is not the NSX management plane. Exam caveat: operators may glance at vCenter for compute inventory and opaque networks, but the component that hosts the NSX UI and API role on this exam is Manager. Operational check: browse to the NSX Manager VIP or node address, confirm UI and API access for segment and policy objects, create or view a test object, and verify host data planes, vSAN health, and Horizon were not used as substitute consoles for NSX authoring. Keep the civic framing visible in runbooks so the next operator can restate why the correct control fits the agency outcome, why each distractor fails by concept, and which Manager or fabric view proves the design after change.