Pass the Nutanix NCP-BC NCP-BC-7.5 Questions and answers with CertsForce

When failing over a virtual machine between different physical locations or availability zones, it is common for the network topology at the recovery site to differ from the primary site. If a VM is recovered into a site where its original subnet is unavailable, it will lose connectivity.

To resolve this, Nutanix Recovery Plans include a " Network Mapping " section. The administrator must configure these mappings to explicitly define which production subnet at the source site corresponds to which valid subnet at the recovery site. During the failover process, the orchestrator uses this mapping to automatically re-configure the VM ' s virtual network interface (vNIC) to connect to the correct local VLAN or overlay network at the destination. While " matching subnet names " (Option D) can simplify management, it is not a requirement if the mapping is correctly defined. Synchronous replication (Option B) does not address the networking layer, as it is a storage-level feature. Network mapping is therefore the essential task for ensuring that workloads are not only recovered but also accessible following a failover.

Nutanix Disaster Recovery to the Cloud is built on the principle of automation and resource optimization. When a failover to a Nutanix Cloud Availability Zone (AZ) occurs, the orchestration engine can dynamically provision virtual networks to ensure recovered VMs have immediate connectivity. These networks are temporary infrastructure components required only while the workloads are running in the cloud. Once the primary on-premises site is restored and a failback is successfully executed, the VMs are migrated back to their original home. At this point, the dynamically created virtual networks at the cloud recovery site no longer host any active entities. The Nutanix orchestration engine is designed to automatically clean up these ephemeral resources (Option B) to prevent " infrastructure sprawl " and to ensure the customer is not billed for unused networking components in the cloud. This automated cleanup is a core feature of the Nutanix Cloud AZ workflow, allowing administrators to focus on stabilizing production rather than performing manual housekeeping tasks on the recovery site. This cycle of dynamic provisioning and automated cleanup ensures that the DR environment is always " right-sized " and ready for the next event.

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.

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.

Validation is a core pillar of a robust Business Continuity and Disaster Recovery (BCDR) strategy. Nutanix provides built-in orchestration through Recovery Plans, which automate the failover process of virtual machines between sites. When a " Test Failover " is executed, the system performs all the necessary steps, such as booting VMs in an isolated network, applying network mappings, and executing any custom scripts. To provide visibility into this process, Nutanix generates an automated execution report upon completion of any Recovery Plan task. This report provides a detailed chronological breakdown of every action performed by the orchestrator, including the exact start and end times for each stage (e.g., " Replication Check, " " Power On, " " IP Assignment " ). This built-in reporting is superior to manual event log filtering because it aggregates all related activities into a single, digestible summary that specifically tracks the performance of the DR plan. For leadership and compliance teams, these execution reports serve as documented proof that the RTO (Recovery Time Objective) is achievable and that every orchestrated step was validated during the test window.

Security hardening for BCDR is focused on protecting the integrity of recovery points against accidental deletion, administrative errors, or malicious intent such as ransomware. While infrastructure-level hardening like SSH keys (Option C) or host-level security (Option A) is important, they do not prevent a user with valid administrative credentials in Prism from deleting a snapshot. To address the specific requirement of ensuring only " authorized " and verified actions can modify or delete snapshots, the administrator should implement an " Approval Policy " .

An Approval Policy introduces a " four-eyes " principle for critical management tasks. When this policy is active, any attempt to delete or modify a recovery point does not execute immediately. Instead, it triggers a request in the Prism Central " Task " console and enters a " Pending Approval " state. A separate authorized user—an " Approver " —must then review the request and explicitly grant permission before the deletion can occur. This creates a vital procedural safeguard, ensuring that no single individual has the unilateral power to destroy the organization ' s backup data. By configuring this policy, the administrator hardens the DR environment against both internal threats and external actors who might gain access to a single set of admin credentials, providing a robust layer of defense for critical data assets.

The fundamental purpose of a " Test Failover " in Nutanix Disaster Recovery is to provide a non-disruptive way to validate the recovery process. During this test, virtual machines are cloned from their most recent snapshots and powered on at the recovery site. If an administrator incorrectly maps the " Test Network " to the actual " Production Network " (VLAN/Subnet) at the recovery site, they create two significant risks.

First, this configuration can lead to immediate IP address conflicts. Because the test VMs have the exact same IP addresses as the live production VMs, having them active on the same logical production network will disrupt routing and potentially cause service outages for real users. Second, it defeats the " isolation " between production and test workflows. A valid DR test should occur in a " sandbox " where test applications can crash or exhibit errors without any possibility of affecting the live environment. By using the production network, the administrator is effectively running a " live " test on the production infrastructure, which is a dangerous violation of standard BCDR best practices. To avoid these outcomes, the administrator must map the test network to a dedicated, isolated VLAN or overlay network at the recovery AZ that has no physical or logical path back to the production segment.

Self-Service Restore (SSR) is a Nutanix feature that allows end-users to recover individual files by mounting a recovery point as a local drive within the guest VM. NearSync replication provides high-frequency protection with Recovery Point Objectives (RPOs) as low as 1 minute using Lightweight Snapshots (LWS). However, there is a technical distinction in how these high-frequency points are handled for end-user recovery.

In a NearSync configuration, the system generates dozens of LWS throughout an hour. While these are available for full VM disaster recovery, Nutanix limits the " granularity " available for Self-Service Restore to manage metadata overhead and guest agent performance. By default, SSR in a NearSync environment typically supports recovery point intervals of 1 hour. This means that while an administrator can restore the entire VM to a state from 5 minutes ago, an end-user using the SSR browser inside the VM will see recovery points at 1-hour increments (the " consolidated " points). This design balances the need for high-frequency disaster protection with the operational efficiency of file-level recovery. If a user needs a file from a point between the hourly intervals, an administrator may need to perform a full VM clone or an " Out-of-place " restore to provide access to those more granular lightweight recovery points.

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.

Synchronous replication is a high-performance disaster recovery solution designed to provide a Zero Recovery Point Objective (RPO) by mirroring every write operation in real-time between two clusters. Because the system must wait for the remote site to acknowledge every write before confirming the operation to the application, the underlying storage media must be capable of extremely low-latency I/O.

On hybrid clusters that utilize both Solid State Drives (SSDs) and Hard Disk Drives (HDDs), Nutanix mandates a minimum of one SSD per node to support synchronous replication. The SSD tier is used to store metadata and provide the high-speed " Oplog " where incoming writes are initially landed before being drained to the HDD tier. If a cluster were to attempt synchronous replication using only HDDs (Option D), the mechanical latency of the spinning disks combined with the network Round Trip Time (RTT) would cause severe application performance degradation, failing the business requirement. Even though the cluster has large capacity requirements (100 TB), the presence of an SSD tier is a technical prerequisite for the software to even enable the synchronous consistency feature. Therefore, ensuring at least one SSD exists in every node of the hybrid cluster is the critical storage validation step required before implementation.