A production AHV VM on a Nutanix cluster must replicate to a remote cluster. The current scheduled asynchronous replication gives an RPO of one hour, but the business now needs a much shorter RPO. The WAN has enough bandwidth, but its latency is higher than Metro availability requires. Which protection method should you choose?
Select an answer to reveal the explanation.
Short Explanation
Think of NearSync as the middle lane on the DR highway: it pushes changes far faster than a scheduled async copy, but it still doesn't demand Metro-grade latency. If your WAN has the bandwidth but not the ultra-low latency, you don't force Metro or settle for hourly snapshots. You pick the mode whose RPO fits the business and whose network constraints fit the link.
Full Explanation
NearSync replication reduces recovery point objectives below scheduled asynchronous replication while avoiding Metro availability's strict latency and bandwidth demands. It applies near-continuous replication between protection domains, so the remote copy stays closer to production than a snapshot-based asynchronous schedule. Here the business needs a shorter RPO than async, and the WAN has enough bandwidth but not the tight latency profile required for synchronous Metro operation, making NearSync appropriate. Asynchronous replication with the shortest supported schedule is wrong because scheduled async copies are periodic, so the recovery point depends on the interval and cannot match NearSync's near-continuous protection. Metro availability using synchronous replication is wrong because it requires stricter network conditions, typically low latency and sufficient bandwidth, and forcing it over a constrained link risks instability or unsupported operation. Local snapshots with periodic export to the remote cluster is wrong because snapshots are point-in-time copies, not ongoing replication, so the remote site's recovery point remains tied to manual or scheduled copies. Exam caveat: compare the required RPO against supported replication behavior and measured WAN latency and bandwidth. Operational check: validate the remote protection domain's replication lag and WAN latency before placing the VM in NearSync.