Nutanix NCP-BC-7.5 Practice Test Questions Answers

In a Nutanix environment, replication health is heavily dependent on the available bandwidth and the consistency of the network path between the source and target sites. When replication fails following an infrastructure change like network segmentation, it often indicates that the system is unable to sustain the current data change rate over the new path. While verifying ports (Option C) is a logical infrastructure step, the provided answer emphasizes managing the replication load by increasing the Recovery Point Objective (RPO) interval. Increasing the RPO (e.g., from 1 hour to 4 hours) reduces the frequency of snapshot transfers, which can help determine if the replication engine (Cerebro) can successfully complete a transfer when given a longer window or reduced pressure. If increasing the RPO resolves the failure, the administrator can conclude that the network change introduced a bottleneck or limited throughput that is insufficient for the original " heavy " schedule. This diagnostic step helps differentiate between a total connectivity blackout and a performance-related failure caused by the newly implemented network segmentation. Once the baseline replication is restored at a higher RPO, the administrator can then proceed to optimize the network or firewall settings to support the more aggressive RPO requirements originally set by the business.

Nutanix 2-node clusters are often used in small remote office (ROBO) environments to provide high availability with a smaller hardware footprint. However, the reduced node count introduces specific limitations on advanced data protection features compared to standard 3-node or larger clusters.

One of the key limitations of a 2-node cluster is the support for high-frequency replication. Technologies like NearSync (which provides RPOs from 1 to 15 minutes) and Synchronous replication (0 RPO) require a minimum of three nodes to manage the necessary metadata overhead, storage consistency, and lightweight snapshot (LWS) engine requirements. In a 2-node cluster, the system is restricted to using standard Asynchronous replication. The minimum RPO supported for standard Asynchronous replication in these small cluster configurations is typically 1 hour (60 minutes). An administrator attempting to set a more aggressive RPO will find that the system does not support the necessary lightweight snapshot infrastructure. Therefore, while a 2-node cluster provides excellent local availability, its off-site disaster recovery capability is limited to a 1-hour RPO, which should be considered during the initial architectural design and risk assessment phase for critical workloads.

A multisite deployment in Nutanix Disaster Recovery allows a single primary cluster to replicate its workloads to multiple destination availability zones (AZs) for increased resilience. While a single " Protection Policy " can define the replication schedules to both recovery sites, the " Recovery Plan " is the separate object responsible for the actual orchestration of the failover.

A Recovery Plan is fundamentally a point-to-point object; it defines how to move workloads from Site A to Site B. If an administrator wants the ability to failover to either of two different recovery AZs, they must create two distinct Recovery Plans: one for AZ1 and another for AZ2. Each plan will contain the site-specific network mappings, boot sequences, and IP mappings relevant to that specific destination. If the administrator has only created a recovery plan for the first AZ, they will be able to see recovery points at both locations but will only have a " target " defined for the first site. The second AZ will not appear as a valid destination in the failover menu until its specific Recovery Plan is built and validated. This modular design ensures that each DR site can have its own customized networking and application orchestration logic.

Nutanix Disaster Recovery provides multisite replication capabilities, allowing a single cluster to protect workloads across multiple locations. However, there are specific architectural constraints regarding the type of replication schedules that can coexist within a single Protection Policy.

The primary limitation in this architect ' s design is that a single Nutanix Protection Policy supports only one synchronous replication schedule. While you can configure a policy to replicate to multiple sites using Asynchronous or NearSync schedules, you cannot natively instruct the system to perform a synchronous " 3-way " write where a single VM mirrors every I/O to two different physical destination clusters simultaneously. This is due to the extreme latency and metadata synchronization overhead that would be required to maintain zero-RPO consistency across three sites for every single write operation. Prism Central does allow pairing with more than one AZ (negating Option B), and synchronous replication is fully supported in Protection Policies (negating Option D). Therefore, to achieve the desired level of protection, the architect would need to use a combination of one synchronous schedule and additional asynchronous schedules to the second AZ, rather than attempting two simultaneous synchronous links within one policy.

The Nutanix Cerebro service manages replication by scheduling snapshots and transferring the delta changes to the remote site. In an asynchronous replication schedule, if a new snapshot is taken before the previous one has finished replicating, the system faces a choice. To ensure that the most current data is available at the recovery site as quickly as possible, Nutanix may " skip " the replication of an older pending snapshot in favor of starting the replication of the newest one.

In this scenario, all infrastructure components (bandwidth, ports, hardware) are verified as healthy and have supported successful replication for months. This points toward a data-level issue rather than a connectivity issue. A " significant one-time surge in change rate " (Option D) means the VM generated a massive amount of new data blocks (churn) in a short period. Because the " Snapshot-on-wire " transfer size is directly tied to the number of changed blocks, this specific snapshot would take much longer than usual to replicate. If the transfer time exceeds the RPO interval, the next scheduled snapshot will trigger. The Cerebro service will see that it has a newer recovery point ready to go and will skip the " stuck " or slow-moving older snapshot to maintain the most recent RPO possible at the target. This behavior generates the " Replication was skipped " warning to notify the administrator that the historical sequence was interrupted due to a temporary imbalance between data churn and available throughput.