NCP-BC-7.5 Exam Dumps - Nutanix NCP-BC Questions and Answers

In a Nutanix legacy Protection Domain (PD) configuration, three primary elements must be in place for data protection to occur: the entities (VMs), the remote site (destination), and the schedule. Even if a VM has been added to a Protection Domain (negating Option A), the cluster will not take any action unless it is explicitly told " when " and " how often " to do so.

If no new snapshots are being created locally and replication is not starting, the most likely issue is that no " Schedule " has been configured for that Protection Domain. The schedule defines the RPO (e.g., hourly, daily) and the retention period for the snapshots. Without an active schedule, the Cerebro service simply has no instruction to initiate the snapshot process. While a missing vStore mapping (Option C) would cause the " replication " to fail, the " local snapshots " would still be created in the PD. Similarly, low bandwidth throttling (Option D) would cause the replication to move slowly or time out, but it would not prevent the initial creation of the local recovery points. Therefore, verifying the presence of a valid, active replication schedule is the mandatory first step for an administrator when a Protection Domain appears to be " idle " despite having VMs assigned to it.

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.

In a Business Continuity strategy, " downtime " can be categorized as either unexpected (disaster) or controlled (maintenance). When an administrator knows that a disruption is coming, such as scheduled network maintenance on a primary cluster, they should utilize the " Planned Failover " mechanism within the Nutanix Recovery Plan.

A Planned Failover is a graceful, orchestrated migration. It first shuts down the virtual machines at the primary site to ensure all data is flushed and no new writes occur. It then performs a final synchronization to the recovery site to ensure zero data loss (Zero RPO), and finally powers the VMs on at the destination site according to the plan ' s sequence. This differs significantly from an " Unplanned Failover " (Option A), which assumes the primary site is already offline and may result in minor data loss depending on the last successful replication. A " Test Failover " (Option D) merely validates the process in an isolated environment and does not move the actual production workload. By executing a Planned Failover before the maintenance begins, the administrator ensures that the services are safely running on the target cluster, maintaining application availability and meeting the objective of zero downtime during the maintenance window.

Testing is the most vital component of a resilient BCDR strategy, as it proves that recovery objectives (RTO/RPO) are achievable before a real emergency occurs. The Nutanix " Test Failover " feature is purpose-built for this requirement. Unlike a Planned Failover (which shuts down production) or an Unplanned Failover (which assumes production is dead), a Test Failover performs a non-disruptive validation.

During a Test Failover, the orchestration engine uses the most recent snapshots to power on VMs at the destination cluster. To satisfy the " without impacting production " requirement, the test VMs are typically attached to an " Isolated " or " Test " network segment that has no route to the live production network. This prevents IP address conflicts and service interference while allowing the administrator to log into the recovered VMs and verify that applications start correctly. Simple " Validation " (Option A) only checks the configuration settings and connectivity but does not actually test the power-on sequence or application logic. By executing a full Test Failover, the organization gains documented proof of its DR readiness, identifying potential issues like missing dependencies or incorrect boot orders without causing any disruption to the users currently accessing the primary site.

Synchronous replication is designed for zero data loss by requiring that every write be acknowledged at both the primary and recovery sites before the application can proceed. This creates a " hard " dependency on the network link between the two clusters . If the network connectivity is interrupted (e.g., during scheduled maintenance), the primary cluster will be unable to receive acknowledgments from the remote site.

By default, if the synchronous link is broken, the primary cluster may pause I/O to the protected VMs to prevent data inconsistency, which would cause the VMs to become unresponsive to users. To prevent this during planned maintenance while ensuring that the VMs stay online at the primary site, the administrator should temporarily transition the protection mode. Changing the Protection Policy from " Synchronous " to " Asynchronous " (Option C) removes the real-time write-mirroring requirement. This allows the VMs to continue serving local I/O independently of the remote site ' s status. While this technically increases the RPO during the maintenance window, it ensures application availability. Once the maintenance is complete and network connectivity is restored, the administrator can change the policy back to Synchronous. The system will then perform a catch-up sync and return to the Zero-RPO state once the data at both sites is identical again. This operational maneuver is a standard best practice for managing " stretched " cluster environments during infrastructure updates.

Nutanix NearSync replication provides a middle ground between traditional asynchronous replication and synchronous mirroring, offering RPOs as low as 1 minute using Lightweight Snapshots (LWS). However, the LWS mechanism and the high-frequency metadata operations required to maintain a 1-to-15 minute RPO have specific hardware and cluster-level requirements.

One of the strict prerequisites for enabling NearSync is the cluster size. Nutanix requires a minimum of a three-node cluster for NearSync replication. This is because the system must have enough resources to distribute the LWS metadata and handle the increased I/O overhead without compromising the cluster ' s availability or performance. In a two-node cluster (which is common for small ROBO deployments), the system does not meet the minimum redundancy and resource thresholds required for the NearSync engine to operate reliably. While two-node clusters support standard Asynchronous replication (with a 60-minute RPO or higher), they are restricted from using the NearSync lightweight snapshot engine. An administrator attempting to set a 5-minute RPO on a two-node cluster will find the option either grayed out or the task will fail validation. To achieve a 5-minute RPO, the organization would need to expand the remote office cluster to at least three nodes or settle for a higher RPO supported by standard asynchronous replication on the existing hardware.

Nutanix Recovery Plans are designed to orchestrate the failover of complex applications that may consist of multiple virtual machines with different protection requirements. However, there are rules regarding which types of replication schedules can be mixed within a single plan.

Nutanix supports mixing Asynchronous and NearSync replication schedules within the same Recovery Plan. This is because both Async and NearSync are fundamentally snapshot-based, " passive " recovery models where the system pulls from recovery points stored at the destination cluster. However, the system generally restricts or warns against mixing Synchronous replication with other types in a single orchestrated plan. Synchronous replication (syncrep) is an " active-active " or " stretched " model that behaves differently during a failover compared to snapshot-based models. In some software versions, including entities protected by synchronous schedules with those on async/nearsync within a single plan can cause the failover task to fail validation because the orchestration logic for zero-RPO failover is distinct from snapshot restoration. Therefore, while mixing Async and NearSync is a supported and common practice, administrators must be cautious with Synchronous workloads.

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.

Preserving IP addresses during a failover is a common requirement for applications with hardcoded IP references or complex inter-service dependencies. In a standard multi-site DR setup, the source and destination sites reside on different Layer 3 subnets, meaning a VM would naturally require a new IP address to be routable at the recovery site. To achieve " IP Preservation, " the underlying network infrastructure must support Layer 2 (L2) stretching.

L2 stretching (often implemented via VXLAN or specialized VPN tunnels like Nutanix Flow Virtual Networking) allows a single logical subnet to span multiple physical locations. When a VM fails over to a cluster on a stretched subnet, it effectively stays on the same network broadcast domain. As a result, its IP address, default gateway, and subnet mask remain valid and unchanged. If the subnets are not stretched, the administrator must rely on the Recovery Plan ' s " IP Mapping " feature to assign a new, valid IP at the destination—which does not " preserve " the original address. While preserving IPs simplifies application recovery, it requires more complex network engineering to ensure that traffic is correctly routed to the active site during a disaster, highlighting the trade-off between application simplicity and infrastructure complexity in BCDR design.

Virtual GPUs (vGPUs) are hardware-dependent resources that are tied to specific physical GPU cards installed in the Nutanix nodes. While Nutanix Disaster Recovery can replicate the VM ' s virtual disks and general configuration, the specific mapping to a physical vGPU profile is often not automatically preserved across clusters due to potential differences in hardware availability or GPU generations at the recovery site.

When the VM fails over and boots up at the secondary site, the guest OS may see the NVIDIA driver but will find that the " backed " hardware resource is missing or incorrectly mapped, leading to a failure in hardware acceleration. To resolve this, the administrator must manually edit the VM ' s hardware settings at the recovery site and re-assign a compatible vGPU profile from the local cluster ' s available GPU resources. This post-failover cleanup task is essential for workloads like VDI (Virtual Desktop Infrastructure) or CAD applications that depend on GPU processing. Relying on NGT (Option A) or reinstalling the OS (Option B) will not fix the underlying missing hardware assignment in the hypervisor, highlighting the need for specialized knowledge when protecting VMs with specialized hardware pass-through or vGPU requirements.