3V0-21.23 · Question #34
An architect is designing a VMware software-defined data center (SDDC) solution based on the following customer requirements: - The solution must initially support 1,000 virtual machines - The…
The correct answer is B. The average resource utilization of a virtual machine C. The size (CPU/RAM/storage) of the average virtual machine. To size an SDDC, the architect must work backward from the workload: knowing the average VM size (C) establishes the per-unit resource footprint, and knowing the average resource utilization (B) determines the consolidation ratio - together these two inputs allow calculation of…
Question
An architect is designing a VMware software-defined data center (SDDC) solution based on the following customer requirements:
- The solution must initially support 1,000 virtual machines
- The solution must scale to support the concurrent running of up to 5,000 virtual machines
- The production environment should be delivered across two data centers
- The solution should have a maximum tolerable downtime (MTD) of four hours
- The solution should have a monthly service availability target of 99.8%
Which two assumptions could the architect make based on the information from the customer to help size the solution- (Choose two.)
Options
- AThe number of vSphere hosts in a cluster
- BThe average resource utilization of a virtual machine
- CThe size (CPU/RAM/storage) of the average virtual machine
- DThe guest operating system for each virtual machine
- EThe size (CPU/RAM/storage) of the vSphere hosts
How the community answered
(45 responses)- A11% (5)
- B80% (36)
- D2% (1)
- E7% (3)
Explanation
To size an SDDC, the architect must work backward from the workload: knowing the average VM size (C) establishes the per-unit resource footprint, and knowing the average resource utilization (B) determines the consolidation ratio - together these two inputs allow calculation of total CPU, RAM, and storage requirements across 5,000 VMs. Without assuming these values, it is impossible to estimate how much physical infrastructure is needed.
The distractors are wrong for distinct reasons: A (hosts per cluster) is an architectural output derived after sizing, not an input assumption; D (guest OS) is irrelevant to infrastructure sizing since the hypervisor abstracts the OS layer; and E (host size/specs) is a design decision the architect makes based on the sizing results, not a customer-driven assumption.
Memory tip: Think of sizing as a recipe - you need the ingredient amount (VM size, C) and the burn rate (utilization, B) before you can decide on your shopping list (host count, cluster layout, host specs). Anything that's a result of the calculation cannot also be an input assumption.
Topics
Community Discussion
No community discussion yet for this question.