CLF-C02 Cloud Concepts Practice Question
A startup company is developing a new mobile application. The development team needs to quickly provision and tear down test environments to experiment with different backend configurations. They want to try new features, run performance tests for a few hours, and then delete all resources without any upfront commitment. They only pay for the compute and storage resources consumed during each test. Which benefit of cloud computing does this scenario BEST represent?
⚠ Common exam trap
Many candidates confuse agility (the ability to rapidly provision and deprovision resources for experimentation) with elasticity (automatic scaling based on load), which is a common misconception because both involve dynamic resource management but serve fundamentally different purposes.
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
✓
Agility
The scenario describes provisioning test environments on demand, running experiments for a few hours, and then tearing everything down with no upfront commitment. This directly maps to agility—the cloud's ability to rapidly create, modify, and delete resources to adapt to changing business or technical needs. The pay-as-you-go model further reinforces agility by removing the need for long-term contracts or hardware procurement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Agility
Why this is correct
Agility in the cloud is the ability to rapidly provision, configure, and release IT resources as needs evolve. For a startup, this means creating and destroying development or test environments in minutes using infrastructure as code or the AWS Management Console, without long procurement cycles or capital expenditure. It is the cloud characteristic that enables fast experimentation and innovation, and it is distinct from elasticity, which is about automatically matching capacity to demand, and high availability, which is about minimizing downtime through redundancy.
- ✗
Elasticity
Why it's wrong here
Elasticity is the automatic scaling of resources up or down in response to changing demand, such as CPU utilization or request count, using services like Amazon EC2 Auto Scaling and Application Auto Scaling. The scenario describes rapid manual or scripted provisioning and decommissioning for experimentation, not dynamic adjustment to fluctuating user traffic. The key distinction is that elasticity is a run-time capacity-management mechanism, whereas agility is an operational speed-and-flexibility benefit during development and innovation.
When this WOULD be correct
A question describing a workload with variable traffic, such as an e-commerce site that scales resources automatically during peak shopping hours and reduces them during low traffic, where the key benefit is paying only for what is used while meeting demand changes.
- ✗
High availability
Why it's wrong here
High availability refers to designing an application to remain accessible with minimal downtime, typically by running redundant workloads across multiple Availability Zones and using load balancers, health checks, and automatic failover. The scenario about quickly provisioning and decommissioning resources for development experiments does not address uptime targets, redundancy, or failure recovery. While AWS can help achieve high availability, this is not the benefit the startup is leveraging when quickly spinning up and tearing down environments.
- ✗
Fault tolerance
Why it's wrong here
Fault tolerance is a system's ability to continue operating correctly and without interruption even when its components fail, usually achieved through redundant resources and transparent failover — for example, deploying an application across multiple Availability Zones with synchronized data. The startup's scenario is about enabling quick experiments by shortening the time to create and remove resources, not about surviving infrastructure failures. Therefore, fault tolerance, while a valuable cloud property, is not the characteristic that matches this use case.
When this WOULD be correct
A question describing a system that must remain operational and serve users without interruption even if individual servers fail, such as a critical e-commerce platform requiring automatic failover and redundancy.
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.
✓AgilityCorrect answer▾
Why this is correct
Agility in the cloud is the ability to rapidly provision, configure, and release IT resources as needs evolve. For a startup, this means creating and destroying development or test environments in minutes using infrastructure as code or the AWS Management Console, without long procurement cycles or capital expenditure. It is the cloud characteristic that enables fast experimentation and innovation, and it is distinct from elasticity, which is about automatically matching capacity to demand, and high availability, which is about minimizing downtime through redundancy.
✗ElasticityWrong answer — click to see why▾
Why this is wrong here
Elasticity refers to automatically scaling resources up or down based on demand, not to quickly provisioning and tearing down test environments for experimentation. The scenario emphasizes rapid setup and teardown for testing, which is agility, not dynamic scaling.
★ When this WOULD be the correct answer
A question describing a workload with variable traffic, such as an e-commerce site that scales resources automatically during peak shopping hours and reduces them during low traffic, where the key benefit is paying only for what is used while meeting demand changes.
Why candidates choose this
Candidates may confuse the ability to quickly provision resources (agility) with the automatic scaling of resources (elasticity), as both involve dynamic resource management and pay-per-use pricing.
✗Fault toleranceWrong answer — click to see why▾
Why this is wrong here
Fault tolerance refers to a system's ability to continue operating despite component failures, not to the rapid provisioning and teardown of test environments with pay-per-use pricing.
★ When this WOULD be the correct answer
A question describing a system that must remain operational and serve users without interruption even if individual servers fail, such as a critical e-commerce platform requiring automatic failover and redundancy.
Why candidates choose this
Candidates may confuse the ability to quickly replace failed resources (fault tolerance) with the ability to quickly provision and deprovision resources (agility), as both involve rapid resource changes.
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.