Examkin

Question

Difficulty: MediumDesigning Infrastructure for Technical Requirements and High Availability

A regional freight logistics company is designing a high-availability backend on Google Cloud for its shipment management platform within a single GCP region. The architecture requires a stateless HTTP microservice tier that automatically scales during peak hours without server management overhead. The relational database tier requires strict ACID compliance, a zero Recovery Point Objective (RPO=0RPO = 0) in the event of a single zonal outage, and automated multi-zone failover to maintain a 99.99% availability target. Which architecture meets these technical requirements with the lowest operational complexity?

  1. Deploy the stateless microservices to Cloud Run, and store relational data in a regional Cloud SQL for PostgreSQL instance with High Availability (HA) enabled across dual zones.Answer
  2. B
    Deploy the stateless microservices to a regional Google Kubernetes Engine (GKE) cluster, and store relational data in a multi-region Cloud Spanner instance.
  3. C
    Deploy the stateless microservices to Cloud Run, and store relational data in a single-zone Cloud SQL instance backed up by automated hourly Cloud Storage database snapshots.
  4. D
    Deploy the stateless microservices to unmanaged Compute Engine virtual machines in a single zone, and store relational data in a single-zone Cloud SQL instance using HA VPN for cross-zone replication.

Answer

Deploying stateless microservices on Cloud Run backed by a regional Cloud SQL for PostgreSQL instance with High Availability (HA) enabled across dual zones provides serverless autoscaling and zero-RPO zonal redundancy with minimum operational overhead.
Combining serverless Cloud Run for the compute tier with dual-zone Cloud SQL HA for the storage tier fulfills all stateless scaling and database zero-RPO (RPO=0RPO = 0) failover requirements while keeping operational complexity low.

Step-by-Step Solution

1
Evaluate compute tier requirements
Cloud Run is selected because it delivers fully managed serverless autoscaling for stateless HTTP workloads, eliminating node/cluster management overhead.
The scenario requires zero server management overhead for stateless HTTP microservices.
2
Evaluate database availability and RPO requirements
Cloud SQL with High Availability (HA) enabled is selected.
Cloud SQL HA uses synchronous replication to a standby instance in a secondary zone within the same region, guaranteeing RPO=0RPO = 0 and automated failover during a zonal outage.
3
Assess architectural complexity and scope
Cloud SQL HA satisfies the single-region 99.99% availability goal without needing multi-region services like Cloud Spanner.
Selecting globally distributed database services for a single-region deployment adds unnecessary cost and operational complexity.

Key Concept

Single-Region High Availability and DR Alignment
Rate this question

Topics

Designing Infrastructure for Technical Requirements and High Availability