An enterprise is designing a business continuity and disaster recovery (DR) strategy on Google Cloud for a mission-critical web application. The application consists of a stateless web/application tier and a transactional database backend. The business continuity plan establishes the following operational criteria: The architecture must withstand a complete regional outage. Recovery Point Objective (RPO): Under 1 minute of data loss. Recovery Time Objective (RTO): Under 15 minutes to resume full production operations in the recovery region. Cost Efficiency: Ongoing secondary region compute costs must be minimized during normal day-to-day operations rather than maintaining redundant, fully provisioned capacity. Which architectural pattern should you select to meet these requirements?

Implement a Warm Standby (Active/Passive) pattern using asynchronous cross-region database replication and a minimal, scaled-down Compute Engine managed instance group in the secondary region ready to scale up upon failover.: ### What the Warm Standby Pattern Is A **Warm Standby** (often implemented alongside pilot light principles) maintains critical background services and data synchronization continuously running in a secondary geographic region, while keeping compute resources scaled down to a minimum footprint during normal operations. ### How It Meets the Requirements - **Regional Outage Resilience**: Deploying secondary infrastructure to an independent Google Cloud region ensures complete isolation from regional disasters and platform incidents. - **RPO < 1 Minute**: Continuous **asynchronous cross-region replication** for the database backend streams transaction logs almost immediately, ensuring minimal lag and keeping data loss well within the 60-second window. - **RTO < 15 Minutes**: Because the core database instance is already provisioned and synced, and baseline compute instances/templates are pre-configured in a **Managed Instance Group (MIG)**, scaling up instance counts and redirecting traffic via **Cloud Load Balancing** or Cloud DNS takes only minutes. - **Cost Efficiency**: Running compute at minimal or zero capacity until triggered avoids paying for duplicate 100% compute capacity in the secondary region during normal operations. ### Key Advantages and Capabilities - **Low Operational Latency on Failover**: Minimal boot and registration delay compared to building infrastructure from scratch. - **Controlled Cost Footprint**: Significantly lower compute consumption relative to active-active deployments. - **Predictable Testing**: Allows regular automated DR drill tests without interfering with primary region traffic. - **Automated Elasticity**: Uses Google Cloud auto-scaling policies to expand compute capacity rapidly when failover is declared. ### Why This Is Optimal The warm standby pattern provides the ideal trade-off between the sub-15-minute RTO and sub-1-minute RPO while avoiding the full expense of a dual-region active-active deployment.

StudyCerts

Evaluate Rto Rpo Dr Standby Patterns | 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

Evaluate Rto Rpo Dr Standby Patterns

Section: Business continuity plan

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 is designing a business continuity and disaster recovery (DR) strategy on Google Cloud for a mission-critical web application. The application consists of a stateless web/application tier and a transactional database backend.

The business continuity plan establishes the following operational criteria:

The architecture must withstand a complete regional outage.
Recovery Point Objective (RPO): Under 1 minute of data loss.
Recovery Time Objective (RTO): Under 15 minutes to resume full production operations in the recovery region.
Cost Efficiency: Ongoing secondary region compute costs must be minimized during normal day-to-day operations rather than maintaining redundant, fully provisioned capacity.

Which architectural pattern should you select to meet these requirements?

Implement a Warm Standby (Active/Passive) pattern using asynchronous cross-region database replication and a minimal, scaled-down Compute Engine managed instance group in the secondary region ready to scale up upon failover.

Implement a Zonal High Availability pattern using synchronous database replication across multiple zones within the primary region and auto-scaling instance groups.

Implement a Cold Standby pattern that exports database backups and snapshots to a multi-region Cloud Storage bucket every 6 hours, and provisions compute instances using automated scripts after a disaster is declared.

Implement a Hot Standby (Active-Active) pattern with equal 100% compute capacity provisioned across both regions, serving live traffic concurrently through an external Application Load Balancer.

Professional Cloud Architect

Evaluate Rto Rpo Dr Standby Patterns

Related questions