Question 760
At the Lakehaven travel platform storage administrators, an administrator cannot identify which volume caused a midday slowdown because only aggregate free-space charts are reviewed. What should be monitored or reviewed during future changes?
Explanation
Correct Answer
For the Lakehaven travel platform storage administrators, this maintenance action preserves the fix: retain useful performance baselines for major applications. It should be revisited as the workload evolves.
Incorrect Answers
Record cross-layer baselines when introducing new applications is not the primary recurring safeguard for this problem. The team should retain useful performance baselines for major applications. For the Lakehaven travel platform storage administrators, the direct corrective action is to use ONTAP System Manager performance views to inspect affected workloads and historical latency.
“Trend snapshot growth alongside workload write rates” checks a different ongoing risk rather than the reported failure: at the Lakehaven travel platform storage administrators, an administrator cannot identify which volume caused a midday slowdown because only aggregate free-space charts are reviewed. The relevant mechanism is capacity charts alone do not explain when and where IO service delay increases; a passing acceptance check would show that the review identifies the affected volume and interval with correlated performance indicators. The directly matched preventive control is “Retain useful performance baselines for major applications”.
The option would have the team monitor placement balance as new applications are provisioned. For this situation, the preventive control should instead be to retain useful performance baselines for major applications. For the Lakehaven travel platform storage administrators, the direct corrective action is to use ONTAP System Manager performance views to inspect affected workloads and historical latency.