A telecommunications provider is designing a mission-critical subscriber authentication service on Google Cloud. The architecture must achieve a 99.99% availability SLA. The service processes stateless API requests from mobile base stations and requires a dedicated private hybrid network connection between on-premises core facilities and Google Cloud capable of sustaining a minimum guaranteed bandwidth of 10 Gbps with high availability. Which TWO architectural decisions should you recommend to meet these technical and availability requirements?
- Deploy the stateless API backend onto Cloud Run across multiple GCP regions fronted by a Global External Application Load Balancer.Answer
- Provision Dedicated Interconnect with redundant connections across two distinct edge availability domains.Answer
- CEstablish HA VPN connections with four active tunnels over the public internet to deliver the required 10 Gbps throughput.
- DDeploy a multi-zone Google Kubernetes Engine (GKE) cluster in a single region with custom ingress controllers to run the stateless API.
- EUse Cloud SQL for PostgreSQL with cross-region read replicas configured for manual failover in disaster recovery scenarios.
Answer
The recommended solution is to deploy the stateless backend on multi-region Cloud Run instances behind a Global External Application Load Balancer, and to establish Dedicated Interconnect with redundant circuits across two edge availability domains.
Deploying stateless APIs to multi-region Cloud Run instances fronted by a Global External Application Load Balancer provides seamless global failover and scaling. Dedicated Interconnect configured across redundant edge availability domains guarantees at least 10 Gbps bandwidth and meets the 99.99% connectivity SLA requirement.
Step-by-Step Solution
Key Concept
High Availability and Hybrid Connectivity Architecture Design
Estimated Time:1m 30s