Disaster recovery plan feature: restoration

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. In a disaster recovery plan, which should be restored first after a disruption?

A Whichever systems are quickest to restore

B Critical systems that the business cannot operate without

2. Which statement describes restoration correctly?

A Bringing systems and data back into use from backups

B Copying live data onto a new backup drive

3. What does the recovery time objective (RTO) measure?

A How quickly a system must be restored after a disruption

B How much recent data can be lost

4. A business backs up nightly at 11 pm and fails at 3 pm the next day. What is the recovery point?

A 11 pm, the time of the last backup

B 3 pm, the time of the failure

5. Which backup schedule gives a smaller recovery point (less data loss)?

A Backing up once a week

B Backing up every hour

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1restoration		Arestore_order = ["payment system", "customer database", "staff intranet"]
2RTO = 4 hours		BThe ordered process of bringing systems and data back into use from backups after a disruption
3Restore the most critical systems first, then less important ones		CRecovery point objective is mixed up with backup frequency. The RPO is the maximum data loss allowed, so frequent backups mean a small RPO, such as 15 minutes, not 24 hours.
4Check the restored data is correct and complete before returning to normal use		DRecovery time objective: the longest acceptable time to get a system working again after a disruption
5RPO = 24 hours (backups taken every 15 minutes)		Everify(restored_data, backup_checksum)
6restore(all_systems); verify(); restore(payment_system)		FThe critical payment system is restored last and verification happens too early. Critical systems should be restored first and data checked after restoring.

Definitions

restoration

Fill in the Blanks

Complete each line of code by filling in the missing parts.

_______ payrollDB FROM latestBackup

RESTORE ________ systems FIRST RESTORE other systems NEXT VERIFY restored data

IF restoreHours <= ___ THEN PRINT "Within recovery time" END IF

IF hoursSinceBackup <= ___ THEN PRINT "Data loss acceptable" END IF

IF HASH(restoredData) _ backupHash THEN PRINT "Restored data verified" END IF

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A 1. Restore payroll database

B 2. Restore email server

C 3. Skip checking restored data

Question 2

A RTO = 2 hours

B RPO = 1 hour

C Backup runs every hour

D RTO is how much data we lose

Question 3

A Tier 1: payments, customer DB

B Tier 2: email, intranet

C Restore Tier 2 first

Question 4

A RESTORE orders FROM backup

B hash = HASH(orders)

C IF hash != saved_hash: PASS

Question 5

A 1. Assess damage

B 2. Restore Tier 1 systems

C 3. Restore Tier 2 systems

D 4. Reopen, then verify data

Answer Key

Disaster recovery plan feature: restoration

Section A: Quick Questions

B — Critical systems that the business cannot operate without

A — Bringing systems and data back into use from backups

A — How quickly a system must be restored after a disruption

A — 11 pm, the time of the last backup

B — Backing up every hour

Section B: Match the Pairs

restoration → The ordered process of bringing systems and data back into use from backups after a disruption

RTO = 4 hours → Recovery time objective: the longest acceptable time to get a system working again after a disruption

Restore the most critical systems first, then less important ones → restore_order = ["payment system", "customer database", "staff intranet"]

Check the restored data is correct and complete before returning to normal use → verify(restored_data, backup_checksum)

RPO = 24 hours (backups taken every 15 minutes) → Recovery point objective is mixed up with backup frequency. The RPO is the maximum data loss allowed, so frequent backups mean a small RPO, such as 15 minutes, not 24 hours.

restore(all_systems); verify(); restore(payment_system) → The critical payment system is restored last and verification happens too early. Critical systems should be restored first and data checked after restoring.

Section C: Definitions

restoration — The ordered process of bringing systems and data back into use from backups after a disruption, restoring critical systems first and then checking the restored data is correct and complete.

Section D: Fill in the Blanks

RESTORE payrollDB FROM latestBackup

RESTORE critical systems FIRST
RESTORE other systems NEXT
VERIFY restored data

IF restoreHours <= RTO THEN
    PRINT "Within recovery time"
END IF

IF hoursSinceBackup <= RPO THEN
    PRINT "Data loss acceptable"
END IF

IF HASH(restoredData) = backupHash THEN
    PRINT "Restored data verified"
END IF

Section E: Spot the Error

C — Restoration is not finished when the data is copied back. The restored data must be verified to confirm it is correct and complete. Line 3 should be '3. Verify restored data'.

D — The recovery time objective (RTO) is how long the organisation can take to restore systems. How much data can be lost is the recovery point objective (RPO). Line 4 should say RTO is time allowed to restore.

C — Critical systems (Tier 1) must be restored first so the business can operate again. Less important systems such as email and the intranet come later. Line 3 should be 'Restore Tier 1 first'.

C — A restored file passes verification only when its hash matches the saved hash taken before the disruption. A mismatch means the data changed or is corrupt. Line 3 should use = not !=.

D — Restored data must be verified before users rely on it. Reopening first risks people using incorrect or incomplete data. Line 4 should be '4. Verify data, then reopen'.