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.

• ✗

  S3 charges a flat monthly fee regardless of storage used

  Why it's wrong here

  Amazon S3 uses a pay-per-use pricing model with no flat monthly fee or subscription commitment. You are billed only for what you consume: storage space (per GB-month), request counts, and data transfer out, with tiered pricing that decreases as usage grows. Even with Reserved Capacity or Savings Plans, you pay for actual usage, not a static monthly charge independent of your S3 activity.

• ✓

  S3 charges per GB stored, per request, and for outbound data transfer

  Why this is correct

  S3 pricing is comprised of three main components: storage (per GB per month, tiered by volume and storage class), requests and data retrievals (per 1,000 operations, with costs varying by operation type like PUT, GET, or lifecycle transitions), and data transfer out of S3 to the internet or to other AWS Regions (with a free tier for the first 100 GB per month in some cases). Data transfer into S3 is free, but outbound transfer incurs charges that often dominate the bill for large downloads. This three-part structure enables fine-grained cost control and is fundamental to estimating S3 expenses accurately.

• ✗

  S3 storage is free; only data transfer is charged

  Why it's wrong here

  S3 storage is not free; you are charged per GB-month for the data you retain, even though AWS offers a limited free tier (e.g., 5 GB of standard storage for 12 months). After the free tier expires or exceeds its limits, you pay full price for storage, and data transfer out is also billed separately. The misconception likely arises from the existence of the free tier, but it is a promotional allowance, not a permanent policy, and both storage and transfer are normally billable.

• ✗

  S3 charges by the number of files stored, not the size

  Why it's wrong here

  S3 does not bill based on the number of objects stored; it charges for the total amount of data stored in gigabytes per month. While a high object count can increase request costs (e.g., PUT/GET operations), the storage charge itself is calculated from aggregate bytes, so one million 1-byte files would cost about the same storage as one 1 MB file. The misconception likely comes from confusing request pricing (per 1,000 requests) with storage pricing, but they are separate line items on the bill.