SK0-004 · Question #864
An administrator is sizing the CPU requirements of a new application. The application requires 12 guest VMs to run concurrently on the host. If each guest requires 500MHz of CPU and the server has…
The correct answer is D. 3.2GHz CPU. The total CPU demand is 12 x 500 MHz = 6,000 MHz; with two sockets, only a 3.2 GHz CPU provides enough aggregate capacity (6,400 MHz) to meet that requirement.
Question
An administrator is sizing the CPU requirements of a new application. The application requires 12 guest VMs to run concurrently on the host. If each guest requires 500MHz of CPU and the server has two sockets, which of the following CPUs will ensure there are sufficient host CPU resources for this application?
Options
- A1.6GHz CPU
- B2.0GHz CPU
- C2.5GHz CPU
- D3.2GHz CPU
How the community answered
(57 responses)- A5% (3)
- B2% (1)
- C12% (7)
- D81% (46)
Why each option
The total CPU demand is 12 x 500 MHz = 6,000 MHz; with two sockets, only a 3.2 GHz CPU provides enough aggregate capacity (6,400 MHz) to meet that requirement.
1.6 GHz x 2 sockets = 3,200 MHz total, which covers only about 53% of the 6,000 MHz required, leaving VMs severely resource-starved.
2.0 GHz x 2 sockets = 4,000 MHz total, which is 2,000 MHz short of the 6,000 MHz needed for all 12 concurrent VMs.
2.5 GHz x 2 sockets = 5,000 MHz total, which is still 1,000 MHz below the 6,000 MHz required and provides no headroom for hypervisor overhead.
A 3.2 GHz CPU in each of the two sockets yields 6,400 MHz of total host CPU capacity, which exceeds the 6,000 MHz needed for all 12 guest VMs (12 x 500 MHz). The other options all fall below the 6,000 MHz threshold and would cause CPU contention and degraded VM performance. Sufficient headroom above the minimum is also important for hypervisor overhead, making 3.2 GHz the only safe choice.
Concept tested: VM CPU resource sizing across multiple sockets
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-resource-management/GUID-6C0EEB01-5016-4C71-B18A-A8B1E9A3FA0B.html
Topics
Community Discussion
No community discussion yet for this question.