A logistics enterprise is planning to deploy an enterprise resource planning (ERP) database on Google Cloud Compute Engine. The workload requires a constant 16 vCPUs and 128 GB of RAM to run continuously 24 hours a day, 7 days a week, with strict high availability SLA requirements. The finance team requires maximum cost optimization for this steady-state workload over a 3-year horizon. Which compute configuration and purchasing strategy should you recommend?
- Provision a standard Compute Engine instance matching the vCPU and RAM requirements, and purchase a 3-year Committed Use Discount for the workload.Answer
- BProvision Spot VMs with custom machine types (16 vCPUs, 128 GB RAM) to minimize compute costs for the continuous database workload.
- CDeploy the database workload using Cloud Run container instances with cpu-always-allocated enabled to eliminate VM management overhead.
- DProvision standard Compute Engine instances and rely solely on automatic Sustained Use Discounts to achieve maximum cost reduction.
Answer
Provision a standard Compute Engine instance matching the vCPU and RAM requirements, and purchase a 3-year Committed Use Discount for the workload.
The correct response combines standard Compute Engine virtual machines with a 3-year Committed Use Discount. Persistent enterprise databases with strict SLA requirements require reliable non-preemptible VMs. When resource consumption is predictable and continuous over a multi-year period, purchasing a Committed Use Discount yields significantly higher savings than on-demand rates or automatic Sustained Use Discounts.
Step-by-Step Solution
Key Concept
Planning Compute Engine Workloads with Committed Use Discounts vs Spot VMs