Which Well-Architected pillar covers recovery from disruptions and dynamic scaling?
Which pillar of the AWS Well-Architected Framework refers to the ability of a system to recover from infrastructure or service disruptions and dynamically acquire computing resources to meet demand?
Community Insight
The exam tests whether you can map the phrase 'recover from disruptions and dynamically acquire resources' to the Reliability pillar rather than the similarly worded performance efficiency pillar.
The AWS Well-Architected Framework's Reliability pillar addresses how a workload keeps performing its intended function and recovers from infrastructure or service disruptions. This page confirms Reliability as the correct answer and separates it from performance efficiency, security, and cost optimization.
Many learners pick Performance efficiency because the phrase 'dynamically acquire computing resources' sounds like scaling for efficiency, but performance efficiency is about selecting and right-sizing resource types, not surviving failures.
Community Discussion (79 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The question bundles two ideas: recovering from infrastructure or service disruptions, and dynamically acquiring computing resources to meet demand. Both belong to the Reliability pillar of the AWS Well-Architected Framework, whose stated focus is workloads performing their intended functions correctly and consistently, including recovering quickly from failure to meet demand. Reliability covers distributed system design, recovery planning, failure mitigation, and adapting to changing requirements through scaling and automation. As jackmuihk summarises it, reliability is about "workloads performing their intended functions and how to recover quickly from failure to meet demand." Another learner, gunalg, put the same point plainly: the pillar "ensures a system can recover quickly from failures and automatically scale resources to handle changes in demand." No other pillar in the framework describes recovery from disruption as its defining concern.
Why the Other Options Are Wrong
Security is about protecting data, systems, and assets through identity, detective controls, infrastructure protection, and incident response — it says nothing about recovery from disruption or elastic capacity acquisition. Performance efficiency is the strongest distractor because it covers scaling, but its scope is the structured and streamlined allocation of resources: choosing optimized resource types and sizes, monitoring performance, and maintaining efficiency as needs evolve, not surviving outages. Cost optimization is about avoiding unnecessary spend and understanding where money goes, which does not describe resilience. As ambikamma reasoned in the thread, the Security pillar "does not describe recovery from failures or scaling resources," while Reliability "is about a system's ability to recover from disruptions."
Community Comment Notes
Consensus in the thread is strongly behind Reliability, with several learners simply posting "B. Reliability" (khulecal, certificate-butcher, Noncy, raj1017). The most useful contribution is the direct AWS reference to the Well-Architected page, which anchors the definition rather than relying on recall. Other commenters clarify the framework's scope: oguzbeliren lists the classic five pillars, while Sreenidhi_Palimar rightly points out that AWS now publishes a sixth pillar, Sustainability — useful context, though it does not change the answer. The thread also does a good job of pre-empting the performance efficiency trap.
Official Reference
Exam Strategy
Memorise one keyword signature per pillar — Security = protect, Reliability = recover and scale, Performance efficiency = right-size and optimize, Cost optimization = avoid waste, Operational excellence = operate and improve. When a stem mentions disruptions, failures, or recovery, map it to Reliability before you read the other options.
Frequently Asked Questions
Why is Performance efficiency not the answer if it also mentions scaling resources?
Performance efficiency is about selecting and right-sizing resource types and monitoring efficiency, not about surviving failures. Recovery from disruption is the defining scope of Reliability.
Does the Well-Architected Framework have five or six pillars?
AWS now publishes six: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. The CLF-C02 stem still points squarely at Reliability.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →