A startup runs a public web application on Amazon EC2 instances that requires a baseline capacity of four instances running 24/7 to handle steady-state traffic. The application writes to an Amazon DynamoDB table that experiences sudden, highly unpredictable spikes in database traffic. In addition, the startup runs daily batch processing jobs on AWS Fargate that are fault-tolerant and can be interrupted at any time.
Which combination of purchasing strategies should a solutions architect recommend to minimize compute costs for these workloads? (Select TWO.)
- Purchase a Compute Savings Plan to cover the steady-state EC2 instances.Answer
- Use AWS Fargate Spot for the batch processing workloads.Answer
- CPurchase a Compute Savings Plan to reduce the cost of the Amazon RDS database instances.
- DMigrate the 24/7 steady-state EC2 instances to AWS Lambda functions to eliminate idle compute costs.
- EConfigure the Amazon DynamoDB table to use Provisioned Capacity mode to handle the unpredictable spiky traffic.
Answer
The solutions architect should purchase a Compute Savings Plan to cover the steady-state EC2 instances and use AWS Fargate Spot for the batch processing workloads.
Purchasing a Compute Savings Plan provides significant savings for the steady-state Amazon EC2 instances since they run continuously 24/7. Using AWS Fargate Spot is the most cost-effective choice for the batch processing workloads because they are fault-tolerant and can tolerate interruptions.
Step-by-Step Solution
Key Concept
Selecting the most cost-effective compute purchasing model based on workload characteristics (steady-state vs. interruptible) and service boundaries.