Question 900
Fictional Eaglewood Services runs the academic portals workload at a central campus storage site. While completing migration readiness, the field handoff documents: A deployment team calls SafeMode a substitute for application recovery tests and long-term retention governance. The team requires a direct technical explanation and measured acceptance check. Which preventive control most directly reduces this failure risk?
Explanation
Correct Answer
The ongoing safeguard is: Schedule independent recovery testing alongside configured SafeMode protections. The recurring exposure to avoid is: The stakeholder expectation confuses protection controls with a complete recoverability program. A continuing effectiveness check is: A documented protection policy and successful authorized test restoration demonstrate the intended recovery capability.
Incorrect Answers
This option focuses on: Validate FC switch and storage-side aliases and zoning in the as-built plan. That can be relevant to fibre channel fabric connectivity fault, but it does not establish the required case-specific result. The current case instead identifies: The stakeholder expectation confuses protection controls with a complete recoverability program. The more directly applicable prevention choice is: Schedule independent recovery testing alongside configured SafeMode protections.
This alternative concerns: Document Fusion join diagnostics and preflight permissions in the fleet runbook. It is associated with fusion fleet join error root cause, rather than the question’s determining condition. The case instead turns on: The stakeholder expectation confuses protection controls with a complete recoverability program. The more directly applicable prevention choice is: Schedule independent recovery testing alongside configured SafeMode protections.
The offered choice addresses: Include signed hardware-health results in every closeout package. That concerns post-change component health report, rather than the specific failure described here. The deciding issue in this scenario is: The stakeholder expectation confuses protection controls with a complete recoverability program. The more directly applicable prevention choice is: Schedule independent recovery testing alongside configured SafeMode protections.