Question 780
At the Northport payment infrastructure operations group, a storage controller slows under heavy IO concentrated on one aggregate while other aggregates remain lightly used. Which ongoing control best prevents this failure from recurring?
Explanation
Correct Answer
The needed prevention is to monitor placement balance as new applications are provisioned. It directly sustains the original change to identify the busy aggregate or media bottleneck and rebalance eligible workloads or capacity. This result addresses the stated challenge at the Northport payment infrastructure operations group.
Incorrect Answers
That routine supports snapshot capacity pressure performance, but the relevant ongoing risk requires the team to monitor placement balance as new applications are provisioned. For the Northport payment infrastructure operations group, the direct corrective action is to identify the busy aggregate or media bottleneck and rebalance eligible workloads or capacity.
Retain useful performance baselines for major applications is not the primary recurring safeguard for this problem. The team should monitor placement balance as new applications are provisioned. For the Northport payment infrastructure operations group, the direct corrective action is to identify the busy aggregate or media bottleneck and rebalance eligible workloads or capacity.
“Trend all three metrics when IO sizes or concurrency change” checks a different ongoing risk rather than the reported failure: at the Northport payment infrastructure operations group, a storage controller slows under heavy IO concentrated on one aggregate while other aggregates remain lightly used. The relevant mechanism is a skewed workload can saturate one storage resource despite free capacity elsewhere, the required evidence must show that per-aggregate latency and utilization improve after a controlled placement adjustment. The directly matched preventive control is “Monitor placement balance as new applications are provisioned”.