Question 170
At fictional Beacon Healthcare, a storage integration engineer supporting hospital systems is evaluating block/file/object architecture and SAN transport during an application migration (HPE-HPE0-J83-FOUNDATION-043). The observed storage integration issue is: An asynchronous replica is called zero-loss protection despite persistent nonzero replication lag. Which recurring preventive or detective control would most directly reduce recurrence?
Explanation
Correct Answer
The specific preventive or detective safeguard is: Monitor replication backlog and alert before RPO is breached. It reduces the risk of: An asynchronous replica is called zero-loss protection despite persistent nonzero replication lag. The associated correction is: Calculate realistic potential data loss and set RPO based on observed lag and link behavior. Successful implementation would show: Recovery testing confirms the documented last-consistent remote point after interruption.
Incorrect Answers
The choice “Maintain a common-cause failure register for multi-site storage.” evaluates another aspect of the storage design: Reassess geographical power network and management dependencies to separate failure domains. The current problem is that an asynchronous replica is called zero-loss protection despite persistent nonzero replication lag. Calculate realistic potential data loss and set RPO based on observed lag and link behavior.
The HPE measure “Test production write profiles against expected inter-site delay.” concerns another storage task: Validate round-trip latency bandwidth and write acknowledgement requirements before choosing sync mode. The actual acceptance gap is that an asynchronous replica is called zero-loss protection despite persistent nonzero replication lag. Calculate realistic potential data loss and set RPO based on observed lag and link behavior.
This option tests a separate storage control: Select a suitable double-parity or mirrored layout when two-disk resilience is required. The reported gap is that an asynchronous replica is called zero-loss protection despite persistent nonzero replication lag. Calculate realistic potential data loss and set RPO based on observed lag and link behavior.