- A
Implement a monolithic architecture to reduce complexity and minimize points of failure.
Why wrong: Monolithic architectures concentrate functionality into a single process. This increases the blast radius; a failure in one part often brings down the entire application. This is an anti-pattern for reliability and does not support automatic recovery from component failures.
- B
Use a single large EC2 instance to minimize the number of components that could fail.
Why wrong: Relying on a single large instance creates a single point of failure. If that instance fails, the entire application goes down. This approach does not provide automatic recovery and contradicts the Reliability pillar principle of distributing workload across multiple components.
- C
Test recovery procedures by simulating infrastructure failures in a staging environment.
Why wrong: While testing recovery procedures is a valuable best practice within the Reliability pillar (the principle 'Test recovery procedures'), it does not by itself implement automatic recovery. It validates that recovery plans work, but the question specifically asks for a design principle that enables the system to automatically recover without manual intervention.
- D
Scale horizontally to increase aggregate system availability.
Horizontal scaling involves adding more instances (e.g., EC2 instances) to distribute the load. If one instance or even an entire Availability Zone fails, the remaining healthy instances continue serving traffic. Combined with automated health checks and Auto Scaling, this design principle ensures automatic recovery from component failures, directly meeting the requirement.
Quick Answer
The answer is to scale horizontally to increase aggregate system availability. This design principle from the AWS Well-Architected Framework's Reliability pillar works by adding more EC2 instances behind a load balancer, so if one instance fails, traffic is automatically redistributed to the remaining healthy ones. By deploying these instances across multiple Availability Zones, the architecture can survive the failure of an entire AZ without any manual intervention, directly meeting the requirement for automatic recovery from infrastructure failures. On the AWS Certified Cloud Practitioner CLF-C02 exam, this concept tests your understanding that horizontal scaling—not vertical scaling—is the key to fault tolerance and high availability. A common trap is confusing scaling up (bigger instances) with scaling out (more instances); remember that only horizontal scaling provides redundancy. Memory tip: think “more cows, not a bigger cow” to recall that spreading load across multiple units ensures automatic recovery when one fails.
CLF-C02 Cloud Technology and Services Practice Question
This CLF-C02 practice question tests your understanding of cloud technology and services. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A company is designing a cloud architecture for a critical customer-facing application. The CTO requires that the architecture automatically recover from infrastructure failures without manual intervention. The solution must be able to withstand the failure of individual components, such as an Amazon EC2 instance or an entire Availability Zone. Which design principle from the AWS Well-Architected Framework's Reliability pillar should the company implement to meet this requirement?
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
Scale horizontally to increase aggregate system availability.
Scaling horizontally (adding more EC2 instances behind a load balancer) increases aggregate system availability because if one instance fails, traffic is redistributed to the remaining healthy instances. This design also supports multi-AZ deployments, allowing the application to survive an entire Availability Zone failure without manual intervention, which directly meets the CTO's requirement for automatic recovery.
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.
- ✗
Implement a monolithic architecture to reduce complexity and minimize points of failure.
Why it's wrong here
Monolithic architectures concentrate functionality into a single process. This increases the blast radius; a failure in one part often brings down the entire application. This is an anti-pattern for reliability and does not support automatic recovery from component failures.
- ✗
Use a single large EC2 instance to minimize the number of components that could fail.
Why it's wrong here
Relying on a single large instance creates a single point of failure. If that instance fails, the entire application goes down. This approach does not provide automatic recovery and contradicts the Reliability pillar principle of distributing workload across multiple components.
- ✗
Test recovery procedures by simulating infrastructure failures in a staging environment.
Why it's wrong here
While testing recovery procedures is a valuable best practice within the Reliability pillar (the principle 'Test recovery procedures'), it does not by itself implement automatic recovery. It validates that recovery plans work, but the question specifically asks for a design principle that enables the system to automatically recover without manual intervention.
- ✓
Scale horizontally to increase aggregate system availability.
Why this is correct
Horizontal scaling involves adding more instances (e.g., EC2 instances) to distribute the load. If one instance or even an entire Availability Zone fails, the remaining healthy instances continue serving traffic. Combined with automated health checks and Auto Scaling, this design principle ensures automatic recovery from component failures, directly meeting the requirement.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse 'testing recovery procedures' (a design principle for validating resilience) with 'implementing automatic recovery' (which requires architectural choices like horizontal scaling and multi-AZ deployment).
Detailed technical explanation
How to think about this question
Horizontal scaling relies on distributing requests across multiple compute resources, typically using an Elastic Load Balancer (ELB) that performs health checks (e.g., HTTP 200 OK) and automatically routes traffic away from unhealthy instances. In a multi-AZ deployment, the load balancer distributes traffic across instances in different Availability Zones, so if an entire AZ becomes unavailable, the load balancer automatically directs traffic only to the healthy AZs, achieving the required automatic recovery without any manual steps.
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 Technology and Services — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Technology and Services 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 Technology and Services — This question tests Cloud Technology and Services — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Scale horizontally to increase aggregate system availability. — Scaling horizontally (adding more EC2 instances behind a load balancer) increases aggregate system availability because if one instance fails, traffic is redistributed to the remaining healthy instances. This design also supports multi-AZ deployments, allowing the application to survive an entire Availability Zone failure without manual intervention, which directly meets the CTO's requirement for automatic recovery.
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 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.