A media company is designing a high-availability solution on Google Cloud for a stateless REST API that serves mobile clients. The solution must automatically scale to handle unpredictable traffic spikes, provide multi-zone redundancy within a single region, and minimize operational infrastructure management overhead. Which TWO architectural components should the cloud architect select to satisfy these requirements? (Select TWO.)
- Cloud Run deployed in the target region to host the stateless API containers with automatic scaling and zero server managementAnswer
- Global External HTTP(S) Load Balancer to manage incoming client traffic, provide TLS termination, and distribute requests to backend servicesAnswer
- CA custom Google Kubernetes Engine (GKE) Standard cluster provisioned across multiple zones to manage stateless microservice pods
- DDedicated Interconnect to connect Google Cloud Availability Zones within the region for low-latency internal compute communication
- EA multi-region Cloud Spanner instance configured to cache temporary HTTP session state for stateless application instances
Answer
The cloud architect should select Cloud Run to host the stateless API containers serverlessly across zones and a Global External HTTP(S) Load Balancer to manage and route incoming client traffic.
To design a highly available, low-maintenance architecture for a stateless REST API, combining Cloud Run and a Global External HTTP(S) Load Balancer is optimal. Cloud Run provides automated multi-zone deployment, serverless scaling, and zero infrastructure management. The Global External HTTP(S) Load Balancer provides robust front-end ingress management, health checks, and global scalability.
Step-by-Step Solution
Key Concept
Serverless High Availability and Traffic Management Architecture