An enterprise financial application hosted on Google Cloud requires strict business continuity targets. Stakeholders have established the following requirements: Recovery Point Objective (RPO): Near zero (synchronous data replication across zones to prevent transaction loss during a zonal outage) Recovery Time Objective (RTO): Under 5 minutes (automatic failover with minimal disruption) Failure scope: Must seamlessly tolerate a full zonal infrastructure failure without data loss or manual database failover procedures Which database and compute architecture on Google Cloud best aligns with these defined recovery objectives?

Deploy a regional Managed Instance Group (MIG) across multiple zones behind an Application Load Balancer, and use Cloud SQL configured in High Availability (HA) mode with synchronous standby replication.: ### What Cloud SQL HA and Regional MIGs Are **Cloud SQL High Availability (HA)** mode provides automatic failover and data redundancy by synchronously replicating data between a primary instance and a standby instance located in two different zones within the same region. Combined with a **regional Managed Instance Group (MIG)** distributed across multiple zones, this pattern provides automated compute and database resilience against zonal failures. ### How it meets RTO and RPO Requirements - **RPO Target (Near Zero):** Cloud SQL HA uses synchronous block-level disk replication across two zones in a region. Every committed transaction is written to both the primary and standby instances before acknowledgement, resulting in an RPO that is effectively zero in the event of a zone outage. - **RTO Target (< 5 minutes):** When a zonal outage or primary instance failure occurs, Cloud SQL detects the issue via internal health checks and automatically switches traffic to the standby instance in the healthy zone. This failover process typically completes in under 2–3 minutes without changing database endpoints or IP configurations. Simultaneously, the regional MIG maintains compute availability in surviving zones. ### Key advantages and capabilities - **Zero manual intervention:** Automatic failover for both compute and database layers. - **Preserved endpoints:** Cloud SQL maintains the same IP address across failover, eliminating application-tier configuration changes. - **Synchronous disk durability:** Writes are mirrored to the standby zone immediately. - **Regional traffic distribution:** The regional MIG automatically balances application compute capacity across multiple zones. ### Why this is optimal This pattern directly aligns with an RPO of near zero and an RTO under 5 minutes without requiring custom orchestrators, manual promotion scripts, or complex multi-region coordination.

StudyCerts

Aligning Rto Rpo Architectural Patterns Gcp | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Aligning Rto Rpo Architectural Patterns Gcp

Section: Business continuity

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise financial application hosted on Google Cloud requires strict business continuity targets. Stakeholders have established the following requirements:

Recovery Point Objective (RPO): Near zero (synchronous data replication across zones to prevent transaction loss during a zonal outage)
Recovery Time Objective (RTO): Under 5 minutes (automatic failover with minimal disruption)
Failure scope: Must seamlessly tolerate a full zonal infrastructure failure without data loss or manual database failover procedures

Which database and compute architecture on Google Cloud best aligns with these defined recovery objectives?

Deploy a zonal Managed Instance Group (MIG) in one zone and use Backup and DR Service to schedule continuous backups to an Archive storage bucket in Cloud Storage.

Deploy a regional Managed Instance Group (MIG) across multiple zones behind an Application Load Balancer, and use Cloud SQL configured in High Availability (HA) mode with synchronous standby replication.

Deploy application servers across multiple zones and configure Cloud SQL with asynchronous cross-region read replicas for automatic cross-region failover.

Deploy a single-zone Compute Engine VM running a self-managed database, configure scheduled hourly Persistent Disk snapshots, and script an automated startup recovery in a new zone using Cloud Monitoring alerts.

Professional Cloud Architect

Aligning Rto Rpo Architectural Patterns Gcp

Related questions