Design a disaster recovery strategy for a critical financial transaction-processing system with a near-zero RPO requirement.
Cover: synchronous replication to a standby (accepting the latency cost) since asynchronous replication cannot meet near-zero RPO; an explicit, automated or rapid manual failover process with a clearly defined RTO; regular (not just initial) DR drills proving the failover actually works under realistic conditions; careful handling of in-flight transactions during failover (ensuring no double-processing or silent loss); and a clear escalation/communication plan for the business during an actual DR event, since technical recovery and business/customer communication need to happen in parallel, no
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response