CLF-C02 Cloud Concepts Practice Question
A retail company uses Amazon EC2 Auto Scaling to automatically launch hundreds of EC2 instances when CPU utilization exceeds 70% during a flash sale. When traffic subsides, the Auto Scaling group terminates the excess instances. This ability to dynamically provision and release compute resources in response to changes in demand best demonstrates which fundamental characteristic of cloud computing?
⚠ Common exam trap
Many candidates confuse resource pooling (the multi-tenant sharing of infrastructure) with rapid elasticity (the dynamic scaling of resources), because both involve 'pooling' or 'sharing' in a broad sense, but only rapid elasticity describes the automatic scaling up and down in response to demand.
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
✓
Rapid elasticity
The scenario describes the ability to automatically scale compute resources up and down in response to real-time demand changes, which is the definition of rapid elasticity. In AWS, this is implemented through EC2 Auto Scaling, which dynamically launches or terminates instances based on CloudWatch alarms (e.g., CPU utilization > 70%). This on-demand provisioning and release of resources without manual intervention is a core characteristic of cloud computing as defined by NIST SP 800-145.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Broad network access
Why it's wrong here
Broad network access is a characteristic of cloud computing where resources are accessible over the network via standard protocols and can be used by diverse client platforms (e.g., laptops, mobile devices, workstations). The scenario describes Auto Scaling modifying EC2 capacity in response to demand—an operational behavior that changes the number of instances—but it does not illustrate anything about network reachability, client diversity, or standard access methods. In this context, broad network access is a property of the infrastructure that remains constant; the scaling action itself is about adjusting compute resources, not about broadening or altering network accessibility.
When this WOULD be correct
A question that asks: 'Which cloud characteristic allows users to access resources from any device with an internet connection using standard protocols (e.g., HTTP, SSH)?' would have broad network access as the correct answer.
- ✗
Resource pooling
Why it's wrong here
Resource pooling is the provider's ability to serve multiple customers using a multi-tenant model, with physical and virtual resources dynamically assigned. The scenario does not describe multi-tenancy or shared infrastructure; it describes scaling up and down.
When this WOULD be correct
A question that asks: 'Which cloud characteristic allows multiple customers to share the same physical infrastructure while maintaining isolation and security?' would have resource pooling as the correct answer, as it describes the multi-tenant model where resources are pooled to serve many consumers.
- ✓
Rapid elasticity
Why this is correct
Rapid elasticity is the ability to provision and release cloud resources quickly, often automatically, to scale in and out with demand. The Auto Scaling behavior shown in the scenario is a direct example of this characteristic.
- ✗
Measured service
Why it's wrong here
Measured service involves metering resource usage, monitoring, and providing transparency for billing. While AWS does measure usage for billing, the scenario is primarily about automatic scaling in response to load, not about monitoring or reporting usage.
When this WOULD be correct
A question asking which cloud characteristic enables pay-per-use billing, where resource usage is metered and charged based on consumption, would have measured service as the correct answer.
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.
✓Rapid elasticityCorrect answer▾
Why this is correct
Rapid elasticity is the ability to provision and release cloud resources quickly, often automatically, to scale in and out with demand. The Auto Scaling behavior shown in the scenario is a direct example of this characteristic.
✗Broad network accessWrong answer — click to see why▾
Why this is wrong here
Broad network access refers to the ability to access cloud resources over the network via standard protocols, not to dynamically scaling resources based on demand. The scenario describes scaling compute capacity up and down, which is rapid elasticity.
★ When this WOULD be the correct answer
A question that asks: 'Which cloud characteristic allows users to access resources from any device with an internet connection using standard protocols (e.g., HTTP, SSH)?' would have broad network access as the correct answer.
Why candidates choose this
Candidates may confuse the ability to access EC2 instances remotely (broad network access) with the automatic scaling behavior, or they may think that 'broad' implies scaling broadly across many instances.
✗Resource poolingWrong answer — click to see why▾
Why this is wrong here
Resource pooling refers to the provider's computing resources being pooled to serve multiple consumers, with physical and virtual resources dynamically assigned according to consumer demand. This question specifically highlights the ability to rapidly scale capacity up and down in response to demand changes, which is the definition of rapid elasticity, not resource pooling.
★ When this WOULD be the correct answer
A question that asks: 'Which cloud characteristic allows multiple customers to share the same physical infrastructure while maintaining isolation and security?' would have resource pooling as the correct answer, as it describes the multi-tenant model where resources are pooled to serve many consumers.
Why candidates choose this
Candidates may confuse resource pooling with elasticity because both involve dynamic allocation of resources. Resource pooling focuses on the shared infrastructure aspect, while elasticity focuses on the ability to scale resources up or down quickly. The mention of 'dynamically provision and release' might lead some to think of pooling, but the key is the scaling in response to demand.
✗Measured serviceWrong answer — click to see why▾
Why this is wrong here
Measured service refers to the ability to monitor, control, and report usage for billing purposes, not the dynamic provisioning and release of resources in response to demand changes.
★ When this WOULD be the correct answer
A question asking which cloud characteristic enables pay-per-use billing, where resource usage is metered and charged based on consumption, would have measured service as the correct answer.
Why candidates choose this
Candidates may confuse measured service with elasticity because both involve resource usage, but measured service is about tracking and billing usage, not scaling resources dynamically.
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?”
Go deeper
Related to this question
About these practice questions
One of 988 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.