AWS - RDS and Relational Databases
You want to minimize AWS RDS costs for a development environment that requires low latency and high availability. Which combination is best?
You want to minimize AWS RDS costs for a development environment that requires low latency and high availability. Which combination is best?
hard📝 Best Practice Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Identify cost and availability needs
Low latency and high availability require Multi-AZ deployment and sufficient instance size.Step 2: Evaluate storage and instance size
gp3 storage is cost-effective and performant; small instance reduces cost while Multi-AZ ensures availability.Step 3: Compare options
Use a small instance with Multi-AZ deployment and gp3 storage balances cost (small instance), availability (Multi-AZ), and performance (gp3 storage).Final Answer:
Use a small instance with Multi-AZ deployment and gp3 storage -> Option AQuick Check:
Small + Multi-AZ + gp3 = cost-effective high availability [OK]
Quick Trick: Multi-AZ + small instance + gp3 balances cost and availability [OK]
Common Mistakes:
- Choosing Magnetic storage which is slower and deprecated
- Ignoring Multi-AZ for high availability
- Picking large instance unnecessarily increasing cost
Master "RDS and Relational Databases" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes