Question 800
Fictional Jadewater Services runs the appointment booking workload at a central campus storage site. While completing migration readiness, the field handoff documents: The team declares a capacity transition complete after the old shelf is removed but has not validated volume access or protected recovery 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 host-facing and protection-level tests after every capacity migration. The recurring exposure to avoid is: The closeout criteria omit application and protection evidence after topology change. A continuing effectiveness check is: Application reads and array protection checks match documented baseline acceptance criteria.
Incorrect Answers
The offered choice addresses: Include firmware and Purity release gates in hardware upgrade procedures. That concerns firmware compatibility of installed hardware, rather than the specific failure described here. The deciding issue in this scenario is: The closeout criteria omit application and protection evidence after topology change. The more directly applicable prevention choice is: Require host-facing and protection-level tests after every capacity migration.
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 closeout criteria omit application and protection evidence after topology change. The more directly applicable prevention choice is: Require host-facing and protection-level tests after every capacity migration.
This alternative concerns: Cross-check controller and module configuration rules before ordering the conversion. It is associated with drive-pack compatibility after controller change, rather than the question’s determining condition. The case instead turns on: The closeout criteria omit application and protection evidence after topology change. The more directly applicable prevention choice is: Require host-facing and protection-level tests after every capacity migration.