A protection domain uses async replication with snapshots every 15 minutes. The most recent snapshot replicated 5 minutes after creation. What approximate RPO should you quote?
Select an answer to reveal the explanation.
Short Explanation
Think of async RPO as the worst-case gap: you lose from the last snapshot plus the time that snapshot took to copy. If snapshots happen every 15 minutes and replication adds 5, your recovery point is 20 minutes. Don't quote only the snapshot interval when the replica is still catching up.
Full Explanation
Async replication in Nutanix Protection Domains is driven by scheduled snapshots: the recovery point is the most recent replicated snapshot, not the moment of failure. If snapshots are created every 15 minutes, the worst case is that a write occurs just after one snapshot and must wait until the next one. Replication delay then adds the time for that snapshot to reach the remote cluster, so the approximate RPO is the snapshot interval plus observed replication latency. A recovery point equal only to the snapshot interval ignores the fact that a locally created snapshot may not yet be available at the DR site. A recovery point equal only to replication delay assumes snapshots are instantaneous and continuous, which is not how scheduled async snapshots work. A doubled interval assumes both the snapshot period and the replication delay are counted twice, which has no basis in the replication model. Exam caveat: on an async replication question, check whether the prompt gives replication lag or only snapshot frequency; if lag is given, include it. Operational check: review the protection domain schedule and recent replication lag from the protection domain details, then compare the calculated RPO with the business requirement.