A startup is optimizing its AWS costs for a single-account workload that consists of:
* A steady-state database running on a single Amazon RDS instance.
* An application tier running on Amazon EC2 instances, which the startup plans to migrate to graviton-based instances in the next quarter.
* Microservices running on AWS Fargate.
Which two purchasing strategies should a SysOps administrator recommend to achieve the highest cost savings while maintaining operational flexibility? (Select TWO.)
- Purchase a Compute Savings Plan to cover the EC2 instances and AWS Fargate tasks.Answer
- Purchase a Reserved Instance for the Amazon RDS database.Answer
- CPurchase an EC2 Instance Savings Plan for the c6i instance family.
- DPurchase a Compute Savings Plan to cover the Amazon RDS database and AWS Fargate tasks.
- EPurchase a regional EC2 Reserved Instance for the c6i.large instances.
Answer
Purchase a Compute Savings Plan to cover the EC2 instances and AWS Fargate tasks, and purchase a Reserved Instance for the Amazon RDS database.
A Compute Savings Plan provides the required flexibility because it applies automatically to both Amazon EC2 and AWS Fargate, regardless of instance family, size, or region. This accommodates the planned migration from the c6i family to the c7g family. Because Savings Plans do not support Amazon RDS, a separate Reserved Instance is needed to optimize the database tier.
Step-by-Step Solution
Key Concept
Operational scope and flexibility differences between Compute Savings Plans, Instance Savings Plans, and Reserved Instances.