When using Nearsync replication (1-minute RPO), the system prioritizes the performance of the primary workload. If the network bandwidth is insufficient to sustain the data change rate, the system will not pause or degrade production I/O. Instead, it automatically and temporarily switches the replication schedule to a 60-minute RPO (Asynchronous mode) to alleviate network congestion. Once the network can support the required rate again, it will attempt to resume the 1-minute RPO schedule. This ensures business continuity without impacting the source application's performance.

A. The system prioritizes write I/O performance on the primary cluster; it will not degrade it. Instead, it adjusts the replication schedule.

C. A failover is a manual or automated disaster recovery invocation, not a response to network bandwidth limitations for replication.

D. Pausing all write I/O would halt the protected application, which is a more severe impact than a temporarily increased RPO.

1. Nutanix University. (2023). Nutanix Business Continuity and Disaster Recovery (BCDR) 7 Courseware. Section: Nearsync Replication. "If the available network bandwidth is not sufficient for the current change rate, the RPO automatically increases to 60 minutes to allow the replication to catch up."

2. Nutanix. (2023). Prism Central Guide v2023.3. Section: Data Protection with Nearsync Replication. "If the network bandwidth is insufficient to meet the 1-minute RPO, Nutanix Disaster Recovery automatically switches to the next-best RPO (one hour) and alerts the administrator."