A media company runs a nightly batch job that processes video thumbnails. The batch can be interrupted at any time, and workers can resume automatically from checkpoints (a termination does not corrupt progress). The business goal is the lowest possible compute cost, and occasional interruptions are acceptable as long as the job continues automatically. Which approach is most cost-optimized?

Run the job on On-Demand EC2 instances to avoid interruptions

On-Demand avoids interruptions, but for an interruption-tolerant, checkpointable batch job it is typically more expensive than using discounted interruptible capacity.

Buy Reserved Instances for the entire job window because interruptions are acceptable anyway

Reserved Instances primarily optimize for steady, long-running capacity. For a batch job that can run on interruptible capacity, Spot usually provides greater cost reduction than committed-purchase models.

Use Savings Plans but schedule the job only during business hours to reduce the commit cost

Savings Plans help reduce cost for qualifying usage, but scheduling the batch does not eliminate the commit obligation. For an interruption-tolerant batch, the main lever is using Spot capacity rather than optimizing around a commit.

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Use EC2 Spot Instances and implement interruption handling with checkpoint-based restarts — The most cost-optimized option is to use EC2 Spot Instances for an interruption-tolerant batch workload and handle termination events with checkpoint-based restarts. Because the job can be safely interrupted and resumed from checkpoints, the team can run on Spot capacity without sacrificing correctness, while achieving substantially lower compute cost than On-Demand or committed-purchase models. On-Demand provides higher reliability but ignores the stated objective of lowest compute cost for a job that can tolerate interruptions. Reserved Instances and Savings Plans can reduce cost for predictable, steady workloads, but they don’t take advantage of Spot’s interruptible pricing and add commitment/constraints that are unnecessary here. Scheduling around committed purchases does not address the key economic driver for this scenario: using interruptible capacity with graceful recovery.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.