Memory Overcommitment Indicators — Interpreting MEMCTL and SWPOUT
Exhibit
Refer to the exhibit. ``` esxtop -b -d 30 -n 2 > /tmp/perf.csv # Sample output (abbreviated): # CPU(%): 10.5, 12.3, 8.9, ... # PMEM(%): 65, 70, 68, ... # MEMCTL(%): 5, 4, 3, ... # SWPOUT(%): 2, 1, 0, ... ```
Refer to the exhibit. The performance data shows MEMCTL at 5% and SWPOUT at 2%. What does this indicate about the host?
Quick Answer
The host is over-committed on memory, causing ballooning and swapping. MEMCTL at 5% means the vmmemctl balloon driver is actively reclaiming memory from VMs, while SWPOUT at 2% indicates the hypervisor is swapping guest memory to disk—together, these metrics confirm the host has exhausted its physical memory and is using both techniques to compensate. On the VCP-DCV exam, this scenario tests your ability to distinguish between ballooning (a cooperative, driver-based reclaim) and swapping (a last-resort, performance-impacting mechanism); a common trap is assuming low percentages are harmless, but any non-zero SWPOUT signals memory pressure. For the exam, remember the mnemonic: “Balloon before swap, swap means stop”—ballooning is the first line of defense, but swapping always indicates critical overcommitment.
⚠ Common exam trap
It's easy for candidates to confuse memory over-commitment indicators (MEMCTL, SWPOUT) with CPU or storage performance metrics, leading them to select CPU contention or storage latency options instead of recognizing the specific memory reclamation counters.
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
✓
The host is over-committed on memory, causing ballooning and swapping.
MEMCTL at 5% indicates the ESXi host's memory balloon driver (vmmemctl) is actively reclaiming memory from virtual machines, while SWPOUT at 2% shows the host is swapping guest memory to disk. Together, these values confirm the host is over-committed on memory, forcing the hypervisor to use both ballooning and swapping to free up memory for VMs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The host is over-committed on memory, causing ballooning and swapping.
Why this is correct
MEMCTL and SWPOUT indicate memory pressure.
- ✗
The host is experiencing CPU contention.
Why it's wrong here
CPU% is moderate, no sign of contention.
- ✗
The host has network congestion.
Why it's wrong here
No network metrics are shown.
- ✗
The host has high storage latency.
Why it's wrong here
No storage metrics are shown.
Go deeper
Related to this question
About these practice questions
Courseiva writes every VCP-DCV question from scratch — 498 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on VCP-DCV
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. Which THREE memory-related metrics in esxtop indicate that a virtual machine is experiencing memory pressure? (Choose three.)
medium- ✓ A.SWCUR
- B.%SYS
- ✓ C.ACTV
- ✓ D.MCTLSZ
- E.%RDY
Why A: SWCUR (current swapped memory) indicates that the VM has swapped memory to disk, a clear sign of memory pressure. MCTLSZ (memory balloon driver size) shows the amount of memory reclaimed by the balloon driver due to contention, also indicating pressure. ACTV (active memory) when high relative to the VM's configured memory can indicate that the VM is actively using memory and may be under pressure, especially when combined with other metrics. %SYS and %RDY are CPU-related metrics and not relevant to memory pressure.
Variation 2. A VM with a large memory footprint is experiencing high swap rates. The host has free memory but the swap rate is still high. What is the most likely cause?
medium- A.The VM's virtual machine swap file is on a slow datastore.
- ✓ B.The VM's memory limit is set too low.
- C.The host is using software iSCSI causing high latency.
- D.The VM's memory reservation is set too high.
Why B: High swap rates despite available host memory indicate the VM is hitting a configured limit, not physical memory shortage. The memory limit caps the amount of host physical memory the VM can consume; if the guest requires more, it must swap. Option B is correct. Option A (slow datastore for swap file) could worsen swap performance but does not cause swapping if host memory is free. Option C (software iSCSI latency) is unrelated to memory swapping. Option D (memory reservation set too high) would guarantee memory, not cause swapping; in fact, high reservation reduces swapping likelihood.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This VCP-DCV practice question is part of Courseiva's free VMware 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 VCP-DCV exam.