Soru

Zorluk: ZorDesigning Infrastructure for Technical Requirements and High Availability

A global financial technology enterprise is architecting its core payment processing engine on Google Cloud. The workload requires strong transactional consistency across multiple geographic regions with a strict Recovery Point Objective (RPO) of zero and a Recovery Time Objective (RTO) under 5 seconds in the event of a regional outage. Additionally, the stateless API microservices tier running on Compute Engine Managed Instance Groups (MIGs) behind an External HTTP(S) Load Balancer must prevent cascading instance recreations and service degradation during temporary database latency spikes. Which deployment architecture fulfills these technical and high availability requirements?

  1. Deploy a multi-region Cloud Spanner configuration for the database tier, and configure the MIG load balancer health checks to query a lightweight local application endpoint that verifies process health without invoking downstream database queries.Cevap
  2. B
    Deploy a Highly Available (HA) regional Cloud SQL instance with cross-region read replicas, and configure the MIG load balancer health checks to query a lightweight local application endpoint.
  3. C
    Deploy a multi-region Cloud Spanner configuration for the database tier, and configure the MIG load balancer health checks to execute an explicit SQL SELECT query against Cloud Spanner to ensure end-to-end transaction pathway viability.
  4. D
    Deploy a multi-region Cloud Spanner configuration for the database tier, and configure the MIG auto-scaler to scale compute capacity based exclusively on CPU utilization metrics.

Cevap

Deploying a multi-region Cloud Spanner database paired with Managed Instance Groups configured with shallow local health checks satisfies the zero RPO multi-region availability requirement while preventing cascading failure modes during traffic spikes.
Cloud Spanner multi-region configurations deliver multi-region high availability with synchronous replication, achieving zero RPO and automatic cross-region failover (RTO < 5 seconds). Coupling this with shallow HTTP health checks on the API compute tier isolates web server operational status from transient backend database latency, avoiding cascading failures.

Adım Adım Çözüm

1
Evaluate the database tier requirements for RPO = 0 and sub-5-second RTO across multiple regions.
Cloud Spanner with a multi-region instance deployment uses Paxos consensus and TrueTime to provide synchronous cross-region write replication, achieving RPO = 0 and automatic failover.
Cloud SQL regional HA only protects against single-zone failures within a single region. Cross-region Cloud SQL replicas use asynchronous replication which cannot guarantee RPO = 0.
2
Evaluate the compute tier high availability and health check configuration for stateless MIG instances.
Load balancer health checks must assess the local HTTP/gRPC responsiveness of the compute instance itself (shallow check) rather than querying backend dependencies.
Deep health checks that test backend databases cause false-positive failures during transient DB latency spikes, causing the load balancer to drain traffic and terminate healthy compute nodes, exacerbating the outage.

Anahtar Kavram

Multi-Region High Availability and Health Check Isolation
Tahmini Süre:2m 0s
Bu soruyu puanla