A financial services startup is launching a mobile application and has two specific server requirements:
* The primary transaction processing API layer, which runs continuously and has a predictable baseline CPU utilization that will not change over the next year.
* An analytics job that runs nightly for 2 hours, performing data transformation. This job is stateless, fault-tolerant, and can be terminated mid-run and retried the next night without data loss.
Which two Amazon EC2 pricing models should the startup select to achieve the most cost-effective solution for these workloads? (Select TWO.)
- Savings Plans to run the continuous, predictable transaction processing API layerCevap
- Spot Instances to run the fault-tolerant, stateless nightly analytics jobsCevap
- COn-Demand Instances to run the baseline transaction processing API layer
- DSpot Instances to run the continuous transaction processing API layer
- EReserved Instances to run the short-term, nightly analytics jobs
Cevap
The startup should select Savings Plans for the continuous, predictable transaction processing API layer, and Spot Instances for the fault-tolerant, stateless nightly analytics jobs.
The correct choices are Savings Plans for the transaction API layer and Spot Instances for the nightly analytics jobs. Savings Plans offer substantial discounts for predictable, continuous compute usage over a 1-year or 3-year term, making them ideal for the API layer. Spot Instances offer the highest discounts for workloads that are flexible, fault-tolerant, and can tolerate interruptions, which perfectly fits the stateless nightly analytics jobs.
Adım Adım Çözüm
Anahtar Kavram
Selecting optimal AWS EC2 pricing models based on workload predictability, duration, and fault tolerance.
Tahmini Süre:2m 0s