CV0-004 Troubleshooting Practice Question
During a cloud migration, a database server is moved from on-premises to a cloud-managed database service. After migration, the application team reports that some queries are running slower than before. The database CPU utilization is low. What is the most likely cause?
⚠ Common exam trap
CV0-004 often tests the correlation between low CPU and slow queries; candidates may blame indexing or instance size, but low CPU points to a non-compute bottleneck like network latency, which is common in cloud migrations.
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
✓
The network latency between the application and the database has increased
When a database is moved to a cloud-managed service and queries slow down while CPU utilization is low, the most likely cause is increased network latency between the application and the database. Low CPU indicates the database is not compute-bound, so the delay is likely in the round-trip time for queries. This is common when the application and database are in different regions or availability zones.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The network latency between the application and the database has increased
Why this is correct
Low CPU indicates the database itself is not the bottleneck, so the added round-trip latency between application and cloud-managed database is the likely cause. Moving off-premises lengthens the network path, slowing query response even when processing is idle.
- ✗
The database is not indexed properly
Why it's wrong here
Poor indexing increases CPU usage, which is low.
- ✗
The database connection pooling is misconfigured
Why it's wrong here
Connection pooling affects how many sessions are reused, not how a query executes; low CPU with slow queries points to data transfer or plan differences, not pool exhaustion. Pooling is tempting because misconfiguration causes latency, and it would be correct if the symptom were connection timeouts under high concurrency.
- ✗
The cloud database instance type has insufficient memory
Why it's wrong here
Insufficient memory would show as swapping, cache eviction or memory-pressure metrics, not low CPU; the symptom of low CPU with slow queries points to network round-trip latency between application and managed database. Instance sizing is tempting because under-provisioning causes slowness, and it would be correct if memory metrics were saturated.
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 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.