Which components define a backup and disaster recovery plan for critical systems in MIPC?

• A. Only back up once a year.
• B. Define RPO/RTO, classify data, implement regular incremental/differential backups, off-site or cloud replication, periodic DR drills, tested restore procedures, and clear runbooks with roles.
• C. DR plans are unnecessary.
• D. Backups should be stored on the same server.

Answer: (B)

This question centers on what makes a robust backup and disaster recovery plan for critical systems. The best answer starts by defining recovery targets: RPO (how much data loss is acceptable) and RTO (how quickly systems must be restored). These goals drive every other aspect of the plan. Next, classify data so you know which information deserves the strongest protection and fastest recovery, ensuring critical systems get priority.

A solid plan uses regular backups that balance coverage and practicality, typically including incremental or differential backups alongside periodic full backups. Off-site or cloud replication is essential to survive local failures or disasters. Periodic disaster recovery drills test your readiness, revealing gaps before a real incident, while tested restore procedures prove you can actually recover within the required time and data loss limits. Clear runbooks with defined roles ensure everyone knows what to do and when, reducing delays and errors during an incident.

By contrast, backing up only once a year leaves you vulnerable to significant data loss; DR plans that aren’t practiced offer little confidence in recovery; and storing backups on the same server creates a single point of failure.