CV0-003 · Question #323
A Type 1 hypervisor has the following specifications: RAM 128GB CPU 4 socket quad-core Storage 16TB Each VM must have 8GB RAM, 1 vCPU, and 512GB storage. Which of the following is the MAXIMUM number…
The correct answer is A. 14. The maximum VM count is 14, constrained by available RAM after accounting for hypervisor overhead, which consumes approximately 16GB of the 128GB physical RAM.
Question
A Type 1 hypervisor has the following specifications:
RAM 128GB CPU 4 socket quad-core Storage 16TB Each VM must have 8GB RAM, 1 vCPU, and 512GB storage. Which of the following is the MAXIMUM number of VMs that can be hosted on this hypervisor?
Options
- A14
- B15
- C31
- D32
How the community answered
(45 responses)- A78% (35)
- B13% (6)
- C7% (3)
- D2% (1)
Why each option
The maximum VM count is 14, constrained by available RAM after accounting for hypervisor overhead, which consumes approximately 16GB of the 128GB physical RAM.
A Type 1 hypervisor requires a portion of host RAM for its own kernel, management services, and control domain - on a 128GB, 4-socket host this overhead is approximately 16GB, leaving 112GB available for guest VMs. At 8GB RAM per VM, 112 / 8 = 14 VMs. Storage (16,384GB / 512GB = 32 VMs) and CPU (16 physical cores / 1 vCPU = 16 VMs) are not the binding constraints; RAM after hypervisor overhead is the bottleneck.
15 VMs would consume 120GB of RAM for guests, leaving only 8GB for the hypervisor itself, which is insufficient for stable operation of a 4-socket Type 1 hypervisor.
31 VMs would require 248GB of RAM for guest workloads alone, which far exceeds the 128GB physically installed in the host.
32 is derived from the storage calculation only (16,384GB / 512GB) and ignores the RAM constraint, which is the actual limiting resource after hypervisor overhead.
Concept tested: Type 1 hypervisor VM density calculation with resource overhead
Source: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server
Topics
Community Discussion
No community discussion yet for this question.