2V0-13.25 · Question #28
A company is deploying a new VMware Cloud Foundation (VCF) environment to support their growing infrastructure requirements. - The company is planning to scale their environment over time by adding…
The correct answer is B. Use multiple workload domains for each department and ensure that each workload domain is. VMware Cloud Foundation scales using workload domains (WLDs). Each WLD provides its own vCenter Server, NSX Manager, and lifecycle independence through SDDC Manager. By using multiple WLDs for each department, the architecture supports independent scaling, policy separation…
Question
A company is deploying a new VMware Cloud Foundation (VCF) environment to support their growing infrastructure requirements.
- The company is planning to scale their environment over time by
adding more workload domains as new applications and departments are onboarded.
- The company requires that the architecture must be highly scalable
and flexible, able to accommodate both current and future demands. They also require a seamless transition when adding new workload domains. Which design decisions should the architect make to meet the stated scalability requirements and facilitate the future growth?
Options
- AUse a single workload domain for all departments and increase the size of the vSphere clusters
- BUse multiple workload domains for each department and ensure that each workload domain is
- CUse a single workload domain and rely on storage and network scaling to accommodate future
- DUse multiple workload domains for each department but combine them into a single vSphere
How the community answered
(34 responses)- A3% (1)
- B76% (26)
- C6% (2)
- D15% (5)
Explanation
VMware Cloud Foundation scales using workload domains (WLDs). Each WLD provides its own vCenter Server, NSX Manager, and lifecycle independence through SDDC Manager. By using multiple WLDs for each department, the architecture supports independent scaling, policy separation, and lifecycle management. Option A or C restricts flexibility as all tenants would share a single WLD, leading to lifecycle constraints and "noisy neighbor" issues. Option D contradicts best practices: multiple departments should not share a single cluster inside a WLD when separation and lifecycle flexibility are required. This design ensures seamless addition of new workload domains as departments and applications grow.
Topics
Community Discussion
No community discussion yet for this question.