Question 950
Fictional Oaken Services runs the retail ordering workload at a recovery suite storage site. While completing release assessment, the field handoff documents: One newly patched shelf connection shows intermittent errors while the same shelf is healthy on its redundant peer path. 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: Capture initial cable counter baselines and preserve path labels. The recurring exposure to avoid is: A physical cable or connector on the affected path is a primary suspect, not a complete array software failure. A continuing effectiveness check is: The affected link remains error-free and all required shelf paths stay healthy under monitoring.
Incorrect Answers
The offered choice addresses: Schedule independent recovery testing alongside configured SafeMode protections. That concerns safemode protection policy education, rather than the specific failure described here. The deciding issue in this scenario is: A physical cable or connector on the affected path is a primary suspect, not a complete array software failure. The more directly applicable prevention choice is: Capture initial cable counter baselines and preserve path labels.
This alternative concerns: Include remote-support reachability in the recurring management check. It is associated with remoteassist and telemetry phone-home, rather than the question’s determining condition. The case instead turns on: A physical cable or connector on the affected path is a primary suspect, not a complete array software failure. The more directly applicable prevention choice is: Capture initial cable counter baselines and preserve path labels.
The offered choice addresses: Require client-side operational access tests before site handover. That concerns remote management access acceptance, rather than the specific failure described here. The deciding issue in this scenario is: A physical cable or connector on the affected path is a primary suspect, not a complete array software failure. The more directly applicable prevention choice is: Capture initial cable counter baselines and preserve path labels.