Question

Difficulty: HardDesigning Infrastructure for Technical Requirements and High Availability

A global healthcare analytics platform is migrating its patient portal to Google Cloud. The architecture consists of a stateless web tier processing patient query requests and a database backend operating within a single Google Cloud region. The design must accommodate 12 Gbps of low-latency, SLA-backed hybrid connectivity between the on-premises electronic health record (EHR) database and the VPC network. Additionally, the web tier must maintain an availability target of 99.99% against zonal outages and prevent health monitoring probes from causing cascading service disruptions if backend database latency spikes. Which deployment architecture meets these technical requirements?

  1. Deploy the web application on Cloud Run across multiple zones behind an External HTTP(S) Load Balancer using shallow endpoint health checks (/healthz), and configure Dedicated Interconnect with redundant VLAN attachments across two metropolitan edge locations for hybrid connectivity.Answer
  2. B
    Deploy the web application on Cloud Run behind an External HTTP(S) Load Balancer, and establish standard High Availability (HA) VPN tunnels with dynamic Cloud Router BGP routing over the public internet for the 12 Gbps hybrid connectivity requirement.
  3. C
    Deploy the web tier across multi-zone Compute Engine Managed Instance Groups (MIGs), and configure the load balancer health check probe to execute an end-to-end SQL query against the transactional database on every health check cycle.
  4. D
    Replace the single-region relational database backend with a multi-region Cloud Spanner instance deployed across globally distributed continents, and configure Partner Interconnect with 1 Gbps subinterfaces for backend replication traffic.

Answer

Deploy the web application on Cloud Run across multiple zones behind an External HTTP(S) Load Balancer using shallow endpoint health checks (/healthz), and configure Dedicated Interconnect with redundant VLAN attachments across two metropolitan edge locations for hybrid connectivity.
Dedicated Interconnect with dual attachments across two edge facilities provides the required 12 Gbps capacity with 99.99% SLA. Coupling this with Cloud Run behind Cloud Load Balancing and shallow health checks (/healthz) ensures high availability across zones without risking cascading failures from database query latency.

Step-by-Step Solution

1
Evaluate hybrid network throughput requirements
12 Gbps throughput exceeds the standard 3 Gbps limit per HA VPN tunnel, requiring GCP Dedicated Interconnect across multiple interconnect locations to provide high throughput and SLA guarantees.
Dedicated Interconnect is designed for enterprise workloads requiring >10 Gbps dedicated throughput and low latency connectivity.
2
Evaluate health check strategy for high availability
Load balancer health checks must probe a shallow HTTP endpoint on the application container rather than deep downstream dependencies like the database.
Deep health check endpoints cause false-positive failures and cascading reboots across compute tiers whenever downstream databases experience transient load.
3
Select compute and regional HA tier
Cloud Run or multi-zone MIGs behind Cloud Load Balancing satisfy stateless application scaling across availability zones.
Fully managed multi-zone serverless compute combined with dedicated hybrid connections meets the 99.99% availability target cleanly.

Key Concept

Hybrid Interconnect Topology & Load Balancer Health Check Isolation
Rate this question