3V0-21.23 · Question #40
An architect is designing a new VMware software-defined data center (SDDC) that will consist of 100 branch sites connected to a single VMware vCenter Server within the primary data center. To allow…
The correct answer is D. A new virtual data center will be created for each branch site. Creating a separate virtual datacenter (VDC) object per branch site within the single vCenter Server solves the naming conflict because each VDC gets its own namespace for vSphere Distributed Switch port groups - allowing identical port group names to exist across all 100 sites…
Question
An architect is designing a new VMware software-defined data center (SDDC) that will consist of 100 branch sites connected to a single VMware vCenter Server within the primary data center. To allow for the use of existing automation scripts, there is a requirement to replicate the names of the virtual distributed port groups across all sites. The procurement team purchases licensing and there is no further budget allocated. Which design decision should the architect make to meet this requirement?
Options
- AA new vCenter Server will be deployed for each branch site
- BA new host and cluster folder will be created for each branch site
- CThe automation script will be updated to reflect unique naming for each site
- DA new virtual data center will be created for each branch site
How the community answered
(28 responses)- A7% (2)
- B14% (4)
- C4% (1)
- D75% (21)
Explanation
Creating a separate virtual datacenter (VDC) object per branch site within the single vCenter Server solves the naming conflict because each VDC gets its own namespace for vSphere Distributed Switch port groups - allowing identical port group names to exist across all 100 sites without collision, while keeping everything under one vCenter license.
Why the distractors fail:
- A - Deploying a new vCenter Server per site would require 100 additional vCenter licenses, directly violating the "no further budget" constraint.
- B - Host and cluster folders are purely organizational containers; they share the same VDS namespace as the parent datacenter and do nothing to resolve duplicate port group naming conflicts.
- C - Updating the automation scripts explicitly contradicts the stated requirement to preserve existing scripts and their naming conventions.
Memory tip: Think of a VMware Virtual Datacenter as a "port group namespace fence." Same names are fine across different VDCs - just like two cities can both have a "Main Street" because they're in different jurisdictions. One vCenter, many VDCs = one budget, many namespaces.
Topics
Community Discussion
No community discussion yet for this question.