Public-safety radio-shop IT is told vCenter Server is the compute manager in the city's SDDC. What role does that identify?
Select an answer to reveal the explanation.
Short Explanation
vCenter is the city's roster of hosts and VMs—the compute manager. NSX still owns the virtual networks those VMs plug into. Mixing the two is like asking the HR directory to run the radio tower.
Full Explanation
vCenter Server is the inventory and control point for hosts and VMs that NSX-T then connects. Public-safety radio-shop IT should identify vCenter as the compute manager: NSX registers it to learn hosts and VMs so networking and security can be applied to those objects. vCenter is not the NSX Edge cluster performing north-south NAT. It is not the Geneve encapsulation format. It does not replace NSX Manager as the distributed firewall policy editor. Exam caveat: compute-manager registration is required for inventory-driven features; networking policy still lives in NSX. Operational check: in NSX, confirm the civic vCenter is listed as a compute manager and that radio-shop hosts/VMs appear for segment and group selection. 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.