Replication in a Nutanix environment always begins with an " initial seed " . This first replication task is a full, 1-to-1 copy of all the data blocks currently occupied by the virtual machines on the source cluster. Unlike subsequent incremental snapshots-which only transfer the changed blocks-the initial seed requires sufficient physical or logical space at the destination to hold the entire data set of the protected VMs.
In this scenario, the administrator attempted to protect 4TB of virtual machine data but restricted the destination container ' s capacity to a mere 200GB. Because the destination container reports only 200GB of available space, the replication job will immediately stall or fail to progress as soon as the incoming data stream exceeds that limit. Nutanix replication requires a " landing zone " that can accommodate the full size of the initial snapshot before it can begin the process of data reduction (like compression or deduplication) at the remote site. To fix this, the administrator must increase the advertised capacity of the VMData container on Cluster B to at least 4TB (plus overhead for future growth and snapshots) to allow the initial full seed to complete successfully, thereby establishing the baseline for the BCDR protection schedule.

Nutanix Disaster Recovery is designed to be bi-directional, supporting both failover and failback . In an unplanned failover, the primary site (AZ1) is assumed to have crashed. Once AZ1 is brought back online, the system must synchronize any data changes that occurred while the VMs were running at AZ2.
Statement C is correct because once the VMs are powered on at AZ2, the Nutanix Cerebro service automatically reverses the protection policy. New recovery points are created at AZ2 and replicated back to AZ1. For a successful, modern failback with zero data loss from the cloud session, the administrator must wait for these recovery points to replicate back to AZ1 before initiating the failback.
Statement B is also correct and describes a specific " recovery of last resort " scenario. If AZ1 is restored but connectivity to AZ2 is permanently lost (e.g., the cloud provider has an issue), an administrator can still " Unplanned Failover " back to AZ1 using the historical snapshots that existed locally on AZ1 before the original outage. This would result in data loss equal to the time the VMs were running at AZ2, but it allows for service restoration when the recovery site itself fails. These two statements highlight the flexibility of the Nutanix DR architecture in handling both controlled failback and emergency local restoration.

Nutanix NearSync replication uses Lightweight Snapshots (LWS) to achieve RPOs as low as 1 minute. To maintain this aggressive schedule, the system must be able to replicate all the " delta " changes (the data that has changed since the last snapshot) within the RPO window. If the data change rate (churn) of the VM increases, or if the available network bandwidth decreases, the system may find that it cannot complete the replication of one LWS before the next one is due.
When the Nutanix Cerebro service detects that it is consistently missing its NearSync target, it will automatically " downshift " the replication to a standard Asynchronous schedule (typically hourly) to ensure that the VM remains protected at a manageable frequency. This is a self-healing mechanism designed to prevent replication jobs from stacking up and causing cluster instability. Insufficient bandwidth (Option D) is the most common cause for this downshift, as the " Snapshot-on-wire " cannot be moved fast enough to satisfy the 5-minute requirement. While high RTT (Option A) is a requirement for Synchronous replication, NearSync is designed to handle higher latencies (up to 80ms or more), making bandwidth the primary bottleneck in these troubleshooting scenarios.

Storage Container mapping is a fundamental requirement for successful replication between Nutanix clusters, as it defines where the replicated recovery point data will reside on the destination cluster. In the early versions of Nutanix Disaster Recovery, administrators had to manually map source containers to destination containers to ensure the replication stream had a valid landing zone. However, to simplify the deployment of BCDR solutions and reduce manual configuration errors, modern Nutanix Disaster Recovery behavior has been enhanced. If the system detects that a VM is protected but no manual container mapping has been established in Prism Central, it will proactively check the recovery site for a container with the same name as the source. If that container does not exist, the orchestrator will automatically create a new storage container with the identical name on the remote cluster to allow replication to proceed without interruption. This automation ensures that " out-of-the-box " protection policies can function immediately even if the recovery site hasn ' t been fully pre-provisioned with storage structures. This behavior prevents replication from failing due to minor administrative oversights and maintains the integrity of the data protection schedule.

Migrating from legacy Protection Domain (PD) based management to the modern Prism Central (PC) based Protection Policies is a recommended best practice for scaling Nutanix Disaster Recovery. This migration involves moving VMs from a " Prism Element " centric management model to a centralized, category-based model in Prism Central.
To ensure that no data is lost during this transition, the most critical prerequisite is to verify that a successful, full replication (backup) of the Protection Domain has recently completed. This ensures that the recovery site already possesses a complete and consistent set of data for the VMs before they are unlinked from the old policy and attached to the new one. While adding VMs to a category (Option A) is a step in the process, it is not the first verification step required for data safety. If an administrator attempts to migrate while a replication is incomplete or failing, the transition to the new policy might leave the VMs unprotected for an extended period, or recovery points might be missing if a disaster occurs mid-migration. By completing a full backup of the PD first, the administrator creates a " safety net " of recovery points that can be used if the migration itself encounters issues. This ensures that the transition to modern DR is performed with minimal risk to the business ' s data protection objectives.