A video processing pipeline runs batch jobs that are safe to interrupt and restart. The jobs checkpoint progress to durable storage every few minutes, and the team can automatically resubmit from the last checkpoint. They want to minimize compute cost while accepting that capacity can be interrupted. Which launch configuration for the processing workers is the best cost-optimized choice?

Launch the worker nodes as On-Demand Instances with no interruption handling so the pipeline never needs resubmission.

On-Demand is more expensive than Spot for the same instance types. The scenario explicitly allows interruption and restart, and it emphasizes minimizing compute cost—so using On-Demand without handling interruption contradicts the cost-optimization goal.

Launch the worker nodes as Reserved Instances to guarantee capacity and reduce cost, ignoring interruptions.

Reserved Instances discount On-Demand pricing but do not align with the scenario’s goal of accepting interruption for maximum savings. Also, ignoring interruptions conflicts with the operational reality that interruptions can still occur (and the scenario specifically provides checkpointing logic to handle interruption safely). The best approach is therefore to use Spot with interruption-aware resubmission.

Use Savings Plans and also set the job scheduler to never start new jobs unless previous jobs finish without interruption.

Savings Plans are commitment-based and can reduce cost, but the added scheduler constraint removes the ability to efficiently recover from interruption and undermines the pipeline’s interrupt-tolerant design. The scenario’s key cost lever is accepting interruptions using Spot, not avoiding them with restrictive scheduling.

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: Launch the worker nodes as Spot Instances, and configure the job resubmission logic to restart from checkpoints upon interruption. — Spot Instances are the best fit because the workload is explicitly interruption-tolerant and checkpointed. Spot can interrupt instances when capacity is reclaimed, but the team can restart from durable checkpoints, preserving overall progress and correctness. This combination provides the largest compute cost reduction among the listed purchasing options while meeting the requirement that jobs can be interrupted and safely resumed. Reserved Instances and Savings Plans reduce cost, but they are not as aligned with maximizing savings for interruptible workloads, and On-Demand is the most expensive option here. On-Demand would work but is typically more costly than Spot for batch jobs that can be interrupted. Reserved Instances and Savings Plans do not specifically optimize for interruption-tolerant designs and generally aim to stabilize capacity rather than maximize savings via Spot interruption handling. The scheduler restriction in D contradicts the provided checkpoint/resubmission model by preventing efficient continuation after interruptions.

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.