Examkin

Soru

Zorluk: ZorDesigning Infrastructure for Technical Requirements and High Availability

An enterprise financial clearinghouse is architecting a core payment processing backend on Google Cloud. The system must achieve a 99.999% availability SLA, support immediate multi-region failover, and maintain a Recovery Point Objective (RPO) of 0 and a Recovery Time Objective (RTO) of less than 5 seconds for strongly consistent relational transaction records during a total regional outage. The application layer consists of stateless HTTP authorization microservices. Which architectural design meets all technical availability, RPO, and RTO requirements while minimizing operational overhead?

  1. Deploy a multi-region Cloud Spanner instance across multiple GCP regions for the database layer, paired with stateless Cloud Run services deployed across those same regions, fronted by a Global External Application Load Balancer.Cevap
  2. B
    Deploy a Cloud SQL for PostgreSQL instance with High Availability (HA) enabled across two zones in a primary region, configured with an asynchronous cross-region read replica in a secondary region, fronted by a Global External Application Load Balancer routing to Cloud Run.
  3. C
    Deploy a multi-region Cloud Spanner instance for data storage, and provision multi-zone Google Kubernetes Engine (GKE) clusters in each region with custom ingress controllers and custom failover scripts to run the stateless microservices.
  4. D
    Deploy a multi-region Cloud Spanner instance fronted by a Global External Application Load Balancer routing to Cloud Run, configuring the load balancer HTTP health checks to execute synchronous SQL read/write transactions against Cloud Spanner.

Cevap

Deploying a multi-region Cloud Spanner instance paired with multi-region Cloud Run services fronted by a Global External Application Load Balancer satisfies the 99.999% SLA, zero RPO, and sub-5-second RTO requirements with minimal operational management.
Combining a multi-region Cloud Spanner deployment with multi-region Cloud Run container instances behind a Global External Application Load Balancer delivers a globally resilient architecture. Cloud Spanner uses Paxos consensus across regions to guarantee synchronous writes with strong consistency (RPO=0) and automatic transparent leader election during regional loss (RTO < 5 seconds). Global External Application Load Balancing routes client traffic via Anycast to the nearest healthy Cloud Run instance, meeting the 99.999% SLA while minimizing operational infrastructure management.

Adım Adım Çözüm

1
Analyze data tier requirements (RPO=0, RTO<5s, strongly consistent relational data across regions).
Identify that only Cloud Spanner configured in a multi-region topology provides synchronous multi-region replication and automatic failover supporting RPO=0 and instantaneous RTO for relational databases.
Cloud SQL relies on asynchronous replication across regions, which cannot guarantee RPO=0 during a regional disaster.
2
Analyze compute and networking tier requirements (stateless microservices, multi-region high availability, minimal operational overhead).
Select Cloud Run in multiple regions fronted by a Global External Application Load Balancer.
Global External Application Load Balancing provides Anycast IP routing with automatic sub-second failover to the nearest healthy backend region, while Cloud Run provides fully managed serverless compute.
3
Evaluate load balancer health check configuration best practices.
Ensure health checks target shallow application endpoint status rather than executing synchronous database read/write queries.
Deep dependency health checking causes cascading outages when downstream database latency occurs.

Anahtar Kavram

Designing Multi-Region High Availability Architectures for Zero RPO Relational Workloads
Tahmini Süre:2m 30s
Bu soruyu puanla

Konular

Designing Infrastructure for Technical Requirements and High Availability