Question 60
At the Lakehaven digital services storage team, administrators schedule a cluster upgrade before validating health and supported upgrade paths. Which ongoing control best prevents this failure from recurring?
Explanation
Correct Answer
The continuing safeguard is to repeat readiness checks after firmware cluster or application changes. It helps avoid the original condition: existing cluster issues or unsupported upgrade paths can compromise an otherwise planned upgrade. This result addresses the stated challenge at the Lakehaven digital services storage team.
Incorrect Answers
“Review cluster limit and compatibility requirements at each expansion phase” checks a different ongoing risk rather than the reported failure: at the Lakehaven digital services storage team, administrators schedule a cluster upgrade before validating health and supported upgrade paths. The relevant mechanism is existing cluster issues or unsupported upgrade paths can compromise an otherwise planned upgrade, the required evidence must show that the upgrade readiness report shows required checks passing before the change begins. The directly matched preventive control is “Repeat readiness checks after firmware cluster or application changes”.
Monitor tiering and recall activity after changing application access patterns is not the primary recurring safeguard for this problem. The team should repeat readiness checks after firmware cluster or application changes. For the Lakehaven digital services storage team, the direct corrective action is to run NetApp-supported upgrade readiness checks and confirm version compatibility and health prerequisites.
“Track cloud instance and disk compatibility before resizing controllers” checks a different ongoing risk rather than the reported failure: at the Lakehaven digital services storage team, administrators schedule a cluster upgrade before validating health and supported upgrade paths. The relevant mechanism is existing cluster issues or unsupported upgrade paths can compromise an otherwise planned upgrade, the required evidence must show that the upgrade readiness report shows required checks passing before the change begins. The directly matched preventive control is “Repeat readiness checks after firmware cluster or application changes”.