SAA-C03 Practice Question 10: Compute Savings Plans Spot Mix
AWS Certified Solutions Architect – Associate (SAA-C03) · Test 1 · question 10 of 10
Finance has flagged a rising compute bill. The account runs three distinct workloads: a steady around-the-clock baseline of roughly 200 vCPUs of EC2 spread across two Regions and several instance families, an AWS Fargate API that must stay online continuously, and a nightly batch fleet that is fully checkpointed and tolerates interruption.
The architect may make a one-year commitment but must preserve the freedom to change EC2 instance families and Regions as the platform evolves. Which combination is most cost-effective?
Show answer and explanation
Answer:
Compute Savings Plans are the most flexible commitment AWS offers: in exchange for a committed dollars-per-hour figure over one or three years they discount EC2 usage regardless of instance family, size, OS, tenancy, or Region, and the same commitment automatically applies to AWS Fargate and AWS Lambda usage. That maps one-to-one onto the constraints: two Regions, changing families, and a Fargate component all covered by a single plan. The interruptible batch fleet is the textbook Spot workload: it is checkpointed, so an interruption costs a restart rather than a failure, and it gets the deepest discount available without any commitment at all. Committing to a plan for a workload that only runs at night would waste coverage during the day.
Option A fails twice. Standard Reserved Instances are locked to an instance family and Region and cannot be exchanged, which directly contradicts the flexibility requirement, and Reserved Instances do not apply to Fargate usage at all. Leaving the interruptible batch fleet on On-Demand throws away the single largest saving available.
Option C fixes half of A: Convertible RIs can be exchanged for a different family, but they still do not cover Fargate, and sizing a commitment to include a fleet that runs only a few hours a night buys coverage that sits idle the rest of the day.
Option D picks the wrong Savings Plan type and misplaces Spot. EC2 Instance Savings Plans commit you to a specific instance family in a specific Region, the opposite of what is required, and, unlike Compute Savings Plans, they do not extend to Fargate or Lambda. Running a continuously available production API on Spot is also a poor fit, since Spot capacity can be reclaimed on two minutes' notice.
Reference: What are Savings Plans?