1. National Institute of Standards and Technology (NIST) Special Publication 800-34 Rev. 1, "Contingency Planning Guide for Federal Information Systems."
Section 5.3, "Contingency Plan Testing," Page 49: This section details different types of tests. It describes "Functional Exercises" as tests that "are designed to test the recovery of a specific system at the alternate site... to determine whether the system can be recovered within the time specified in the plan." This aligns directly with the methodology described in option B as the proper way to validate an RTO.
2. HPE White Paper, "Business continuity for HPE Nimble Storage" (Document ID: a00059683enw, Published: May 2019).
Page 10, Section "Testing the disaster recovery plan": The document states, "The only way to be certain that a DR plan will work is to test it... A full test involves failing over the applications to the DR site, verifying that they are working correctly, and then failing them back to the production site." This supports the principle of a full, practical failover test to validate recovery capabilities.
3. HPE Technical White Paper, "HPE 3PAR Remote Copy" (Document ID: 4AA4-8869ENW, Published: August 2016).
Page 25, Section "Disaster recovery testing": This section emphasizes the importance of non-disruptive testing of DR plans. It states, "It is a best practice to periodically test the DR plan to ensure that the RTO and RPO can be met." This reinforces that meeting the RTO is a primary goal of DR testing, which requires a practical failover exercise.