A company is designing a cost-optimization strategy for three distinct workloads running on Amazon EC2:
1. A continuous, predictable baseline of containerized microservices that runs 24/7.
2. A nightly batch data processing job that is highly parallelizable, runs for 3 hours, and can resume from checkpoints if interrupted.
3. A critical, monthly database reconciliation process that runs for 6 hours on the first day of each month and must not be interrupted.
Which combination of Amazon EC2 pricing models provides the most cost-effective solution while ensuring all performance requirements are met?
- Savings Plans for the continuous baseline, Spot Instances for the nightly batch processing, and On-Demand Instances for the monthly database reconciliation.Cevap
- BOn-Demand Instances for the continuous baseline, Savings Plans for the nightly batch processing, and Spot Instances for the monthly database reconciliation.
- CSavings Plans for both the continuous baseline and the nightly batch processing, and Spot Instances for the monthly database reconciliation.
- DDedicated Hosts for the continuous baseline, Reserved Instances for the nightly batch processing, and Savings Plans for the monthly database reconciliation.
Cevap
Savings Plans for the continuous baseline, Spot Instances for the nightly batch processing, and On-Demand Instances for the monthly database reconciliation.
The strategy of using Savings Plans for the continuous baseline, Spot Instances for the nightly batch processing, and On-Demand Instances for the monthly database reconciliation represents the absolute cost-optimum. The continuous baseline receives commitment discounts, the fault-tolerant batch job leverages the deep discounts of Spot Instances, and the short-duration, critical database reconciliation is run on On-Demand to guarantee execution without paying for idle capacity during the rest of the month.
Adım Adım Çözüm
Anahtar Kavram
Selecting the optimal Amazon EC2 pricing model based on workload predictability, duration, and fault tolerance.