Which design principles are included in the reliability pillar of the AWS Well-Architected Framework?
(Choose two.)
Automatically recover from failure.
Grant everyone access to increase AWS service quotas.
Stop guessing capacity.
Design applications to run in a single Availability Zone.
Plan to increase AWS service quotas first in a secondary AWS Region.
Explanations:
Automatically recovering from failure is a key principle of the Reliability pillar. It ensures that systems can quickly recover from issues to maintain high availability.
Granting everyone access to increase service quotas is not related to reliability. It is more about security and permissions management.
While it is important to plan capacity, “stop guessing capacity” focuses on efficiency, and it is more of a best practice for the Performance Efficiency pillar rather than Reliability.
Designing applications to run in a single Availability Zone contradicts the Reliability pillar’s emphasis on building resilient architectures across multiple Availability Zones.
Planning to increase AWS service quotas in a secondary AWS Region is not a Reliability principle. Reliability focuses on recovery and redundancy, not service quotas in regions.
I arrange that the answer is:
Automatically recover from failure.
I weigh that the answer is:
Automatically recover from failure.