Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
An enterprise hosts a mission-critical database on a Cloud SQL instance configured for high availability (HA) within a single Google Cloud region. The organization wants to expand its disaster recovery (DR) architecture to protect against a potential full regional outage and achieve a recovery time objective (RTO) measured in minutes.
Which replication strategy should the enterprise implement?
Cloud SQL High Availability (HA) is a regional resilience feature that provisions a primary database instance in one zone and a standby instance in a secondary zone within the same Google Cloud region. Data is synchronously replicated across both zones using regional persistent disks before transactions are committed.
The requirement stated: "Protect the Cloud SQL instance against a single zone or hardware failure within the same region with automated sub-minute failover and zero data loss."
While HA is essential for local fault tolerance, true regional disaster recovery requires pairing regional HA with an asynchronous cross-region replica in a secondary region.
A cross-region read replica is a separate Cloud SQL instance provisioned in a different geographic region from the primary database instance. It continuously synchronizes data from the primary instance using asynchronous replication. In disaster recovery (DR) planning, cross-region replicas provide geographic redundancy across independent failure domains.
Standard Cloud SQL High Availability (HA) protects only against zonal failures within a single region. When business continuity demands protection against an entire regional outage with short RTO/RPO targets, configuring and promoting a cross-region read replica is Google Cloud's recommended architecture. Alternative approaches, such as restoring from backups or re-importing data dumps, require significant time to provision storage and replay files, resulting in hours of downtime instead of minutes.
Regional Persistent Disks (rePDS) provide synchronous, block-level storage replication across two zones located within the same Google Cloud region. They are the underlying storage technology used by Cloud SQL to keep primary and standby instances synchronized in a High Availability (HA) configuration.
The scenario asked how Cloud SQL synchronizes data between primary and standby instances across different zones within a single regional high availability setup.
All cross-region database replication in Cloud SQL is handled at the database engine level via asynchronous read replication, never via synchronous block-level disk replication.
Export and restore is a traditional backup-based disaster recovery method where the contents of a Cloud SQL database are exported (typically as SQL dump or CSV files) to a Cloud Storage bucket on a scheduled basis. In an emergency, a new Cloud SQL instance is provisioned from scratch and the data is imported.
The organization had very relaxed recovery targets (e.g., "RTO and RPO of 24 hours or greater") and prioritized minimizing ongoing compute costs over rapid system availability.
While backups and exports are essential components of data protection, active cross-region read replication is required to maintain warm standby data for near-instantaneous failover.
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