3V0-21.23 · Question #23
An architect is designing a series of new vSphere environments for an organization. The environments will be deployed in their US-East and US-West region data centers. Each data center may have one…
The correct answer is B. Create a local content library for the primary vSphere environment in each data center. Option B is correct because the requirements call for a localized content library per data center, not per individual vSphere environment. Since Enhanced Linked Mode (ELM) connects all vSphere environments within a data center, a single content library on the primary vCenter is…
Question
An architect is designing a series of new vSphere environments for an organization. The environments will be deployed in their US-East and US-West region data centers. Each data center may have one or more dedicated vSphere environments. Only the vSphere environments within a data center will be configured with Enhanced Linked Mode. The Chief Technology Officer (CTO) has authorized the use of VMware vRealize Automation Cloud for automation. The build team creates standardized virtual machine images for various operating systems in Open Virtualization Format (OVF) and publishes the latest version on an as-needed basis to an internal HTTPS-accessible repository. The architect must design a content library topology that meets the following requirements:
- A localized content library must be available in each data center.
- Each content library must be updated when an image is updated and released by the build
team.
- The cloud automation platform must be able to consume the latest approved content library
images.
- It must leverage the existing build team processes.
What should the architect recommend to meet the requirements?
Options
- AWork with the build team to create a local content library for each vSphere environment.
- BCreate a local content library for the primary vSphere environment in each data center.
- CWork with the build team to automate a JSON-based manifest to the repository when changes
- DWork with the build team to automate a JSON-based manifest to the repository when changes
How the community answered
(18 responses)- A6% (1)
- B72% (13)
- C6% (1)
- D17% (3)
Explanation
Option B is correct because the requirements call for a localized content library per data center, not per individual vSphere environment. Since Enhanced Linked Mode (ELM) connects all vSphere environments within a data center, a single content library on the primary vCenter is automatically accessible to every other vCenter in that same data center - satisfying the localization requirement without redundant copies. Additionally, a subscribed content library on each primary vCenter can point to the build team's existing HTTPS OVF repository, so updates flow automatically when the build team publishes new images, and vRealize Automation Cloud can consume them directly.
Option A is wrong because it places a separate local library in every vSphere environment, ignoring the sharing capability that ELM already provides. This violates the "leverage existing build team processes" requirement by forcing manual or duplicated synchronization across environments within the same data center.
Options C and D are wrong (both appear truncated, but they describe automating a JSON-based manifest) because while a JSON manifest is how subscribed content libraries sync from an HTTPS repository, these options focus only on the update mechanism - not the architectural placement of the libraries. The question asks for the topology recommendation, and without anchoring libraries to the primary vCenter per data center, ELM-based sharing is unused.
Memory tip: Think "one library per data center, not per vCenter." ELM handles intra-DC sharing, so you only need one library in each DC - place it on the primary vCenter and let ELM do the rest.
Topics
Community Discussion
No community discussion yet for this question.