- A
Scalability
Why wrong: Scalability is the ability to handle growing amounts of work by adding resources — it's about capacity management, not failure tolerance.
- B
Elasticity
Why wrong: Elasticity is automatic scaling based on demand — it's a capacity optimization concept, not specifically about fault handling.
- C
Fault tolerance
Fault tolerance ensures system continuity despite component failures through redundancy, replication, and automatic failover — a core cloud design principle.
- D
Agility
Why wrong: Agility describes the speed and flexibility of provisioning and changing cloud resources — it's about development velocity, not failure handling.
Quick Answer
Fault tolerance is the correct choice because it specifically describes a system’s ability to continue operating without interruption when individual components fail, using techniques like redundancy, replication, and automatic failover. In AWS, this means deploying resources across multiple Availability Zones, synchronously replicating data in Amazon RDS Multi-AZ, and using Route 53 health checks to trigger failover to a standby resource—all aimed at eliminating single points of failure. On the AWS Certified Cloud Practitioner CLF-C02 exam, this concept tests your understanding of how AWS services maintain uptime despite underlying failures, and it often appears alongside high availability, which focuses on minimizing downtime rather than preventing it entirely. A common trap is confusing the two: high availability aims for quick recovery, while fault tolerance aims for zero disruption. Remember the memory tip: “Fault tolerance = no break; high availability = quick fix.”
CLF-C02 Cloud Concepts Practice Question
This CLF-C02 practice question tests your understanding of cloud concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which cloud concept describes the ability of cloud services to remain operational even when individual components fail, through techniques like redundancy, replication, and automatic failover?
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
Fault tolerance
Fault tolerance is the correct answer because it directly refers to a system's ability to continue operating without interruption when one or more of its components fail. This is achieved through techniques such as redundancy (e.g., deploying multiple EC2 instances across Availability Zones), replication (e.g., synchronously replicating data in Amazon RDS Multi-AZ), and automatic failover (e.g., Route 53 health checks triggering a switch to a standby resource). The core goal is to eliminate single points of failure and maintain service availability despite underlying failures.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Scalability
Why it's wrong here
Scalability is the ability to handle growing amounts of work by adding resources — it's about capacity management, not failure tolerance.
- ✗
Elasticity
Why it's wrong here
Elasticity is automatic scaling based on demand — it's a capacity optimization concept, not specifically about fault handling.
- ✓
Fault tolerance
Why this is correct
Fault tolerance ensures system continuity despite component failures through redundancy, replication, and automatic failover — a core cloud design principle.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Agility
Why it's wrong here
Agility describes the speed and flexibility of provisioning and changing cloud resources — it's about development velocity, not failure handling.
Common exam traps
Common exam trap: answer the scenario, not the keyword
AWS often tests the distinction between fault tolerance and high availability (HA), where the trap is that candidates confuse 'remaining operational during failures' (fault tolerance) with 'quickly recovering from failures' (HA), but in this question the explicit mention of redundancy, replication, and automatic failover points directly to fault tolerance.
Detailed technical explanation
How to think about this question
Under the hood, fault tolerance in AWS often relies on distributing workloads across multiple Availability Zones (AZs) within a Region, using services like Elastic Load Balancing (ELB) to route traffic away from failed instances. For stateful services, Amazon RDS Multi-AZ uses synchronous replication to a standby in a different AZ, with a DNS CNAME update and automatic failover typically completing within 60-120 seconds. A real-world scenario is an e-commerce site using an Application Load Balancer (ALB) with health checks across EC2 instances in three AZs; if one AZ's power fails, the ALB automatically stops sending traffic to that AZ's instances, ensuring zero downtime for users.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Cloud Concepts — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Concepts practice questions
Targeted practice on this topic area only
- →
All CLF-C02 questions
1,024 questions across all exam domains
- →
AWS Certified Cloud Practitioner CLF-C02 study guide
Full concept coverage aligned to exam objectives
- →
CLF-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CLF-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cloud Concepts practice questions
Practise CLF-C02 questions linked to Cloud Concepts.
Security and Compliance practice questions
Practise CLF-C02 questions linked to Security and Compliance.
Cloud Technology and Services practice questions
Practise CLF-C02 questions linked to Cloud Technology and Services.
Billing, Pricing, and Support practice questions
Practise CLF-C02 questions linked to Billing, Pricing, and Support.
AWS shared responsibility model practice questions
Practise CLF-C02 questions linked to AWS shared responsibility model.
AWS IAM practice questions
Practise CLF-C02 questions linked to AWS IAM.
AWS pricing practice questions
Practise CLF-C02 questions linked to AWS pricing.
AWS support plans practice questions
Practise CLF-C02 questions linked to AWS support plans.
AWS S3 practice questions
Practise CLF-C02 questions linked to AWS S3.
AWS EC2 practice questions
Practise CLF-C02 questions linked to AWS EC2.
Practice this exam
Start a free CLF-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CLF-C02 question test?
Cloud Concepts — This question tests Cloud Concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Fault tolerance — Fault tolerance is the correct answer because it directly refers to a system's ability to continue operating without interruption when one or more of its components fail. This is achieved through techniques such as redundancy (e.g., deploying multiple EC2 instances across Availability Zones), replication (e.g., synchronously replicating data in Amazon RDS Multi-AZ), and automatic failover (e.g., Route 53 health checks triggering a switch to a standby resource). The core goal is to eliminate single points of failure and maintain service availability despite underlying failures.
What should I do if I get this CLF-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 30, 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.