A company is migrating a two-tier enterprise application to Google Compute Engine. The workload consists of two main components:
1. A stateful transactional SQL database that runs continuously 24/7 and cannot tolerate unexpected shutdowns or interruptions.
2. A nightly data transformation batch process that runs for 2 hours, is fully fault-tolerant, and regularly saves state to checkpoint files.
Which TWO deployment strategies should the cloud engineer select to meet these operational requirements while maximizing cost effectiveness?
- Purchase Committed Use Discounts (CUDs) for the compute resources allocated to the continuous 24/7 transactional database instance.Cevap
- Provision Spot Virtual Machines (Spot VMs) for the fault-tolerant nightly data transformation batch processing job.Cevap
- CDeploy the transactional SQL database on Spot VMs to achieve maximum cost reduction across all compute tiers.
- DRely solely on standard pay-as-you-go pricing for the 24/7 database instance to maximize Sustained Use Discounts while purchasing CUDs for the 2-hour batch job.
Cevap
Purchasing Committed Use Discounts (CUDs) for the continuous 24/7 database instance and provisioning Spot VMs for the fault-tolerant nightly batch processing job.
Purchasing Committed Use Discounts (CUDs) for the continuous 24/7 database instance ensures stable, uninterrupted capacity at significantly reduced costs. Provisioning Spot VMs for the batch transformation job minimizes compute costs for fault-tolerant, checkpoint-enabled processing.
Adım Adım Çözüm
Anahtar Kavram
Planning Compute Engine Workloads: Aligning Committed Use Discounts (CUDs) with continuous baseline workloads and Spot VMs with fault-tolerant batch workloads.
Tahmini Süre:1m 30s