The answer is Cloud Trace, because it provides end-to-end distributed tracing that captures the exact latency contribution of each gRPC call across microservices and regional clusters. When diagnosing gRPC latency between GKE clusters, Cloud Trace reveals whether delays stem from network round-trip time (RTT) over Cloud VPN or from application-level processing within a service, by breaking down each request into spans with precise timing. On the Google Professional Cloud Developer exam, this scenario tests your ability to distinguish observability tools: Cloud Monitoring shows metrics, Cloud Logging shows events, but only Cloud Trace can pinpoint the exact cause of latency in a distributed call chain. A common trap is to jump to network diagnostics, but the question explicitly asks for pinpointing the cause across both application and network layers. Memory tip: Trace the trace—if you need to see where time is spent across services, think "spans for spans."
PCD Practice Question: Designing highly scalable, available, and reliable cloud-native applications
This PCD practice question tests your understanding of designing highly scalable, available, and reliable cloud-native applications. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 multinational corporation runs a web application on Google Kubernetes Engine (GKE) with multiple microservices. They use Cloud Service Mesh (Anthos) for observability and security. The application uses gRPC for inter-service communication. Recently, they have observed increased latency and occasional timeouts between services in different regional clusters connected via Cloud VPN. The team wants to diagnose the issue and improve reliability. They suspect network round-trip time (RTT) is causing the latency, but they are not sure if the problem is at the application or network layer. Which tool should they use to pinpoint the exact 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 traces and identify bottlenecks in request paths.
Cloud Trace is the correct tool because it provides end-to-end distributed tracing, which can capture the exact latency contribution of each gRPC call across microservices and regional clusters. By analyzing trace spans, the team can determine whether the increased latency is due to network round-trip time (RTT) between clusters or due to application-level processing delays within a service.
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.
✗
Use Cloud Monitoring to view gRPC latency distributions and break down by service and method.
Why it's wrong here
Cloud Monitoring provides aggregate metrics, not per-request tracing.
✓
Use Cloud Trace to analyze distributed traces and identify bottlenecks in request paths.
Why this is correct
Cloud Trace captures end-to-end latency for each request.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use VPC Flow Logs to examine network throughput and packet loss.
Why it's wrong here
VPC Flow Logs show network-level data but not application-layer latency.
✗
Use Cloud Logging to search for error logs in the application containers.
Why it's wrong here
Logging shows errors but not latency breakdown.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse aggregated metrics (Cloud Monitoring) with distributed tracing (Cloud Trace), failing to recognize that only tracing can break down latency per request hop across services and clusters.
Trap categories for this question
Command / output trap
VPC Flow Logs show network-level data but not application-layer latency.
Detailed technical explanation
How to think about this question
Cloud Trace uses the Cloud Trace API to collect latency data from instrumented applications, including gRPC spans that carry trace context via propagation headers (e.g., 'x-cloud-trace-context'). In a multi-cluster GKE environment with Cloud Service Mesh, Envoy sidecar proxies automatically generate trace spans for each gRPC call, allowing the team to see the exact RTT between clusters (network hop) versus processing time within a service. A common subtlety is that gRPC uses HTTP/2 multiplexing, so a single TCP connection can carry multiple streams; Cloud Trace can still attribute each stream's latency individually, which VPC Flow Logs cannot.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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.
Designing highly scalable, available, and reliable cloud-native applications — This question tests Designing highly scalable, available, and reliable cloud-native applications — 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 traces and identify bottlenecks in request paths. — Cloud Trace is the correct tool because it provides end-to-end distributed tracing, which can capture the exact latency contribution of each gRPC call across microservices and regional clusters. By analyzing trace spans, the team can determine whether the increased latency is due to network round-trip time (RTT) between clusters or due to application-level processing delays within a service.
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 →
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.