Question 640
Fictional Cinder Energy runs the inventory reservations workload at a northern rack row storage site. While completing data-path check, the field handoff documents: The storage team plans a Purity upgrade without confirming host I/O survives a controlled controller failover. 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 multipath path count and failover evidence in upgrade readiness. The recurring exposure to avoid is: The claimed nondisruptive path is unverified at the operating-system multipath layer. A continuing effectiveness check is: A controlled failover check retains expected host data access through supported alternative paths.
Incorrect Answers
This alternative concerns: Validate generation transitions before hardware purchase or scheduling. It is associated with hardware generation support matrix, rather than the question’s determining condition. The case instead turns on: The claimed nondisruptive path is unverified at the operating-system multipath layer. The more directly applicable prevention choice is: Include multipath path count and failover evidence in upgrade readiness.
The offered choice addresses: Maintain an inventory of enabled features against future software changes. That concerns purity feature interoperability review, rather than the specific failure described here. The deciding issue in this scenario is: The claimed nondisruptive path is unverified at the operating-system multipath layer. The more directly applicable prevention choice is: Include multipath path count and failover evidence in upgrade readiness.
This option focuses on: Run a backend path checklist before each capacity expansion. That can be relevant to shelf addition backend path review, but it does not establish the required case-specific result. The current case instead identifies: The claimed nondisruptive path is unverified at the operating-system multipath layer. The more directly applicable prevention choice is: Include multipath path count and failover evidence in upgrade readiness.