You are managing multiple applications connecting to a database on Cloud SQL for PostgreSQL. You need to be able to monitor database performance to easily identify applications with long- running and

Question

Options

• AUse log messages produced by Cloud SQL.
• BUse Query Insights for Cloud SQL.
• CUse the Cloud Monitoring dashboard with available metrics from Cloud SQL.
• DUse Cloud SQL instance monitoring in the Google Cloud Console.

• A
  12% (2)
• B
  82% (14)
• D
  6% (1)

Explanation

Query Insights for Cloud SQL is a purpose-built observability feature that provides query-level performance data including average latency, CPU time, I/O wait, lock wait, rows returned, and the full query text and execution plan. Critically, it tags each query with the originating application name, database user, and client IP, making it straightforward to identify which specific application is responsible for long-running or resource-intensive queries. Option A (log messages) records slow queries but lacks structured analytics and application attribution. Option C (Cloud Monitoring metrics) provides instance-level aggregates such as CPU utilization and connections, but not per-query or per-application breakdowns. Option D (Cloud SQL instance monitoring in the console) shows the same instance-level resource graphs and does not offer query-level attribution.

No community discussion yet for this question.