Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are designing the database tier for an e-commerce platform using Cloud SQL for PostgreSQL in us-central1. Your architecture must meet the following resilience and performance requirements:
us-east1 so the database can immediately operate with high availability after failover.How should you configure your Cloud SQL architecture?
us-central1, and store automated backups in a multi-region Cloud Storage bucket for recovery in us-east1.This configuration combines a Cloud SQL regional (HA) instance for in-region resilience with automated backups stored in a multi-region Cloud Storage location so that data survives a complete regional outage and can be restored into another region.
us-east1 using backups, exports, or point-in-time recovery requires provisioning a new instance and restoring all database data. For large production databases, this process can take hours rather than minutes, violating the requirement to minimize RTO.us-central1 automatically with RPO = 0 and ~60-second failover.us-central1.Your regional disaster recovery requirements allowed an RTO of several hours, you did not need to offload read queries, and you wanted to minimize ongoing costs by avoiding a continuously running cross-region read replica.
Multi-region backups are an essential layer of protection against accidental data corruption or deletion, but they are a cold-recovery mechanism rather than a low-RTO failover target. For minutes-level regional RTO and read scaling, a cross-region read replica is required.
us-central1, and deploy read replicas in a second zone of us-central1 and in us-east1 for failover.A zonal Cloud SQL instance runs in a single zone without a synchronized standby instance. While you can attach read replicas in other zones or regions to offload read queries and serve as disaster recovery targets, read replicas rely on asynchronous replication rather than synchronous regional persistent disks.
us-east1: Unless HA is explicitly enabled on the cross-region replica, promoting it during a regional outage leaves the newly promoted primary running as a single-zone instance.Your workload could tolerate non-zero data loss during zonal disruptions, manual failover procedures, and application connection updates, and you wanted to avoid the cost of a regional HA instance.
A common misconception is that placing a read replica in another zone provides automatic high availability. In Cloud SQL, automatic zero-data-loss zonal failover requires the regional (HA) availability type, while read replicas in a third zone complement HA by keeping read capacity online during a primary zone failure.
us-central1, and deploy an HA-enabled cross-region read replica in us-east1.A Cloud SQL regional (high availability) instance pairs a primary instance and a standby instance in two separate zones within the same Google Cloud region, backed by regional persistent disks that synchronously replicate every write before committing. Adding an HA-enabled cross-region read replica extends this protection across regions while providing a dedicated endpoint for read-only workloads.
us-east1 keeps a near-real-time copy of the database ready for promotion, reducing RTO from hours to minutes compared to restoring backups. Enabling HA in advance on the read replica ensures that as soon as it is promoted to primary, it already has its own standby instance in a second zone of us-east1.This managed architecture satisfies both zonal HA (RPO = 0, ~60-second automatic failover) and rapid regional disaster recovery while offloading read traffic, all without requiring the operational overhead of managing database clustering or storage replication manually.
us-central1, and replicate scheduled snapshots to us-east1.This Infrastructure-as-a-Service (IaaS) pattern runs PostgreSQL on Compute Engine VMs managed by a regional managed instance group (MIG), using a regional Persistent Disk for synchronous block-level replication across two zones and scheduled snapshots for cross-region backup.
us-east1 from scheduled snapshots incurs data loss equal to the snapshot interval and requires provisioning instances and restoring disks, resulting in a much higher RTO than promoting a live cross-region read replica.You required full operating system control, custom PostgreSQL extensions unsupported by Cloud SQL, and could tolerate manual or custom-scripted failover along with higher regional recovery times.
Using Cloud SQL abstracts away disk attachment, VM recreation, and failover orchestration, delivering predictable ~60-second zonal failover and simple cross-region read replica promotion.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated