This website uses cookies to ensure you get the best experience.
Learn more.
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
- Discard all replication and recovery-state evidence before promotion.
- Assume DNS changes instantly disconnect every old database client.
- Use an explicit writer-promotion procedure with appropriate fencing or routing and access controls for the former writer.
- Validate replication state, expected data loss, and application readiness before completing the traffic cutover.
- Allow unrestricted writes to both databases while claiming they are one consistent writer.
Comments — 0
Sign in to comment