Question 790
Fictional Hillsong Services runs the field operations workload at a remote operations wing storage site. While completing hardware modernization, the field handoff documents: A shelf evacuation is scheduled during peak transaction load without monitoring the I/O overhead and service-level risk. 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: Use observed workload patterns to choose future data-movement windows. The recurring exposure to avoid is: The data movement plan ignores workload performance and migration-throttle considerations. A continuing effectiveness check is: Measured application latency and array health stay within the agreed limits throughout evacuation.
Incorrect Answers
This alternative concerns: Monitor remote management health and egress requirements before planned maintenance. It is associated with pure1 self-service upgrade readiness, rather than the question’s determining condition. The case instead turns on: The data movement plan ignores workload performance and migration-throttle considerations. The more directly applicable prevention choice is: Use observed workload patterns to choose future data-movement windows.
This option focuses on: Record media admission checkpoints and recovery actions in the runbook. That can be relevant to staged two-step media admission, but it does not establish the required case-specific result. The current case instead identifies: The data movement plan ignores workload performance and migration-throttle considerations. The more directly applicable prevention choice is: Use observed workload patterns to choose future data-movement windows.
This alternative concerns: Run a backend path checklist before each capacity expansion. It is associated with shelf addition backend path review, rather than the question’s determining condition. The case instead turns on: The data movement plan ignores workload performance and migration-throttle considerations. The more directly applicable prevention choice is: Use observed workload patterns to choose future data-movement windows.