Reliability pillar principles in AWS - Mini Project: Build & Apply

Understanding AWS Reliability Pillar Principles

📖 Scenario: You are working as a cloud architect for a small company. Your team wants to build a reliable web application on AWS that stays available and recovers quickly from failures.

🎯 Goal: Learn and apply the core principles of the AWS Reliability Pillar by creating a simple AWS infrastructure setup that follows these principles.

📋 What You'll Learn

Create a dictionary with AWS reliability principles and their descriptions

Add a variable to select a principle to focus on

Write a loop to print the selected principle and its description

Add a final statement confirming the reliability principle focus

💡 Why This Matters

🌍 Real World

Understanding and applying AWS Reliability Pillar principles helps build cloud systems that stay available and recover quickly from problems.

💼 Career

Cloud architects and engineers use these principles daily to design and maintain reliable AWS infrastructure.

1

Create AWS Reliability Principles Dictionary

Create a dictionary called reliability_principles with these exact entries: 'Foundations' mapped to 'Establish a reliable base by setting up AWS accounts and networking', 'Change Management' mapped to 'Manage changes carefully to avoid failures', and 'Failure Management' mapped to 'Prepare for and recover from failures quickly'.

AWS

# Your code here

Hint

Use a Python dictionary with the exact keys and values given.

2

Select a Reliability Principle

Add a variable called selected_principle and set it to the string 'Failure Management'.

AWS

reliability_principles = {
    'Foundations': 'Establish a reliable base by setting up AWS accounts and networking',
    'Change Management': 'Manage changes carefully to avoid failures',
    'Failure Management': 'Prepare for and recover from failures quickly'
}
# Your code here

Hint

Assign the exact string to the variable.

3

Print Selected Principle and Description

Use a for loop with variables principle and description to iterate over reliability_principles.items(). Inside the loop, write an if statement to check if principle equals selected_principle. If yes, assign a variable output to the string combining principle and description separated by a colon and a space.

AWS

reliability_principles = {
    'Foundations': 'Establish a reliable base by setting up AWS accounts and networking',
    'Change Management': 'Manage changes carefully to avoid failures',
    'Failure Management': 'Prepare for and recover from failures quickly'
}

selected_principle = 'Failure Management'

# Your code here

Hint

Use a for loop and an if condition to find the selected principle and create the output string.

4

Confirm Reliability Principle Focus

Add a variable called confirmation and set it to the string 'Focused on AWS Reliability Pillar principle'.

AWS

reliability_principles = {
    'Foundations': 'Establish a reliable base by setting up AWS accounts and networking',
    'Change Management': 'Manage changes carefully to avoid failures',
    'Failure Management': 'Prepare for and recover from failures quickly'
}

selected_principle = 'Failure Management'

for principle, description in reliability_principles.items():
    if principle == selected_principle:
        output = f"{principle}: {description}"

# Your code here

Hint

Assign the exact string to the variable.

Practice

1. What is the main goal of the Reliability pillar in cloud architecture?

easy

A. To reduce the cost of cloud services

B. To keep systems working well and recover quickly from failures

C. To improve the visual design of applications

D. To increase the speed of data processing

Solution

1. Step 1: Understand the purpose of the Reliability pillar

   The Reliability pillar focuses on system uptime and fast recovery from issues.

2. Step 2: Compare options with the pillar's goal

   Only To keep systems working well and recover quickly from failures matches the goal of keeping systems working well and recovering quickly.

3. Final Answer:

   To keep systems working well and recover quickly from failures -> Option B

4. Quick Check:

   Reliability = keep systems working and recover fast [OK]

Hint: Reliability means uptime and fast recovery [OK]

Common Mistakes:

• Confusing reliability with cost savings
• Thinking reliability is about design or speed only
• Ignoring recovery after failure

2. Which AWS service is commonly used to monitor system health and trigger alerts for reliability?

easy

A. Amazon S3

B. Amazon EC2

C. Amazon CloudWatch

D. AWS Lambda

Solution

1. Step 1: Identify monitoring services in AWS

   Amazon CloudWatch is designed to monitor resources and send alerts.

2. Step 2: Eliminate unrelated services

   Amazon S3 is for storage, Lambda for running code, EC2 for servers, so they don't primarily monitor health.

3. Final Answer:

   Amazon CloudWatch -> Option C

4. Quick Check:

   Monitoring and alerts = CloudWatch [OK]

Hint: CloudWatch monitors and alerts in AWS [OK]

Common Mistakes:

• Choosing storage or compute services instead of monitoring
• Confusing Lambda with monitoring
• Not knowing CloudWatch's role

3. Consider this AWS setup: An application uses multiple Availability Zones (AZs) with automatic failover. What is the expected behavior if one AZ fails?

medium

A. The application performance improves in the failed AZ

B. The application stops working until the failed AZ is restored

C. The application data is lost permanently

D. Traffic automatically shifts to healthy AZs to keep the app running

Solution

1. Step 1: Understand multi-AZ and failover

   Using multiple AZs with failover means if one AZ fails, traffic moves to others automatically.

2. Step 2: Analyze each option

   The application stops working until the failed AZ is restored is false because failover prevents downtime. The application data is lost permanently is false because data is replicated. The application performance improves in the failed AZ is illogical as failed AZ cannot improve performance.

3. Final Answer:

   Traffic automatically shifts to healthy AZs to keep the app running -> Option D

4. Quick Check:

   Multi-AZ failover = automatic traffic shift [OK]

Hint: Failover shifts traffic to healthy zones automatically [OK]

Common Mistakes:

• Assuming app stops during AZ failure
• Thinking data is lost without backups
• Believing failed AZ improves performance

4. You have a backup system that runs daily but sometimes misses backups due to network issues. What is the best way to improve reliability?

medium

A. Add monitoring and alerts to detect backup failures immediately

B. Reduce backup frequency to weekly

C. Ignore the missed backups since they are rare

D. Delete old backups to save space

Solution

1. Step 1: Identify the problem with backup reliability

   Missed backups reduce reliability and risk data loss.

2. Step 2: Choose a solution that improves detection and response

   Adding monitoring and alerts helps detect failures quickly and fix them, improving reliability.

3. Final Answer:

   Add monitoring and alerts to detect backup failures immediately -> Option A

4. Quick Check:

   Detect failures fast = add monitoring and alerts [OK]

Hint: Monitor backups to catch failures early [OK]

Common Mistakes:

• Ignoring backup failures
• Reducing backup frequency which lowers reliability
• Deleting backups without ensuring new ones exist

5. A company wants to design a highly reliable web application on AWS. Which combination of strategies best supports the Reliability pillar?

hard

A. Deploy across multiple Availability Zones, automate backups, and enable CloudWatch alarms

B. Use single Availability Zone, manual backups, and no monitoring

C. Use only on-premises servers with no cloud services

D. Deploy in one region with no failover and no testing

Solution

1. Step 1: Identify key reliability strategies

   Reliability requires redundancy (multi-AZ), automated backups, and monitoring with alerts.

2. Step 2: Evaluate each option

   Deploy across multiple Availability Zones, automate backups, and enable CloudWatch alarms includes all key strategies. Options A, C, and D lack redundancy, automation, or monitoring, reducing reliability.

3. Final Answer:

   Deploy across multiple Availability Zones, automate backups, and enable CloudWatch alarms -> Option A

4. Quick Check:

   Multi-AZ + backups + monitoring = high reliability [OK]

Hint: Combine multi-AZ, backups, and monitoring for reliability [OK]

Common Mistakes:

• Choosing single AZ or no monitoring
• Ignoring automation and failover
• Relying only on on-premises servers