CompTIA DataSys+ (DS0-001)Business ContinuityHard
A financial institution's database system requires continuous availability and zero data loss for critical transactions. The primary and secondary database servers are geographically separated but connected by a high-speed, low-latency network. Which replication method is most appropriate for achieving these stringent requirements?
- ASnapshot Replication
- BTransactional Replication
- CAsynchronous Replication
- DSynchronous Replication
Show answer & explanationAnswer & explanation
Correct answer: D. Synchronous Replication
Synchronous replication ensures that a transaction is committed on both the primary and secondary databases before the primary confirms the commit to the application. This guarantees zero data loss (zero RPO) but requires a high-speed, low-latency network to minimize performance impact, which is available in the scenario.
Why the other options are wrong
- A. Snapshot replication involves periodically copying the entire database or a large portion, which is unsuitable for continuous availability and zero data loss on critical transactions.
- B. Transactional replication typically focuses on replicating ongoing changes for specific tables or objects, but it often operates asynchronously and may not guarantee zero data loss in a failover scenario without additional mechanisms.
- C. Asynchronous replication allows the primary to commit transactions independently of the secondary, leading to potential data loss in case of a primary failure before replication completes. This does not meet the 'zero data loss' requirement.
Synchronous Replication
Synchronous replication ensures that a write operation is committed to both the primary and secondary databases before the primary acknowledges the write to the application. This guarantees zero data loss (RPO = 0) but can introduce latency.
- Guarantees zero data loss (RPO = 0).
- Transaction commits on primary and secondary before acknowledgment.
- Requires high-speed, low-latency network to minimize performance impact.
Memory trick: Sync for zero loss, Async for speed, Snapshot for moments, Transaction for need.