Question 490
Fictional Willowby Logistics runs the reservation systems workload at a remote operations wing storage site. While completing hardware modernization, the field handoff documents: An in-service controller upgrade is planned while host multipath testing shows no viable alternate path through the peer controller. 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: Make multipath path-state evidence a mandatory upgrade go or no-go artifact. The recurring exposure to avoid is: The proposed nondisruptive upgrade lacks verified host path redundancy. A continuing effectiveness check is: A controlled path test demonstrates host I/O continues when one supported controller path is unavailable.
Incorrect Answers
This alternative concerns: Require recovery-asset and maintenance-window verification before hardware transitions. It is associated with rollback and recovery hardware readiness, rather than the question’s determining condition. The case instead turns on: The proposed nondisruptive upgrade lacks verified host path redundancy. The more directly applicable prevention choice is: Make multipath path-state evidence a mandatory upgrade go or no-go artifact.
This option focuses on: Include replication health and remote-site owners in change approval. That can be relevant to replication health before upgrade, but it does not establish the required case-specific result. The current case instead identifies: The proposed nondisruptive upgrade lacks verified host path redundancy. The more directly applicable prevention choice is: Make multipath path-state evidence a mandatory upgrade go or no-go artifact.
This alternative concerns: Prevalidate elevation and account expiration before the maintenance window. It is associated with privileged upgrade access authorization, rather than the question’s determining condition. The case instead turns on: The proposed nondisruptive upgrade lacks verified host path redundancy. The more directly applicable prevention choice is: Make multipath path-state evidence a mandatory upgrade go or no-go artifact.