Examkin

Question

Difficulty: MediumDesigning Infrastructure for Technical Requirements and High Availability

A digital media streaming provider is designing a high-availability architecture on Google Cloud for its user profile and session management REST API service. The workload consists of stateless HTTP services experiencing variable traffic up to 5,000 requests per second. The backend database requires regional transactional consistency with low Recovery Time Objective (RTO) zonal failover, but does not require global multi-region write replication. The on-premises operations center requires a resilient connection to the Google Cloud VPC, with aggregate peak traffic limited to 1.5 Gbps. Which architecture meets all technical and high availability requirements while minimizing operational overhead and cost?

  1. Deploy the stateless REST API service on Cloud Run with a Serverless VPC Access connector, store user profile data in a regional Cloud SQL instance configured for High Availability across multiple zones, and establish hybrid connectivity using HA Cloud VPN.Answer
  2. B
    Deploy the stateless REST API service on Google Kubernetes Engine (GKE) Autopilot across multiple zones, store user profile data in a regional Cloud SQL instance configured for High Availability, and establish hybrid connectivity using HA Cloud VPN.
  3. C
    Deploy the stateless REST API service on Cloud Run with a Serverless VPC Access connector, store user profile data in a multi-region Cloud Spanner instance, and establish hybrid connectivity using HA Cloud VPN.
  4. D
    Deploy the stateless REST API service on Cloud Run with a Serverless VPC Access connector, store user profile data in a regional Cloud SQL instance configured for High Availability, and provision a 10 Gbps Dedicated Interconnect connection.

Answer

The optimal architecture combines Cloud Run for stateless compute auto-scaling, a Regional Cloud SQL instance configured for zonal High Availability (HA), and HA Cloud VPN for hybrid network connectivity under 3 Gbps.
The solution combining Cloud Run, regional HA Cloud SQL, and HA Cloud VPN meets all operational SLAs with minimal cost and management overhead. Cloud Run auto-scales stateless HTTP APIs efficiently. Regional Cloud SQL with HA provides automatic failover between zones in a single region to satisfy RTO/RPO goals. HA Cloud VPN supports up to 3 Gbps per tunnel with a 99.99% SLA, making it ideal for the 1.5 Gbps peak hybrid bandwidth requirement.

Step-by-Step Solution

1
Evaluate Compute Requirements
Cloud Run is selected over GKE because the service consists of simple stateless HTTP REST APIs requiring serverless scale-to-zero without cluster management overhead.
Choosing GKE for simple HTTP REST services adds unnecessary cluster management complexity and baseline infrastructure cost.
2
Evaluate Database High Availability Requirements
Regional Cloud SQL with HA (primary and standby instances in separate zones within the same region with automatic failover) meets the RTO and transactional consistency requirements.
Cloud Spanner is designed for globally distributed relational databases across regions; using it for regional workloads introduces excessive cost and over-engineering.
3
Evaluate Hybrid Connectivity Throughput Requirements
HA Cloud VPN provides 99.99% availability and up to 3 Gbps bandwidth per tunnel, satisfying the 1.5 Gbps peak bandwidth requirement.
Dedicated Interconnect is intended for high-bandwidth workloads (10 Gbps/100 Gbps) or strict non-Internet connectivity, making it cost-prohibitive for a 1.5 Gbps connection.

Key Concept

Selecting right-sized high-availability compute, database, and networking primitives to meet technical RTO/RPO SLAs without over-engineering.
Rate this question

Topics

Designing Infrastructure for Technical Requirements and High Availability