CV0-004 Troubleshooting Practice Question
A cloud engineer is troubleshooting a VM that is experiencing high latency. The VM is hosted on a hypervisor with other VMs. Which TWO metrics should the engineer review to identify if resource contention is occurring?
⚠ Common exam trap
CompTIA often tests the distinction between guest-level metrics (swap usage, disk queue length) and hypervisor-level metrics (ballooning, ready time), and the trap here is that candidates confuse swap usage (guest OS paging) with memory ballooning (hypervisor reclaim), or assume network packet drops indicate VM contention rather than network issues.
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 ballooning
Memory ballooning (A) is correct because it directly indicates that the hypervisor is reclaiming guest memory under host-level memory pressure, which is a classic sign of memory contention among co-hosted VMs and can cause latency from paging or reduced cache. CPU ready time (B) is correct because it measures the time a vCPU is runnable but waiting for a physical CPU, which is the definitive metric for CPU contention on an oversubscribed hypervisor. Network packet drops (C) reflect network congestion or NIC issues rather than hypervisor resource contention. Swap usage (D) is a guest-OS symptom that can result from memory pressure but does not itself identify contention between VMs. Disk queue length (E) indicates storage latency or an overloaded datastore, not contention for hypervisor CPU or memory resources.
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 this is correct
Memory ballooning reveals host memory pressure: the hypervisor reclaims guest pages via the balloon driver, forcing the VM to swap and stall. Rising ballooning indicates the host is overcommitted on RAM, making it a direct contention signal alongside CPU ready time.
- ✓
CPU ready time
Why this is correct
CPU ready time measures how long a VM's vCPUs sat in the host run queue waiting for a physical core. Elevated values confirm CPU oversubscription on the hypervisor, directly explaining the latency the VM is experiencing.
- ✗
Network packet drops
Why it's wrong here
Packet drops indicate network-path faults such as congestion or duplex mismatch, not contention for a shared hypervisor resource. They are the right metric when latency traces to the network fabric. Resource contention on a host instead shows as CPU ready time, memory ballooning or datastore latency.
- ✗
Swap usage
Why it's wrong here
Swap usage reflects memory pressure inside the guest or host, but the question asks about contention between co-hosted VMs, which surfaces as CPU ready time, memory ballooning or storage latency. Swap is the right metric when diagnosing paging caused by insufficient RAM, not shared-resource contention.
- ✗
Disk queue length
Why it's wrong here
Disk queue length measures outstanding I/O requests at a device, useful for storage saturation, but it does not reveal contention between co-hosted VMs across CPU and memory. Host-level contention appears as CPU ready time, ballooning or datastore latency. Queue length is correct when diagnosing a single slow LUN.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CV0-004 question from scratch — 834 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CV0-004 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 CV0-004 exam.