Which Workloads Belong on EC2 Spot Instances

CLF-C02 By islever Editorial Last updated

Identify AWS compute services. Compare AWS pricing models.

Short answer

B Run fault-tolerant workloads that can be interrupted and can control costs on Amazon EC2 Spot Instances to gain up to 90% off On-Demand pricing.

Question

Which type of workload should a company run on Amazon EC2 Spot Instances?
  1. A steady-state workload that requires a particular EC2 instance configuration for a long period of time
  2. A workload that can be interrupted and can control costs Correct Answer
  3. A steady-state workload that does not require a long-term commitment
  4. A workload that cannot be interrupted and can control costs

Key Takeaways

The exam tests whether you understand that Spot Instances trade availability for up to 90% savings, so the defining trait is interruption tolerance, not steady-state or uninterrupted operation.

Amazon EC2 Spot Instances let you run fault-tolerant, flexible workloads at steep discounts by using spare AWS capacity that AWS can reclaim with a two-minute interruption notice. This page confirms that a workload which can tolerate interruption while still controlling costs is the correct fit for Spot Instances.

Common mistake: Learners often pick D, believing 'can control costs' alone is the Spot trait; but option D describes workloads that cannot be interrupted, which is the opposite of Spot's reclaimable capacity and better served by On-Demand or Savings Plans. Options A and C describe steady-state or non-committed workloads, which are On-Demand use cases.

Expert Analysis

Why the Answer Is Correct

Spot Instances let you request spare EC2 capacity at discounts of up to 90% compared with On-Demand prices. The trade-off is that AWS can reclaim that capacity at any time, providing only a two-minute interruption notice. Therefore the ideal Spot workload is one that is fault-tolerant, flexible about instance type and availability zone, and explicitly able to be interrupted — while still letting you cap spend with max price settings, Spot block, or allocation strategies. Option B captures both halves of the Spot value proposition: interruption tolerance plus cost control.

Why the Other Options Are Wrong

Option A describes a steady-state workload needing a specific instance configuration for a long period — that is a Savings Plans or Reserved Instances scenario, where you pay for committed capacity rather than reclaimable spare capacity. Option C, a steady-state workload without long-term commitment, maps to On-Demand Instances, which give unlimited scale with no commitment but no Spot discount. Option D combines cost control with a no-interruption requirement; because Spot capacity can be taken back by AWS, an interruption-intolerant workload such as a production database or critical long-running application must not run on Spot and belongs on On-Demand, Reserved Instances, or Dedicated Hosts.

Community Comment Notes

The community responses unanimously selected B. As Nikmah summarized, Spot Instances are best for "short workloads, cheap, can lose instances (less reliable)," which correctly identifies both the discount and the interruption risk. ShaiTay and d00b229 echoed the same verdict, quoting option B verbatim. The vote distribution of 100% for B aligns with AWS's own documentation, so here the crowd judgment and the official guidance agree.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

On CLF-C02, match instance purchasing options to workload traits: interruption-tolerant and flexible to Spot, steady and committed to Savings Plans or Reserved Instances, and steady but uncommitted to On-Demand. Watch for the word 'interrupted' — it is the keyword that signals Spot Instances.

Frequently Asked Questions

Why is 'cannot be interrupted and can control costs' wrong for Spot Instances?

Spot capacity can be reclaimed by AWS with a two-minute notice, so interruption-intolerant workloads such as critical databases should use On-Demand, Savings Plans, or Dedicated Hosts instead.

What is the main difference between Spot Instances and On-Demand Instances?

On-Demand offers unlimited scale with no commitment and no interruption risk, while Spot provides deep discounts in exchange for accepting that AWS may reclaim the capacity at any time.

More CLF-C02 FAQ →

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 2 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 2

  1. Nikmah 👍 1 Answered B
    Spot Instances – short workloads, cheap, can lose instances (less reliable)
  2. ShaiTay 👍 1 Answered B
    B. A workload that can be interrupted and can control costs

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Which migration strategies move a cloud-incompatible CMS with least effort?

S-grade

Launching Third-Party IDS in AWS

S-grade

Which AWS Support Plan Offers API Access Most Cost-Effectively?

S-grade

S3 Express One Zone for Single-Digit Millisecond Latency

S-grade

Practice All CLF-C02 Questions

Access 120 questions with complete answers and detailed explanations.

View Full CLF-C02 Practice Test →

← Back to CLF-C02 Study Guide