CLF-C02 Billing, Pricing, and Support Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  On-Demand Instances

  Why it's wrong here

  On-Demand Instances are billed per second or per hour with no upfront commitment or volume discounts, which makes them the most expensive way to run a continuous, 3-year steady-state workload. While they offer total flexibility and no long-term contract, the cumulative cost over three years for a fleet of EC2 instances would be significantly higher than any committed-use pricing model, and they do not provide any cost optimization benefits for predictable, uninterrupted workloads.

  When this WOULD be correct

  A company needs to run a short-term, unpredictable workload (e.g., less than a month) with no upfront commitment and wants the flexibility to stop instances at any time without penalty.

• ✗

  Standard Reserved Instances

  Why it's wrong here

  Standard Reserved Instances provide the largest discount (up to 72%) but require a 1- or 3-year commitment tied to a specific instance family, region, and operating system. This lock-in means that if the company needs to change instance families — for example, to adopt a newer generation or different instance type to meet evolving performance needs — the reserved capacity cannot be flexibly applied, and modifying or exchanging the reservation may not be supported. The lack of flexibility to shift between families is exactly the constraint the company wants to avoid, making Standard Reserved Instances a poor fit despite the deep discount.

  When this WOULD be correct

  A company needs to run a predictable, steady-state workload for 3 years with no need to change instance families, and wants the lowest cost. Standard Reserved Instances offer significant discounts over On-Demand for such commitments.

• ✓

  Compute Savings Plans

  Why this is correct

  Compute Savings Plans provide a flexible pricing model where you commit to a consistent amount of compute usage (measured in dollars per hour) for a 1- or 3-year term, and in return, you receive a discounted rate (up to 66%) that automatically applies across any EC2 instance family, region, or operating system. This flexibility is ideal for a fleet that may need to change instance families over time, making it the lowest-cost option that still allows you to adapt your infrastructure without being locked into a fixed configuration.

• ✗

  Spot Instances

  Why it's wrong here

  Spot Instances leverage spare AWS EC2 capacity and can offer discounts of up to 90% compared to On-Demand, but they are interruptible with only a two-minute warning before AWS reclaims the capacity. Because the workload in question must run continuously for 3 years without interruption, Spot Instances are unsuitable — a single spot capacity reclamation event would cause downtime or require failover, breaking the steady-state requirement. Their temporary, non-guaranteed nature cannot support a long-term, predictable fleet.

  When this WOULD be correct

  For a fault-tolerant, stateless, or batch processing workload that can handle interruptions and requires the lowest possible cost, Spot Instances would be the correct choice.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question