NSX must inventory the property-appraiser ESXi hosts and VMs so groups and transport-node prep can see them. Which vSphere product role is that compute manager?
Select an answer to reveal the explanation.
Short Explanation
vCenter is the civic property roll NSX reads: hosts, clusters, and VMs. Avi load-balances applications, Horizon brokers desktops, and vSAN File Service shares files. None of those is the compute manager.
Full Explanation
vCenter Server is registered with NSX as the compute manager so NSX can inventory ESXi hosts, clusters, and virtual machines for transport-node preparation and grouping on the property-appraiser estate. vCenter is the civic property roll NSX reads before it can see hosts and VMs in groups. NSX Advanced Load Balancer is an application-delivery product and is not the host inventory source for NSX preparation. Horizon Connection Server is EUC brokering and is not the compute manager. vSAN File Service presents file shares; it is not the NSX inventory source for clusters and VMs. Exam caveat: without a healthy compute-manager registration, Inventory VM lists and many dynamic groups will not populate even if the underlay is fine. Operational check: in NSX System settings, confirm vCenter is registered and connected as compute manager, open Inventory Virtual Machines for appraiser workloads, and reject Avi, Horizon, and vSAN File Service as the inventory feed. 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. 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.