AWS - RDS and Relational DatabasesYou created a read replica but notice it is not receiving updates from the source database. What is a likely cause?AThe source database has no write trafficBThe read replica was created in a different AWS regionCThe read replica is set to multi-AZ deploymentDThe source database is not configured for automated backupsCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand replication requirementsRead replicas require the source database to have automated backups enabled to support replication.Step 2: Analyze the cause of no updatesIf automated backups are off, replication cannot start, so the replica won't receive updates.Final Answer:The source database is not configured for automated backups -> Option DQuick Check:Automated backups must be enabled for replication [OK]Quick Trick: Check if automated backups are enabled on source [OK]Common Mistakes:Assuming region mismatch always blocks replicationConfusing multi-AZ with read replica settingsThinking no write traffic stops replication
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