AWS - RDS and Relational DatabasesAn RDS Multi-AZ instance fails to failover during a primary AZ outage. You find the standby is unhealthy. What should you do?ACheck and fix standby instance health or recreate Multi-AZ setupBReboot the primary instance onlyCDisable Multi-AZ to fix the issueDSwitch to a read replica for failoverCheck Answer
Step-by-Step SolutionSolution:Step 1: Diagnose standby healthFailover depends on a healthy standby; if unhealthy, fix or recreate Multi-AZ setup.Step 2: Avoid incorrect fixesRebooting primary won't help standby; disabling Multi-AZ removes failover; read replicas differ from Multi-AZ.Final Answer:Check and fix standby instance health or recreate Multi-AZ setup -> Option AQuick Check:Healthy standby needed for failover [OK]Quick Trick: Standby health is key for failover [OK]Common Mistakes:Rebooting primary onlyDisabling Multi-AZ instead of fixingConfusing read replicas with Multi-AZ
Master "RDS and Relational Databases" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - API deployment and stages - Quiz 6medium API Gateway - REST API creation - Quiz 3easy API Gateway - Why API Gateway matters - Quiz 6medium AWS Lambda - Lambda execution model - Quiz 14medium Auto Scaling - Predictive scaling overview - Quiz 3easy Auto Scaling - Auto Scaling with ELB integration - Quiz 3easy Auto Scaling - Scaling policies (target tracking, step, simple) - Quiz 6medium CloudWatch - Log groups and log streams - Quiz 14medium Elastic Load Balancing - Cross-zone load balancing - Quiz 9hard RDS and Relational Databases - Why managed databases matter - Quiz 15hard