A financial services company is planning to deploy a dedicated transaction reporting microservice on Google Cloud Compute Engine. The service runs continuously 24/7 and requires an uninterrupted baseline of 4 vCPUs and 26 GB of RAM to meet strict Service Level Agreements (SLAs). Standard machine types offer either insufficient memory or excess unneeded vCPUs for this specific memory ratio. Which compute provisioning strategy should you choose to meet the operational requirements while minimizing costs?
- Provision a custom machine type with 4 vCPUs and 26 GB of RAM on Compute Engine, and purchase a Committed Use Discount (CUD) for the baseline capacity.Cevap
- BProvision a Spot VM instance with 4 vCPUs and 26 GB of RAM to achieve maximum baseline cost reduction.
- CDeploy the application to Google Cloud Functions to automatically manage memory scaling and eliminate VM overhead.
- DDeploy the workload to a GKE Autopilot cluster configured with a standard preset N2 machine family node pool.
Cevap
Provision a custom machine type with 4 vCPUs and 26 GB of RAM on Compute Engine, and purchase a Committed Use Discount (CUD) for the baseline capacity.
Custom Machine Types enable exact tailoring of CPU and RAM allocations when standard predefined shapes do not match the required memory ratio. Purchasing a Committed Use Discount (CUD) provides deep pricing discounts for steady-state 24/7 baseline capacity without risking preemption.
Adım Adım Çözüm
Anahtar Kavram
Custom Machine Types and Committed Use Discounts (CUDs) for continuous Compute Engine workloads