Question 140
At fictional Keystone Hospitality, a storage integration engineer supporting guest-services platforms is evaluating storage monitoring, alerts and service telemetry during an HPE storage platform refresh (HPE-HPE0-J83-MONITOR-035). The observed storage integration issue is: A storage team tracks annual availability but never measures duration of individual outages or failover recovery. Which recurring preventive or detective control would most directly reduce recurrence?
Explanation
Correct Answer
The specific preventive or detective safeguard is: Review monthly outage trend and repeat-root-cause incidents. It reduces the risk of: A storage team tracks annual availability but never measures duration of individual outages or failover recovery. The associated correction is: Collect incident start end recovery cause and affected-service identifiers. Successful implementation would show: Availability and MTTR reporting reflect real service events and drive corrective action.
Incorrect Answers
This option tests a separate storage control: Replace credentials with a supported read-only service role. The reported gap is that a storage team tracks annual availability but never measures duration of individual outages or failover recovery. Collect incident start end recovery cause and affected-service identifiers.
The choice “Audit NTP sync and log retention across hosts fabrics and storage.” evaluates another aspect of the storage design: Use synchronized time and correlate events by host array and port identifiers. The current problem is that a storage team tracks annual availability but never measures duration of individual outages or failover recovery. Collect incident start end recovery cause and affected-service identifiers.
The HPE measure “Verify external log ingestion and retention by regular sample replay.” concerns another storage task: Forward required audit and administrative events to protected central retention. The actual acceptance gap is that a storage team tracks annual availability but never measures duration of individual outages or failover recovery. Collect incident start end recovery cause and affected-service identifiers.