Question 788 of 988
CLF-C02 Cloud Concepts Practice Question
A company is migrating its on-premises application to AWS. The application currently runs on a single server and experiences occasional traffic spikes that cause performance degradation. The company wants to take advantage of cloud computing benefits to handle these spikes automatically without manual intervention. Which AWS Cloud concept would directly address this requirement?
⚠ Common exam trap
Watch out — candidates often confuse elasticity with high availability or fault tolerance, mistakenly thinking that any redundancy or failover mechanism automatically handles traffic spikes, but elasticity specifically addresses dynamic scaling to match demand, not just maintaining uptime during failures.
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
✓
Elasticity
Elasticity is the correct concept because it refers to the ability of an AWS infrastructure to automatically scale resources up or down based on demand. In this scenario, the company needs to handle occasional traffic spikes without manual intervention, which is directly addressed by AWS Auto Scaling groups and services like Amazon EC2 Auto Scaling or AWS Lambda's concurrency scaling. This ensures that additional compute capacity is provisioned during spikes and released when demand decreases, optimizing both performance and cost.
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 this is correct
Elasticity is the ability of an AWS resource, such as an Auto Scaling group or a DynamoDB table, to dynamically adjust its capacity in response to real-time demand. It directly addresses the requirement of handling traffic spikes by automatically adding or removing compute or storage resources without manual intervention, ensuring cost efficiency and consistent performance. This is distinct from durability, fault tolerance, and high availability, which focus on data persistence, failure resilience, and uptime, not on scaling with demand.
- ✗
High availability
Why it's wrong here
High availability refers to minimizing downtime by ensuring an application remains accessible and operational for a high percentage of time, typically achieved through redundancy across multiple Availability Zones and failover mechanisms. While high availability helps keep the application running during component or AZ failures, it does not imply that the system can increase its processing power or storage capacity when demand suddenly rises. An application can be highly available—always up and reachable—yet still become overwhelmed or degraded under a traffic spike because it lacks the ability to scale elastically, so this characteristic alone is insufficient for the stated requirement.
When this WOULD be correct
A question that asks: 'A company needs to ensure its application remains accessible even if an entire AWS Availability Zone fails. Which concept should they implement?' — here high availability would be correct.
- ✗
Fault tolerance
Why it's wrong here
Fault tolerance is the design principle that enables a system to continue operating correctly even when one or more of its components fail, often by eliminating single points of failure and using redundant components that can take over seamlessly. This characteristic is valuable for maintaining service availability during hardware or software failures, but it does not involve modifying the total capacity of the system in response to changes in user load. Traffic spikes require scaling out resources, not merely surviving failures, so fault tolerance alone does not meet the application's need for automatic demand-based adjustment.
When this WOULD be correct
A question asking how to design an application that continues to function without interruption when an AWS Availability Zone fails would make fault tolerance the correct answer.
- ✗
Durability
Why it's wrong here
Durability is a data persistence guarantee that ensures stored data will not be lost or corrupted over time, typically achieved through redundant storage mechanisms like Amazon S3's 99.999999999% durability and replication across multiple Availability Zones. While important for protecting application data, it has no bearing on the ability to scale resources in response to traffic fluctuations. A durable storage system can remain perfectly resilient to data loss yet still lack the capacity to handle sudden spikes in compute or processing demand, so it does not satisfy the stated requirement.
When this WOULD be correct
A question asking which AWS concept ensures data remains intact and recoverable after failures, such as 'Which AWS feature guarantees that stored objects survive the loss of multiple devices?' would make durability 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.
✓ElasticityCorrect answer▾
Why this is correct
Elasticity is the ability of an AWS resource, such as an Auto Scaling group or a DynamoDB table, to dynamically adjust its capacity in response to real-time demand. It directly addresses the requirement of handling traffic spikes by automatically adding or removing compute or storage resources without manual intervention, ensuring cost efficiency and consistent performance. This is distinct from durability, fault tolerance, and high availability, which focus on data persistence, failure resilience, and uptime, not on scaling with demand.
✗High availabilityWrong answer — click to see why▾
Why this is wrong here
High availability focuses on minimizing downtime through redundant components across multiple Availability Zones, but the question specifically requires automatic handling of traffic spikes without manual intervention, which is elasticity.
★ When this WOULD be the correct answer
A question that asks: 'A company needs to ensure its application remains accessible even if an entire AWS Availability Zone fails. Which concept should they implement?' — here high availability would be correct.
Why candidates choose this
Candidates may confuse high availability with elasticity because both involve scaling or redundancy, but high availability is about uptime, not dynamic scaling to meet demand spikes.
✗Fault toleranceWrong answer — click to see why▾
Why this is wrong here
Fault tolerance ensures system operation despite component failures, but the question's core need is automatic scaling to handle traffic spikes, which is elasticity.
★ When this WOULD be the correct answer
A question asking how to design an application that continues to function without interruption when an AWS Availability Zone fails would make fault tolerance the correct answer.
Why candidates choose this
Candidates may confuse fault tolerance with elasticity because both involve handling unexpected events, but fault tolerance focuses on failure resilience, not scaling to meet demand.
✗DurabilityWrong answer — click to see why▾
Why this is wrong here
Durability refers to the ability to prevent data loss, typically through replication and backups, not to automatically scaling resources to handle traffic spikes.
★ When this WOULD be the correct answer
A question asking which AWS concept ensures data remains intact and recoverable after failures, such as 'Which AWS feature guarantees that stored objects survive the loss of multiple devices?' would make durability the correct answer.
Why candidates choose this
Candidates may confuse durability with elasticity because both involve handling failures or changes, but durability is about data persistence, not resource 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?”
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.