SAA-C03 · Question #552
A company is developing a monolithic Microsoft Windows based application that will run on Amazon EC2 instances. The application will run long data-processing jobs that must not be in- terrupted. The…
The correct answer is A. Purchase a Compute Savings Plan with a 3-year commitment. Adjust the hourly commit-ment. For steady, predictable EC2 usage with potential changes in instance families over time, AWS recommends Savings Plans. Compute Savings Plans "apply to any EC2 instance regardless of region, instance family, operating system, or tenancy," and also apply to AWS Fargate and AWS…
Question
A company is developing a monolithic Microsoft Windows based application that will run on Amazon EC2 instances. The application will run long data-processing jobs that must not be in- terrupted. The company has modeled expected usage growth for the next 3 years. The company wants to optimize costs for the EC2 instances during the 3-year growth period. Which solution will meet these requirements in the MOST cost-effective way?
Options
- APurchase a Compute Savings Plan with a 3-year commitment. Adjust the hourly commit-ment
- BPurchase an EC2 Instance Savings Plan with a 3-year commitment. Adjust the hourly com-
- CPurchase a Compute Savings Plan with a 1-year commitment. Renew the purchase and adjust
- DDeploy the application on EC2 Spot Instances. Use an Auto Scaling group with a minimum size of
How the community answered
(32 responses)- A75% (24)
- B16% (5)
- C3% (1)
- D6% (2)
Explanation
For steady, predictable EC2 usage with potential changes in instance families over time, AWS recommends Savings Plans. Compute Savings Plans "apply to any EC2 instance regardless of region, instance family, operating system, or tenancy," and also apply to AWS Fargate and AWS Lambda, delivering the most flexibility over a multi-year horizon. A 3-year term provides the highest discount among Savings Plans for long-lived workloads. EC2 Instance Savings Plans are limited to a chosen instance family in a region; as needs evolve (e.g., size or family changes), discounts may not fully apply. Spot Instances are not appropriate for long, interruption-sensitive jobs because Spot capacity can be reclaimed with short notice. Therefore, a Compute Savings Plan (3-year) best matches cost optimization with flexibility for growth and changes.
Community Discussion
No community discussion yet for this question.