CV0-004 Troubleshooting Practice Question
A cloud administrator notices that a virtual machine is unresponsive. The VM is running on a hypervisor host that shows high CPU utilization. What should the administrator do first?
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
✓
Check the VM console for OS-level issues
The first step in troubleshooting an unresponsive VM is to check the VM console for OS-level issues. This allows the administrator to see if the OS is hung, has a kernel panic, or is waiting for input. Option A is wrong because rebooting the hypervisor host would affect all VMs and is a drastic measure that should only be taken after other diagnostics. Option B is wrong because increasing the VM's vCPU count does not address the root cause of unresponsiveness and could worsen resource contention on an already overloaded host. Option C is wrong because migrating the VM to another host is premature without first determining if the issue is OS-related; also, migration might not be possible if the VM is completely unresponsive.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reboot the hypervisor host
Why it's wrong here
Rebooting the host disrupts every other tenant VM to resolve one guest's symptom, and high host CPU may simply reflect contention rather than a fault. Live migration or per-VM resource inspection addresses the actual cause. Host reboot suits a wedged hypervisor where management agents are unreachable.
- ✗
Increase the VM's vCPU count
Why it's wrong here
Adding vCPUs increases contention on an already saturated host, worsening the symptom. It is tempting because CPU starvation resembles under-provisioning, and would be correct if host utilisation were low and the VM itself were the bottleneck; here the constraint sits at host level.
- ✗
Migrate the VM to another host
Why it's wrong here
Migration moves the workload but leaves the saturated host unresolved and risks disrupting other VMs during the move. It is tempting because it relieves the affected VM, and would be correct once the host fault is identified; first the administrator should confirm whether host-level contention is the actual cause.
- ✓
Check the VM console for OS-level issues
Why this is correct
High host CPU utilisation may be caused by the guest OS itself, so checking the VM console first distinguishes an OS-level hang or runaway process from genuine hypervisor contention. This is the least disruptive diagnostic step before migrating or restarting the VM.
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.