An organization is designing a new cloud architecture for two distinct workloads:
1. A stateless containerized HTTP API that experiences unpredictable traffic spikes and requires automatic scaling down to zero instances during idle periods to minimize costs with zero node-management overhead.
2. A fault-tolerant nightly batch processing worker that processes queued images for several hours and can tolerate sudden node interruptions without data loss.
Which TWO Google Cloud compute deployment options should the cloud engineer select to meet these requirements while optimizing cost and operational efficiency? (Select TWO.)
- Deploy the stateless containerized HTTP API to Cloud Run.Cevap
- Deploy the fault-tolerant nightly batch processing workload on Spot Compute Engine virtual machines.Cevap
- CDeploy the stateless containerized HTTP API to Cloud Functions by refactoring the container into individual single-purpose event scripts.
- DDeploy the stateless containerized HTTP API to a GKE Standard cluster with manually configured fixed node pools to eliminate management overhead.
- EDeploy a non-fault-tolerant primary database on Spot Compute Engine virtual machines to reduce overall compute costs.
Cevap
The correct compute choices are deploying the stateless containerized HTTP API on Cloud Run and deploying the fault-tolerant nightly batch processing workload on Spot Compute Engine virtual machines.
Deploying the stateless containerized HTTP API on Cloud Run satisfies the requirement for container execution with scale-to-zero capabilities and minimal operational overhead. Deploying the fault-tolerant batch processing workload on Spot Compute Engine VMs leverages deeply discounted compute capacity suited for interruptible jobs.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Compute Services Based on Workload Characteristics (Cloud Run vs Spot VMs vs GKE)