A retail company is expanding its digital storefront globally to accelerate market entry and support rapid user growth. The product strategy defines strict business continuity and resilience objectives for core transaction processing: Recovery Point Objective (RPO): 0 (zero transactional data loss) Recovery Time Objective (RTO): < 1 minute during a total regional outage Global Availability: Low-latency access for global users with seamless failover Which technical architecture aligns with the company's product strategy while fulfilling these business continuity objectives?

Deploy active-active application services across multiple regions behind a global External Application Load Balancer, using a multi-region Cloud Spanner instance and pre-warmed compute capacity that relies solely on data plane operations during failover: ### What the Multi-Region Active-Active Solution Is This architecture combines global traffic management via a **global External Application Load Balancer**, multi-region active compute deployments, and a globally distributed, synchronously replicated database using **Cloud Spanner**. It adheres to Google Cloud resilience best practices by ensuring that runtime request processing and automatic failover depend exclusively on the **data plane** rather than management plane APIs. ### How It Meets the Business and Continuity Requirements - **RPO = 0:** Multi-region **Cloud Spanner** uses synchronous Paxos-based replication across regions and witness zones, guaranteeing zero data loss (RPO = 0) even if an entire region suffers a disaster. - **RTO < 1 minute:** Because application instances are active-active and pre-provisioned across regions, failure handling is performed at the network data plane by the **External Application Load Balancer**, instantly steering healthy traffic away from an impaired region without waiting for new infrastructure provisioning. - **Accelerated Time-to-Market and Scale:** Managed services like Cloud Spanner and global load balancing scale seamlessly without requiring custom sharding or bespoke failover orchestration. ### Key Advantages and Capabilities - **Data plane independence:** Eliminates dependencies on control/management plane calls (such as `compute.instances.create` or IAM policy propagation) during failover. - **Anycast routing:** Provides a single global IP address that terminates TLS at edge points of presence close to users worldwide. - **Synchronous consistency:** Delivers strong transactional consistency globally without sacrificing high availability. ### Why This Is Optimal Alternative architectures that rely on asynchronous replication or dynamic cold-standby provisioning fail both the zero-data-loss requirement and the sub-minute recovery timeline. Pre-allocated active capacity coupled with synchronous multi-region replication is the only pattern that fulfills these rigorous constraints.

StudyCerts

Align Product Strategy Rto Rpo Multi Region | 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

Align Product Strategy Rto Rpo Multi Region

Section: Business use cases and product strategy

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.

A retail company is expanding its digital storefront globally to accelerate market entry and support rapid user growth. The product strategy defines strict business continuity and resilience objectives for core transaction processing:

Recovery Point Objective (RPO): 0 (zero transactional data loss)
Recovery Time Objective (RTO): < 1 minute during a total regional outage
Global Availability: Low-latency access for global users with seamless failover

Which technical architecture aligns with the company's product strategy while fulfilling these business continuity objectives?

Deploy active-passive application instances across two regions using Cloud SQL with cross-region asynchronous read replicas, configuring Cloud Functions to promote the replica to primary upon failover

Deploy redundant application instances across three zones in a single region, backing up database transactions to Cloud Storage every 5 minutes

Deploy primary application workloads in a single primary region, using Cloud Build and Infrastructure as Code pipelines to provision Compute Engine instances in a secondary region dynamically when health checks fail

Deploy active-active application services across multiple regions behind a global External Application Load Balancer, using a multi-region Cloud Spanner instance and pre-warmed compute capacity that relies solely on data plane operations during failover

Professional Cloud Architect

Align Product Strategy Rto Rpo Multi Region

Related questions