Question 270
During a Cisco data center readiness review, engineers observe: An MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete. Which operational guardrail would prevent a similar outage?
Explanation
Correct Answer
This safeguard addresses cisco mds nondisruptive upgrade prechecks: The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. The appropriate prevention is: Require SAN path redundancy and release-matrix signoff before MDS firmware activation. Other subsystem controls would not address the specified recurring failure.
Incorrect Answers
The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. “Validate iSCSI authentication lifecycle and secret rotation with connectivity testing” would address that alternative cause, not the condition in this question: the selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites.
“Review SAN health telemetry and alert thresholds after changes in storage workload patterns” responds to this separate finding: the SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. This question instead needs “Require SAN path redundancy and release-matrix signoff before MDS firmware activation”, so the alternative does not meet the stated condition.
The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. “Include EPLD impact and recovery planning when scheduling MDS component software updates” applies to that separate problem. The observed case is an MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete; choosing this alternative would address the wrong failure mode.