CLF-C02 Cloud Concepts Practice Question
A startup runs an application on AWS and receives a monthly bill that charges exactly for the number of compute hours used, the gigabytes of data stored, and the gigabytes of data transferred. The company pays nothing for resources they did not use. Which cloud computing characteristic does this represent?
⚠ Common exam trap
Watch out — candidates often confuse 'measured service' with 'on-demand self-service' because both involve user control, but measured service specifically focuses on the metering and billing aspect, not the provisioning mechanism.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Measured service
This scenario describes a pay-per-use model where costs directly correlate with actual consumption of compute hours, storage, and data transfer. Measured service is the cloud characteristic that enables this by automatically monitoring, controlling, and reporting resource usage, providing transparency for both the provider and consumer. AWS implements this through services like AWS CloudTrail and detailed billing reports, ensuring customers are charged only for what they consume.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Measured service
Why this is correct
Measured service is the cloud characteristic where resource consumption—such as vCPU hours, storage GB-months, and data transfer—is automatically metered, recorded, and reported. AWS uses these metering data to calculate charges, so you pay only for what you actually use, down to per-second or per-request granularity for many services. The provider also offers transparency through detailed billing reports, Cost Explorer, and billing alerts. This metering and reporting capability is the direct foundation of the pay-as-you-go pricing model.
- ✗
Rapid elasticity
Why it's wrong here
Rapid elasticity is the ability to scale computing resources out or in quickly, often automatically, in response to workload changes. It describes capacity agility—for example, adding EC2 instances during a traffic spike and terminating them afterward. However, it does not define how consumption is metered or billed; you could scale elastically and still be charged via a flat rate, subscription, or other pricing models. In a pay-per-use cloud, elasticity works alongside metered billing but is not the billing mechanism itself.
- ✗
On-demand self-service
Why it's wrong here
On-demand self-service is the ability for users to provision and configure cloud resources through a web portal, CLI, or API without requiring manual approval or human interaction from the provider. It gives customers immediate control over spinning up or shutting down services, eliminating procurement wait times. However, this characteristic is about access and autonomy, not about how charges are calculated. Even though a user can self-provision, the actual bill is still derived from metered usage, so on-demand self-service does not itself define pay-per-use billing.
- ✗
Resource pooling
Why it's wrong here
Resource pooling refers to the provider's multi-tenant model where compute, storage, and network resources are shared among many customers using virtualization, with logical isolation. It explains how AWS can achieve economies of scale and location independence, but it says nothing about how usage is charged to individual customers. A customer's bill is still generated by metering their specific consumption, not by the fact that physical infrastructure is shared. Thus, pooling is a characteristic that enables efficiency, but it is distinct from the pay-per-use billing mechanism.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
One of 993 original CLF-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CLF-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CLF-C02 exam.