PCDE Deploy scalable and highly available databases in Google Cloud — Timed 10 Questions

Question 1

A healthcare company uses Cloud Bigtable for patient event logs. They need to ensure data is available in another region in case of a regional outage. They set up a second cluster in a different region with replication. What is the RPO characteristic of Bigtable replication, and what routing policy ensures reads continue if the primary cluster fails?

10 minute time limit — choose an answer to begin.

Accepted Answer

RPO is near zero (synchronous replication); use 'multi-cluster' routing. Google Cloud Bigtable replication is asynchronous, so the RPO is the replication lag (typically seconds to minutes). However, the question asks about the routing policy that ensures reads continue if the primary cluster fails. The correct routing policy for automatic failover is 'multi-cluster routing', which sends read requests to the nearest available cluster. Option B correctly identifies this policy, even though its RPO description ('near zero, synchronous') is inaccurate; the focus of the question is the routing policy. Options A, C, and D use non-standard or incorrect terms.

Answer

RPO is asynchronous (replication lag); use 'any-replica' routing policy

Answer

RPO is up to 1 hour; use 'single-cluster' routing

Answer

RPO is synchronous (near zero); use 'read-failover' routing policy

Question 2

A company runs a Cloud Bigtable instance with a single cluster in us-central1. They want to implement a disaster recovery plan that meets an RPO of 5 minutes and an RTO of 10 minutes in case of a regional outage. Which actions should they take?

Accepted Answer

Add a second cluster in a different region, configure replication, and use 'any-replica' routing policy. Bigtable replication allows you to add a second cluster in a different region. Replication is asynchronous, so RPO depends on replication lag. With proper configuration and low write load, RPO can be as low as seconds, but typically a few minutes. To achieve RPO of 5 minutes, you need to monitor replication lag. For RTO of 10 minutes, you need automatic failover. The correct approach is to add a second cluster in a different region and use cluster-group routing (formerly known as multi-cluster routing) to automatically route requests to the secondary cluster if the primary is down. Option D describes this approach, although the term 'any-replica' is not the official name; the official policy is cluster-group routing. The other options either use the wrong technology (Cloud SQL), cannot meet the RPO (scheduled backups every 5 minutes may not achieve 5-minute RPO due to backup window and restoration time), or use a suboptimal routing policy (read-failover is for reads only).

Answer

Use Bigtable replication with 'read-failover' routing policy and use Cloud Functions to failover

Answer

Use Cloud SQL for MySQL with cross-region replica for better RPO

Answer

Create a scheduled backup every 5 minutes to Cloud Storage and restore in another region on failure

Question 3

A company uses Cloud SQL for PostgreSQL with cross-region read replicas for DR. They want to automate the failover process to reduce RTO. Which THREE components should they include in their automation? (Choose 3 correct answers.)

Accepted Answer

A configuration to automatically create a new read replica after promotion. Automating cross-region failover for Cloud SQL for PostgreSQL requires three key components: (1) a health check mechanism to detect primary region failure (Option D), (2) a script to promote the cross-region read replica to primary using 'gcloud sql instances promote-replica' (Option B), and (3) a configuration to automatically create a new read replica after promotion (Option A) to maintain cross-region DR capability. Option C (creating a new read replica in the DR region) is unnecessary because the replica is already set up. Option E (weighted routing) is not appropriate for failover; instead, DNS should be updated with a failover routing policy.

Answer

A script to create a new read replica in the DR region

Answer

A Cloud DNS managed zone with a weighted routing policy to split traffic evenly across regions

Question 4

A company runs a critical application on Cloud SQL for SQL Server and wants to implement a disaster recovery plan with RPO < 5 minutes and RTO < 1 hour. They are willing to accept some manual steps during failover. Which two strategies should they combine? (Choose TWO)

Accepted Answer

Use Cloud SQL point-in-time recovery (PITR) to a cross-region instance. For Cloud SQL, cross-region read replicas provide asynchronous replication with RPO typically under 5 minutes if monitored. Manual promotion of the replica can achieve RTO under 1 hour. Additionally, point-in-time recovery (PITR) using binary logs can provide RPO within 5 minutes by recovering to a specific time, but restoring from a backup takes longer. However, combining a cross-region replica (for faster failover) with PITR (for additional recovery options) gives flexibility. Option E (HA instance) is same-region only. Option B (on-demand backups) has higher RPO. Option A (CBR) is for Spanner, not Cloud SQL. The best combination is cross-region replica for failover and PITR for point-in-time recovery.

Answer

Use Cloud Backup for DR (CBR) to create backup plans

Answer

Schedule on-demand backups every 5 minutes and restore to another region

Answer

Use a Cloud SQL HA instance with automatic failover

Question 5

A company needs to store petabytes of time-series IoT sensor data and query it with single-digit millisecond latency at millions of reads per second. The data has a simple key-value structure with timestamps. Which Google Cloud database is MOST appropriate?

Accepted Answer

Cloud Bigtable. Cloud Bigtable is designed for petabyte-scale, low-latency (single-digit ms), high-throughput NoSQL storage for time-series, IoT, and financial data. It scales horizontally by adding nodes. BigQuery is optimised for analytics (seconds-to-minutes latency), Cloud SQL is for OLTP (limited to tens of thousands of QPS), and Firestore is for document data with hierarchical structure.

Answer

Cloud Spanner

Answer

BigQuery

Answer

Firestore

Question 6

A company runs a Cloud SQL for PostgreSQL instance with a cross-region read replica in a different region for disaster recovery. The primary region experiences a complete outage. What is the expected RPO and RTO for promoting the read replica to become the new primary?

Accepted Answer

RPO: equals the replication lag (seconds to minutes); RTO: minutes (manual promotion). Promoting a cross-region read replica involves manual intervention. The RPO equals the replication lag (which can be seconds to minutes depending on network and workload), not zero. The RTO is measured in minutes because you must verify the replica, promote it, and reconfigure applications. Cloud SQL HA failover (same region) achieves RPO near zero and RTO under 60 seconds, but cross-region replication is asynchronous.

Answer

RPO: up to 1 hour; RTO: up to 24 hours

Answer

RPO: near zero (loss of last few transactions); RTO: under 60 seconds

Answer

RPO: zero; RTO: less than 1 minute

Question 7

A global financial services company requires a multi-region Spanner instance with an RPO of zero and an RTO of less than 5 seconds for a critical transactional workload. The application writes to a single region and reads from multiple regions. Which Spanner configuration should they choose?

Accepted Answer

A two-region multi-region configuration (e.g., nam6). For zero RPO and sub-5-second RTO, a multi-region configuration with synchronous replication is needed. Spanner multi-region configurations like nam6 use synchronous replication across a primary and secondary region (with both read-write replicas). The leader region handles writes, and read-only replicas are for reads. A two-region multi-region config (e.g., nam6) provides synchronous replication (RPO=0) and automatic failover in <5 seconds. Three-region configs (nam-eur-asia1) have higher write latency due to longer distances.

Answer

A single-region configuration with read replicas in multiple zones

Answer

A dual-region configuration with two read-write regions and one read-only region

Answer

A three-region multi-region configuration (e.g., nam-eur-asia1)

Question 8

A company uses AlloyDB for an e-commerce platform. They want to achieve the highest availability within a single region. What configuration should they use, and what is the expected failover RTO?

Accepted Answer

Use a primary instance with a standby in a different zone in the same region; RTO less than 30 seconds. AlloyDB offers an HA configuration with a primary instance and a standby (read pool) in different zones within the same region. Automatic failover occurs in less than 30 seconds. Cross-zone failover is automatic. There is no cross-region HA in AlloyDB (you can use cross-region replicas but that requires manual promotion).

Answer

Use a primary instance with a standby in the same zone; RTO less than 10 seconds

Answer

Use a primary instance with multiple read pools; RTO less than 5 seconds

Answer

Use a primary instance with a cross-region read replica; RTO less than 1 minute

Question 9

A company has a Cloud SQL for MySQL instance with point-in-time recovery (PITR) enabled. They need to restore the database to a specific time exactly 2 hours ago to recover from an accidental data deletion. What is the minimum requirement for this operation?

Accepted Answer

Binary logging must be enabled, and the transaction log retention period must cover the desired restore time. PITR in Cloud SQL relies on binary log (binlog) backups. To restore to a specific time, you need to have binary logging enabled and transaction log retention set appropriately. The binlog retention period determines how far back you can perform PITR. The default is 7 days, but you can configure it. The backup window and number of automatic backups are not directly related to PITR granularity.

Answer

The instance must have a backup window configured within the last 2 hours

Answer

The instance must have at least one automatic backup taken after the desired restore time

Answer

The instance must be stopped before initiating the restore

Question 10

A company uses Cloud Spanner and needs to back up a large database (several TB) for compliance reasons. They want to retain the backup for 400 days. What is the optimal approach to meet this requirement?

Accepted Answer

Export the database to Cloud Storage using Dataflow or an export job, which can be retained indefinitely. Cloud Spanner allows creating backups that can be retained for up to 365 days. For a retention of 400 days, you cannot use a single backup. Instead, you can create a backup and then take another backup before the first expires, or export data to Cloud Storage (e.g., using Dataflow) which has no expiration limit. Using the console, you are limited to 365 days; to exceed that, you must use long-term retention outside of Spanner backups.

Answer

Create a backup with 365-day retention, and before it expires, create another backup to extend coverage

Answer

Create a backup and set the expiration time to 400 days using the gcloud command

Answer

Use continuous PITR to retain transaction logs for 400 days