Ahhh it is D. D. A new virtual data center will be created for each branch site Just tested it.

A >> Only one vCenter is planned to be deployed. Deploying more is not necessary, and would need more licences. B >> Won’t help anything for the duplicate names C >> Won’t help either D >> Having multiples vSphere Datacenters is the only way to have duplicate names in the same vCenter Server

I give credit to nemisis95. D is the answer. A. License cost - No further budget B. Host and Cluster folder won't do anything - Network Folder will allow duplicate ports C. Automation script will be updated - Requirement to replicate DPG's D. New DC - Allows duplicate DPG's (just tried it)

D, new DC object can allow the same naming for portgroups and virtual switches.

D. A new virtual data center will be created for each branch site

D. A new virtual data center will be created for each branch site

It is b. The vds s a construct within a dc so to use a single vds they need to have the locations within the same cd in centre. https://communities.vmware.com/t5/ESXi-Discussions/Distributed-Switch-across-datacenters-and-clusters/td-p/1684595

IT is D

D is correct one, i have verified it.

D Hosts provisioned with vSphere Auto Deploy cache the image (stateless caching): Set up and apply a host profile for stateless caching. You can cache the image on a local disk, a remote disk, or a USB drive. Continue provisioning this host with vSphere Auto Deploy. If the vSphere Auto Deploy server becomes unavailable, for example because hundreds of hosts attempt to access it simultaneously, the host boots from the cache. The host attempts to reach the vSphere Auto Deploy server after the boot operation to complete configuration. Hosts provisioned with vSphere Auto Deploy become stateful hosts: Set up and apply a host profile for stateful installs. When you provision a host with vSphere Auto Deploy, the image is installed on the local disk, a remote disk, or a USB drive. For subsequent boots, you boot from the disk. The host no longer uses vSphere Auto Deploy. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.install.doc/GUID-C6FBA22C-048A-455F-9D45-58834445ACA5.html

Changed my answer to C C. The automation script will be updated to reflect unique naming for each site Process of elimination. A. A new vCenter Server will be deployed for each branch site No - "100 branch sites connected to a single VMware vCenter Server within the primary data center" B. A new host and cluster folder will be created for each branch site Just tested this. You can't create a "New Host and Cluster Folder" in the Networking section of vCenter D. A new virtual data center will be created for each branch site Even with a Virtual Datacenter per branch, you still won't be able to replicate the names of the virtual distributed port groups

Changing my answer to B. A new host and cluster folder will be created for each branch site https://docs.delltechnologies.com/bundle/PS_MG_1000V_VDS/page/GUID-942B8E0B-439B-4602-9E01-93372180586E.html "Starting with vCenter 6.0, duplicate port groups names are allowed across different distributed switches if those switches are in different network folders." I know the link says network folders, but I assume it would work with host and cluster folder too

maybe will be C?

D. new Datacenter object

I'd say D