VCP-DCV vSphere Performance and Scaling Practice Question
A vSphere administrator is troubleshooting intermittent performance degradation on a production VM. The VM resides on a datastore backed by a storage array that is also serving several other clusters. The administrator needs to determine whether the latency is caused by the storage array or by the ESXi host's storage stack. Which esxtop metric should be compared to the array's reported latency to make this determination?
⚠ Common exam trap
Candidates often confuse the various latency metrics in esxtop (KAVG, DAVG, GAVG) and assuming that the guest-level latency is the best indicator of array performance.
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
✓
DAVG (device average latency) in the device view of esxtop
The device view of esxtop provides DAVG, which is the average latency of I/O operations as seen by the ESXi host. By comparing DAVG with the storage array's own latency statistics, an administrator can determine whether the bottleneck is within the host's storage stack or the array itself. This is a standard method for isolating storage performance issues in vSphere.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
DAVG (device average latency) in the device view of esxtop
Why this is correct
DAVG in the device view reports the average latency of I/O operations as measured by the ESXi host's storage stack. Comparing DAVG to the array's own reported latency helps isolate whether the delay originates in the host stack or at the array. A significant discrepancy suggests host-side queuing or path issues, while matching values point to the array.
- ✗
GAVG (guest average latency) in the virtual machine view of esxtop
Why it's wrong here
GAVG is the sum of KAVG and DAVG, representing the total latency experienced by the guest operating system. While it is an important end-to-end metric, it includes both host and array components. Using GAVG alone would not distinguish whether the array or the host stack is responsible for the latency.
- ✗
QAVG (queue average latency) in the virtual machine view of esxtop
Why it's wrong here
QAVG is not a standard esxtop metric; the correct queue-related metric is KAVG. Even if it existed, it would measure queuing time rather than the device response time. The administrator needs a device-level latency metric to compare against the array's reported latency.
- ✗
KAVG (kernel average latency) in the device view of esxtop
Why it's wrong here
KAVG measures the time an I/O request spends in the VMkernel queue before being issued to the device. It is useful for diagnosing host-side queuing but does not represent the round-trip latency seen by the storage array. Comparing KAVG to array latency would not accurately isolate the source of the delay.
Go deeper
Related to this question
About these practice questions
One of 281 original VCP-DCV 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official VMware exam blueprint
This VCP-DCV practice question is part of Courseiva's free VMware 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 VCP-DCV exam.