nerdexam
Google

PROFESSIONAL-CLOUD-DEVELOPER · Question #331

You are developing a discussion portal that is built on Cloud Run. Incoming external requests are routed through a set of microservices before a response is sent. Some of these microservices connect t

The correct answer is B. Configure Cloud Trace to capture the requests from the load testing clients. Review the timings in. Cloud Trace is Google's distributed tracing service specifically designed to identify latency bottlenecks across microservices. When a request flows through multiple services (and databases), Cloud Trace captures timing data for each hop without requiring significant code changes

Monitoring, Logging, and Troubleshooting

Question

You are developing a discussion portal that is built on Cloud Run. Incoming external requests are routed through a set of microservices before a response is sent. Some of these microservices connect to databases. You need to run a load test to identify any bottlenecks in the application when it is under load. You want to follow Google-recommended practices. What should you do?

Options

  • AModify the response to include a time series that shows elapsed time per service. Use Log
  • BConfigure Cloud Trace to capture the requests from the load testing clients. Review the timings in
  • CExpose the latency metrics per service for each request. Configure Google Cloud Managed
  • DAdd log statements that capture elapsed time. Analyze the logs and metrics by using BigQuery.

How the community answered

(30 responses)
  • A
    7% (2)
  • B
    77% (23)
  • C
    3% (1)
  • D
    13% (4)

Explanation

Cloud Trace is Google's distributed tracing service specifically designed to identify latency bottlenecks across microservices. When a request flows through multiple services (and databases), Cloud Trace captures timing data for each hop without requiring significant code changes. Reviewing the trace waterfall diagrams in the Cloud Trace console reveals exactly which service or database call is the slowest under load-this is the Google-recommended approach for diagnosing distributed system bottlenecks. Option A requires modifying each service's response, Option D requires adding log statements throughout and then querying BigQuery (higher effort, no real-time visibility), and Option C is incomplete/more complex than needed.

Topics

#Cloud Trace#Performance Monitoring#Microservices#Bottleneck Identification

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVELOPER Practice