Question 530
For Westlake Retail, a proposed storage change affects commerce SAN databases and team NAS shares. The identified control failure is: A replicated volume shows increasing lag during peak writes but administrators mark the relationship healthy because it still exists. The team reports that the correction is complete. Which observation BEST proves the stated problem is resolved?
Explanation
Correct Answer
Replication lag returns below the documented threshold during a representative peak. The observation verifies that the chosen action (Track transfer duration, backlog, throughput and the configured RPO and remediate the true bottleneck) has corrected the initiating failure (A replicated volume shows increasing lag during peak writes but administrators mark the relationship healthy because it still exists). This is directly measurable for Westlake Retail's commerce SAN databases and team NAS shares rather than merely reporting task completion.
Incorrect Answers
The intended destination serves authorized client I/O and the activation state is documented. This is a valid test for another condition (After a source cluster outage the destination SnapMirror volume exists but hosts cannot access it because required activation and NAS configuration were skipped) after a different correction (Follow a supported disaster recovery activation runbook including volume promotion and SVM client access). It does not establish the necessary result for Westlake Retail's commerce SAN databases and team NAS shares: Replication lag returns below the documented threshold during a representative peak.
A resumed transfer completes and the replication destination has sufficient remaining space. This is a valid test for another condition (A SnapMirror transfer stops after the destination fills but an operator repeatedly restarts the transfer without reviewing the error) after a different correction (Investigate destination capacity and relationship status and resolve the resource limit before resuming updates). It does not establish the necessary result for Westlake Retail's commerce SAN databases and team NAS shares: Replication lag returns below the documented threshold during a representative peak.
Monitoring reports current replication health without masking a newly injected transfer failure. This is a valid test for another condition (A protection job raises repeated alerts even after replication succeeds because obsolete relationship errors remain in monitoring) after a different correction (Reconcile active relationship state with event timestamps and clear or close only resolved incident conditions). It does not establish the necessary result for Westlake Retail's commerce SAN databases and team NAS shares: Replication lag returns below the documented threshold during a representative peak.