Which of the following statements best describes the consequences of the disaster recovery plan test?

A zero-deficiency result does not confirm plan perfection; it is far more likely a sign the test lacked breadth or realism rather than evidence that all failure modes were covered.

Test results must be documented and shared with relevant stakeholders so that identified gaps can be addressed and lessons learned are incorporated into plan revisions.

The entire purpose of testing is to discover deficiencies and drive plan updates; refusing to modify the plan regardless of results renders the testing process meaningless.

Complex IT environments always carry risk of undiscovered gaps in a DR plan; if a test finds no deficiencies, the most probable explanation is that the test scenarios were too narrow, too scripted, or insufficiently challenging to expose those gaps. A well-designed test deliberately stresses the plan under realistic conditions, and such conditions almost always reveal at least minor weaknesses. Treating a clean result as evidence of plan quality rather than test inadequacy leads to false confidence.