The remote replication feature is mainly used in disaster recovery and backup scenarios. Which of the following statements about the remote replication feature is correct:
I'm a bit confused about the bandwidth comparison in option C; I thought synchronous was supposed to be more reliable, but does that mean it has lower peak bandwidth?
I remember studying that if the replication link fails, the data on the slave might not be accessible, but I'm not sure if that's the case for all scenarios.
Okay, let's see. The key is understanding the use cases for remote replication, like disaster recovery and backup. I'll focus on that as I read through the options.
I'm going with option A. If the replication link fails suddenly, the slave data will be unavailable, and that's just common sense. Unless, of course, the replication is being done by a team of superheroes.
Haha, option C is hilarious. As if anyone would choose asynchronous replication over synchronous for its 'peak bandwidth'! That's like choosing a Ferrari for its fuel efficiency.
Option B sounds like a good strategy. Being able to map the remote replication slave LUN to the host in advance can definitely help with faster business recovery.
I think option D is the correct answer. Synchronous remote replication is recommended for a disaster recovery solution with RPO=0, as it ensures zero data loss during failover.
Alesia
3 months agoElsa
3 months agoBenton
3 months agoKarma
4 months agoLashonda
4 months agoReita
4 months agoMarya
4 months agoKimberlie
4 months agoKattie
5 months agoKayleigh
5 months agoCandida
5 months agoPrecious
5 months agoAn
5 months agoVicki
5 months agoSilvana
10 months agoCristal
9 months agoChantell
9 months agoSylvie
9 months agoTimothy
10 months agoMila
8 months agoKenda
8 months agoJessenia
10 months agoSherrell
10 months agoShonda
10 months agoDorothy
10 months agoJeannetta
11 months agoReynalda
11 months agoWhitney
11 months ago