mediumMultiple Select
CV0-004 Practice Question: A cloud administrator is troubleshooting a…
A cloud administrator is troubleshooting a performance issue in a virtualized environment. Which TWO metrics should the administrator monitor to identify CPU contention? (Choose two.)
⚠ Common exam trap
Watch out — candidates often confuse CPU usage percentage with CPU contention, but usage measures consumption while ready time and co-stop time directly measure waiting caused by resource competition.
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
✓
CPU ready time
CPU ready time (B) is the correct metric because it measures the amount of time a virtual machine was ready to run but could not be scheduled on a physical CPU, which directly indicates CPU contention or overcommitment on the host. CPU co-stop time (C) is also correct because it reflects the time a vCPU was ready but had to wait for other vCPUs in the same virtual machine to be co-scheduled, a symptom of CPU contention in multi-vCPU VMs. CPU usage percentage (A) only shows how busy a CPU is and can be high without contention, so it does not specifically identify contention. CPU frequency (D) is a hardware characteristic and does not indicate scheduling delays or contention. CPU load average (E) is a host-level metric that may suggest demand but does not isolate per-VM scheduling latency like ready and co-stop times do.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
CPU usage percentage
Why it's wrong here
CPU usage percentage reports only how much processor time a VM consumes, not whether it is waiting for physical cores, so it cannot reveal contention. It is tempting because it is the standard metric for capacity planning and spotting a genuinely overloaded guest, where high consumption with no wait states would be the correct finding.
- ✓
CPU ready time
Why this is correct
CPU ready time measures the milliseconds a virtual machine waits for a physical core, directly exposing contention. This satisfies the troubleshooting requirement by quantifying scheduling delay, unlike utilisation percentages that show demand but not competition.
- ✓
CPU co-stop time
Why this is correct
CPU co-stop time measures how long a vCPU is ready but blocked because the physical cores are overcommitted by the hypervisor scheduler. Elevated co-stop values directly indicate CPU contention, distinguishing it from guest-level CPU saturation.
- ✗
CPU frequency
Why it's wrong here
CPU frequency is a static per-core clock rate, not a contention signal; contention appears as CPU ready time (scheduling delay) and CPU usage or demand relative to allocated vCPUs. Frequency monitoring suits capacity planning or thermal throttling checks, not identifying contention.
- ✗
CPU load average
Why it's wrong here
CPU load average reports the runnable and uninterruptible task count over time, so it cannot separate virtual machines competing for physical cores from other causes. It is tempting because load average is a standard Linux health metric, and it would be the right choice when sizing a single host or spotting sustained oversubscription rather than identifying contention between guests.
Go deeper
Related to this question
About these practice questions
One of 834 original CV0-004 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.