A security infrastructure team is designing a Google Compute Engine architecture for a 24/7 continuous log parsing engine. Profiling shows that the workload requires exactly and of RAM during steady-state operations. Standard machine types either under-allocate RAM or over-allocate vCPUs, leading to unnecessary operational expenses. The application cannot tolerate preemption or unexpected instance termination. Which configuration and purchasing strategy should the cloud engineer recommend to minimize cost while meeting all technical requirements?
- Provision a Compute Engine instance using a custom machine type with 6 vCPUs and 45 GB of RAM, and purchase Committed Use Discounts (CUDs) for the required vCPU and memory capacity.Cevap
- BProvision Spot VM instances configured with a custom machine type of 6 vCPUs and 45 GB of RAM to achieve the highest per-hour cost savings without contractual commitments.
- CProvision standard N2 machine instances with 8 vCPUs and 64 GB of RAM, relying entirely on automatic Sustained Use Discounts (SUDs) to achieve maximum cost savings.
- DMigrate the continuous long-running log parsing engine to event-driven Cloud Functions to eliminate instance sizing decisions entirely.
Cevap
Provision a Compute Engine instance using a custom machine type with 6 vCPUs and 45 GB of RAM, combined with Committed Use Discounts for the baseline vCPU and RAM capacity.
The combination of custom machine types and Committed Use Discounts (CUDs) directly addresses both requirements: custom sizing eliminates waste from unused vCPUs by configuring exactly 6 vCPUs and 45 GB RAM, while CUDs offer the highest price reduction for steady 24/7 non-interruptible workloads.
Adım Adım Çözüm
Anahtar Kavram
Compute Engine Custom Machine Types and Committed Use Discount Planning
Tahmini Süre:2m 0s