mediumMultiple ChoiceObjective-mapped
Using Cloud Trace to Identify Latency Across Microservices on GKE
A company runs a microservices application on Google Kubernetes Engine (GKE). Users report intermittent slow responses. Developers suspect a specific service is causing latency. Which Google Cloud tool should they use to trace requests across services and identify the root cause?
Quick Answer
The answer is Cloud Trace, the correct tool for tracing requests across microservices to identify latency. Cloud Trace provides distributed tracing that captures end-to-end request propagation through services, recording detailed span timing data as each microservice handles a portion of the call. By analyzing these trace spans and their latency breakdowns, developers can pinpoint exactly which service introduces delay, directly addressing the intermittent slow responses described. On the Google Professional Cloud Developer exam, this question tests your understanding of observability tools in a microservices context—a common trap is confusing Cloud Monitoring (which tracks metrics and alerts) or Cloud Logging (which stores logs) with Cloud Trace’s unique ability to follow a single request’s path across service boundaries. A helpful memory tip: think of Cloud Trace as a “breadcrumb trail” for each request, showing you exactly where the slowdown happens in the chain.
⚠ Common exam trap
Many exam-takers confuse Cloud Monitoring's alerting and dashboard capabilities with the distributed tracing needed to follow a single request across multiple services, leading them to pick Cloud Monitoring instead of Cloud Trace.
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
✓
Cloud Trace
Cloud Trace is the correct tool because it provides distributed tracing capabilities that capture end-to-end latency data as requests propagate through microservices. By analyzing trace spans and their timing, developers can pinpoint which specific service is introducing delay, directly addressing the intermittent slow responses described.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Cloud Debugger
Why it's wrong here
Cloud Debugger allows inspection of code state without stopping the application, but does not trace requests.
- ✓
Cloud Trace
Why this is correct
Cloud Trace provides distributed tracing to identify latency bottlenecks across microservices.
- ✗
Cloud Monitoring
Why it's wrong here
Cloud Monitoring tracks metrics and sets alerts, but does not provide end-to-end request tracing.
- ✗
Cloud Logging
Why it's wrong here
Cloud Logging aggregates logs, but does not trace requests across services.
Go deeper
Related to this question
About these practice questions
This PCD question is part of Courseiva's 964-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 →
Same concept, more angles
1 more way this is tested on PCD
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An application deployed on Google Kubernetes Engine (GKE) is experiencing intermittent high latency. The operations team wants to quickly identify which specific code path is causing the delay. What should they use?
easy- ✓ A.Enable Cloud Trace and analyze trace spans.
- B.Use Cloud Profiler to identify memory leaks.
- C.Set up a Cloud Monitoring uptime check.
- D.Review Cloud Logging logs to find error messages.
Why A: Cloud Trace is designed specifically for latency analysis in distributed systems like GKE. It captures end-to-end request latency and breaks it down into individual spans, each representing a specific code path or service call. By analyzing these spans, the operations team can pinpoint which exact code path (e.g., a database query, external API call, or internal function) is causing the intermittent high latency.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCD practice question is part of Courseiva's free Google Cloud 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 PCD exam.