Which design principles are included in the reliability pillar of the AWS Well-Architected Framework? (Choose two.)

Question

Options

• AAutomatically recover from failure.
• BGrant everyone access to increase AWS service quotas.
• CStop guessing capacity.
• DDesign applications to run in a single Availability Zone.
• EPlan to increase AWS service quotas first in a secondary AWS Region.

• A
  89% (16)
• D
  6% (1)
• E
  6% (1)

Explanation

AWS Well-Architected Framework – Reliability Pillar

Automatically recover from failure (A) is a core reliability principle because it ensures systems can detect failures and self-heal without manual intervention, minimizing downtime. Stop guessing capacity (C) is also a reliability principle, as over- or under-provisioning resources can lead to performance degradation or outages - using Auto Scaling and monitoring allows systems to match demand dynamically.

Why the distractors are wrong:

• B is incorrect because access to increase service quotas should be granted only to authorized personnel, not everyone - this violates security best practices.
• D is the opposite of good reliability design; workloads should span multiple Availability Zones to avoid single points of failure.
• E is a fabricated distractor; while planning for capacity in multiple Regions can be good practice, this is not a defined reliability design principle in the framework.

Memory Tip: Think of the reliability pillar as building systems that bounce back and scale smart - recover automatically and stop guessing capacity are both about removing human error and reactive decision-making from your architecture. If an answer suggests limiting redundancy or granting broad access, it's almost certainly wrong.

No community discussion yet for this question.