Question 580
Fictional Pinnacle Energy runs the partner portal workload at a primary cluster room storage site. While completing change preflight, the field handoff documents: A hardware swap is approved while the current Purity version lacks support for the target controller firmware combination. 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 firmware and Purity release gates in hardware upgrade procedures. The recurring exposure to avoid is: The software and controller firmware baseline is inconsistent with the target upgrade path. A continuing effectiveness check is: System inventory shows the approved Purity level and healthy target controllers after conversion.
Incorrect Answers
This alternative concerns: Include multipath path count and failover evidence in upgrade readiness. It is associated with host multipath failover rehearsal, rather than the question’s determining condition. The case instead turns on: The software and controller firmware baseline is inconsistent with the target upgrade path. The more directly applicable prevention choice is: Include firmware and Purity release gates in hardware upgrade procedures.
The offered choice addresses: Require host-facing and protection-level tests after every capacity migration. That concerns post-consolidation completeness verification, rather than the specific failure described here. The deciding issue in this scenario is: The software and controller firmware baseline is inconsistent with the target upgrade path. The more directly applicable prevention choice is: Include firmware and Purity release gates in hardware upgrade procedures.
This option focuses on: Retain an integrated storage-and-application maintenance approval checklist. That can be relevant to software maintenance change ownership, but it does not establish the required case-specific result. The current case instead identifies: The software and controller firmware baseline is inconsistent with the target upgrade path. The more directly applicable prevention choice is: Include firmware and Purity release gates in hardware upgrade procedures.