An engineer is configuring AHV networking for a new three-node Nutanix cluster. The cluster must be managed by Prism Element and Prism Central, and CVMs must communicate for cluster services. Which networking requirement must be met for the CVM IP addresses?
Select an answer to reveal the explanation.
Short Explanation
Think of the management VLAN as the cluster's control-room phone line. Your CVMs need that line so Prism, NCC, and cluster services can talk to every CVM. Put them on storage or VM data VLANs and the cluster can still move I/O while you can't manage it.
Full Explanation
CVM IP addresses are the network identity used for cluster control traffic. They let Prism Element, Prism Central, NCC, LCM, and inter-CVM services reach each controller VM on every node. For that reason, those addresses must be placed on the management VLAN, or an equivalent management network, so administrators and management services can reach them consistently. A dedicated storage VLAN is wrong because it is intended for storage data movement between hosts and controllers, not for controller management reachability. A VLAN shared with VM data traffic is wrong because it mixes tenant workload traffic with cluster control traffic, which can create reachability, security, and troubleshooting problems. A separate untagged native VLAN is wrong because an untagged native network is not a reliable management placement; it may lack the required routing, ACLs, and monitored reachability that management traffic needs. Exam caveat: do not confuse the CVM IP used for management with the storage data path or the VM data path. Operational check: confirm each CVM IP is in the management subnet, then test reachability to every CVM IP and to Prism Element from the management network.