The answer is Cloud Trace, because it is the only tool that provides distributed tracing to identify slow service calls across your GKE microservices. While Cloud Monitoring and Cloud Logging offer aggregate metrics and raw logs, they lack the granular, request-level visibility needed to pinpoint intermittent latency spikes. Cloud Trace captures individual spans for each request, allowing you to trace the exact path through services and isolate high-latency operations like a slow database query or a flaky external API call. On the Google Professional Cloud Developer exam, this question tests your understanding that distributed tracing is essential for diagnosing transient performance issues that don’t appear in averages or logs. A common trap is choosing Cloud Monitoring for its dashboards, but remember: metrics show the *what*, not the *where*. For a memory tip, think “Trace the race”—when a request is slow, follow its spans to find the lagging service.
PCD Managing application performance monitoring Practice Question
This PCD practice question tests your understanding of managing application performance monitoring. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your application running on Google Kubernetes Engine (GKE) is experiencing intermittent latency spikes. You have enabled Cloud Monitoring and Cloud Logging. Which approach would be MOST effective to identify the root cause?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Cloud Trace to analyze distributed tracing data for slow requests.
Cloud Trace is the most effective tool for identifying intermittent latency spikes because it provides end-to-end distributed tracing, allowing you to pinpoint which specific service or request path is causing the delay. Unlike aggregate metrics or logs, Cloud Trace captures individual request spans and can reveal high-latency operations, such as slow database queries or external API calls, that occur only under certain conditions.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Increase the number of replicas or switch to a larger machine type.
Why it's wrong here
This is a reactive scaling action, not a diagnostic approach.
✓
Use Cloud Trace to analyze distributed tracing data for slow requests.
Why this is correct
Tracing reveals per-request latencies and bottlenecks.
Related concept
Read the scenario before looking for a memorised answer.
✗
Examine CPU and memory utilization metrics in Cloud Monitoring for the GKE cluster.
Why it's wrong here
Metrics show aggregate resource usage, not request-level latency causes.
✗
Review recent Cloud Logging entries for error messages.
Why it's wrong here
Logs may show errors but not the root cause of intermittent latency.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between aggregate monitoring (metrics, logs) and distributed tracing, trapping candidates who assume that high CPU/memory or error logs are the only indicators of performance issues, when in fact intermittent latency spikes are best diagnosed with trace-level data that shows the exact request path and timing.
Trap categories for this question
Command / output trap
Metrics show aggregate resource usage, not request-level latency causes.
Detailed technical explanation
How to think about this question
Cloud Trace uses a sampling mechanism (often 1 request per 10 seconds by default) to collect latency data from instrumented applications, and it can correlate spans across services using trace context propagation via HTTP headers (e.g., X-Cloud-Trace-Context). In GKE, you can enable automatic instrumentation for common languages (e.g., Java, Python, Go) using the OpenTelemetry SDK, which captures per-span latency and can reveal subtle issues like tail latency due to garbage collection pauses or network congestion on a specific node. A real-world scenario is a microservice that makes a synchronous call to a third-party API that occasionally times out after 10 seconds, causing a latency spike that would be invisible in CPU/memory metrics but clearly visible as a single slow span in Cloud Trace.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Managing application performance monitoring — This question tests Managing application performance monitoring — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Cloud Trace to analyze distributed tracing data for slow requests. — Cloud Trace is the most effective tool for identifying intermittent latency spikes because it provides end-to-end distributed tracing, allowing you to pinpoint which specific service or request path is causing the delay. Unlike aggregate metrics or logs, Cloud Trace captures individual request spans and can reveal high-latency operations, such as slow database queries or external API calls, that occur only under certain conditions.
What should I do if I get this PCD question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
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. A team is investigating increased latency in a web application deployed on Google Kubernetes Engine (GKE). They want to identify which specific service calls are slow. Which Google Cloud tool should they use?
medium
✓ A.Cloud Trace
B.Cloud Monitoring dashboards
C.Cloud Profiler
D.Cloud Logging
Why A: Cloud Trace is the correct tool because it provides end-to-end latency tracking for requests in distributed systems, including GKE. It captures detailed spans for each service call, allowing the team to pinpoint which specific microservice or API call is causing the increased latency. This aligns directly with the need to identify slow service calls in a web application.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.