Medium1 markMultiple Choice
Domain 5: Managing Implementation and Ensuring ReliabilityDomain 5Cloud TraceObservabilityMicroservices

GCP PCA · Question 29 · Domain 5: Managing Implementation and Ensuring Reliability

A complex microservices application running on GKE is experiencing intermittent high latency. The application consists of 15 different services written in Go and Java. Users report that the checkout process sometimes takes 5 seconds instead of the usual 200ms. You need to identify exactly which microservice is causing the bottleneck. Which GCP observability tool should you use?

Answer options:

A.

Cloud Profiler.

B.

Cloud Trace.

C.

Cloud Logging.

D.

Cloud Monitoring.

How to approach this question

Match the problem 'latency across multiple microservices' to the tool 'distributed tracing'. Cloud Trace is GCP's distributed tracing tool.

Full Answer

B.Cloud Trace.✓ Correct
Cloud Trace.
In a microservices architecture, a single user request might hit dozens of services. When latency occurs, you need Distributed Tracing to see the path of the request. Cloud Trace provides a waterfall view of RPC calls, allowing you to instantly see which specific microservice (or database call) is responsible for the 5-second delay.

Common mistakes

Confusing Cloud Trace with Cloud Profiler (A). Profiler looks *inside* a single program (e.g., which function is using the most CPU). Trace looks *across* multiple programs (e.g., Service A called Service B and waited 4 seconds).

Practice the full GCP Professional Cloud Architect Practice Exam 3

50 questions · hints · full answers · grading

More questions from this exam