A financial institution is designing compute infrastructure on Google Cloud for two distinct sub-components of a credit risk platform:
1. Workload 1: A stateless, containerized HTTP web service that experiences unpredictable request spikes during trading hours and no traffic overnight. Minimizing costs during idle periods by scaling to zero is a critical requirement.
2. Workload 2: A batch processing job that executes highly parallelized risk simulations. The job is fault-tolerant and can easily resume if an underlying instance is suddenly terminated.
Which TWO compute platform strategies should you recommend to meet these requirements efficiently? (Select TWO)
- Deploy Workload 1 on Cloud Run to automatically scale container instances dynamically with HTTP traffic and scale down to zero when idle.Answer
- Provision Compute Engine Spot VMs for Workload 2 to run the parallel batch simulation tasks at a significantly lower cost.Answer
- CDeploy Workload 1 on Cloud Functions by refactoring the containerized application into individual event-driven functions.
- DProvision standard, non-preemptible Compute Engine VMs with 3-year Committed Use Discounts for Workload 2 to avoid job interruptions.
- EDeploy Workload 1 on a GKE Autopilot cluster configured with custom OS kernel modules to enable scale-to-zero container execution.
Answer
Deploy Workload 1 on Cloud Run for stateless container scaling to zero, and provision Compute Engine Spot VMs for Workload 2 to execute fault-tolerant batch workloads cost-effectively.
Cloud Run is the optimal compute choice for stateless HTTP container workloads needing automatic scaling down to zero during idle periods. Compute Engine Spot VMs provide maximum cost optimization for batch compute jobs that are resilient to node interruptions.
Step-by-Step Solution
Key Concept
Selecting optimal GCP compute services based on containerization, scaling characteristics, cost sensitivity, and fault tolerance.