The AWS Well-Architected Framework's Reliability Pillar focuses on ensuring a workload performs its intended function correctly and consistently. Two of its core design principles are "Automatically recover from failure" and "Stop guessing capacity."

"Automatically recover from failure" involves monitoring for failures and designing systems to trigger automated recovery processes without requiring human intervention. "Stop guessing capacity" addresses a common cause of failure: resource exhaustion. By monitoring demand and automating the addition or removal of resources, a system can maintain optimal levels to satisfy demand, thus preventing failures related to insufficient capacity.

B. Granting everyone access violates the security principle of least privilege and is an operational anti-pattern, not a reliability principle.

D. Designing for a single Availability Zone is contrary to reliability best practices, which recommend multi-AZ architectures for high availability and fault tolerance.

E. This describes a specific operational tactic for managing quotas, not a foundational design principle of the Reliability Pillar itself.

1. AWS Well-Architected Framework. (2023

July). AWS Whitepaper. Page 6

Table 1 "Pillars of the AWS Well-Architected Framework". The table explicitly lists "Automatically recover from failure" and "Stop guessing capacity" as design principles for the Reliability Pillar.

Source: https://d1.awsstatic.com/whitepapers/architecture/AWSWell-ArchitectedFramework.pdf

2. AWS Well-Architected Framework Documentation. (n.d.). Reliability Pillar: Design Principles. AWS. The documentation lists the five design principles for reliability

which include "Automatically recover from failure" and "Stop guessing capacity."

Source: https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/design-principles.html