Okay, gotta remember the differences between Sync and StrictSync. A and D make sense - the key is ensuring the primary and secondary are identical, no matter what.
User 1: A) In Sync mode, the application I/O fails if the write to the secondary storage is not completed, thereby ensuring that the primary and secondary storage are identical.
Haha, imagine if the app could just keep writing to the primary even if the secondary was down. That would be like trying to save your work on a broken USB drive!
D) In StrictSync mode, the application I/O fails if the write to the secondary storage is not completed, thereby ensuring that the primary and secondary storage are identical.
A) In Sync mode, the application I/O fails if the write to the secondary storage is not completed, thereby ensuring that the primary and secondary storage are identical.
Hmm, I'm a bit unsure about C. Doesn't that go against the whole purpose of Sync replication? The app should not be able to continue writing if the secondary write fails.
A and D seem to be the correct answers. In Sync mode, the app I/O fails if the secondary write isn't completed, ensuring data integrity. In StrictSync, the same thing happens, again maintaining data consistency.
D) In StrictSync mode, the application I/O fails if the write to the secondary storage is not completed, thereby ensuring that the primary and secondary storage are identical.
A) In Sync mode, the application I/O fails if the write to the secondary storage is not completed, thereby ensuring that the primary and secondary storage are identical.
I disagree, I believe B is true because it says in StrictSync mode, the application can continue writing to the primary storage even if the write to the secondary storage is not completed.
Ceola
29 days agoIvory
8 days agoStefanie
1 months agoLeonard
23 days agoClaudio
24 days agoSantos
30 days agoBernardine
1 months agoYuette
2 months agoJodi
21 days agoAudra
1 months agoEliz
2 months agoJudy
2 months agoEliz
2 months ago