CLF-C02 - Billing, Pricing, and Support (12% of the exam) - Section 4.1
Compare AWS pricing models, including On-Demand Instances, Reserved Instances, Spot Instances, Savings Plans and Dedicated Hosts, and understand data transfer and storage tier charges.
Compare AWS EC2 pricing models: On-Demand for flexible short-term use; Reserved Instances and Savings Plans for predictable workloads that justify a one- or three-year commitment for discounts; Spot Instances for interruptible, fault-tolerant work at the lowest price; and Dedicated Hosts for licensing or compliance needs. Recognise that data transfer and storage tiers also affect cost.
lock_openFree sampleBilling, Pricing, and Supportmedium
A company runs a steady, predictable baseline of Amazon EC2 compute that it expects to keep for the next three years, and it wants a lower rate than On-Demand by making a term commitment. Which TWO pricing models reward such a one-year or three-year commitment with a discount? (Select TWO.)
AReserved Instances, which grant a lower rate in exchange for committing to a one-year or three-year term.check_circle Correct
BOn-Demand Instances, which charge the standard rate by the second with no term commitment of any kind.
CSavings Plans, which give a discount in return for committing to a steady amount of spend per hour for a term.check_circle Correct
DSpot Instances, which sell spare capacity at a deep discount that AWS can reclaim at very short notice.
EDedicated Hosts, which provide a whole physical server for one tenant to satisfy licensing or isolation rules.
Reserved Instances and Savings Plans both lower the rate below On-Demand in return for a one-year or three-year commitment, matching steady predictable baseline usage. A steady multi-year baseline is best served by a commitment-based model: Reserved Instances commit to a specific instance term for a discount, while Savings Plans commit to an hourly spend amount for a term and apply the saving automatically; On-Demand carries no commitment and so no discount, Spot trades price for interruption, and Dedicated Hosts solve isolation rather than committed baseline cost.
Why A is correct: Reserved Instances trade a one-year or three-year term commitment for a discount, exactly matching the steady baseline described.
Why B is wrong: On-Demand is tempting for its flexibility but offers no commitment discount, so it costs more for a steady predictable baseline.
Why C is correct: Savings Plans reward an hourly spend commitment over a one-year or three-year term, fitting the predictable baseline at a lower rate.
Why D is wrong: Spot relies on interruptible spare capacity rather than a term commitment, so it does not suit an always-on baseline workload.
Why E is wrong: Dedicated Hosts address physical isolation and licensing, not a term-commitment discount on steady baseline compute.
Answers that look right on this material and are not. Each one is a distractor from a different question in the CLF-C02 bank for this domain.
A primary production database holding customer orders that must stay available every hour of the day.
errorWhy it is wrong: An always-on production database cannot tolerate sudden reclamation, so Spot is unsafe and a steady-baseline model fits instead.
On-Demand Instances, paying the standard per-second rate with no commitment for the running servers
errorWhy it is wrong: On-Demand suits short or unpredictable workloads, but for steady multi-year usage it costs more than a committed model, so it is the tempting default rather than the cheapest choice.
Spot Instances, which run on spare capacity at a discount and can be reclaimed by AWS whenever that capacity is needed elsewhere
errorWhy it is wrong: Spot Instances run on shared spare capacity and can be interrupted, so they give neither dedicated hardware nor the socket visibility a per-socket licence needs.