Two Edge VMs should share settings and provide high availability for city NAT. Which SDN building block groups them?
Select an answer to reveal the explanation.
Short Explanation
An Edge cluster is the HA team for the appliances that do NAT and other centralized jobs. A vSphere DRS cluster can host those VMs, but it is not the NSX object that fails over Edge services.
Full Explanation
Two Edge VMs that must share settings and provide high availability for city NAT are grouped into an NSX Edge cluster. That SDN building block is the collection of Edge nodes with shared configuration that provides HA for centralized services such as NAT, load balancing, and other north-south functions the distributed host data plane cannot fully own alone. A vSphere DRS cluster can host those Edge VMs on compute and help with placement, but DRS membership is not the NSX object that defines Edge service failover. A Horizon Cloud pod failing traffic over to a Unified Access Gateway confuses EUC access infrastructure with NSX Edge HA for fabric services. A Carbon Black sensor group cannot elect an active NAT node or synchronize Edge service state. Exam caveat: good designs still place Edges with anti-affinity on appropriate compute, yet operators must create and monitor the NSX Edge cluster itself for service HA. Knowing active/standby exists matters more at associate level than memorizing every failover timer. Operational check: create an Edge cluster containing both Edge nodes, attach the Tier-0 or Tier-1 services that own NAT, fail the active Edge during a maintenance window, and confirm NAT continuity on the peer while documenting that DRS alone did not define that failover domain.