PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #37
Your retail organization is preparing for the holiday season. Use of catalog services is increasing, and your DevOps team is supporting the Cloud SQL databases that power a microservices-based…
The correct answer is A. Watch Query Insights for long running queries. Sqlcommenter automatically appends structured metadata (microservice name, route, framework, etc.) as SQL comments to every query. Cloud SQL Query Insights parses these tags and surfaces them in its dashboard, letting you correlate slow or failed queries directly back to the…
Question
Your retail organization is preparing for the holiday season. Use of catalog services is increasing, and your DevOps team is supporting the Cloud SQL databases that power a microservices-based application. The DevOps team has added instrumentation through Sqlcommenter. You need to identify the root cause of why certain microservice calls are failing. What should you do?
Options
- AWatch Query Insights for long running queries.
- BWatch the Cloud SQL instance monitor for CPU utilization metrics.
- CWatch the Cloud SQL recommenders for overprovisioned instances.
- DWatch Cloud Trace for application requests that are failing.
How the community answered
(43 responses)- A86% (37)
- B2% (1)
- C7% (3)
- D5% (2)
Explanation
Sqlcommenter automatically appends structured metadata (microservice name, route, framework, etc.) as SQL comments to every query. Cloud SQL Query Insights parses these tags and surfaces them in its dashboard, letting you correlate slow or failed queries directly back to the specific microservice and code path that generated them. This is precisely the tool designed for this scenario. CPU utilization metrics (option B) and recommenders (option C) do not provide query-level call tracing, and Cloud Trace (option D) traces application requests but does not expose the SQL-level root cause the way Query Insights does.
Topics
Community Discussion
No community discussion yet for this question.