Your AHV protection domain replicates asynchronously to a second Nutanix cluster. Management requires an RPO of 2 hours for a group of VMs. Which configuration should you adjust first to control how often recovery points are created?
Select an answer to reveal the explanation.
Short Explanation
Think of async replication like a time-lapse camera: the gap between shots sets how old your newest photo can be. If you're allowed to lose two hours of work, you set the snapshot schedule to take a recovery point at least every two hours. Retention just decides how many old photos you keep.
Full Explanation
In Nutanix asynchronous replication, the protection domain snapshot schedule is the primary control for RPO. Each scheduled snapshot creates a consistent recovery point and, when a remote site is configured, a replicated copy, so the interval between snapshots sets the maximum age of the newest recovery point. For a two-hour RPO, the schedule must take snapshots at least every two hours, and in practice a little more often to leave room for replication time. Async schedules start at one hour; anything tighter moves into NearSync (1 to 15 minutes). A retention policy only decides how many snapshots are kept and for how long, which changes how far back you can restore, not how current the newest point is. A network QoS policy can shape replication bandwidth, but it doesn't set the cadence of snapshots, and extra bandwidth can't shorten an interval set by the schedule. The VM disk controller type affects guest I/O and compatibility, not replication timing. Exam caveat: set the schedule to meet the RPO, then confirm retention and bandwidth support it. Operational check: review the protection domain schedule and confirm that the age of the latest replicated snapshot at the remote site stays within two hours.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.