Question 770
Original unofficial HPE0-J83 storage practice case R183-CASE-193 — Regional insurer wants replication visibility. Observed evidence: DR dashboard shows last successful sync but omits current lag and RPO. After the scoped corrective action, which observation most directly demonstrates that this issue is resolved?
Explanation
Correct Answer
The acceptance result A delayed replica triggers warning before the promised RPO is exceeded directly tests recovery for this situation: Replication status alone cannot establish recovery-point freshness. The prior signal was: DR dashboard shows last successful sync but omits current lag and RPO. The planned intervention was: Chart current lag backlog and peer health against the committed RPO. This targeted evidence is more useful than merely reporting that an array is online.
Incorrect Answers
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Device cloud registration or network reachability stopped, signaled by: One system has no telemetry although on-array usage is high. The current symptom is: DR dashboard shows last successful sync but omits current lag and RPO. Verify this incident by checking: A delayed replica triggers warning before the promised RPO is exceeded.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Log retention duration is shorter than required investigation period, signaled by: Storage audit logs are rotated before monthly access review. The current symptom is: DR dashboard shows last successful sync but omits current lag and RPO. Verify this incident by checking: A delayed replica triggers warning before the promised RPO is exceeded.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Capacity monitoring lacks usable and physical utilization indicators, signaled by: Only raw array capacity is plotted while thin-pool physical occupancy rises. The current symptom is: DR dashboard shows last successful sync but omits current lag and RPO. Verify this incident by checking: A delayed replica triggers warning before the promised RPO is exceeded.