A smart agriculture company is deploying two distinct workloads on Amazon EC2. The first workload is a telemetry ingestion engine that runs continuously throughout the year with a highly predictable baseline resource utilization. The second workload is a periodic, non-critical data analysis job that can be interrupted and resumed at any time without affecting the application's integrity. Which two Amazon EC2 pricing models should the company select to achieve the most cost-effective solution? (Select TWO).
- Savings Plans for the telemetry ingestion engineAnswer
- Spot Instances for the periodic data analysis jobAnswer
- COn-Demand Instances for both workloads to maximize flexibility
- DDedicated Hosts for the telemetry ingestion engine to ensure physical isolation
- ESpot Instances for the telemetry ingestion engine to reduce baseline costs
Answer
Savings Plans for the telemetry ingestion engine and Spot Instances for the periodic data analysis job.
Savings Plans provide substantial discounts (up to 72%) compared to On-Demand pricing in exchange for a commitment to a consistent amount of compute usage, making them ideal for the continuous, predictable telemetry workload. Spot Instances leverage spare AWS capacity to offer discounts up to 90%, which is perfect for non-critical, interruptible data analysis jobs.
Step-by-Step Solution
Key Concept
AWS Pricing Models for EC2 instances based on workload characteristics
Estimated Time:1m 30s