Question 640
Original unofficial HPE0-J83 storage practice case R183-CASE-160 — Regional government DR copy stops. Observed evidence: Replication pair reports suspended after a remote site network-policy change. Which operational acceptance gate would best detect a recurrence of this same fault?
Explanation
Correct Answer
The acceptance gate requires: Replication resumes and lag returns inside the agreed RPO; it alerts on the warning sign: Replication pair reports suspended after a remote site network-policy change. That linkage targets the root issue: Required replication peer connectivity was blocked. 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: Thin allocation exhausts physical pool despite unchanged host LUN sizes. For the current root issue — Required replication peer connectivity was blocked — require: Replication resumes and lag returns inside the agreed RPO, and detect recurrence of: Replication pair reports suspended after a remote site network-policy change.
Incorrect for this recurring-fault gate. The proposed gate belongs to a different case indicated by: SCSI device stays online but path state changes to failed after a switch reboot. For the current root issue — Required replication peer connectivity was blocked — require: Replication resumes and lag returns inside the agreed RPO, and detect recurrence of: Replication pair reports suspended after a remote site network-policy change.
Incorrect for this recurring-fault gate. The proposed gate belongs to a different case indicated by: After intersite partition both sides attempt to accept writes. For the current root issue — Required replication peer connectivity was blocked — require: Replication resumes and lag returns inside the agreed RPO, and detect recurrence of: Replication pair reports suspended after a remote site network-policy change.