Operational excellence pillar in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of the Operational Excellence pillar in AWS Well-Architected Framework?

To run and monitor systems to deliver business value and to continually improve supporting processes and procedures.

beginner

Name two key design principles of the Operational Excellence pillar.

Perform operations as code and make frequent, small, reversible changes.

beginner

Why is 'automating changes' important in operational excellence?

Automation reduces human error, speeds up processes, and ensures consistency in operations.

beginner

What role does 'monitoring' play in the Operational Excellence pillar?

Monitoring helps detect issues early, understand system behavior, and guide improvements.

beginner

How does the Operational Excellence pillar relate to continuous improvement?

It encourages learning from failures and successes to improve processes and systems over time.

Which of the following is a key practice in the Operational Excellence pillar?

A Avoiding changes to production

B Ignoring system monitoring

C Automating operational procedures

D Manual configuration only

Automating operational procedures helps reduce errors and improve efficiency, which is a key practice in operational excellence.

What does 'perform operations as code' mean in operational excellence?

A Manual troubleshooting

B Writing code only for applications

C Avoiding automation

D Managing operations through scripts and automation

Performing operations as code means using scripts and automation to manage operations, improving repeatability and reliability.

Why should changes be small and reversible in operational excellence?

A To make troubleshooting easier and reduce risk

B To delay deployments

C To increase complexity

D To avoid documentation

Small, reversible changes make it easier to find and fix problems quickly, reducing risk.

Which AWS service can help with monitoring for operational excellence?

A AWS Lambda

B Amazon CloudWatch

C Amazon S3

D Amazon EC2

Amazon CloudWatch collects and tracks metrics, logs, and events to monitor AWS resources and applications.

Continuous improvement in operational excellence means:

A Learning from failures and successes to improve

B Avoiding automation

C Stopping changes after deployment

D Ignoring feedback

Continuous improvement involves learning from both failures and successes to enhance processes and systems.

Explain the key practices that support the Operational Excellence pillar in AWS.

Think about how AWS encourages managing operations and improving them over time.

Describe how monitoring and automation contribute to operational excellence.

Consider the benefits of watching systems and using scripts to manage tasks.

Practice

1. What is the main goal of the Operational Excellence pillar in AWS Well-Architected Framework?

easy

A. To optimize costs and reduce spending

B. To secure data and control access to resources

C. To improve and automate processes for better system reliability and efficiency

D. To design systems for high availability and fault tolerance

Solution

1. Step 1: Understand the focus of Operational Excellence

   Operational Excellence focuses on running and monitoring systems to deliver business value and continually improve processes.

2. Step 2: Differentiate from other pillars

   Security focuses on protection, Cost Optimization on spending, Reliability on availability. Operational Excellence is about process improvement and automation.

3. Final Answer:

   To improve and automate processes for better system reliability and efficiency -> Option C

4. Quick Check:

   Operational Excellence = process improvement and automation [OK]

Hint: Operational Excellence = improve processes + automation [OK]

Common Mistakes:

• Confusing Operational Excellence with Security or Cost Optimization
• Thinking it only covers system uptime
• Ignoring the importance of continuous improvement

2. Which AWS service is primarily used to automate operational tasks and workflows?

easy

A. AWS Systems Manager

B. Amazon S3

C. Amazon RDS

D. AWS CloudTrail

Solution

1. Step 1: Identify services for automation

   AWS Systems Manager provides automation for operational tasks like patching, configuration, and runbook execution.

2. Step 2: Exclude unrelated services

   Amazon S3 is storage, Amazon RDS is database, CloudTrail is for logging API calls, not automation.

3. Final Answer:

   AWS Systems Manager -> Option A

4. Quick Check:

   Automation service = AWS Systems Manager [OK]

Hint: Automation in AWS? Think Systems Manager [OK]

Common Mistakes:

• Choosing storage or database services for automation
• Confusing logging services with automation
• Not knowing AWS Systems Manager capabilities

3. Consider this AWS CloudWatch alarm configuration snippet:

{
  "AlarmName": "HighCPU",
  "MetricName": "CPUUtilization",
  "Namespace": "AWS/EC2",
  "Statistic": "Average",
  "Period": 300,
  "EvaluationPeriods": 2,
  "Threshold": 80,
  "ComparisonOperator": "GreaterThanThreshold"
}

What happens when the average CPU utilization exceeds 80% for 10 minutes?

medium

A. The alarm triggers after two consecutive 5-minute periods above 80%

B. The alarm triggers immediately when CPU exceeds 80%

C. The alarm never triggers because threshold is too high

D. The alarm triggers only if CPU stays above 80% for 30 minutes

Solution

1. Step 1: Understand EvaluationPeriods and Period

   The alarm evaluates CPU utilization every 5 minutes (Period=300 seconds) and requires 2 consecutive periods above threshold.

2. Step 2: Calculate total time to trigger

   2 periods x 5 minutes = 10 minutes of CPU > 80% triggers the alarm.

3. Final Answer:

   The alarm triggers after two consecutive 5-minute periods above 80% -> Option A

4. Quick Check:

   EvaluationPeriods x Period = trigger time [OK]

Hint: Alarm triggers after EvaluationPeriods x Period time above threshold [OK]

Common Mistakes:

• Thinking alarm triggers immediately on threshold breach
• Ignoring EvaluationPeriods count
• Misunderstanding Period as total time

4. You have an AWS Lambda function that fails intermittently. Which step helps you debug and improve operational excellence?

medium

A. Remove error handling code to simplify the function

B. Enable detailed CloudWatch Logs and set up alarms on error metrics

C. Manually restart the Lambda function every hour

D. Disable all logging to improve performance

Solution

1. Step 1: Use monitoring to detect issues

   Enabling detailed logs and alarms helps identify failure causes and patterns.

2. Step 2: Avoid harmful practices

   Disabling logs hides problems, manual restarts are inefficient, removing error handling worsens reliability.

3. Final Answer:

   Enable detailed CloudWatch Logs and set up alarms on error metrics -> Option B

4. Quick Check:

   Monitoring + alarms = better debugging [OK]

Hint: Use logs and alarms to find and fix errors [OK]

Common Mistakes:

• Turning off logs to 'speed up' functions
• Ignoring automated monitoring tools
• Relying on manual fixes instead of automation

5. A company wants to improve operational excellence by automating incident response for their EC2 fleet. Which combination of AWS services best achieves this?

hard

A. Amazon RDS + Amazon DynamoDB + AWS Elastic Beanstalk

B. Amazon S3 + AWS Glue + Amazon Athena

C. AWS IAM + AWS KMS + AWS Shield

D. AWS Systems Manager Automation + Amazon CloudWatch Events + AWS Lambda

Solution

1. Step 1: Identify services for automation and event-driven response

   AWS Systems Manager Automation runs operational tasks, CloudWatch Events detect incidents, Lambda executes custom code.

2. Step 2: Exclude unrelated services

   S3, Glue, Athena are for data analytics; IAM, KMS, Shield focus on security; RDS, DynamoDB, Elastic Beanstalk are for databases and app deployment.

3. Final Answer:

   AWS Systems Manager Automation + Amazon CloudWatch Events + AWS Lambda -> Option D

4. Quick Check:

   Automation + event detection + code execution = incident response [OK]

Hint: Combine automation, events, and Lambda for incident response [OK]

Common Mistakes:

• Choosing unrelated data or security services
• Not combining event detection with automation
• Ignoring Lambda's role in custom logic