CLF-C02 Cloud Technology and Services Practice Question
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?
⚠ Common exam trap
A common mix-up: candidates 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).
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.
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.
When this WOULD be correct
If the question asked for a design principle to minimize cost for a non-critical batch processing workload that can tolerate downtime, and the options included using a single large instance to reduce overhead, then B could be correct.
- ✗
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.
When this WOULD be correct
Option C would be correct for a question asking: 'Which action should a company take to validate that its disaster recovery plan works as expected?' or 'What is a best practice for ensuring recovery procedures are effective?'
- ✓
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.
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.
✓Scale horizontally to increase aggregate system availability.Correct answer▾
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.
✗Use a single large EC2 instance to minimize the number of components that could fail.Wrong answer — click to see why▾
Why this is wrong here
Using a single large EC2 instance creates a single point of failure; if the instance or its Availability Zone fails, the application goes down, violating the requirement for automatic recovery from component or AZ failures.
★ When this WOULD be the correct answer
If the question asked for a design principle to minimize cost for a non-critical batch processing workload that can tolerate downtime, and the options included using a single large instance to reduce overhead, then B could be correct.
Why candidates choose this
Candidates may mistakenly believe that a single large instance is more reliable because it has fewer components, overlooking that it is a single point of failure and does not provide fault tolerance.
✗Test recovery procedures by simulating infrastructure failures in a staging environment.Wrong answer — click to see why▾
Why this is wrong here
Testing recovery procedures (option C) is a recommended practice for validating reliability, but it does not directly achieve automatic recovery from infrastructure failures without manual intervention. The requirement is for automatic recovery, which is a design principle, not a testing activity.
★ When this WOULD be the correct answer
Option C would be correct for a question asking: 'Which action should a company take to validate that its disaster recovery plan works as expected?' or 'What is a best practice for ensuring recovery procedures are effective?'
Why candidates choose this
Candidates may confuse testing recovery procedures with implementing automatic recovery, thinking that testing alone fulfills the requirement for automated resilience, or they may overlook that the question asks for a design principle, not a testing method.
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.