Scale-out Prism Central deployments consist of multiple nodes running the Prism Central service. Nutanix documentation emphasizes that:
"When deploying multi-node Prism Central, an FQDN backed by DNS can provide request distribution across all Prism Central nodes, enabling load balancing and increased concurrency." A Virtual IP in contrast only directs traffic to a single active Prism Central node. Internal behavior notes:
* "A VIP is not active-active; it designates one node as primary for all inbound requests."
* "Using an FQDN with DNS round-robin or an external load balancer allows the cluster to distribute workload across all PC nodes." The FQDN allows:
* distributing API/UI traffic across multiple Prism Central nodes
* improving performance under heavy load
* enabling parallel query handling
* avoiding bottlenecks on the primary node
SSL certificates apply to either VIP or FQDN. Segmentation and resiliency are unrelated to FQDN usage.
Thus, the correct answer is Load Balancing.