Compute pricing is the heart of the cost-optimization domain, and the SAA-C03 tests it as a matching exercise: four ways to pay, and a workload shape that selects exactly one. Read the workload for two properties — can it commit? and can it tolerate interruption? — and the answer falls out.
The four options by commitment and interruption
- On-Demand — full price, no commitment, never interrupted. For short, unpredictable workloads that cannot commit.
- Reserved Instances / Savings Plans — up to ~70% off for a 1- or 3-year commitment. For steady baseline usage.
- Spot — up to ~90% off, but reclaimable with ~2 minutes’ notice. For fault-tolerant, interruptible workloads.
Two questions settle most scenarios. Predictable and long-running? A commitment plan. Interruption-tolerant and after the deepest discount? Spot. Neither — short and must stay up? On-Demand.
Savings Plans: Compute vs EC2 Instance
When the answer is a commitment, the exam often asks which Savings Plan:
- Compute Savings Plan — the most flexible: change instance family, size, Region, OS, and it even covers Fargate and Lambda. Less discount, maximum freedom.
- EC2 Instance Savings Plan — commit to a specific family in a Region for a deeper discount, keeping size flexibility within that family.
Flexibility versus depth of discount is the trade, and the requirement words — “change families and Regions” versus “one family, biggest discount” — tell you which.
The Spot discipline
Spot’s saving is real, but it only applies to workloads that can survive being reclaimed: stateless rendering with checkpoints, fault-tolerant big-data clusters, retryable CI/CD builds. The wrong-fit answer is always a stateful, must-stay-up workload — a production database on Spot is the classic mistake. If it cannot be interrupted, it cannot be on Spot, no matter how tempting the discount.
How to use the six scenarios below
Answer each one before opening the explanation, and when you miss, name the two properties that decided it — “can commit?”, “can be interrupted?”. Every explanation states them and dismantles the distractors, which are usually a cheaper option the workload cannot actually use. Cost questions look like arithmetic but are really about matching a workload to the right commitment, and the reasoning below builds that instinct. For the domain overview, see Design Cost-Optimized Architectures.
Updated for SAA-C03 (July 2026). The sample questions above are our own work
in the style of the exam — not real exam items. The exam itself is set and marked
by the certification body.