easyMultiple Choice
CV0-004 Practice Question: A cloud administrator notices that a virtual…
A cloud administrator notices that a virtual machine in a public cloud is running slower than expected. The VM is part of a production web application. The administrator has verified that the VM's CPU and memory utilization are below 50%. What should the administrator check next?
⚠ Common exam trap
CompTIA often tests the misconception that low CPU/memory always means the VM is underutilized, when in fact network or I/O throttling can cause severe performance issues without affecting compute metrics.
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 network bandwidth and I/O throttling limits.
When CPU and memory are well below capacity, performance degradation in a public cloud VM is often caused by resource throttling at the network or storage layer. Cloud providers enforce bandwidth caps and I/O limits per VM size, and hitting those limits can cause packet loss, queuing, and high latency even when compute resources are idle. Checking network bandwidth and I/O throttling limits is the correct next step to identify if the VM is being rate-limited.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Check the network bandwidth and I/O throttling limits.
Why this is correct
With CPU and memory below 50%, the bottleneck lies elsewhere. Network bandwidth saturation or storage IOPS throttling limits imposed by the cloud provider commonly degrade VM performance despite adequate compute, so these should be examined next.
- ✗
Migrate the VM to a different availability zone.
Why it's wrong here
Moving zones only helps when the current zone suffers a localised outage or degraded host; the stem reports no availability event, and the performance symptom persists across zones. It is tempting because zone placement affects latency and resilience, and would be correct if the provider confirmed an incident in that zone.
- ✗
Increase the VM's vCPU count.
Why it's wrong here
Adding vCPUs addresses CPU saturation, yet utilisation is already below 50%, so the bottleneck lies elsewhere, such as disk IOPS, network throughput or a quota limit. It is tempting because scaling up is the standard remedy for slow VMs, and would be correct if CPU metrics showed sustained high utilisation.
- ✗
Reboot the VM.
Why it's wrong here
Rebooting clears transient state but does not diagnose or fix an underlying resource constraint, and the VM would slow again once load resumes. It is tempting because restarts often appear to resolve intermittent slowness, and would be correct for a hung process or stuck agent rather than a persistent bottleneck.
Go deeper
Related to this question
About these practice questions
This CV0-004 question is part of Courseiva's 834-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.