Operators must list the compute VMs that NSX already knows from the city's vCenter compute manager. Which NSX GUI path shows that inventory?
Select an answer to reveal the explanation.
Short Explanation
NSX keeps a city roster of VMs it learned from vCenter. That roster is Inventory, then Virtual Machines — not the host-node list, not Horizon Machines, and not vSAN objects.
Full Explanation
After a vCenter compute manager is registered, NSX shows discovered compute VMs under Inventory, then Virtual Machines. That roster is the city list of VMs NSX learned from vCenter—not the host-node list, not Horizon Machines, and not vSAN objects. System Fabric Nodes is the transport-node view for hosts and Edges, not the VM roster. Horizon Administrator Machines is an EUC inventory. vSAN Virtual Objects are storage objects, not the NSX compute inventory. Exam caveat: if Inventory VMs is empty, check compute-manager registration before assuming NSX is broken. Operational check: open Inventory Virtual Machines, confirm city VMs from vCenter appear, cross-check that Fabric Nodes shows hosts separately, and reject Horizon Machines and vSAN Capacity views as the NSX VM inventory path. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish.