CV0-004 Operations and Support Practice Question
A cloud application is experiencing intermittent high latency. The operations team has enabled distributed tracing using AWS X-Ray but is unable to pinpoint the source. Which additional step should the team take to identify the root cause of the latency?
⚠ Common exam trap
CV0-004 often tests the confusion between network-level monitoring (VPC Flow Logs) and application-level tracing (X-Ray), leading candidates to choose network tools for application latency issues.
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
✓
Analyze traces in X-Ray to identify which service segment has the highest duration.
AWS X-Ray provides distributed tracing that captures latency data for each segment of a request. To pinpoint the source of intermittent high latency, the team should analyze the traces to identify which service segment has the highest duration. This directly reveals the bottleneck, whether it's a database call, external API, or compute-intensive operation. Other steps like VPC Flow Logs or application logs may provide additional context but are not as directly actionable for latency root cause.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable VPC Flow Logs to analyze network traffic patterns.
Why it's wrong here
VPC Flow Logs capture IP-level metadata such as source, destination and accept/reject decisions, not application-layer timing across services. It is tempting because it is a network diagnostic tool, but it cannot correlate the request path that X-Ray traces already cover.
- ✗
Increase the auto-scaling group size to handle the load.
Why it's wrong here
Increasing the auto-scaling group size adds capacity to absorb load but does not reveal which component introduces the intermittent delay. It is tempting because scaling often resolves performance issues, yet here the root cause remains unidentified, so adding instances may mask or worsen the latency without diagnosis.
- ✓
Analyze traces in X-Ray to identify which service segment has the highest duration.
Why this is correct
X-Ray traces already capture per-segment timing, so comparing segment durations isolates the subcomponent responsible for latency. Ranking segments by duration pinpoints the slow service or downstream call driving the intermittent spikes, which aggregate tracing alone cannot reveal.
- ✗
Examine application logs on each virtual machine.
Why it's wrong here
Application logs record discrete events and errors on individual instances, not the cross-service timing spans X-Ray already captured. It is tempting because logs are a standard troubleshooting source, but they cannot correlate the distributed request path where the intermittent latency actually originates.
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.