A financial services company is optimizing the deployment costs for two newly migrated workloads on Amazon EC2. The first workload is a real-time trading API that experiences sudden, sharp spikes in demand during market hours. The API cannot tolerate any service interruptions or latency increases, and the capacity requirement during non-trading hours is negligible. The second workload is a batch risk-modeling simulation that runs nightly, requires hundreds of vCPUs, is designed to tolerate interruptions by saving state, and must be completed at the lowest possible cost.
Which of the following EC2 pricing models should the company combine to achieve the most cost-effective solution for both workloads? (Select TWO.)
- On-Demand Instances to handle the sudden, unpredictable scaling demands of the trading APICevap
- Spot Instances for the fault-tolerant, nightly batch risk-modeling simulationCevap
- CDedicated Instances to guarantee hardware isolation for the nightly batch risk-modeling simulation
- DReserved Instances to cover the peak capacity needs of the trading API spikes
- ESavings Plans to cover the compute usage of the nightly batch risk-modeling simulation
Cevap
The company should combine On-Demand Instances to handle the sudden, unpredictable scaling demands of the trading API and Spot Instances for the fault-tolerant, nightly batch risk-modeling simulation.
The correct combination consists of On-Demand Instances and Spot Instances. On-Demand Instances provide uninterrupted compute capability without long-term commitments, which matches the trading API's strict SLAs and unpredictable spike patterns. Spot Instances offer the deepest discounts (up to 90%) for the nightly batch risk-modeling simulation, which is designed to tolerate interruptions by saving state.
Adım Adım Çözüm
Anahtar Kavram
Selecting the most cost-effective EC2 pricing models based on workload predictability, tolerance to interruption, and duration.