Examkin

Question

Difficulty: HardDesigning Infrastructure for Technical Requirements and High Availability

A global medical device company is architecting a patient telemetry platform on Google Cloud. The solution must enforce a strict Recovery Point Objective (RPO) of zero, maintain a 99.999% availability service level agreement (SLA), and guarantee strong global consistency for transactional data across multiple geographic regions. Furthermore, the frontend HTTP ingestion service consists of lightweight, stateless REST API endpoints that must dynamically scale to zero during idle periods without incurring baseline infrastructure management overhead. Which architecture satisfies these high-availability and technical requirements?

  1. Deploy the stateless HTTP ingestion services on Cloud Run across multiple regions behind a Global External HTTP(S) Load Balancer, and store transactional data in a multi-region Cloud Spanner instance configuration.Answer
  2. B
    Deploy the stateless HTTP ingestion services on a multi-region Google Kubernetes Engine (GKE) Standard cluster, and store transactional data in Cloud SQL for PostgreSQL configured with cross-region asynchronous read replicas.
  3. C
    Deploy the stateless HTTP ingestion services on Cloud Run behind a Global External HTTP(S) Load Balancer, and persist transactional records to a highly available regional Cloud SQL for MySQL instance with cross-region database backups.
  4. D
    Deploy the stateless HTTP ingestion services across regional Compute Engine Managed Instance Groups (MIGs), using a pilot-light disaster recovery strategy that restores database state from multi-region Cloud Storage buckets.

Answer

Deploying stateless ingestion microservices on Cloud Run integrated with a multi-region Cloud Spanner instance behind a Global External HTTP(S) Load Balancer.
The combination of Cloud Run and multi-region Cloud Spanner behind a Global External HTTP(S) Load Balancer meets all constraints: Cloud Run scales stateless HTTP microservices down to zero without cluster management overhead, while multi-region Cloud Spanner provides a 99.999% SLA with synchronous multi-region replication ensuring strong consistency and zero RPO.

Step-by-Step Solution

1
Evaluate compute tier requirements
Cloud Run is selected over GKE or Compute Engine MIGs because it natively supports stateless container execution, zero-scaling, and eliminates node management overhead.
The requirement specifies stateless HTTP microservices that dynamically scale to zero with minimal operational management overhead.
2
Evaluate data persistence tier requirements for availability and consistency
Multi-region Cloud Spanner is selected over Cloud SQL regional or cross-region replica setups.
Cloud Spanner utilizes Paxos consensus and TrueTime across multiple regions to guarantee strong external consistency, zero RPO, and a 99.999% uptime SLA.
3
Validate global routing and high availability architecture
Global External HTTP(S) Load Balancer routes traffic to the nearest healthy Cloud Run region.
This guarantees seamless multi-region failover and high availability for the HTTP ingestion layer.

Key Concept

Designing Multi-Region High Availability and Zero-RPO Architectures on GCP
Rate this question

Topics

Designing Infrastructure for Technical Requirements and High Availability