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 DB instances

  Why it's wrong here

  On-Demand DB instances incur the full standard per-hour rate with no long-term commitment or volume discount, making them the most expensive pricing model for a database that will run continuously for three years. While they offer flexibility and no upfront payment, they fail to minimize compute costs, which is a mandatory requirement for this migration. Unlike Reserved Instances, On-Demand pricing never rewards sustained usage, so the total expenditure over 36 months would be substantially higher than even a 1-year reservation.

  When this WOULD be correct

  A company needs a database for a short-term project (e.g., 6 months) with unpredictable usage patterns, and they want to avoid any long-term commitment or upfront costs. On-Demand would be the best choice for flexibility.

• ✗

  1-Year All Upfront Reserved DB instances

  Why it's wrong here

  1-Year All Upfront Reserved DB instances require paying the entire compute cost for the year at the moment of purchase, which directly violates the stated restriction that the finance team cannot make a large upfront payment. Even setting aside the cash-flow issue, a 1-year Reserved Instance offers a lower discount percentage than a 3-year commitment, so it does not minimize total cost over the database's expected lifespan. This option is therefore disqualified both by the upfront payment barrier and by its inferior long-term savings compared to a 3-year No Upfront reservation.

  When this WOULD be correct

  A company needs a database for only 1 year, has sufficient upfront budget to pay all at once, and wants to maximize discount for that single year. In that case, 1-Year All Upfront Reserved instances offer the highest discount among 1-year options.

• ✗

  3-Year Partial Upfront Reserved DB instances

  Why it's wrong here

  3-Year Partial Upfront Reserved Instances offer a good discount for a 3-year term, but they require some upfront payment. The question specifies no large upfront payment, so this option does not fully meet the requirement.

  When this WOULD be correct

  A company has a moderate upfront budget and wants a higher discount than No Upfront but cannot pay all upfront. For example, a 3-Year Partial Upfront Reserved Instance would be correct if the question states 'can make a partial upfront payment to reduce monthly costs.'

• ✓

  3-Year No Upfront Reserved DB instances

  Why this is correct

  3-Year No Upfront Reserved DB instances are the correct choice because they lock in a significantly reduced hourly rate for a 36-month term with zero upfront capital expenditure. This payment option for Amazon RDS Reserved Instances provides the deepest discount available without requiring a large initial payment, directly satisfying the finance team's budget constraint. Over a continuous three-year production workload, this yields the lowest total compute cost while maintaining the same database performance and availability as On-Demand.

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?”