Question 850
Fictional Thornhill Services runs the compliance reporting workload at a recovery suite storage site. While completing release assessment, the field handoff documents: The array is reachable and reports mapped volumes but the application's host still sees a degraded multipath state. 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 representative host read/write and failover checks at customer handover. The recurring exposure to avoid is: Host-to-array connectivity and supported multipath configuration are not fully verified. A continuing effectiveness check is: The host shows the intended LUNs healthy redundant paths and successful controlled I/O.
Incorrect Answers
This alternative concerns: Monitor clock drift and record time-source configuration at handover. It is associated with clock skew and event log correlation, rather than the question’s determining condition. The case instead turns on: Host-to-array connectivity and supported multipath configuration are not fully verified. The more directly applicable prevention choice is: Require representative host read/write and failover checks at customer handover.
This option focuses on: Document Fusion join diagnostics and preflight permissions in the fleet runbook. That can be relevant to fusion fleet join error root cause, but it does not establish the required case-specific result. The current case instead identifies: Host-to-array connectivity and supported multipath configuration are not fully verified. The more directly applicable prevention choice is: Require representative host read/write and failover checks at customer handover.
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: Host-to-array connectivity and supported multipath configuration are not fully verified. The more directly applicable prevention choice is: Require representative host read/write and failover checks at customer handover.