A cloud solution architect is planning Google Cloud compute infrastructure for two separate organizational workloads:
1. A stateless, fault-tolerant batch processing job that can tolerate unexpected node preemptions and requires maximum cost reduction.
2. A lightweight containerized webhook service that experiences intermittent HTTP requests, needs to scale down to zero, and requires zero node management overhead.
Which TWO of the following Google Cloud compute configurations should be recommended for these workloads?
- Compute Engine Spot VMs for the stateless batch processing workloadAnswer
- Cloud Run for the containerized HTTP webhook serviceAnswer
- CCompute Engine Spot VMs to host a primary, continuous stateful relational database instance
- DGoogle Kubernetes Engine (GKE) Standard clusters for the webhook service to eliminate node management overhead
- ECloud Functions for deploying multi-container legacy monolithic applications with custom OS package dependencies
Answer
The correct compute choices are Compute Engine Spot VMs for the stateless batch job and Cloud Run for the containerized webhook service.
Selecting Compute Engine Spot VMs for the batch job leverages maximum cost efficiency for interruption-tolerant processing. Selecting Cloud Run for the containerized HTTP webhook satisfies the need for zero infrastructure node management and automatic scaling to zero when idle.
Step-by-Step Solution
Key Concept
Matching Google Cloud compute options (Spot VMs vs Cloud Run vs GKE Standard vs Cloud Functions) to specific workload fault-tolerance, operational overhead, and scaling requirements.