A cloud engineer is using the Google Cloud Pricing Calculator to estimate the monthly compute expenses for a company migrating a multi-tier application. The workload requirements specify two distinct operational profiles:
1. A set of web frontend virtual machines running continuously 24 hours a day, 7 days a week, with a predictable baseline resource demand planned for a 3-year operational lifecycle.
2. A cluster of batch processing worker instances that execute non-critical, fault-tolerant data transformation jobs intermittently whenever spare capacity is available.
Which combination of VM pricing configurations should the engineer select in the Pricing Calculator to achieve the most accurate and cost-effective estimate for these components?
- AApply 3-Year Committed Use Discounts (CUDs) to both the continuous web frontend instances and the intermittent batch processing worker instances.
- Configure 3-Year Committed Use Discounts (CUDs) for the continuous web frontend instances, and select Spot Virtual Machines for the fault-tolerant batch processing workers.Cevap
- CManually add Sustained Use Discounts (SUDs) to both the web frontend instances and the batch processing workers in the Pricing Calculator.
- DProvision both component workloads using GKE Autopilot and select 3-Year Committed Use Discounts for the ephemeral container tasks.
Cevap
The correct option specifies configuring 3-Year Committed Use Discounts (CUDs) for the continuous web frontend instances and selecting Spot Virtual Machines for the fault-tolerant batch processing workers.
The correct strategy combines 3-Year Committed Use Discounts (CUDs) for predictable 24/7 baseline compute resources with Spot VMs for fault-tolerant, intermittent batch jobs. CUDs deliver the maximum savings for long-term continuous workloads, whereas Spot VMs offer steep discounts for non-critical tasks that can sustain interruptions.
Adım Adım Çözüm
Anahtar Kavram
Selecting optimal Google Cloud pricing models (Committed Use Discounts vs. Spot VMs) based on workload stability and fault tolerance.