AWS - RDS and Relational DatabasesAfter launching a read replica, it does not respond to read queries. Which misconfiguration is the most probable cause?AThe primary database is set to multi-AZ deploymentBThe read replica's security group does not allow inbound traffic from the applicationCThe read replica is in a different AWS region than the primaryDThe read replica has automated backups disabledCheck Answer
Step-by-Step SolutionSolution:Step 1: Check connectivityIf the read replica does not respond, network access is a common issue.Step 2: Verify security groupsThe replica's security group must allow inbound traffic from the application or clients.Final Answer:The read replica's security group does not allow inbound traffic from the application -> Option BQuick Check:Multi-AZ or backups do not block reads; region difference affects latency [OK]Quick Trick: Check security group inbound rules for read replica [OK]Common Mistakes:Assuming multi-AZ disables reads on replicasIgnoring network access controlsConfusing backup settings with read availability
Master "RDS and Relational Databases" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - REST API creation - Quiz 10hard Auto Scaling - Minimum, maximum, and desired capacity - Quiz 3easy Auto Scaling - Predictive scaling overview - Quiz 3easy Auto Scaling - Minimum, maximum, and desired capacity - Quiz 11easy CloudWatch - CloudWatch metrics - Quiz 4medium Elastic Load Balancing - ALB vs NLB decision - Quiz 8hard Elastic Load Balancing - ALB vs NLB decision - Quiz 15hard RDS and Relational Databases - Launching an RDS instance - Quiz 9hard RDS and Relational Databases - Multi-AZ deployment for high availability - Quiz 8hard SNS and SQS - Standard vs FIFO queues - Quiz 4medium