Question 440
Fictional Mistvale Logistics runs the fulfillment planning workload at a northern rack row storage site. While completing data-path check, the field handoff documents: Both host-facing FC data links from a FlashArray terminate on the same upstream switch despite a dual-fabric design requirement. 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: Include fabric independence tests in cabling acceptance before application cutover. The recurring exposure to avoid is: The host storage paths share a switch failure domain and do not provide fabric diversity. A continuing effectiveness check is: Host path status proves active alternate routes through separate intended switches.
Incorrect Answers
The offered choice addresses: Record install seating checks for each field-replaceable module. That concerns controller module fully seated, rather than the specific failure described here. The deciding issue in this scenario is: The host storage paths share a switch failure domain and do not provide fabric diversity. The more directly applicable prevention choice is: Include fabric independence tests in cabling acceptance before application cutover.
This option focuses on: Add software version baselines to fleet onboarding prechecks. That can be relevant to pure fusion minimum release preflight, but it does not establish the required case-specific result. The current case instead identifies: The host storage paths share a switch failure domain and do not provide fabric diversity. The more directly applicable prevention choice is: Include fabric independence tests in cabling acceptance before application cutover.
This alternative concerns: Verify mounting hardware and cabinet load ratings before any heavy chassis lift. It is associated with approved rail kit for rack load, rather than the question’s determining condition. The case instead turns on: The host storage paths share a switch failure domain and do not provide fabric diversity. The more directly applicable prevention choice is: Include fabric independence tests in cabling acceptance before application cutover.