Question 760
At fictional Fairport Manufacturing, a storage integration engineer supporting production lines is evaluating block/file/object architecture and SAN transport during a storage security audit (HPE-HPE0-J83-FOUNDATION-190). The observed storage integration issue is: A business sets its recovery-point objective below one hour but schedules replication only once daily. Which recurring preventive or detective control would most directly reduce recurrence?
Explanation
Correct Answer
The specific preventive or detective safeguard is: Measure actual replication lag and recovery-point age during failover drills. It reduces the risk of: A business sets its recovery-point objective below one hour but schedules replication only once daily. The associated correction is: Choose replication or backup frequency that can satisfy the stated maximum data loss. Successful implementation would show: Simulated site loss yields a recovery point no older than the agreed RPO.
Incorrect Answers
“Alert on long rebuilds and elevated protection risk after drive replacement.” would examine another storage topic: Monitor rebuild or reconstruction progress and avoid additional planned risks until protection is restored. That does not resolve the stated failure: a business sets its recovery-point objective below one hour but schedules replication only once daily. Choose replication or backup frequency that can satisfy the stated maximum data loss.
This option tests a separate storage control: Calculate effective capacity including RAID protection spares metadata and reserved headroom. The reported gap is that a business sets its recovery-point objective below one hour but schedules replication only once daily. Choose replication or backup frequency that can satisfy the stated maximum data loss.
The HPE measure “Track SSD wear and host write volume over the planned service life.” concerns another storage task: Evaluate drive endurance and write-rate suitability alongside throughput and latency. The actual acceptance gap is that a business sets its recovery-point objective below one hour but schedules replication only once daily. Choose replication or backup frequency that can satisfy the stated maximum data loss.