A large image-conversion batch runs overnight.
It can resume from checkpoints and has a flexible completion time.
Why are Spot Instances appropriate? Choose TWO.
Spot uses discounted spare EC2 capacity but can be interrupted, so it fits restartable workloads with flexible deadlines.
Detailed explanation
Spot uses spare EC2 capacity and can cost less than On-Demand capacity.
Spot uses spare EC2 capacity and can cost less than On-Demand capacity.
Because Spot can be interrupted, checkpointing and retry make the workload resilient.
Because Spot can be interrupted, checkpointing and retry make the workload resilient.
Capacity Reservations address capacity availability in an AZ.
Capacity Reservations address capacity availability in an AZ.
Spot does not provide a no-interruption guarantee.
Spot does not provide a no-interruption guarantee.
Physical-host allocation is a Dedicated Hosts use case, not a defining Spot feature.
Physical-host allocation is a Dedicated Hosts use case, not a defining Spot feature.
Check official documentation
Compare the following points with the official documentation.
Amazon EC2 Spot Instancesの中断と適したワークロードを確認する。
Official references
What to confirm
割引と中断許容設計を組み合わせて説明できる。
Key points
- Spot
- Interruption
- Checkpoint
Notes
- Environment:
- Pricing and conditions can change. Check the current AWS pricing page for the service and Region before implementation.
Foundation review
Interruption resilience
Use queues, idempotency, and checkpoints so another worker can continue.
Suitable workloads
Flexible batch and distributed processing commonly fit Spot.