Memory Overcommitment: How Hypervisors Allocate More Virtual Memory Than Available
A system administrator deploys a Type 1 hypervisor on a physical host with 16 GB of RAM. The administrator creates four virtual machines, each configured with 8 GB of allocated memory. Despite the total allocation being 32 GB, all four VMs operate normally without any performance degradation. The administrator checks and sees that the host's memory usage is steady at 85%. Which virtualization feature is MOST likely enabling this configuration?
Quick Answer
The answer is memory overcommitment, the virtualization feature that allows a hypervisor to allocate more virtual memory to VMs than the physical host actually possesses. This works because hypervisors, especially Type 1 hypervisors, dynamically assign only the memory each VM actively needs, rather than reserving the full configured amount; since VMs rarely use their peak allocation simultaneously, the host can safely oversubscribe memory without performance degradation. On the CompTIA A+ Core 1 220-1101 exam, this concept tests your understanding of how hypervisors optimize resource usage, often appearing in scenarios where total VM allocations exceed host RAM but the system runs normally. A common trap is confusing memory overcommitment with memory ballooning—overcommitment is the policy, while ballooning is a technique to reclaim memory from idle VMs. Remember the mnemonic: “Overcommit means overallocate, not overall use.”
⚠ Common exam trap
Many candidates confuse memory overcommitment with dynamic memory allocation, but dynamic memory adjusts per-VM allocations dynamically rather than allowing the total configured memory to exceed physical RAM without adjustment.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Memory overcommitment
Memory overcommitment allows a hypervisor to allocate more virtual memory to VMs than the physical host actually has, relying on the fact that VMs rarely use their full allocation simultaneously. In this scenario, the host has 16 GB of RAM but the VMs are configured with a total of 32 GB; the hypervisor (Type 1) uses memory overcommitment to assign only the memory actually needed by each VM, keeping host usage at 85% (approximately 13.6 GB) without performance degradation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Memory ballooning
Why it's wrong here
Memory ballooning reclaims pages from VMs under host pressure, but it requires a balloon driver and typically degrades guest performance; here all four VMs run normally with no degradation. It is tempting because ballooning genuinely permits overcommitment, yet it is the right answer only when the host is memory-constrained and guests can tolerate reclaimed pages.
- ✗
Dynamic memory allocation
Why it's wrong here
Dynamic memory allocation reclaims unused RAM from idle VMs, letting four 8 GB allocations share 16 GB. However, the stem shows steady 85% host usage with no degradation, which points to transparent page sharing deduplicating identical memory pages across VMs, not ballooning. Dynamic memory suits overcommitment where VMs genuinely idle.
- ✓
Memory overcommitment
Why this is correct
Memory overcommitment lets the hypervisor allocate more RAM to VMs than physically installed, using techniques such as ballooning, transparent page sharing and swapping to reclaim idle pages. The 32GB allocation on 16GB of host memory succeeds because actual concurrent demand stays below physical capacity.
- ✗
Virtual memory paging
Why it's wrong here
Paging swaps memory to disk, which would cause severe performance degradation, contradicting the reported normal operation. It is tempting because paging does let hosts exceed physical RAM, and it would be correct if the VMs were visibly slow with heavy disk activity.
Go deeper
Related to this question
Learn chapter
Multi-Monitor Configuration
Key term
Dual In-line Memory Module
A Dual In-line Memory Module (DIMM) is a small circuit board that holds memory chips and plugs into a computer's motherboard to provide Random Access Memory (RAM).
Key term
RAM
RAM (Random-Access Memory) is volatile computer memory that temporarily stores data for quick access by the CPU.
About these practice questions
This 220-1101 question is part of Courseiva's 896-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on 220-1101
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A system administrator manages a virtualized web server on a Type 1 hypervisor. The web server's memory usage fluctuates significantly throughout the day due to varying traffic. The administrator wants the VM to automatically use only the memory it needs, allowing the hypervisor to reclaim unused memory for other VMs. Which feature should the administrator configure on the VM?
medium- A.Virtual machine snapshots
- ✓ B.Memory ballooning
- C.Fault tolerance
- D.CPU hot-add
Why B: Memory ballooning is a feature in virtualization that allows the hypervisor to reclaim unused memory from a VM by inflating a 'balloon' driver inside the guest OS, which forces the guest to release memory pages back to the hypervisor. This is ideal for the described scenario where the VM's memory usage fluctuates, as it dynamically adjusts the VM's memory footprint without requiring a reboot or manual intervention.
Variation 2. An administrator manages a virtualized environment running on a Type 1 hypervisor (VMware ESXi). The physical host has 64 GB of RAM. The sum of allocated memory to all running VMs is 80 GB, and the hypervisor is using memory ballooning to reclaim memory from VMs. A critical database VM is experiencing significant performance degradation. Which of the following is the MOST likely cause of the performance issue?
hard- A.The hypervisor is overcommitting CPU resources, causing contention.
- B.The VM's virtual disk is on a slow network storage link.
- ✓ C.The database VM is experiencing memory starvation due to the hypervisor reclaiming memory via ballooning.
- D.The hypervisor has insufficient network bandwidth for inter-VM communication.
Why C: The physical host has only 64 GB of RAM, but the sum of allocated memory to all running VMs is 80 GB, which is a 25% overcommitment. VMware ESXi uses memory ballooning to reclaim memory from VMs by forcing the VM's balloon driver to allocate guest memory, which the hypervisor then reclaims for other VMs. The critical database VM is experiencing significant performance degradation because the hypervisor is reclaiming memory from it via ballooning, causing the VM to swap to disk (memory starvation), which severely impacts database performance.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1101 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1101 exam.