A company is planning the Google Compute Engine architecture for two distinct workloads. Workload A is a nightly 4-hour batch processing job that is fault-tolerant and can resume from checkpoints if interrupted. Workload B is a 24/7 production relational database requiring steady, predictable vCPU performance with zero tolerance for abrupt termination. Which Compute Engine resource strategy minimizes total cost while meeting the operational requirements for both workloads?
- Provision Spot VMs for Workload A, and provision standard VM instances with Committed Use Discounts (CUDs) for Workload B.Cevap
- BProvision Spot VMs for both Workload A and Workload B to maximize cost savings across all Compute Engine instances.
- CProvision standard VM instances with Sustained Use Discounts (SUDs) for Workload A, and provision Spot VMs with Committed Use Discounts (CUDs) for Workload B.
- DMigrate Workload A to Cloud Functions and deploy Workload B on Cloud Run with min-instances set to zero.
Cevap
Provision Spot VMs for Workload A, and provision standard VM instances with Committed Use Discounts (CUDs) for Workload B.
Spot VMs are designed specifically for fault-tolerant, batch, or checkpointed workloads like Workload A, offering heavy discounts without risking service SLA. For continuous 24/7 workloads like Workload B, standard VM instances paired with Committed Use Discounts (CUDs) deliver predictable cost savings without preemption risk.
Adım Adım Çözüm
Anahtar Kavram
Compute Engine Resource Planning & Spot VM Suitability vs Committed Use Discounts