Question 560
A capacity upgrade plan depends on a spare controller from a different product family. Authorized maintenance rehearsal: The first approved remediation attempt has failed the agreed operational gate. What should the team do BEFORE extending this change?
Explanation
Correct Answer
This is the controlled correction: Pause the rollout, preserve or restore the validated safe state, and investigate again: Reconcile controller family, supported chassis pairing and existing data-pack configuration against upgrade rules. Recheck the acceptance gate: Array reports a supported paired-controller configuration with all modules healthy after upgrade. A failed acceptance gate requires a controlled pause, protected recovery state and renewed evidence before expansion. In this implementation case, A capacity upgrade plan depends on a spare controller from a different product family.
Incorrect Answers
This alternative proposes: Deploy the same unverified change to every related system immediately: Acquire approved same-path controller hardware or revise the supported upgrade path. Expanding the failed change compounds operational risk and loses a supported recovery point. In this implementation case, A capacity upgrade plan depends on a spare controller from a different product family.
This alternative proposes: Mix controller generations without checking firmware and support matrices. Repeating the unsafe proposal is not a valid recovery path. In this implementation case, A capacity upgrade plan depends on a spare controller from a different product family.
This alternative proposes: Treat this tangential observation as proof that the failed gate can be ignored: Verify DNS reverse lookup instead of validating whether the spare controller is supported. A tangential measurement cannot override the failed acceptance criterion. In this implementation case, A capacity upgrade plan depends on a spare controller from a different product family.