mediumMultiple Choice
CV0-004 Practice Question: A cloud administrator receives an alert that a…
A cloud administrator receives an alert that a virtual machine is unresponsive. The hypervisor shows the VM status as 'running'. Which of the following should the administrator check FIRST to diagnose the issue?
⚠ Common exam trap
CompTIA often tests the distinction between 'VM status' (hypervisor-level) and 'guest OS responsiveness' (OS-level), and the trap here is that candidates assume a 'running' VM is fully operational and immediately check network or resource issues, ignoring the need to verify the OS state via console.
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
✓
Access the VM's console to view the operating system screen.
When a VM is unresponsive but the hypervisor shows its status as 'running', the most direct way to determine if the guest OS has crashed or is stuck in a boot loop is to access the VM's console. This provides a direct view of the OS screen, allowing the administrator to see if the OS is hung, at a login prompt, or displaying an error, which is the first step in isolating the issue before checking network or resource configurations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Access the VM's console to view the operating system screen.
Why this is correct
The hypervisor reports the VM as running, so the fault lies inside the guest rather than at the host layer. Opening the console reveals the operating system's actual state — kernel panic, boot hang or frozen services — which remote access cannot show when the OS is unresponsive.
- ✗
Verify the security group rules for the VM's subnet.
Why it's wrong here
Security group rules filter traffic at the network layer, so they cannot make a running guest unresponsive to hypervisor-level or console access. It is tempting because misconfigured rules commonly break connectivity, and would be correct when the VM responds locally but remote sessions or specific ports time out.
- ✗
Review the hypervisor's CPU and memory utilization for the VM.
Why it's wrong here
Hypervisor CPU and memory metrics describe host-level contention, which would not leave the guest reported as running yet unresponsive to its own agent. It is tempting because resource exhaustion is a common cause of guest hangs, and would be the right check when the hypervisor reports the VM as paused or starved.
- ✗
Check the virtual network interface for disconnection.
Why it's wrong here
A disconnected virtual NIC removes network reachability but leaves the guest OS running and responsive through its console. It is tempting because NIC disconnection is a frequent cause of lost connectivity, and would be correct when the VM answers on the console but no network traffic reaches it.
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.