How many Troubleshooting Scenario Questions questions are on this page?

This page has 5 Troubleshooting Scenario Questions scenario questions for the PCDE exam, each with detailed explanations and wrong-answer analysis.

How should I approach PCDE scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Google Professional Cloud Database Engineer questions

Scenario-based practice

Troubleshooting Scenario Questions

Practise Google Professional Cloud Database Engineer practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

PCDE

exam code

Google Cloud

vendor

Scenario guide

How to approach troubleshooting scenario questions

These questions describe a network symptom and ask you to identify the root cause or the correct fix. They appear across all certification exams and reward systematic thinking over memorisation. The best candidates follow a consistent troubleshooting framework even under time pressure.

Quick answer

Troubleshooting Scenario Questions questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Practice scenarios

Question 1mediumdrag order

Full question →

Order the steps to troubleshoot a connection timeout from an application to Cloud SQL.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 2mediummulti select

Full question →

You are troubleshooting a slow-performing query on Cloud Spanner. The query scans a large table with a secondary index. Which TWO metrics from the Query Insights dashboard would most directly indicate the source of the performance issue?

A
CPU time
High CPU time indicates the query is computationally expensive.
B
Rows scanned
High rows scanned suggests the query is reading too many rows, possibly due to missing filters.
C
Storage utilization
Why wrong: Storage utilization is a capacity metric.
D
Commit latency
Why wrong: Commit latency applies to write transactions, not read queries.
E
Lock wait time
Why wrong: Lock wait time is for write contention, not read queries.

Full breakdown with real-world context →

Question 3mediummulti select

Full question →

A BI team is troubleshooting a slow BigQuery query. Which TWO actions can help identify the bottleneck?

A
Review the query execution plan in the BigQuery UI.
Execution plan reveals stages, timing, and data shuffling.
B
Increase the number of slots to maximum.
Why wrong: Increasing slots may speed up but doesn't identify the root cause.
C
Remove all WHERE clauses to simplify.
Why wrong: Removing filters increases scanned data, worsening performance.
D
Rewrite the query to use only CTEs.
Why wrong: CTEs don't inherently improve performance; they may even hinder optimization.
E
Check the bytes processed and shuffle bytes.
High bytes indicate inefficient filtering; shuffle bytes indicate join issues.

Full breakdown with real-world context →

Question 4hardmulti select

Full question →

Which TWO of the following are valid approaches when troubleshooting a slow BI query in BigQuery that includes a complex JOIN between a large fact table and multiple dimension tables?

A
Ensure the fact table is clustered on the join key
Clustering improves join efficiency by colocating data.
B
Split the fact table into multiple smaller tables by region
Why wrong: Splitting tables can lead to union queries and may not help the join.
C
Filter the fact table before the JOIN to reduce the number of rows
Reducing input rows early minimizes shuffle and processing.
D
Move the data to Cloud SQL for faster joins
Why wrong: Cloud SQL is not designed for large-scale BI joins.
E
Add indexes on the join columns
Why wrong: BigQuery does not use traditional indexes.

Full breakdown with real-world context →

Question 5easymultiple choice

Full question →

A database engineer is reviewing the configuration of a Cloud SQL for MySQL instance. The backup configuration shows binaryLogEnabled and pointInTimeRecoveryEnabled set to true. However, the engineer is unable to perform a point-in-time recovery (PITR) to a specific second within the last 30 days. What is the most likely reason?

Exhibit

Refer to the exhibit.

```
gcloud sql instances describe my-instance --format=json
{
  "kind": "sql#instance",
  "name": "my-instance",
  "databaseVersion": "MYSQL_8_0",
  "state": "RUNNABLE",
  "region": "us-central1",
  "settings": {
    "tier": "db-n1-standard-2",
    "activationPolicy": "ALWAYS",
    "backupConfiguration": {
      "enabled": true,
      "binaryLogEnabled": true,
      "pointInTimeRecoveryEnabled": true,
      "startTime": "07:00",
      "retentionSettings": {
        "retentionUnit": "COUNT",
        "retainedBackupsCount": 7
      }
    }
  },
  "ipAddresses": [
    {
      "ipAddress": "34.71.123.45",
      "type": "PRIMARY"
    }
  ]
}
```

A
Binary logging is not enabled for all databases on the instance.
Why wrong: Binary logging is enabled at the instance level; the output shows binaryLogEnabled: true.
B
The transaction log retention period is not set, defaulting to 7 days, so logs older than that are purged.
PITR requires transaction logs to be retained for the desired recovery window; the default is 7 days.
C
The instance is not in a runnable state.
Why wrong: The state is RUNNABLE, so the instance is operational.
D
The database version is MySQL 8.0, which does not support PITR.
Why wrong: MySQL 8.0 supports PITR when binary logging is enabled.

Full breakdown with real-world context →

These PCDE practice questions are part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style PCDE questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Troubleshooting Scenario Questions

How to approach troubleshooting scenario questions

Quick answer

Related PCDE topic practice pages

Plan and manage database infrastructure practice questions

Define data structures and implement SQL for Business Intelligence practice questions

Design and implement database schemas practice questions

Monitor and optimize database performance practice questions

PCDE fundamentals practice questions

PCDE scenario practice questions

PCDE troubleshooting practice questions

Practice scenarios

Order the steps to troubleshoot a connection timeout from an application to Cloud SQL.

You are troubleshooting a slow-performing query on Cloud Spanner. The query scans a large table with a secondary index. Which TWO metrics from the Query Insights dashboard would most directly indicate the source of the performance issue?

A BI team is troubleshooting a slow BigQuery query. Which TWO actions can help identify the bottleneck?

Which TWO of the following are valid approaches when troubleshooting a slow BI query in BigQuery that includes a complex JOIN between a large fact table and multiple dimension tables?

Exhibit