AWS - RDS and Relational Databases
For a fault-tolerant web application using AWS RDS Multi-AZ and EC2, which design best minimizes downtime during an AZ outage?
For a fault-tolerant web application using AWS RDS Multi-AZ and EC2, which design best minimizes downtime during an AZ outage?
hard📝 Architecture Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Understand high availability requirements
Minimizing downtime requires both compute and database layers to be resilient to AZ failures.Step 2: Evaluate options
Deploy EC2 instances in multiple AZs behind an Elastic Load Balancer and use RDS Multi-AZ for database failover deploys EC2 instances across multiple AZs with a load balancer and uses RDS Multi-AZ, providing fault tolerance at both layers. Deploy EC2 instances in a single AZ with RDS Multi-AZ enabled for database redundancy limits EC2 to one AZ, risking compute failure. Use a single EC2 instance with RDS read replicas in multiple AZs uses read replicas which do not provide automatic failover. Deploy EC2 instances in multiple AZs but use a single-AZ RDS instance has multi-AZ EC2 but single-AZ RDS, risking database downtime.Final Answer:
Deploy EC2 instances in multiple AZs behind an Elastic Load Balancer and use RDS Multi-AZ for database failover -> Option AQuick Check:
Multi-AZ + multi-AZ EC2 with ELB ensures minimal downtime [OK]
Quick Trick: Both compute and database must be multi-AZ for high availability [OK]
Common Mistakes:
- Assuming RDS Multi-AZ alone ensures full app availability
- Using single AZ for EC2 instances
- Confusing read replicas with failover solutions
Master "RDS and Relational Databases" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes