Which technology can achieve zero RPO?

Question

Options

• ASnapshots
• BAsynchronous replication
• CActive-active
• DClone

• A
  3% (1)
• B
  6% (2)
• C
  77% (27)
• D
  14% (5)

Explanation

Active-active replication achieves zero RPO because writes are committed simultaneously to multiple nodes before being acknowledged - if one site fails, its peer already holds every byte of data, leaving nothing to recover. Snapshots (A) and clones (D) are both point-in-time copies: any data written after the last snapshot or clone is taken will be lost in a failure, making RPO equal to the elapsed time since the last copy. Asynchronous replication (B) acknowledges writes on the primary before the secondary confirms receipt, so a crash during that replication lag causes some data loss - RPO is always greater than zero.

Memory tip: Zero RPO requires zero lag. Active-active = both sites are always active and identical; "active" appears twice because both sides accept and mirror every write in real time. Anything with a delay (async) or a gap (snapshots/clones) can't make that promise.

No community discussion yet for this question.