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 the least cost-effective for a production workload that runs continuously. With no commitment, you pay the full list price per second or hour, and AWS applies no discount for predictable, steady-state usage. Over a 3-year period, an always-on mix of EC2 instances would accrue significantly higher costs than committing to Compute Savings Plans, which offer the same flexibility at a substantial discount. Therefore, On-Demand is technically valid but financially suboptimal for this scenario.

  When this WOULD be correct

  A company with unpredictable workloads that cannot commit to a 1- or 3-year term, or needs maximum flexibility to stop/start instances at any time without penalty, should choose On-Demand instances.

• ✗

  Standard Reserved Instances (no upfront, 3-year term)

  Why it's wrong here

  Standard Reserved Instances provide a considerable discount, but they require a 1- or 3-year commitment to a specific instance family, region, and platform (e.g., Linux, Windows). This locks you into a fixed configuration, so if the company's 'mix' of EC2 instances changes—whether by resizing, changing instance types, or moving regions—the RI discount cannot be applied to those new configurations. While no upfront and 3-year terms align with the stated cost-saving goals, the lack of attribute flexibility across instance families makes Standard RIs a poor match for a company that values flexibility alongside savings. Compute Savings Plans deliver similar discounts without that rigidity.

  When this WOULD be correct

  A company has a steady-state workload with predictable resource usage, requires a specific instance family and Region for 3 years, and wants to minimize costs without upfront payment. Standard RIs (no upfront, 3-year) would be the best choice.

• ✓

  Compute Savings Plans (no upfront, 3-year term)

  Why this is correct

  Compute Savings Plans offer flexible compute coverage across EC2 instance families, sizes, Regions, OS, and tenancy. The 3-year term with no upfront payment provides cost savings without an initial cash outlay, exactly meeting the stated needs.

• ✗

  Spot Instances

  Why it's wrong here

  Spot Instances offer the deepest discounts—up to 90% off On-Demand prices—but they are interruptible and can be reclaimed by AWS with as little as a two-minute warning when EC2 capacity is needed elsewhere. A production application requiring 24/7 availability cannot tolerate these abrupt interruptions without building in significant redundancy, checkpointing, and failover logic, which adds architectural complexity and may undermine the cost savings. Thus, Spot Instances are suitable only for fault-tolerant or time-flexible workloads, not for a steady-state production deployment.

  When this WOULD be correct

  A company runs a fault-tolerant, stateless batch processing job that can handle interruptions and wants the lowest possible compute cost, with no requirement for 24/7 operation.

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