The answer is Cloud Monitoring, Cloud Logging, and Cloud Trace. This combination is correct because monitoring microservices on GKE requires more than just basic metrics; you need to capture inter-service latency and error rates across distributed components. Cloud Monitoring collects and visualizes those metrics in dashboards and alerts, Cloud Logging aggregates structured logs for root-cause analysis, and Cloud Trace provides distributed tracing to follow a single request as it hops between services, revealing where latency spikes occur. On the Google Professional Cloud Developer exam, this question tests your understanding that observability is a three-legged stool—many candidates mistakenly pick only Monitoring and Logging, forgetting that Trace is essential for pinpointing inter-service delays. A common trap is confusing Cloud Trace with simple logging; remember that Trace tracks request paths, not just log entries. Memory tip: think “M-L-T” for Metrics, Logs, Traces—the three pillars of GKE observability.
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.
A company is deploying a microservices architecture on Google Kubernetes Engine (GKE). They need to monitor inter-service latency and error rates. Which set of Google Cloud services should they use to collect and visualize these metrics?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Cloud Monitoring, Cloud Logging, and Cloud Trace
Option B is correct because Cloud Monitoring collects metrics like latency and error rates, Cloud Logging aggregates logs for deeper analysis, and Cloud Trace provides distributed tracing to track requests across microservices. Together, they enable end-to-end observability of inter-service performance in GKE, with Cloud Monitoring visualizing the data via dashboards and alerts.
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.
✗
Cloud Trace, Cloud Debugger, and Cloud Profiler
Why it's wrong here
Cloud Debugger and Cloud Profiler are for debugging and profiling, not for collecting latency and error metrics.
✓
Cloud Monitoring, Cloud Logging, and Cloud Trace
Why this is correct
These three services together provide metrics, logs, and traces for observability.
Related concept
Read the scenario before looking for a memorised answer.
✗
Cloud Logging, Cloud Run, and Cloud Build
Why it's wrong here
Cloud Run and Cloud Build are not monitoring tools.
✗
Cloud Monitoring, Cloud Functions, and Cloud Pub/Sub
Why it's wrong here
Cloud Functions and Pub/Sub are not primary monitoring services.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Cloud Debugger and Cloud Profiler with monitoring tools, but they are for debugging and profiling, not for collecting inter-service latency or error rate metrics.
Detailed technical explanation
How to think about this question
Cloud Trace uses a sampling rate (default 1/1000 requests) and propagates trace context via HTTP headers (e.g., X-Cloud-Trace-Context) to correlate spans across microservices. Cloud Monitoring ingests these trace-derived latency distributions and error counts via the Stackdriver API, enabling SLO-based alerting. In a real-world GKE deployment, a sudden increase in p99 latency visible in Cloud Monitoring can be drilled down into specific spans in Cloud Trace to identify a slow downstream service.
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: Cloud Monitoring, Cloud Logging, and Cloud Trace — Option B is correct because Cloud Monitoring collects metrics like latency and error rates, Cloud Logging aggregates logs for deeper analysis, and Cloud Trace provides distributed tracing to track requests across microservices. Together, they enable end-to-end observability of inter-service performance in GKE, with Cloud Monitoring visualizing the data via dashboards and alerts.
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. You are troubleshooting a performance issue in a microservices application. Which TWO tools from Google Cloud's operations suite would you use to trace a request across services and identify the slowest component?
medium
✓ A.Cloud Monitoring
B.Error Reporting
C.Cloud Profiler
D.Cloud Logging
✓ E.Cloud Trace
Why A: Cloud Trace is the dedicated Google Cloud service for distributed tracing, capturing latency data as requests propagate through microservices. Cloud Monitoring provides the dashboards and alerting to visualize trace data and pinpoint the slowest component. Together, they enable end-to-end request tracing and performance bottleneck identification.
Last reviewed: Jun 25, 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.