AWS - RDS and Relational Databases
You want to design a highly available web application using AWS RDS with Multi-AZ and EC2 instances. Which architecture best ensures minimal downtime during an AZ failure?
You want to design a highly available web application using AWS RDS with Multi-AZ and EC2 instances. Which architecture best ensures minimal downtime during an AZ failure?
hard📝 Best Practice Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Understand high availability for both compute and database
To avoid downtime, both EC2 and RDS should be spread across AZs.Step 2: Analyze options
Deploy EC2 instances across multiple AZs and enable RDS Multi-AZ. deploys EC2 instances in multiple AZs and enables RDS Multi-AZ, ensuring failover for both layers.Step 3: Reject other options
Configurations with EC2 instances in a single AZ risk downtime if that AZ fails. Configurations with EC2 across multiple AZs but RDS Multi-AZ disabled risk database downtime.Final Answer:
Deploy EC2 instances across multiple AZs and enable RDS Multi-AZ. -> Option BQuick Check:
Multi-AZ + multi-AZ EC2 = minimal downtime [OK]
Quick Trick: Spread both EC2 and RDS across AZs for full availability [OK]
Common Mistakes:
MISTAKES- Deploying EC2 in one AZ only
- Disabling RDS Multi-AZ
- Ignoring compute layer availability
Master "RDS and Relational Databases" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes