A logistics enterprise is designing the cloud architecture for its real-time package tracking API and regional operational backend on Google Cloud. The solution must satisfy the following technical and high-availability requirements:
1. The stateless tracking API microservices receive bursty HTTP traffic and must auto-scale dynamically without introducing server management overhead.
2. Hybrid connectivity between the on-premises data center and GCP must support up to of encrypted steady-state throughput with availability.
Which TWO architectural decisions should you include in your design to meet these requirements? (Select 2 answers)
- Deploy the stateless tracking API microservices to Cloud Run and front them with an External Application Load Balancer.Cevap
- Provision HA Cloud VPN with two active-active IPsec tunnels using BGP dynamic routing across distinct availability zones.Cevap
- CDeploy the stateless tracking API microservices on a multi-zonal Google Kubernetes Engine (GKE) cluster configured with custom node pools and Service Mesh.
- DProvision a multi-region Cloud Spanner instance to store single-region operational metadata.
- EProvision a 10 Gbps Dedicated Interconnect circuit with Cloud Router to handle the hybrid networking throughput requirement.
Cevap
Deploy the stateless API microservices using Cloud Run fronted by an External Application Load Balancer, and establish hybrid connectivity using HA Cloud VPN with two active-active IPsec tunnels via BGP dynamic routing.
Deploying the microservices on Cloud Run provides serverless container execution that scales automatically down to zero and handles bursty HTTP traffic without cluster maintenance. Pairing this with HA Cloud VPN satisfies the 1.5 Gbps bandwidth requirement (as HA Cloud VPN supports up to 3 Gbps per tunnel) while delivering a high availability SLA of 99.99% through dual active-active IPsec tunnels across separate availability zones.
Adım Adım Çözüm
Anahtar Kavram
Designing high-availability cloud architecture balancing managed compute and redundant hybrid networking based on explicit technical SLAs and capacity requirements.