A protected application must meet a five-minute RPO and a one-hour RTO. After failover, VM startup and application boot take about five minutes. Which replication design best meets the requirements without overprovisioning?
Select an answer to reveal the explanation.
Short Explanation
Think of RPO as how much data you can lose and RTO as how long you can be down. A five-minute RPO is below async's one-hour minimum, so NearSync at five minutes is the fit. Boot time sits inside the RTO, and no replication mode makes VMs boot faster.
Full Explanation
RPO is set by how often recovery points are captured and shipped. Nutanix asynchronous replication schedules start at one hour, so it cannot meet a five-minute RPO. NearSync covers RPOs from 1 to 15 minutes by shipping lightweight snapshots at the configured interval, so a five-minute NearSync schedule meets the data-loss target exactly without the cost of synchronous replication. RTO is a separate measure: failover orchestration, VM power-on and application start must fit within an hour, and five minutes of boot time leaves plenty of room. A sixty-minute async schedule meets the RTO but leaves up to an hour of lost data, missing the RPO. Metro Availability delivers a zero RPO with synchronous writes and strict latency limits; that overprovisions a five-minute requirement and doesn't change boot time. Choosing NearSync because it supposedly shortens application startup is wrong reasoning: replication frequency affects data loss, not how fast VMs boot, so that option reaches the right mode for the wrong reason. Exam caveat: map RPO to replication mode and frequency, and RTO to failover orchestration and boot time. Operational check: verify the protection policy shows a five-minute NearSync schedule and recent recovery points at the remote site, then run a test failover to time the recovery against the one-hour RTO.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.