Question 670
Original unofficial HPE0-J83 storage practice case R183-CASE-168 — Telecom backup data shows unexpected transfer delay. Observed evidence: Copy job saturates intersite link during business peak and protection lag rises. After the scoped corrective action, which observation most directly demonstrates that this issue is resolved?
Explanation
Correct Answer
The acceptance result Replica catch-up completes within SLA on peak-day traffic model directly tests recovery for this situation: Replication bandwidth contention is causing delayed restore points. The prior signal was: Copy job saturates intersite link during business peak and protection lag rises. The planned intervention was: Measure link congestion and prioritize protection traffic according to policy. 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: Multipath claim rules no longer match array device identifiers, signaled by: Two SAN fabrics are detected as separate LUNs after an OS upgrade. The current symptom is: Copy job saturates intersite link during business peak and protection lag rises. Verify this incident by checking: Replica catch-up completes within SLA on peak-day traffic model.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: A fabric port or zoning issue removed one redundant path, signaled by: SCSI device stays online but path state changes to failed after a switch reboot. The current symptom is: Copy job saturates intersite link during business peak and protection lag rises. Verify this incident by checking: Replica catch-up completes within SLA on peak-day traffic model.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Physical FC optics or cabling errors are causing retransmissions, signaled by: Specific switch port accumulates CRC during high load while its peers remain clean. The current symptom is: Copy job saturates intersite link during business peak and protection lag rises. Verify this incident by checking: Replica catch-up completes within SLA on peak-day traffic model.