CV0-004 Operations and Support Practice Question
A cloud engineer is troubleshooting a performance issue in a microservices application. Which THREE tools can help with distributed tracing and latency diagnosis?
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
✓
GCP Cloud Trace
GCP Cloud Trace (B) is correct because it is Google Cloud's native distributed tracing service, capturing latency data across microservices and rendering span waterfalls that pinpoint slow calls. Azure Application Insights (C) is correct because it provides distributed tracing via correlation IDs and the Application Map, showing end-to-end request latency across services and dependencies. AWS X-Ray (D) is correct because it traces requests through AWS-hosted microservices, building service maps and segment/subsegment timing to isolate latency bottlenecks. AWS CloudTrail (A) is not a tracing tool; it records API activity for auditing and governance, not request latency. VPC Flow Logs (E) capture IP-level network traffic metadata for connectivity and security analysis, not per-request distributed traces.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
AWS CloudTrail
Why it's wrong here
CloudTrail records AWS API control-plane activity, not per-request latency or service-to-service spans. It is tempting because it is the default audit trail for AWS actions, but it captures who called which API, not the timing of application requests.
- ✓
GCP Cloud Trace
Why this is correct
GCP Cloud Trace captures distributed traces across microservices and reports per-span latency, satisfying the need to pinpoint slow service hops. Its trace-to-log correlation and latency distribution analysis directly expose bottlenecks in request paths, making it valid for diagnosing the performance issue described.
- ✓
Azure Application Insights
Why this is correct
Azure Application Insights ingests OpenTelemetry spans from each microservice, stitching them into an end-to-end transaction view that exposes per-hop latency and failing dependencies. This satisfies the stem's distributed tracing requirement, letting the engineer pinpoint which service in the call chain causes the performance issue.
- ✓
AWS X-Ray
Why this is correct
AWS X-Ray traces requests across microservices, generating service maps and segment timelines that expose where latency accumulates. It satisfies the distributed tracing requirement by correlating individual requests end-to-end, letting the engineer pinpoint the specific service or downstream call responsible for the performance bottleneck.
- ✗
VPC Flow Logs
Why it's wrong here
VPC Flow Logs capture IP-level accept and reject metadata for network interfaces, carrying no trace identifiers or span timings. It is tempting for connectivity faults, where flow logs excel, but latency diagnosis across microservice calls needs distributed tracing tooling.
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 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.