An administrator is tasked with making an existing vSphere Supervisor highly available by adding two additional vSphere Zones. How should the administrator perform this task?

The topology of a vSphere Supervisor, whether it runs on a single vSphere cluster or is stretched across three clusters in a multi-zone configuration, is determined at the time of its initial enablement. An existing Supervisor that was deployed on a single vSphere cluster (a single zone) cannot be converted or extended into a multi-zone Supervisor by adding more vSphere clusters/zones to it after the fact. To create a highly available, multi-zone Supervisor, it must be configured with three vSphere Zones from the outset.

B. Create a new multi-zone deployment and assign an existing vSphere cluster to it: This is not a valid procedure. A multi-zone Supervisor is enabled on three clusters simultaneously, not by assigning an existing one.
C. Create a new vSphere Zone and add the Supervisor to the new vSphere Zone: This reverses the relationship. A Supervisor runs on a cluster, which is placed in a zone; you cannot "add" a Supervisor to a zone.
D. Select Configure, select vSphere Zones, and click Add New vSphere Zone: This action creates the vSphere Zone object in vCenter but does not extend an existing Supervisor into it.

1. VMware vSphere with Tanzu Documentation, "vSphere with Tanzu Architecture and Components," Section: "Supervisor Deployment Topologies". This section describes the two topologies: "A Supervisor that is deployed on a single vSphere cluster" and "A Supervisor that is deployed on three vSphere clusters." It clarifies these are distinct deployment models.

2. VMware vSphere with Tanzu Documentation, "Deploy a Supervisor with a Three-Zone Configuration," Section: "Prerequisites". The prerequisites clearly state the need for three vSphere clusters, each in a separate vSphere Zone, before enabling the Supervisor, implying this is a day-0 configuration.