Question 790
During a storage solution review, this situation emerges: An application team documents the age of restored data but does not time the recovery. What is the governing behavior?
Explanation
Correct Answer
This behavior follows from recovery-point and recovery-time objectives measure distinct aspects of recoverability. The corresponding corrective work is record both RPO and RTO measurements and remediation actions for every drill. The expected evidence is: The test report shows data age and service-restoration time within agreed limits.
Incorrect Answers
This addresses a different storage problem, such as: A replicated dataset is assumed recoverable because the dashboard reports synchronized. That problem points toward perform a controlled application restore or failover test with integrity verification. The present incident instead requires record both RPO and RTO measurements and remediation actions for every drill. and validation that the test report shows data age and service-restoration time within agreed limits.
The proposed principle is relevant when a recovery playbook assumes its standby compute system has access to the protected LUNs. Its governing principle is that disaster recovery requires an executable complete destination architecture. Here the better diagnosis follows recovery-point and recovery-time objectives measure distinct aspects of recoverability.
That alternative could help with the separate condition: A new thin provisioned datastore is created but capacity alerts remain at disabled defaults. It would be checked by a controlled growth test reaches the warning threshold before host write failure. For the described case, the necessary correction is record both RPO and RTO measurements and remediation actions for every drill.