Question 760
Original unofficial HPE0-J83 storage practice case R183-CASE-190 — Financial firm has unexplained I/O latency. Observed evidence: Average latency dashboard masks brief p99 write spikes. Which operational acceptance gate would best detect a recurrence of this same fault?
Explanation
Correct Answer
The acceptance gate requires: Peak events are visible with the application timestamp and host path; it alerts on the warning sign: Average latency dashboard masks brief p99 write spikes. That linkage targets the root issue: Coarse telemetry aggregation hides service-affecting bursts. The gate was derived from the case recovery facts, not independently certified by an HPE engineer.
Incorrect Answers
Incorrect for this recurring-fault gate. The proposed gate belongs to a different case indicated by: Hardware-health alert is not routed because email destination was never validated. For the current root issue — Coarse telemetry aggregation hides service-affecting bursts — require: Peak events are visible with the application timestamp and host path, and detect recurrence of: Average latency dashboard masks brief p99 write spikes.
Incorrect for this recurring-fault gate. The proposed gate belongs to a different case indicated by: Array fan alarms appear only in local console never in centralized NOC. For the current root issue — Coarse telemetry aggregation hides service-affecting bursts — require: Peak events are visible with the application timestamp and host path, and detect recurrence of: Average latency dashboard masks brief p99 write spikes.
Incorrect for this recurring-fault gate. The proposed gate belongs to a different case indicated by: One system has no telemetry although on-array usage is high. For the current root issue — Coarse telemetry aggregation hides service-affecting bursts — require: Peak events are visible with the application timestamp and host path, and detect recurrence of: Average latency dashboard masks brief p99 write spikes.