Question 860
A server operations team encounters the following situation: A geographically remote recovery database is asynchronous but monitors only connection uptime, overlooking hours of growing replication lag. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Link connectivity does not prove replication is keeping up with source changes. It builds validation into the affected workflow and supports the expected recovery result: A throttled replication test raises an alert before data age breaches the threshold.
Incorrect Answers
This control addresses a different scenario: A finance service uses asynchronous replication across continents but promises zero data loss during complete primary-site failure. That event's root mechanism was asynchronous replication can leave recent committed data unreplicated. The described incident instead arises from: Link connectivity does not prove replication is keeping up with source changes.
This control addresses a different scenario: A manufacturing operation needs recovery within minutes, but its disaster recovery plan specifies an empty cold site with no preinstalled servers. That event's root mechanism was a cold site entails equipment provisioning time inconsistent with short recovery demands. The described incident instead arises from: Link connectivity does not prove replication is keeping up with source changes.
This control addresses a different scenario: A warm site has correct hardware but its application configuration was not updated in six months, and a simulated failover fails to start modern services. That event's root mechanism was hardware readiness alone does not ensure application-level DR readiness. The described incident instead arises from: Link connectivity does not prove replication is keeping up with source changes.