Question 660
During a routine health assessment at Eastport Research Hospital, the ONTAP administrators find the following ONTAP problem: A shared cluster has no per-workload reporting so operators cannot tell which tenant consumes peak IOPS. The team reports that the correction is complete. Which observation BEST proves the stated problem is resolved?
Explanation
Correct Answer
A load replay identifies the high-consumption workload and separates its traffic from others. The observation verifies that the chosen action (Enable workload-specific performance views or supported QoS counters for each affected SVM or volume) has corrected the initiating failure (A shared cluster has no per-workload reporting so operators cannot tell which tenant consumes peak IOPS). This is directly measurable for Eastport Research Hospital's imaging file shares and patient databases rather than merely reporting task completion.
Incorrect Answers
The monitored interval distinguishes transient spikes from repeated SLO violations with recorded evidence. This is a valid test for another condition (An operations team treats a one-second peak as proof of persistent storage slowness without a time-series trend) after a different correction (Review sustained performance trends and compare relevant IOPS, throughput and latency percentiles). It does not establish the necessary result for Eastport Research Hospital's imaging file shares and patient databases: A load replay identifies the high-consumption workload and separates its traffic from others.
The diagnostic report identifies the affected volume or protocol path instead of attributing all delay to the cluster. This is a valid test for another condition (A storage cluster reports high average latency but no one distinguishes node, volume and protocol-level contributors) after a different correction (Correlate ONTAP workload performance counters by object and time window before tuning placement). It does not establish the necessary result for Eastport Research Hospital's imaging file shares and patient databases: A load replay identifies the high-consumption workload and separates its traffic from others.
A normal batch generates no false incident while a deliberately slow workload crosses the action threshold. This is a valid test for another condition (A new performance alert triggers continuously during normal batch windows because thresholds were selected without baseline data) after a different correction (Establish representative service baselines and configure alert thresholds around workload-specific SLOs). It does not establish the necessary result for Eastport Research Hospital's imaging file shares and patient databases: A load replay identifies the high-consumption workload and separates its traffic from others.