Question 58 of 503
Monitor and optimize database performancemediumMultiple SelectObjective-mapped

Quick Answer

The answer is Query Insights and Cloud Monitoring. Query Insights provides granular, query-level diagnostics such as execution plans, lock contention, and slow query analysis, directly pinpointing the problematic SQL statements in Cloud SQL for PostgreSQL, while Cloud Monitoring offers broader performance metrics like CPU utilization, memory pressure, and disk I/O to identify resource bottlenecks that degrade query speed. On the Google Professional Cloud Database Engineer exam, this pairing tests your understanding of layered troubleshooting: Cloud Monitoring flags the symptom (high resource usage), and Query Insights reveals the cause (inefficient queries). A common trap is choosing only one tool, but the question explicitly asks for two that together cover both infrastructure and query-level root causes. Remember the mnemonic "Monitor the machine, Insight the query" to recall that Cloud Monitoring watches the host, while Query Insights inspects the SQL.

PCDE Monitor and optimize database performance Practice Question

This PCDE practice question tests your understanding of monitor and optimize database performance. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A company is experiencing slow query performance in Cloud SQL for PostgreSQL. Which TWO tools can help identify the root cause?

Question 1mediummulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Cloud Monitoring

Cloud Monitoring provides metrics and dashboards to track database performance indicators like CPU utilization, memory usage, disk I/O, and query latency, helping identify resource bottlenecks. Query Insights offers detailed query-level diagnostics, including execution plans, lock contention, and slow query analysis, directly pinpointing problematic SQL statements in Cloud SQL for PostgreSQL.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Cloud Monitoring

    Why this is correct

    Cloud Monitoring shows instance-level resource metrics that can indicate bottlenecks.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Query Insights

    Why this is correct

    Query Insights provides detailed query performance data.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Cloud Logging with error reporting

    Why it's wrong here

    Error reporting only surfaces errors, not slow queries.

  • Cloud Profiler

    Why it's wrong here

    Cloud Profiler profiles application code, not database queries.

  • Cloud Trace

    Why it's wrong here

    Cloud Trace is for tracing requests across microservices, not database queries.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse Cloud Logging’s error reporting with performance diagnostics, or assume Cloud Profiler and Cloud Trace can analyze database internals, when in fact they are application-layer tools not designed for PostgreSQL query tuning.

Detailed technical explanation

How to think about this question

Query Insights leverages the pg_stat_statements extension in PostgreSQL to collect normalized query statistics, including total execution time, rows returned, and block read/write patterns, enabling identification of queries with high latency or frequent I/O. Cloud Monitoring integrates with Cloud SQL’s agent to expose over 50 database-specific metrics, such as PostgreSQL’s transaction commit rate and replication lag, which can correlate with slow query periods. In a real-world scenario, a sudden spike in disk IOPS seen in Cloud Monitoring might lead to Query Insights revealing a missing index causing sequential scans on a large table.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related PCDE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PCDE practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PCDE question test?

Monitor and optimize database performance — This question tests Monitor and optimize database performance — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Cloud Monitoring — Cloud Monitoring provides metrics and dashboards to track database performance indicators like CPU utilization, memory usage, disk I/O, and query latency, helping identify resource bottlenecks. Query Insights offers detailed query-level diagnostics, including execution plans, lock contention, and slow query analysis, directly pinpointing problematic SQL statements in Cloud SQL for PostgreSQL.

What should I do if I get this PCDE question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This PCDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCDE exam.