In a scale-out Prism Central deployment, what additional functionality does configuring an FQDN instead of a Virtual IP provide?

Question

Options

• ALoad balancing
• BResiliency
• CSegmentation
• DSSL Certificate

• A
  92% (58)
• B
  5% (3)
• C
  2% (1)
• D
  2% (1)

Explanation

In a scale-out Prism Central deployment (3 or more VMs), a Virtual IP (VIP) provides a single floating IP address that routes traffic to one active Prism Central node at a time, which provides resiliency/failover but not distribution. Configuring an FQDN (Fully Qualified Domain Name) with multiple DNS A records pointing to all Prism Central nodes enables DNS round-robin load balancing, distributing client connections across all nodes in the scale-out cluster, improving throughput and reducing load on any single node.

Why the other options are wrong:

• B (Resiliency): Resiliency is already provided by the Virtual IP configuration and the scale-out architecture itself; FQDN does not add new resiliency.
• C (Segmentation): Network segmentation is a separate concept related to VLANs and security policies.
• D (SSL Certificate): SSL certificates are tied to the hostname/FQDN in general, but an FQDN is not uniquely required for SSL - certificates can also be issued for IPs.

No community discussion yet for this question.