CLF-C02 Cloud Concepts Practice Question
A company is migrating its on-premises data analytics workload to AWS. Previously, the company had to purchase and maintain dedicated servers with fixed capacity to handle peak workloads, resulting in low utilization during off-peak hours. On AWS, the company can launch compute resources, run the analytics job, and terminate the resources when done. The company only pays for the compute time and storage used during the job. Which essential characteristic of cloud computing does this scenario BEST demonstrate?
⚠ Common exam trap
Watch out — candidates often confuse 'pay only for what you use' (measured service) with the ability to scale resources up/down automatically (rapid elasticity), as both involve dynamic resource management but address different cloud characteristics.
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
Measured service is the cloud characteristic that enables pay-as-you-go pricing by metering resource usage (compute time, storage) and billing only for what is consumed. In this scenario, the company launches resources for the analytics job, runs it, and terminates them, paying solely for the compute time and storage used — a direct demonstration of metered usage and cost transparency.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Rapid elasticity
Why it's wrong here
Rapid elasticity is the ability to quickly scale resources up or down. This scenario does mention launching and terminating resources, but the primary focus is on paying only for what is used, not on automatic scaling. Elasticity is more about dynamic capacity adjustments rather than billing model.
- ✓
Measured service
Why this is correct
Measured service is the correct answer. Cloud providers meter usage (compute time, storage, etc.) and bill customers based on actual consumption. This eliminates the need to pay for idle capacity and aligns cost directly with usage, as described in the scenario.
- ✗
Resource pooling
Why it's wrong here
Resource pooling refers to the provider's ability to serve multiple customers using shared physical resources with logical isolation. While AWS uses resource pooling to achieve economies of scale, the scenario is about the billing advantage of paying only for consumed resources, not about multi-tenancy.
When this WOULD be correct
A question describing how a cloud provider uses multi-tenant infrastructure to serve many customers with varying demands, dynamically allocating and reallocating resources among them, would make resource pooling the correct answer.
- ✗
On-demand self-service
Why it's wrong here
On-demand self-service in AWS is the capability for customers to provision computing resources automatically—through the Management Console, CLI, or SDKs—without requiring any human interaction or manual approval from the cloud provider. While the scenario does involve launching and terminating resources, which is a self-service action, the core advantage being highlighted is purely financial: paying only for the exact capacity consumed rather than for pre-provisioned idle infrastructure. That pay-per-use billing model is the defining trait of measured service, whereas on-demand self-service focuses solely on the access and provisioning mechanism.
When this WOULD be correct
A question describing a scenario where a user can provision and configure AWS resources (e.g., launch an EC2 instance) through a web console or API without needing to contact AWS support or submit a request.
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.
✓Measured serviceCorrect answer▾
Why this is correct
Measured service is the correct answer. Cloud providers meter usage (compute time, storage, etc.) and bill customers based on actual consumption. This eliminates the need to pay for idle capacity and aligns cost directly with usage, as described in the scenario.
✗Resource poolingWrong answer — click to see why▾
Why this is wrong here
Resource pooling refers to the provider's ability to serve multiple customers from shared physical resources, not to the pay-per-use billing model. The scenario emphasizes paying only for consumed compute and storage, which is measured service, not resource pooling.
★ When this WOULD be the correct answer
A question describing how a cloud provider uses multi-tenant infrastructure to serve many customers with varying demands, dynamically allocating and reallocating resources among them, would make resource pooling the correct answer.
Why candidates choose this
Candidates may confuse resource pooling with the general idea of shared, on-demand resources, but the key differentiator here is the pay-per-use billing aspect, which is measured service.
✗On-demand self-serviceWrong answer — click to see why▾
Why this is wrong here
On-demand self-service refers to the ability to provision resources without human interaction, but the question emphasizes paying only for what is used (compute time and storage), which is measured service.
★ When this WOULD be the correct answer
A question describing a scenario where a user can provision and configure AWS resources (e.g., launch an EC2 instance) through a web console or API without needing to contact AWS support or submit a request.
Why candidates choose this
Candidates may confuse the ability to launch and terminate resources on demand with the on-demand self-service characteristic, but the key here is the pay-per-use billing model, not the provisioning method.
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?”
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
This CLF-C02 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.