AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A global enterprise runs its production workloads on AWS, managed under AWS Organizations. The company has a significant and stable EC2 usage for its core data processing applications, which consistently run on m5.4xlarge instances in the us-east-1 Region. Additionally, the company is rapidly expanding its use of microservices, with a growing and fluctuating workload on both AWS Fargate and AWS Lambda across multiple regions.
The finance team has tasked the lead solutions architect with implementing a cost-optimization strategy that maximizes savings on this compute spend while maintaining flexibility for future architectural changes. The strategy must cover all existing and future compute usage effectively.
Which approach provides the most effective cost savings and operational flexibility for this scenario?
Purchase a combination of Savings Plans: EC2 Instance Savings Plans to cover the baseline, stable usage of m5.4xlarge instances in us-east-1, and a separate Compute Savings Plan to cover the variable usage of AWS Fargate and Lambda.
Purchase a single, large Compute Savings Plan to cover the total estimated hourly compute spend across EC2, Fargate, and Lambda.
Purchase Convertible Reserved Instances for the stable EC2 workload and commit to using Spot Instances for all Fargate and Lambda tasks.
Purchase EC2 Instance Savings Plans for the entire committed spend, covering the EC2 instances and an estimated amount for Fargate and Lambda.
The correct answer is to purchase a combination of Savings Plans. EC2 Instance Savings Plans offer the highest discount (up to 72%) but are limited to a specific instance family and AWS Region. This makes them ideal for the company's stable and predictable m5.4xlarge workload in us-east-1, maximizing savings for that portion. Compute Savings Plans offer a slightly lower discount (up to 66%) but provide significant flexibility, as they apply to EC2, Fargate, and Lambda usage across any region, instance family, or size. This makes them perfect for the growing and fluctuating microservices workload. This hybrid strategy achieves the highest overall savings by matching the right plan to the right workload characteristic, while still providing flexibility for the dynamic parts of the architecture.
Purchasing only a Compute Savings Plan is a valid but suboptimal strategy. While it provides maximum flexibility, it forgoes the higher discount that an EC2 Instance Savings Plan offers for the stable, predictable EC2 workload, thus not maximizing savings.
Purchasing only EC2 Instance Savings Plans is incorrect because these plans do not apply to AWS Fargate or AWS Lambda usage. This would leave a significant and growing portion of the company's compute spend without any discount.
Using Convertible RIs and Spot Instances is a plausible cost-saving strategy, but relying entirely on Spot for production Fargate and Lambda tasks introduces significant operational risk due to potential interruptions. This may not be suitable for all production workloads and does not fully address the request to create a comprehensive plan that effectively covers all compute usage with a reliable discount model.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are EC2 Instance Savings Plans?
Open an interactive chat with Bash
What is a Compute Savings Plan, and how does it differ from EC2 Instance Savings Plans?
Open an interactive chat with Bash
Why are Savings Plans better than Reserved Instances for this scenario?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design Solutions for Organizational Complexity
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access