A citizen portal has steady baseline EC2 demand all year, while a monthly batch job spikes briefly and can tolerate interruption. How should purchasing options be matched?
Select an answer to reveal the explanation.
Short Explanation
The always-on front desk gets a season pass; the once-a-month cleanup crew can take surplus tickets. Savings Plans for the steady portal, Spot for the interruptible batch spike.
Full Explanation
Savings Plans and Reserved Instances reduce cost for predictable steady-state compute, while Spot suits fault-tolerant, interruptible workloads such as batch. Applying Spot to latency-sensitive citizen transactions risks capacity reclamation. Pure On-Demand for baseline demand forgoes known savings. Over-committing specialty capacity only for tiny batch windows is rarely cost-efficient.