Without performing a final update after a disaster, what is the most likely condition of the destination volume?

Without performing a final update after a disaster, what is the most likely condition of the destination volume?

• A. Destination will be missing the latest deltas
• B. Destination will be fully synchronized
• C. Destination will have low latency
• D. Destination will require re-authentication

Answer: (A)

In replication workflows, changes are sent incrementally as deltas to keep the destination current. After a disaster, you need one last update to push any changes that occurred during the outage. If you skip that final update, the destination won’t have those latest deltas and won’t reflect the most recent state. So the destination volume will be missing the latest deltas. The other options don’t fit because being fully synchronized requires that final update to have completed, low latency is about timing rather than data state after recovery, and re-authentication concerns access, not the data refresh status.

In replication workflows, changes are sent incrementally as deltas to keep the destination current. After a disaster, you need one last update to push any changes that occurred during the outage. If you skip that final update, the destination won’t have those latest deltas and won’t reflect the most recent state. So the destination volume will be missing the latest deltas.

The other options don’t fit because being fully synchronized requires that final update to have completed, low latency is about timing rather than data state after recovery, and re-authentication concerns access, not the data refresh status.