CV0-004 Operations and Support Practice Question
A cloud engineer is troubleshooting a Microsoft Azure virtual machine that becomes unresponsive under sustained load. The engineer suspects a storage performance bottleneck but needs to confirm whether the issue is IOPS throttling or throughput throttling on the managed disk. Which Azure Monitor metrics should the engineer examine to distinguish between these two causes?
⚠ Common exam trap
The trap here is relying on guest OS queue depth to identify throttling, when only platform consumption percentages reveal which provisioned limit is actually being reached.
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
✓
Disk IOPS Consumed Percentage and Disk Bandwidth Consumed Percentage
Azure Monitor exposes Disk IOPS Consumed Percentage and Disk Bandwidth Consumed Percentage as platform metrics for managed disks. Comparing which percentage approaches saturation reveals whether the workload is being limited by the provisioned IOPS ceiling or the throughput ceiling, which is the exact distinction the engineer needs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Disk IOPS Consumed Percentage and Disk Bandwidth Consumed Percentage
Why this is correct
These two platform metrics express consumed IOPS and consumed bandwidth as percentages of the disk's provisioned limits. If IOPS Consumed Percentage approaches 100 while bandwidth remains low, the disk is IOPS-throttled; if bandwidth percentage saturates first, it is throughput-throttled. This directly distinguishes the two causes described.
- ✗
Disk Latency and Disk Transactions per second from Azure Monitor
Why it's wrong here
Disk latency and transaction counts show symptoms of slowness and workload volume but not the percentage of provisioned limits consumed. Without comparing consumption against the disk's provisioned IOPS and throughput ceilings, the engineer cannot determine which specific limit is being reached, so this pair does not distinguish the two causes.
- ✗
OS Disk Queue Depth and OS Disk Read Operations/sec from the guest OS
Why it's wrong here
Guest OS metrics such as queue depth and read operations per second describe observed workload behavior but not the platform-imposed limits. A deep queue can result from either IOPS or bandwidth throttling, so these metrics cannot isolate which limit is being hit. They are useful corroborating evidence but not the distinguishing signal.
- ✗
VM CPU Credits Remaining and VM Network In Total
Why it's wrong here
CPU credits apply to burstable VM sizes and network metrics describe traffic volume, neither of which reflects managed disk throttling. These metrics would be relevant for CPU burst exhaustion or network saturation scenarios, but they do not reveal whether disk operations are limited by IOPS or bandwidth caps.
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.