Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon BDS-C00 Exam - Topic 5 Question 126 Discussion

My Read Replica appears "stuck" after a Multi-AZ failover and is unable to obtain or apply updates from the source DB Instance. What do I do?
A) You will need to delete the Read Replica and create a new one to replace it.
B) You will need to disassociate the DB Engine and re associate it.
C) The instance should be deployed to Single AZ and then moved to Multi- AZ once again
D) You will need to delete the DB Instance and create a new one to replace it.

Amazon BDS-C00 Exam - Topic 5 Question 126 Discussion

Actual exam question for Amazon's BDS-C00 exam
Question #: 126
Topic #: 5
[All BDS-C00 Questions]

My Read Replica appears "stuck" after a Multi-AZ failover and is unable to obtain or apply updates from the source DB Instance. What do I do?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Dorothy at Jan 28, 2026, 09:50 AM

Limited Time Offer

25%

Off

Get Premium BDS-C00 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Amber
24 days ago
Really? A reboot? That seems too simple...
upvoted 0 times
...
Ozell
29 days ago
Are you sure the failover was successful?
upvoted 0 times
...
Emilio
1 month ago
I had this happen once, a reboot fixed it!
upvoted 0 times
...
Elke
1 month ago
Sounds like a network issue to me.
upvoted 0 times
...
Charisse
1 month ago
Check the replication status first.
upvoted 0 times
...
Charlesetta
2 months ago
I heard that if you stare at the Read Replica long enough, it might just start working again. Worth a shot!
upvoted 0 times
...
Royal
2 months ago
Wouldn't it be better to try resetting the Read Replica first before doing anything drastic?
upvoted 0 times
...
Jaime
2 months ago
Ah, the classic "Read Replica stuck" problem. Time to break out the duct tape and WD-40!
upvoted 0 times
...
Jovita
2 months ago
Hmm, I'm not sure about that. Wouldn't it be better to contact AWS support and let them handle it?
upvoted 0 times
...
Lavonna
2 months ago
I think the answer is to manually promote the Read Replica to become the new primary instance.
upvoted 0 times
...
Iesha
3 months ago
I think I read that sometimes you need to promote the read replica if it’s stuck for too long, but I’m not 100% sure how that affects data consistency.
upvoted 0 times
...
Tijuana
3 months ago
I’m a bit confused about the Multi-AZ setup. Should I be looking at the primary instance's logs for errors?
upvoted 0 times
...
Rebecka
3 months ago
If I recall correctly, there might be a way to manually restart the replication process. I practiced a similar question on this last week.
upvoted 0 times
...
Vivan
4 months ago
I think I remember something about checking the replication status in the AWS console? But I'm not entirely sure how to do that.
upvoted 0 times
...
Rebbecca
4 months ago
Ah, I remember learning about this in class. Let me think through the key things to look for and the potential solutions. I've got a good strategy for tackling this.
upvoted 0 times
...
Val
4 months ago
No problem, I've got this. I'll start by checking the status of the read replica and the source DB instance, then follow the recommended steps to get it back in sync.
upvoted 0 times
...
Valentin
4 months ago
I'm a bit unsure about this one. I'll need to review the material on managing read replicas and failovers to make sure I understand the right troubleshooting process.
upvoted 0 times
...
Haydee
4 months ago
Okay, I've seen this issue before. I think I know the right approach, but I'll double-check my notes just to be sure.
upvoted 0 times
...
Gabriele
5 months ago
Hmm, this seems like a tricky one. I'll need to think through the steps carefully to make sure I don't miss anything.
upvoted 0 times
...

Save Cancel