Question

Difficulty: MediumBusiness Continuity and Disaster Recovery

An enterprise network storage server experiences severe database corruption on a Thursday morning. To recover system functionality with zero data loss, the network team must execute a restoration plan. The organization's backup policy includes a weekly full backup performed every Sunday at 00:00, daily differential backups taken at 23:00, and continuous transaction logging. In what correct chronological order should the administrator execute the restoration steps?

  1. 1Restore the baseline full backup image from Sunday.
  2. 2Apply the single most recent differential backup from Wednesday evening.
  3. 3Replay the uncommitted transaction logs generated between Wednesday night and Thursday morning.
  4. 4Perform data integrity validation and re-enable operational network access.

Answer

The correct restoration sequence starts by restoring the full backup from Sunday, applying the latest differential backup from Wednesday night, replaying the transaction logs up to the moment of failure on Thursday morning, and completing post-restoration data integrity checks before reconnecting network services.
When executing a disaster recovery plan involving full and differential backups, the baseline full backup (Sunday) must be restored first. Next, because differential backups accumulate all changes since the previous full backup, only the latest differential backup (Wednesday) needs to be applied. Point-in-time transaction logs are then replayed to bring data up to the exact moment of failure on Thursday morning. Finally, verification is performed before resuming production network operations.

Step-by-Step Solution

1
Restore the Sunday full backup image
Re-establishes the core operating environment and data baseline as of Sunday 00:00.
Full backups contain the complete data set and serve as the essential baseline required for any subsequent differential or incremental restoration.
2
Apply the Wednesday night differential backup set
Updates all modified data cumulatively from Sunday 00:00 to Wednesday 23:00.
Because differential backups record all cumulative changes made since the last full backup, only the most recent differential backup (Wednesday) is needed.
3
Replay transaction logs recorded after Wednesday 23:00
Recovers granular data deltas up to the exact point of failure on Thursday morning.
Transaction logs capture point-in-time transactions occurring after the latest differential backup to achieve a near-zero Recovery Point Objective (RPO).
4
Validate data integrity and reinstate production network connectivity
Confirms system health and restores service availability safely.
System state validation prevents serving corrupted or inconsistent data to clients when operational connectivity is restored.

Key Concept

Full and Differential Backup Restoration Sequence
Estimated Time:1m 30s
Rate this question