Answer-first summary for fast verification
Answer: Watch Cloud Trace for application requests that are failing.
To identify the root cause of why certain microservice calls are failing, especially with the context of Sqlcommenter being used for instrumentation, the most effective approach is to monitor the application requests that are failing. Cloud Trace provides detailed information about the latency of requests and can help pinpoint where failures are occurring in the microservices architecture. Watching Query Insights for long running queries (A) or the Cloud SQL instance monitor for CPU utilization metrics (B) might provide some insights but won't directly identify failing microservice calls. Watching Cloud SQL recommenders for overprovisioned instances (C) is more about optimizing resource usage rather than diagnosing failures. Therefore, the correct answer is to watch Cloud Trace for application requests that are failing (D).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
How can you determine the root cause of failing microservice calls in your Cloud SQL-backed microservices application, which uses Sqlcommenter for instrumentation, as your retail organization scales catalog services for the holiday season?
A
Watch Query Insights for long running queries.
B
Watch the Cloud SQL instance monitor for CPU utilization metrics.
C
Watch the Cloud SQL recommenders for overprovisioned instances.
D
Watch Cloud Trace for application requests that are failing.
No comments yet.