Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise runs a mission-critical transactional workload on a Cloud SQL instance in the us-central1 region. The organization needs to design a disaster recovery (DR) strategy that meets the following business continuity requirements:
us-east4) with minimal Recovery Time Objective (RTO).Which replication and recovery strategy should the cloud architect implement?
Cloud SQL High Availability (HA) provides zonal redundancy within a single Google Cloud region by maintaining a synchronous standby node in an alternate zone. The recreate lagging replica setting automatically deletes and recreates a read replica from a snapshot if its replication lag exceeds a specified threshold (such as 300 seconds).
us-central1 region fails, regional HA cannot recover the database to us-east4.The business continuity requirement only required resilience against single-zone data center hardware outages within the primary region.
us-east4 and use Cloud SQL advanced disaster recovery to invoke a replica failover during an outage.Cloud SQL Advanced Disaster Recovery (DR) allows organizations to provision a cross-region read replica in an alternate region (such as us-east4) and perform an immediate replica failover during an unexpected disaster or regional outage.
us-central1 comes back online after the disaster, Cloud SQL automatically takes a final backup to preserve any split-brain transactions that occurred before the primary went offline.us-east4.
This approach provides an out-of-the-box, fully managed solution that fulfills all data persistence, backup continuity, and automated multi-region topology requirements without custom scripting or significant administrative overhead.
us-east4 upon failure.This pattern relies on scheduled logical data exports (such as SQL dumps) saved into a Multi-Region Cloud Storage bucket, paired with an event-driven Cloud Function that provisions a brand-new Cloud SQL instance and imports the SQL dump during a disaster.
The workload tolerated hours of downtime and data loss, prioritizing minimal standby compute costs over high availability and automated failover.
us-east4 using pglogical or binlog replication, manually execute a promote command during a regional failure, and rebuild the primary instance from a manual export after the disaster resolves.External read replicas and manual replication configurations rely on custom database replication tools (such as native MySQL binlog replication or PostgreSQL pglogical) configured between independent virtual machines or managed databases across regions without native Cloud SQL DR orchestration.
The scenario required cross-cloud or hybrid replication to an on-premises datacenter where managed Cloud SQL cross-region DR capabilities are unavailable.
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