Examkin

Question

Difficulty: MediumDesigning Infrastructure for Technical Requirements and High Availability

A financial services organization is designing a high-availability architecture for its stateless payment gateway microservices on Google Cloud. The architecture must achieve a 99.99% availability SLA, support automatic multi-region failover during a regional outage, and handle unpredictable traffic bursts seamlessly. To minimize operational costs and infrastructure management overhead, which compute deployment strategy should you recommend?

  1. Deploy the stateless microservices to Cloud Run across multiple regions behind a global External HTTP(S) Load Balancer.Answer
  2. B
    Deploy multi-zonal Google Kubernetes Engine (GKE) clusters in two regions with node auto-provisioning behind a global External HTTP(S) Load Balancer.
  3. C
    Deploy the microservices on Compute Engine Virtual Machines within a single regional Managed Instance Group (MIG) configured with CPU-based autoscaling.
  4. D
    Deploy Compute Engine Virtual Machines across two separate VPC networks and rely on VPC Network Peering to handle transitive cross-region application failover.

Answer

Deploy the stateless microservices to Cloud Run across multiple regions behind a global External HTTP(S) Load Balancer.
Deploying stateless microservices to Cloud Run in multiple regions behind a global External HTTP(S) Load Balancer meets the 99.99% availability requirement with automatic cross-region failover while removing compute management overhead.

Step-by-Step Solution

1
Analyze technical and operational requirements
Identified stateless microservice workload needing multi-region high availability (99.99% SLA) and minimal management overhead.
Stateless containerized services benefit most from serverless infrastructure.
2
Select optimal compute layer
Selected Cloud Run deployed in multiple GCP regions.
Cloud Run scales instantly from zero to handle unpredictable bursts without requiring cluster administration or VM patch management.
3
Configure global traffic management
Added a global External HTTP(S) Load Balancer routing to Serverless Network Endpoint Groups (NEGs) in each region.
The global load balancer directs user traffic to the nearest healthy region and automatically redirects requests if a region becomes unavailable.

Key Concept

Designing High Availability for Stateless Microservices using Cloud Run and Global Load Balancing
Estimated Time:1m 30s
Rate this question

Topics

Designing Infrastructure for Technical Requirements and High Availability