A cloud engineer is tasked with estimating monthly infrastructure costs using the Google Cloud Pricing Calculator for a mission-critical, high-availability PostgreSQL database running on Compute Engine instances. The workload requires persistent data storage with daily automated backups that will be accessed regularly by automated audit scripts. Which approach in the Pricing Calculator correctly applies GCP billing mechanics and pricing options for this workload?
- Model the database instances as Standard Compute Engine VMs with Committed Use Discounts (CUDs) applied, and select Standard Cloud Storage for the daily backup bucket.Cevap
- BModel the database instances as Spot VMs to lower compute costs by up to 90%, and configure persistent disks for high availability.
- CConfigure the backup bucket using Archive Cloud Storage class to minimize initial monthly storage costs for daily automated backups.
- DApply a 3-year Committed Use Discount (CUD) parameter while also enabling Sustained Use Discount (SUD) stacking in the calculator settings to maximize compute savings.
Cevap
Model the database instances as Standard Compute Engine VMs with Committed Use Discounts (CUDs) applied, and select Standard Cloud Storage for the daily backup bucket.
Modeling the workload as Standard Compute Engine VMs with Committed Use Discounts accurately reflects the baseline pricing for a continuous database, while Standard Cloud Storage accommodates frequent backup reads without incurring high retrieval charges.
Adım Adım Çözüm
Anahtar Kavram
Accurate cost estimation for continuous database workloads requires selecting Committed Use Discounts for compute instances and evaluating access pattern retrieval costs when choosing storage classes in the GCP Pricing Calculator.
Tahmini Süre:2m 0s