A company is using Amazon EC2 and wants to understand the difference between Compute Savings Plans and EC2 Instance Savings Plans. Which statement is accurate?
Compute Savings Plans offer maximum flexibility (any family, any region, includes Fargate and Lambda) at a slightly lower discount. EC2 Instance Plans offer higher discounts for committing to a specific family and region.
Why this answer
Option C is correct because Compute Savings Plans offer the broadest flexibility, automatically applying to any EC2 instance (regardless of family, size, or region), as well as AWS Fargate and AWS Lambda usage. In contrast, EC2 Instance Savings Plans are restricted to a specific instance family within a chosen region, providing a narrower scope of coverage. This distinction is fundamental to understanding how each plan optimizes costs based on workload flexibility.
Exam trap
The trap here is that candidates often assume Compute Savings Plans always provide higher discounts due to their broader scope, but in reality, the discount is lower because flexibility is traded for a reduced rate, while EC2 Instance Savings Plans offer higher discounts for committing to a more specific usage pattern.
How to eliminate wrong answers
Option A is wrong because Compute Savings Plans generally provide lower discounts (up to 66%) compared to EC2 Instance Savings Plans (up to 72%), as the trade-off for greater flexibility is a reduced discount rate. Option B is wrong because EC2 Instance Savings Plans are less flexible—they apply only to a specific instance family (e.g., m5) within a single region, not across all instance families. Option D is wrong because neither Savings Plans type requires specifying the exact instance size at purchase; both plans cover all sizes within the chosen instance family (for EC2 Instance Savings Plans) or across all instances (for Compute Savings Plans), with the discount applied at the instance family or compute level.