It is advised that you watch the Amazon CloudWatch ''_____'' metric (available via the AWS Management Console or Amazon Cloud Watch APIs) carefully and recreate the Read Replica should it fall behind due to replication errors.
You guys are spot on. 'C) Replica Lag' is definitely the answer here. Although, I have to say, I'm a bit surprised they're not asking about 'D) Single Replica' - that would be a real nightmare to deal with if it fell behind! *chuckles*
Ah, I see what they're getting at. Yeah, 'C) Replica Lag' is the way to go. We don't want our Read Replica falling too far behind, otherwise we could lose data or have issues with consistency. Gotta stay on top of that replica lag!
I agree, 'C) Replica Lag' sounds like the right answer. We need to keep an eye on how far behind the Read Replica is, not the actual write lag or the replica itself. Monitoring the replica lag is crucial to ensure your data stays in sync.
Hmm, this question seems a bit tricky. I'm thinking the answer is 'C) Replica Lag'. That makes the most sense to me, since we're talking about monitoring the replication lag on a Read Replica, not the actual write lag or the replica itself.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Mireya
7 days agoRonny
8 days agoRenato
9 days agoKathrine
10 days ago