A production AHV cluster replicates to a remote Nutanix cluster over a constrained WAN. The business requires a one-hour RPO, and replication traffic must not compete with production VLAN traffic. Which replication path should an administrator select?

A one-hour RPO is the natural fit for asynchronous replication, whose schedules start at one hour and ship snapshots in the background without adding latency to VM writes. The second requirement is isolation: replication traffic must not share the production VLAN. Nutanix lets you segment replication traffic onto a dedicated network or VLAN on both clusters, so snapshot transfers have their own path and can be bandwidth-throttled without touching user traffic. Async over the production VLAN meets the RPO but violates the isolation requirement, and on a constrained WAN it can cause contention during replication windows. NearSync would deliver a tighter RPO than needed, and in this option it still rides the production VLAN, so it fails the isolation rule as well; QoS markings don't change which segment the traffic shares. Metro Availability is synchronous, needs very low latency and adds WAN round-trips to every write; it doesn't belong on a constrained WAN, and throttling would hurt production writes directly. Exam caveat: meet the RPO with the right mode first, then pick the network path that keeps replication traffic off production segments. Operational check: verify the replication network or VLAN is configured on both clusters, confirm the hourly schedule, and monitor WAN utilization and recovery point age during replication windows.