An online video processing platform is designing a Google Kubernetes Engine (GKE) cluster architecture to support two distinct workloads:
1. A real-time web API serving client requests where the operations team requires fully managed infrastructure with zero node provisioning or cluster node maintenance overhead.
2. A stateless frame-rendering batch processing pipeline that is fault-tolerant and requires significant cost reduction on compute resources.
Which TWO architectural choices should you combine to meet these workload requirements while minimizing operational complexity and compute expense?
- Deploy a GKE Autopilot cluster for the real-time web API workload.Answer
- Provision a node pool composed of Spot VMs in GKE Standard for the stateless batch rendering workload.Answer
- CDeploy a GKE Standard cluster with fixed custom node pools to eliminate node management overhead for the web API.
- DProvision a dedicated Spot VM node pool to host the platform's persistent stateful database workloads.
- EConfigure the Horizontal Pod Autoscaler (HPA) to add physical Compute Engine instances when batch rendering demand spikes.
Answer
Deploy a GKE Autopilot cluster for the real-time web API workload, and provision a Spot VM node pool for the stateless batch rendering workload.
Combining GKE Autopilot for the web API workload and a Spot VM node pool for the batch workload satisfies all requirements. Autopilot offloads all node management and infrastructure maintenance to Google Cloud, matching the zero-node-management constraint for the web API. Spot VMs offer up to 60-90% savings for stateless, fault-tolerant batch workloads where preemption does not cause data loss.
Step-by-Step Solution
Key Concept
GKE Cluster Architectural Modes and Node Pool Selection Strategy