CV0-004 Troubleshooting Practice Question
A cloud administrator is troubleshooting a VM whose performance metrics show high 'CPU ready' (or 'CPU steal') time, even though the VM's own CPU utilization is only 20%. The VM runs a latency-sensitive database and is hosted on a shared hypervisor. Which action is the MOST appropriate first step to resolve the performance issue?
⚠ Common exam trap
The trap here is assuming that high CPU ready time means the VM needs more vCPUs, when it actually indicates the VM is waiting for physical CPU time due to host contention.
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
✓
Migrate the VM to a dedicated host or a host with lower oversubscription.
High CPU ready time indicates the VM is waiting for physical CPU resources due to host oversubscription. The most effective first step is to reduce contention by moving the VM to a dedicated host or a host with lower oversubscription. Increasing vCPUs or enabling hot-add does not address the host-level bottleneck and can worsen scheduling delays. CPU affinity is not a reliable fix for oversubscription.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure CPU affinity to pin the VM to a specific physical core.
Why it's wrong here
CPU affinity can sometimes improve cache locality, but pinning a VM to a single physical core can cause contention if other VMs share that core. It does not guarantee reduced ready time and may limit the hypervisor's ability to schedule the VM across available cores. This is not the most appropriate first step for host-level oversubscription.
- ✗
Enable CPU hot-add and dynamically add more cores during peak hours.
Why it's wrong here
CPU hot-add allows adding vCPUs without downtime, but it does not address host-level CPU contention. The VM already has low CPU utilization, so adding cores will not reduce ready time. In fact, more vCPUs can increase scheduling overhead. This action fails to resolve the root cause of the performance degradation.
- ✗
Increase the number of vCPUs assigned to the VM.
Why it's wrong here
Adding vCPUs can worsen CPU ready time because the hypervisor must schedule more virtual CPUs simultaneously, increasing scheduling latency. The VM's own CPU utilization is low, so it is not lacking processing capacity; it is waiting for physical CPU time. Adding vCPUs does not resolve the underlying host contention and may exacerbate the issue.
- ✓
Migrate the VM to a dedicated host or a host with lower oversubscription.
Why this is correct
High CPU ready time indicates the VM is waiting for physical CPU resources because the hypervisor is oversubscribed. Moving the VM to a dedicated host or a host with lower oversubscription reduces contention, directly addressing the root cause. This is the most appropriate first step because it targets the resource bottleneck without unnecessary changes to the VM's configuration.
Visual reference
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.