Question 250
A systems architect notes: An incompatible spare is fitted and the array remains unprotected. Which underlying distinction is most relevant?
Explanation
Correct Answer
The central distinction is that drive replacement alone does not guarantee restored redundancy. For this case the integrator should validate drive eligibility and supported rebuild state. The result to verify is: The array reaches protected healthy state.
Incorrect Answers
The proposed principle is relevant when a firmware update disrupts remote copy while host data stays online. Its governing principle is that replication health is separate from local volume I/O. Here the better diagnosis follows drive replacement alone does not guarantee restored redundancy.
This choice concerns Root-cause analysis of storage failures, for example: A disaster test copies volumes but excludes identity and network dependencies. The current storage issue instead hinges on drive replacement alone does not guarantee restored redundancy. The appropriate evidence is the array reaches protected healthy state.
Although this option is reasonable for 'Hosts report slow I/O while array media response is fast.', it is not the specific dependency in the stem. Its action is correlate SAN link errors with host I/O latency. The stem is resolved more directly by validate drive eligibility and supported rebuild state.