A healthcare provider runs a patient analytics application on AWS. The application consists of three main components:
* An Amazon ECS cluster running API services on a baseline fleet of Amazon EC2 instances that operate continuously.
* A batch processing workload running on Amazon EC2 instances that executes for 2 hours each night. This workload is stateless, fault-tolerant, and designed to resume from checkpoints if interrupted.
* An Amazon Aurora PostgreSQL database cluster that stores patient records.
Which combination of purchasing strategies will minimize compute costs while meeting the application requirements? (Select TWO.)
- Purchase EC2 Instance Savings Plans to cover the baseline EC2 instances running the API services.Answer
- Use Spot Instances to run the daily batch processing workload.Answer
- CPurchase Compute Savings Plans to cover both the baseline EC2 instances and the Amazon Aurora PostgreSQL database cluster.
- DConfigure the daily batch processing workload to run on AWS Lambda functions.
- EPurchase an Amazon EC2 Instance Savings Plan to cover both the baseline EC2 instances and the Amazon Aurora PostgreSQL database cluster.
Answer
Purchase EC2 Instance Savings Plans to cover the baseline EC2 instances running the API services, and use Spot Instances to run the daily batch processing workload.
Purchasing an EC2 Instance Savings Plan is correct because the baseline ECS API services run continuously, making them steady-state workloads that benefit from the high discount of a committed savings plan. Using Spot Instances is correct because the daily batch processing workload is stateless, runs for a limited time (2 hours), and can resume from checkpoints, making it ideal for the high discounts of Spot instances without being impacted by potential interruptions.
Step-by-Step Solution
Key Concept
Selecting the most cost-effective EC2 purchasing option (Savings Plans vs. Spot Instances) based on workload predictability, duration, and fault tolerance.
Estimated Time:2m 0s