A financial services organization is migrating two distinct workloads to Google Cloud. The architecture team requires solution designs that minimize operational maintenance and infrastructure cost.
• Workload 1: A stateless, containerized HTTP REST API servicing unpredictable fraud check queries that must automatically scale to zero instances during idle periods.
• Workload 2: A containerized nightly batch process that executes non-HTTP financial risk simulations for up to 3 hours per run.
Which TWO Google Cloud compute platform configurations should you select to meet these requirements? (Select TWO.)
- Deploy Workload 1 as a Cloud Run service configured with request-based autoscaling.Answer
- Deploy Workload 2 as a Cloud Run job scheduled to execute the containerized task to completion.Answer
- CDeploy Workload 1 to a Google Kubernetes Engine (GKE) cluster managed with the Horizontal Pod Autoscaler.
- DDeploy Workload 2 as an HTTP-triggered Cloud Function with max instances set to 1.
Answer
Deploy Workload 1 as a Cloud Run service configured with request-based autoscaling, and deploy Workload 2 as a Cloud Run job scheduled to execute the containerized task to completion.
For stateless HTTP APIs that require scaling to zero and zero server management, Cloud Run services provide fully managed container deployment with request-driven autoscaling. For batch containers that run to completion without listening for incoming network requests, Cloud Run Jobs provides a fully managed execution environment supporting long-running tasks.
Step-by-Step Solution
Key Concept
Selecting serverless container services (Cloud Run services vs Cloud Run Jobs) based on traffic patterns, execution duration, and event triggers.