CLF-C02 Cloud Concepts Practice Question
A company is launching a new application and expects user demand to grow gradually over the next 12 months. To control upfront costs, the company plans to start with a small number of Amazon EC2 instances and manually add more instances each month as the user base increases. The operations team will monitor usage and adjust capacity based on observed trends. Which cloud computing concept does this approach BEST illustrate?
⚠ Common exam trap
Many candidates confuse scalability with elasticity, assuming any capacity adjustment is elasticity, but the key differentiator is automation—elasticity requires automatic, real-time scaling, while manual, planned adjustments are scalability.
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
✓
Scalability
The scenario describes manually adding EC2 instances over time to match growing demand, which is a classic example of scalability—the ability to increase or decrease resources to handle changing workloads. Scalability focuses on planned capacity adjustments, whereas elasticity involves automatic, real-time scaling in response to demand fluctuations. Here, the manual, monthly additions based on observed trends align with scalability, not the automated provisioning that defines elasticity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Elasticity
Why it's wrong here
Elasticity refers to automatically scaling resources in and out in response to real-time demand fluctuations, typically via Amazon EC2 Auto Scaling, CloudWatch alarms, and target tracking policies. The scenario explicitly describes a manual, planned approach to adding instances over time, not an automated, reactive process. Because there is no dynamic load-based adjustment, this option is incorrect.
When this WOULD be correct
A company expects unpredictable traffic spikes and configures EC2 Auto Scaling to automatically add instances during high demand and remove them when demand drops. This would illustrate elasticity.
- ✓
Scalability
Why this is correct
Scalability is the ability to increase capacity to handle greater load. The company's approach of manually adding EC2 instances as user demand grows is a direct example of scaling up over time, making this the correct answer.
- ✗
High availability
Why it's wrong here
High availability maximizes uptime by distributing workloads across multiple Availability Zones, using Elastic Load Balancing health checks, and enabling automatic failover to healthy instances. The given scenario focuses on accommodating anticipated user growth rather than designing for redundancy, failover, or recovery from infrastructure failures. Since no availability SLA or multi-AZ requirement is mentioned, this option is incorrect.
When this WOULD be correct
A question asks: 'A company runs a critical e-commerce platform that must remain accessible even if one Availability Zone fails. Which concept does this requirement illustrate?' High availability would be correct because it involves designing systems to operate continuously despite component failures.
- ✗
Fault tolerance
Why it's wrong here
Fault tolerance demands that the workload continues operating seamlessly even when a component, such as an EC2 instance or database node, fails — often achieved through fully redundant active-active deployments. Unlike availability, fault-tolerant designs aim for zero downtime during failures, requiring duplicate infrastructure. The scenario addresses capacity growth for an expanding user base, not resilience to component failure, making this option incorrect.
When this WOULD be correct
A question that asks: 'An application must continue to operate without interruption even if an EC2 instance fails. Which concept does this requirement illustrate?' would make fault tolerance 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.
✓ScalabilityCorrect answer▾
Why this is correct
Scalability is the ability to increase capacity to handle greater load. The company's approach of manually adding EC2 instances as user demand grows is a direct example of scaling up over time, making this the correct answer.
✗ElasticityWrong answer — click to see why▾
Why this is wrong here
Elasticity refers to automatically scaling resources up or down based on demand, but the question describes manually adding instances each month, which is not automatic.
★ When this WOULD be the correct answer
A company expects unpredictable traffic spikes and configures EC2 Auto Scaling to automatically add instances during high demand and remove them when demand drops. This would illustrate elasticity.
Why candidates choose this
Candidates often confuse scalability with elasticity, thinking any capacity adjustment is elasticity, but elasticity specifically implies automatic, dynamic scaling.
✗High availabilityWrong answer — click to see why▾
Why this is wrong here
High availability focuses on ensuring application uptime and resilience through redundant components, not on adjusting capacity over time as demand grows. The question describes adding instances monthly to match gradual user growth, which is a scalability concern, not high availability.
★ When this WOULD be the correct answer
A question asks: 'A company runs a critical e-commerce platform that must remain accessible even if one Availability Zone fails. Which concept does this requirement illustrate?' High availability would be correct because it involves designing systems to operate continuously despite component failures.
Why candidates choose this
Candidates may confuse high availability with scalability because both involve multiple instances, but high availability is about uptime and redundancy, not about adjusting capacity to meet changing demand.
✗Fault toleranceWrong answer — click to see why▾
Why this is wrong here
Fault tolerance focuses on maintaining system operation during component failures, not on adjusting capacity to meet changing demand. The question describes manually adding instances over time to handle gradual growth, which is about scalability, not fault tolerance.
★ When this WOULD be the correct answer
A question that asks: 'An application must continue to operate without interruption even if an EC2 instance fails. Which concept does this requirement illustrate?' would make fault tolerance the correct answer.
Why candidates choose this
Candidates may confuse fault tolerance with the ability to handle increased load, or they might think that adding instances is a way to ensure the system tolerates faults, but fault tolerance specifically addresses failure recovery, not capacity scaling.
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
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.