Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam BDS-C00 Topic 8 Question 87 Discussion

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

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.

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Alana
5 months ago
I see your point, Lenna. Monitoring the Read Replica status is crucial for data integrity in AWS environments.
upvoted 0 times
...
Lenna
6 months ago
I think B) Read Replica is a better choice, as it specifically mentions recreating the Read Replica.
upvoted 0 times
...
Dianne
6 months ago
That's a good point, Yen. Monitoring both write lag and replica lag is important for maintaining data consistency.
upvoted 0 times
...
Yen
6 months ago
I believe it could also be C) Replica Lag, as that would indicate replication errors.
upvoted 0 times
...
Vilma
6 months ago
I agree with Dianne, it makes sense to watch the write lag metric.
upvoted 0 times
...
Dianne
6 months ago
I think the answer is A) Write Lag.
upvoted 0 times
...
Nilsa
7 months ago
I'm not sure about this one. Could it be C) Replica Lag instead?
upvoted 0 times
...
Tequila
7 months ago
I agree with Annette. The answer is B) Read Replica because the question mentions recreating the Read Replica.
upvoted 0 times
...
Annette
7 months ago
I disagree with you Albina. I believe the correct answer is B) Read Replica.
upvoted 0 times
...
Albina
7 months ago
I think the answer is A) Write Lag.
upvoted 0 times
...
Mireya
8 months ago
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*
upvoted 0 times
...
Ronny
8 months ago
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!
upvoted 0 times
...
Renato
8 months ago
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.
upvoted 0 times
...
Kathrine
8 months ago
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
Ronny
8 months ago
C) Replica Lag
upvoted 0 times
...
Roosevelt
8 months ago
D) Single Replica
upvoted 0 times
...
Mollie
8 months ago
C) Replica Lag
upvoted 0 times
...
Leah
8 months ago
B) Read Replica
upvoted 0 times
...
Valentine
8 months ago
A) Write Lag
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77