A bioinformatics research organization is planning its compute architecture on Google Cloud for two upcoming workloads:
1. Genomic Pipeline: Interruptible, stateless batch jobs that process large genomic dataset files overnight and can resume from checkpoints if interrupted.
2. Patient Portal API: A continuous 24/7 web application backend with predictable, steady-state resource utilization throughout the year.
Which TWO strategies should the cloud engineer implement to optimize cost and performance for these Compute Engine resources?
- Provision Spot VMs for the genomic processing batch jobs to achieve significant cost savings on fault-tolerant workloads.Cevap
- Purchase Committed Use Discounts (CUDs) for the vCPU and memory baseline required by the patient portal API.Cevap
- CProvision Spot VMs for the relational database backend of the patient portal API to reduce infrastructure costs.
- DDeploy the patient portal API legacy multi-container workload onto Cloud Functions to minimize compute overhead.
Cevap
Provision Spot VMs for the genomic processing batch jobs and purchase Committed Use Discounts (CUDs) for the patient portal API vCPU and memory baseline.
The correct strategy combines Spot VMs for interruptible batch workloads and Committed Use Discounts (CUDs) for continuous steady-state baseline workloads. Spot VMs deliver deep discounts for batch jobs that tolerate preemption, while CUDs provide predictable cost savings for 24/7 web API workloads without preemption risks.
Adım Adım Çözüm
Anahtar Kavram
Planning Compute Engine Workload Cost Optimization Strategy