Question 560
Fictional Linden Energy runs the manufacturing planning workload at a metro data hall storage site. While completing service continuity review, the field handoff documents: An expansion shelf is mounted but additional capacity is unavailable because the new shelf path is only connected to one required backend leg. 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: Run a backend path checklist before each capacity expansion. The recurring exposure to avoid is: The storage shelf does not have the supported complete backend connectivity. A continuing effectiveness check is: The array reports all required shelf paths and components online with no missing-path alerts.
Incorrect Answers
The offered choice addresses: Plan capacity conversions using realistic data movement and onsite staging assumptions. That concerns multi-visit transition sequencing, rather than the specific failure described here. The deciding issue in this scenario is: The storage shelf does not have the supported complete backend connectivity. The more directly applicable prevention choice is: Run a backend path checklist before each capacity expansion.
This option focuses on: Include firmware and Purity release gates in hardware upgrade procedures. That can be relevant to firmware compatibility of installed hardware, but it does not establish the required case-specific result. The current case instead identifies: The storage shelf does not have the supported complete backend connectivity. The more directly applicable prevention choice is: Run a backend path checklist before each capacity expansion.
This alternative concerns: Publish raw effective and protected usable capacity separately in planning sheets. It is associated with usable versus raw capacity accounting, rather than the question’s determining condition. The case instead turns on: The storage shelf does not have the supported complete backend connectivity. The more directly applicable prevention choice is: Run a backend path checklist before each capacity expansion.