AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A global enterprise runs a data analytics platform on AWS. The platform has a consistent, predictable baseline EC2 usage of approximately $50/hour, 24/7. It also experiences significant, unpredictable spikes in demand from data science teams, which require various instance families (m-series, r-series, c-series) for short periods. The company has a 3-year commitment to AWS and wants to implement the most cost-effective strategy that also provides the flexibility to adopt new instance families over the 3-year term without requiring manual exchanges. Which pricing model strategy should a Solutions Architect recommend?
Purchase a 3-year, All Upfront Compute Savings Plan to cover the baseline usage and use a combination of Spot Instances and On-Demand Instances for the spiky workloads.
Purchase 3-year, All Upfront Standard Reserved Instances for the most common instance type to cover the baseline usage and use On-Demand Instances for the spiky workloads.
Purchase a 1-year, No Upfront EC2 Instance Savings Plan for the baseline usage and rely on a fleet of Spot Instances for all spiky workloads.
Purchase 3-year, All Upfront Convertible Reserved Instances to cover the baseline usage and use an On-Demand Capacity Reservation for the spiky workloads.
The correct approach is to purchase a 3-year, All Upfront Compute Savings Plan for the baseline usage and use Spot Instances, supplemented by On-Demand Instances, for the spiky workloads.
Compute Savings Plans offer the most flexibility, automatically applying discounts across different instance families, sizes, operating systems, and AWS Regions. This directly addresses the requirement to adopt new instance families without manual intervention, which would be required with Convertible RIs. Committing to a 3-year term with an all-upfront payment provides the maximum possible discount for the predictable baseline usage.
Standard Reserved Instances are not suitable because they lock the user into a specific instance family, which contradicts the flexibility requirement.
EC2 Instance Savings Plans are also less suitable than Compute Savings Plans because they are restricted to a single instance family within a specific AWS Region, offering less flexibility.
For the unpredictable, spiky workloads, Spot Instances are the most cost-effective choice, offering discounts of up to 90% off On-Demand prices for fault-tolerant workloads. On-Demand instances can supplement Spot Instances for any workloads that cannot be interrupted. Using Capacity Reservations is not a cost-optimization strategy, as it only reserves capacity at On-Demand rates without providing a discount.
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 is the difference between a Compute Savings Plan and Standard Reserved Instances?
Open an interactive chat with Bash
How do Spot Instances differ from On-Demand Instances in terms of cost and reliability?
Open an interactive chat with Bash
Why is a Compute Savings Plan better suited for spiky, unpredictable workloads than an EC2 Instance Savings Plan?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design for New Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access