Question 600
Fictional Thornhill Energy runs the customer onboarding workload at a central campus storage site. While completing migration readiness, the field handoff documents: The team plans a multi-stage controller and shelf conversion without retaining vendor-required fallback modules or a documented stop point. 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: Require recovery-asset and maintenance-window verification before hardware transitions. The recurring exposure to avoid is: The change lacks a supported recovery path if a stage fails acceptance. A continuing effectiveness check is: The change plan lists each stage's success gate and authorized fallback or escalation path.
Incorrect Answers
This option focuses on: Monitor hardware state throughout upgrades and record check results. That can be relevant to module state consistency before software change, but it does not establish the required case-specific result. The current case instead identifies: The change lacks a supported recovery path if a stage fails acceptance. The more directly applicable prevention choice is: Require recovery-asset and maintenance-window verification before hardware transitions.
This alternative concerns: Make multipath path-state evidence a mandatory upgrade go or no-go artifact. It is associated with controller upgrade host path continuity, rather than the question’s determining condition. The case instead turns on: The change lacks a supported recovery path if a stage fails acceptance. The more directly applicable prevention choice is: Require recovery-asset and maintenance-window verification before hardware transitions.
The offered choice addresses: Run a backend path checklist before each capacity expansion. That concerns shelf addition backend path review, rather than the specific failure described here. The deciding issue in this scenario is: The change lacks a supported recovery path if a stage fails acceptance. The more directly applicable prevention choice is: Require recovery-asset and maintenance-window verification before hardware transitions.