CV0-004 Distributed Tracing Practice Question
A cloud administrator notices that an application's latency has increased. The application is distributed across multiple microservices. Which tool can help trace requests across services to identify the bottleneck?
⚠ Common exam trap
CV0-004 often tests the confusion between logging and tracing, so candidates pick centralized logging when the scenario explicitly requires following a request across services.
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
✓
Distributed tracing tool
A distributed tracing tool is designed to follow a single request as it propagates through multiple microservices, capturing spans, timing, and parent-child relationships. This lets the administrator pinpoint which service or call in the chain is adding latency. Centralized logging aggregates logs but does not natively reconstruct cross-service request paths with timing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Centralized logging service
Why it's wrong here
Centralised logging aggregates stdout and application events into one searchable store, but log lines lack the propagated trace and span identifiers needed to reconstruct one request's path across microservices. It is tempting because it correlates events from many services, yet it would be the right choice for debugging errors, not measuring per-hop latency.
- ✗
Vulnerability assessment tool
Why it's wrong here
Vulnerability assessment scans hosts and images for known weaknesses; it produces no per-request timing or span data, so it cannot locate a latency bottleneck across microservices. It is tempting because it also examines the distributed estate, but it would be the right tool for finding exploitable software flaws, not tracing request paths.
- ✓
Distributed tracing tool
Why this is correct
Distributed tracing propagates a shared trace context across service boundaries, letting the administrator visualise each span's duration and pinpoint the microservice causing increased latency. Unlike metrics or logs, which show isolated per-service data, it reconstructs the full request path, directly satisfying the requirement to trace requests across distributed microservices.
- ✗
Audit logging service
Why it's wrong here
Audit logging records discrete security-relevant events such as configuration changes and access attempts; it captures no parent-child span relationships or durations, so it cannot trace a request across services. It is tempting because it aggregates activity centrally, but it would be correct for compliance and forensic reconstruction, not latency diagnosis.
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 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.