Question 670
At fictional Lakeshore Finance, a storage integration engineer supporting transaction processing is evaluating customer storage sizing and solution requirements during a site failover exercise (HPE-HPE0-J83-PLAN-168). The observed storage integration issue is: A workload requirements document uses average IOPS only and ignores 99th-percentile response latency. Which specific storage integration action best addresses the reported issue?
Explanation
Correct Answer
The most direct corrective action is: Capture burst and tail latency under a representative concurrency profile. The specific problem is: A workload requirements document uses average IOPS only and ignores 99th-percentile response latency. Expected acceptance evidence is: Peak-period percentile latency remains within a signed target. The underlying storage principle is: Mean performance can hide intermittent storage stalls that hurt applications.
Incorrect Answers
The choice “Assign recovery ownership and escalation paths across storage backup and application teams.” evaluates another aspect of the storage design: another storage design or acceptance condition. The current problem is that a workload requirements document uses average IOPS only and ignores 99th-percentile response latency. Mean performance can hide intermittent storage stalls that hurt applications.
The HPE measure “Forecast logical physical and performance growth with clear scaling triggers.” concerns another storage task: another storage design or acceptance condition. The actual acceptance gap is that a workload requirements document uses average IOPS only and ignores 99th-percentile response latency. Mean performance can hide intermittent storage stalls that hurt applications.
This option tests a separate storage control: another storage design or acceptance condition. The reported gap is that a workload requirements document uses average IOPS only and ignores 99th-percentile response latency. Mean performance can hide intermittent storage stalls that hurt applications.