A regional disaster-recovery procedure promotes a secondary database while the original writer may still be reachable to some clients. Which controls reduce the risk of conflicting writes? Select 2 answers.

Published
  1. Discard all replication and recovery-state evidence before promotion.
  2. Assume DNS changes instantly disconnect every old database client.
  3. Use an explicit writer-promotion procedure with appropriate fencing or routing and access controls for the former writer.
  4. Validate replication state, expected data loss, and application readiness before completing the traffic cutover.
  5. Allow unrestricted writes to both databases while claiming they are one consistent writer.

Comments — 0