Why is disaster recovery testing and why is it required?

• A. Testing DR plans to verify the ability to restore IT services after a disruption
• B. Auditing payroll processes for errors
• C. Evaluating market risk exposure
• D. Training staff on customer service

Answer: (A)

Disaster recovery testing focuses on whether the plans to recover IT systems after a disruption actually work in practice. It isn’t enough to have written procedures; testing puts those procedures to the test—often through simulated outages, failover to backup sites, data restores, and stakeholder communications—to confirm that services can be brought back online within target timeframes and data can be restored to an acceptable point in time. This testing is required to protect the business from extended outages, minimize financial and reputational damage, and verify that recovery objectives (RTOs and RPOs) are achievable. It also helps identify gaps in people, processes, or technology before an real incident occurs and supports compliance with governance and regulatory expectations that mandate exercising continuity plans. Other options focus on payroll controls, market risk, or customer service training, which address different areas and do not assess the ability to restore IT services after a disruption.