Both are the Design Principals:
Annotate documentation – Automate the creation of annotated documentation after every build.
Anticipate failure.
So, confused.
AWS Well-Architected Framework:
1. Perform operations as code
2. Make frequent, small, reversible changes
3. Refine operations procedures frequently
4. Anticipate failure
5. Learn from all operational failures
.... Anticipate failure is in there
Anticipate failure: Maximize operational success by driving failure scenarios to understand the workload’s risk profile and its impact on your business outcomes. Test the effectiveness of your procedures and your team’s response against these simulated failures. Make informed decisions to manage open risks that are identified by your testing.
https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/operational-excellence.html
AWS Well-Architected Framework -> Operational Excellence Pillar -> Design Principles
1. Implement observability for actional insights
2. Safely automate where possible
3. Make frequent, small, reversible changes
4. Refine operations procedures frequently
>> 5. Anticipate failure <<
6. Learn from all operational events and metrics
7. Use managed services
Current as of 10-12-24:
https://docs.aws.amazon.com/pdfs/wellarchitected/latest/operational-excellence-pillar/wellarchitected-operational-excellence-pillar.pdf
The design principle included in the Operational Excellence pillar of the AWS Well-Architected Framework is:
A. Create annotated documentation.
This principle emphasizes the importance of maintaining up-to-date, detailed documentation that helps teams operate systems efficiently, understand system behavior, and respond effectively during incidents or changes.
Here's a breakdown of the other options:
B. Anticipate failure: Belongs to the Reliability pillar.
C. Ensure performance efficiency: Belongs to the Performance Efficiency pillar.
D. Optimize costs: Belongs to the Cost Optimization pillar.
Thus, creating annotated documentation is the correct answer for the Operational Excellence pillar.
At first glance, it looks like it could be A or B. But the operational excellence principal recommends annotating documentation, NOT creating annotated documentation - so it has to be B, anticipate failure.
Option B, "Anticipate failure," means planning and designing systems in a way that anticipates and can gracefully handle potential failures. This principle is actually part of the Reliability pillar of the AWS Well-Architected Framework, not the Operational Excellence pillar. The Reliability pillar emphasizes the importance of anticipating failures and automatically healing from them to prevent downtime. It seems there's a misconception among the individuals who are suggesting option B. It's always good to refer back to the official AWS documentation for clarity.
B. Anticipate failure.
"Anticipate failure: Perform 'pre-mortem' exercises to identify potential sources of failure so that they can be removed or mitigated. Test your failure scenarios and validate your understanding of their impact. Test your response procedures to ensure they are effective and that teams are familiar with their process. Set up regular game days to test workload and team responses to simulated events."
https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/operational-excellence.html
This principle emphasizes the importance of designing systems that can withstand and recover from failures, rather than assuming that failures will not occur. By anticipating failure, organizations can proactively implement measures such as redundancy, fault tolerance, and automated recovery to ensure the overall resilience and availability of their systems.
The design principle included in the operational excellence pillar of the AWS Well-Architected Framework that anticipates failure is:
B. Anticipate failure.
This principle recommends designing systems that can withstand failure and that can be quickly recovered from any failure that may occur. It also emphasizes the importance of testing and experimenting to improve system resilience, and the implementation of automated responses to potential failures to minimize downtime and ensure system continuity.
Answer is B, since part of the operational excellence is to anticipate failures by running and managing along with monitoring production workloads. Also continuous improvement is part of Operational Excellence.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
saifee_khan
Highly Voted 2 years, 1 month agoYuval711
Highly Voted 1 year, 8 months agochini786
1 year, 2 months agoHebaXX
Most Recent 3 weeks, 2 days agoawsx
6 months, 1 week agoalexmirmao
7 months agogpcrane
7 months, 2 weeks agojonyc
1 year, 5 months agoDanielki
1 year, 7 months agoPranava_GCP
1 year, 8 months agoKaran997420
1 year, 8 months agoKaran997420
1 year, 8 months agoman5484
1 year, 9 months agoShabz1
1 year, 9 months agosamXXX
1 year, 11 months agoGuru4Cloud
2 years agoalexandercamachop
2 years, 2 months agoSaif93
2 years, 2 months ago