CV0-004 Troubleshooting Practice Question
A cloud administrator is troubleshooting a performance issue where a web application is responding slowly. The application runs on virtual machines in a private cloud. The administrator has verified that CPU and memory utilization are within normal limits. Which TWO additional metrics should the administrator check to diagnose the issue?
⚠ Common exam trap
CompTIA often tests the distinction between VM-level metrics (CPU/memory) and infrastructure-level metrics (network/storage), trapping candidates who overlook that application performance can degrade due to external dependencies even when the VM itself appears healthy.
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
✓
Network latency between the application and database servers
Network latency between the application and database servers is a critical metric because slow database queries or network congestion can cause the web application to respond slowly even when CPU and memory on the VMs are normal. High latency increases round-trip time for SQL queries, directly impacting page load times. Disk I/O wait time on the hypervisor is also essential because excessive I/O wait indicates storage contention, which can throttle read/write operations for the VMs, leading to application sluggishness.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Number of running processes
Why it's wrong here
Process count reflects application internals, not the resource contention causing slow responses when CPU and memory are normal; disk I/O latency and network throughput are the metrics to check. It is tempting because runaway processes can degrade performance, but that would already surface as elevated CPU or memory.
- ✓
Network latency between the application and database servers
Why this is correct
Network latency directly affects request round-trip time between application and database tiers, a bottleneck CPU and memory metrics cannot reveal. Since the stem confirms compute resources are normal, measuring inter-tier latency isolates transport delay or congestion as the cause of slow responses, satisfying the need to identify non-compute performance constraints.
- ✓
Disk I/O wait time on the hypervisor
Why this is correct
Storage contention on the host can stall guest I/O even when CPU and memory look healthy. Checking disk I/O wait time on the hypervisor reveals whether slow disk access, not compute, is delaying the application's responses.
- ✗
Virtual machine snapshot size
Why it's wrong here
Snapshot size is a capacity figure, not a live performance metric; it does not reveal the I/O latency or network throughput causing slow responses. It is tempting because large snapshots can degrade disk performance, but the actionable metric is storage latency, not the snapshot's size.
- ✗
Hypervisor version
Why it's wrong here
Hypervisor version is a static configuration detail, not a runtime metric, and a stable version cannot explain a new slowdown; storage latency and network throughput are the relevant measurements. It is tempting because hypervisor bugs can affect guest performance, but version alone provides no diagnostic signal during troubleshooting.
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.