Nutanix Nutanix Certified Professional - Business Continuity (NCP-BC) 7.5 NCP-BC-7.5 Exam Dumps: Updated Questions & Answers (April 2026)

Nutanix Disaster Recovery (formerly Leap) utilizes a " policy-driven " approach where virtual machines are protected based on assigned " Categories " rather than individual VM names. This allows for automated protection: any VM tagged with a specific category (e.g., App:Web) is automatically picked up by the associated Protection Policy. When existing VMs are replicating fine but new ones are not, and there are no network or storage errors, the root cause is almost always an administrative oversight during provisioning.

If the separate team that deployed the VMs followed a checklist that didn ' t include category assignment, those VMs exist as " unprotected entities " in the eyes of Prism Central. The Protection Policy will ignore them because they do not match the entity selection criteria defined in the policy ' s configuration. To resolve this, the administrator must simply apply the correct category to the new VMs. Once tagged, the Cerebro service will identify the new members during its next scan and initiate the initial full seed replication to the recovery site. This scenario highlights the critical need for cross-team coordination and the use of automated deployment tools (like Nutanix Self-Service or Calm) to ensure that security and BCDR requirements are applied consistently during the VM lifecycle.

Nutanix Metro Availability is a continuous availability solution that provides a zero Recovery Point Objective (RPO) and near-zero Recovery Time Objective (RTO) across two sites. For this configuration, there are two distinct latency requirements that administrators must manage. First, the Round Trip Time (RTT) latency between the two storage clusters participating in the synchronous replication must be less than 5ms to ensure application performance is not significantly degraded by the write-synchronization process. Second, the Witness VM, which acts as an external arbitrator to prevent " split-brain " scenarios during a site failure, has a more flexible latency requirement. The maximum RTT between the Witness VM and the managed Protection Domains (PDs) must be less than 200ms. This higher threshold allows the Witness to be placed in a separate geographical region or a third-party cloud availability zone (AZ), ensuring it remains independent of the failure domain affecting the primary and secondary sites. If the latency to the Witness exceeds 200ms, the cluster may be unable to quickly acquire the lock necessary to automate failover, potentially causing the Metro Availability configuration to fail during an actual disaster event.

Volume Groups (VGs) are used in Nutanix to provide block storage to virtual machines, often for high-performance applications like SQL Server. VGs can be attached to VMs in two ways: " In-guest " (using iSCSI initiators) or " Hypervisor-attached " (where the hypervisor handles the connection).

In a disaster recovery scenario managed by Recovery Plans, there is a technical distinction in how these attachments are handled. While Nutanix Disaster Recovery can replicate the data in the Volume Groups and recover the VM itself, VGs that are " hypervisor-attached " do not currently support automatic reattachment as part of the orchestration workflow in all AOS versions. When the failover completes, the VM powers on at the recovery site, but the VGs are not connected to the VM at the hypervisor level. This causes the application (SQL) to find its data disks missing, resulting in the database staying offline. To resolve this, the administrator must manually reattach the Volume Groups to the VM at the recovery site using the Prism interface or a script. This limitation highlights the need to verify specific application storage configurations during DR testing. For automated recovery of VGs, using " In-guest " iSCSI attachments is often preferred because the iSCSI initiator within the guest OS can re-establish the connection to the new cluster ' s Data Services IP once the network is active.

Failing over to Nutanix Cloud Clusters (NC2) on AWS involves moving workloads from a local, on-premises networking environment into a cloud-native Virtual Private Cloud (VPC). While Nutanix Flow Virtual Networking (FVN) allows the VMs to keep their internal IP addresses using overlay networks, external visibility requires integration with AWS networking components.

Standard internal IP addresses in an overlay network are not natively routable from the public internet or from the AWS VPC outside of the NC2 cluster. To bridge this gap, Nutanix uses " Floating IPs " . A Floating IP is an AWS Elastic IP that is mapped to the internal IP of the guest VM. When an external user attempts to reach the website, the traffic hits the AWS public-facing Floating IP, which is then translated and routed through the NC2 bare-metal nodes to the specific guest VM. This mapping can be automated as part of the Recovery Plan or configured manually post-failover. Without this configuration, the VMs will remain " isolated " from external traffic, even if the application is running perfectly and internal cluster connectivity is healthy. This demonstrates the importance of cloud-native networking knowledge when extending on-premises BCDR plans into public cloud environments like NC2.

Cross-Hypervisor Disaster Recovery (CHDR) allows for the seamless replication and failover of workloads between different hypervisor platforms, such as moving from VMware ESXi to Nutanix AHV. The primary technical challenge in CHDR is ensuring that the virtual machine has the correct storage and network drivers to boot on the new hypervisor. For instance, a VM running on ESXi uses VMware-specific drivers, while AHV requires Nutanix VirtIO drivers.

Nutanix Guest Tools (NGT) is the mandatory component that handles this translation process automatically. When NGT is installed on a VM running on ESXi, it includes the necessary Nutanix drivers in a dormant state. During a failover to an AHV cluster, the Nutanix orchestration engine uses the NGT hooks to inject and activate these drivers, ensuring the VM can successfully recognize its virtual disks and network adapters upon power-on at the recovery site. Without NGT, the VM would likely suffer a " Blue Screen of Death " (BSOD) on Windows or a kernel panic on Linux due to the missing boot drivers. While manual VirtIO installation (Option A) is possible, NGT provides the integrated orchestration required for a reliable, automated BCDR workflow, making it the essential component for CHDR success.

Nutanix Recovery Plans allow for granular control over networking during different failover scenarios. The " Test Network " setting is specifically designed to provide an isolated sandbox for validation. If an administrator incorrectly maps this test network to the actual " Production Network " VLAN at the recovery site, they are effectively bypassing the safety mechanisms intended to isolate the test.

When the Test Failover is executed, the test VMs will boot up on the production VLAN using the exact same IP addresses they have at the source site. If the primary site is still online (which is the case during a test), the existence of two identical VMs with identical IPs on the same logical network will cause immediate IP address conflicts. This can disrupt live production traffic, cause routing instability, and potentially lead to service outages at both sites. The system does not " automatically " isolate traffic (Option B) if the administrator has explicitly directed the test VMs to the production segment. This scenario emphasizes the critical importance of network planning in BCDR: a " Test " network must always be an isolated, non-routable segment to ensure that validation remains non-disruptive as intended.

In modern Nutanix Disaster Recovery (using Prism Central-based Protection Policies), storage placement is often governed by Storage Policies rather than simple container-to-container mapping. Storage Policies use Nutanix Categories to determine where a VM should be placed to meet performance or compliance requirements. In this scenario, the VMs were successfully replicated and recovered, but they were placed in " all the storage containers " rather than the intended FIN-PROD container at the Marseille site. This indicates that while the data arrived, the " destination placement rules " were missing. If a storage policy was created on the Paris cluster to keep these VMs in FIN-PROD but that policy was not mirrored or assigned at the Marseille cluster, the system defaults to the Acropolis Dynamic Scheduler (ADS) placement. ADS will distribute the VMs across all available containers to balance load and capacity, leading to the " scattered " result observed. To resolve this and ensure consistent failover behavior, the administrator must ensure that both the categories and the corresponding storage policies are identical and active at both availability zones. While a missing container (Option C) would typically cause a replication failure rather than scattered recovery, a missing storage policy specifically explains the lack of orchestrated placement during the failover event.

In a Nutanix environment, " Advertised Capacity " is a logical limit (a quota) that an administrator can set on a specific storage container. Even if the physical storage pool has terabytes of free space, if a container ' s advertised capacity is reached, the hypervisor and the Nutanix services will perceive the container as being 100% full.

In this troubleshooting scenario, the " nfs status 28 " error code is a standard indicator for " No space left on device " . Since the administrator confirmed the pool is healthy, the logical limit on the container is the only remaining bottleneck. Replication jobs will " hang " because the destination Stargate service cannot write the incoming data blocks to a container that reports zero free space. To resolve this, the administrator must either increase the advertised capacity value in Prism or remove the limit entirely to allow the container to consume the available physical space in the pool. This highlights a common configuration " trap " where logical quotas—intended for multi-tenant management—can inadvertently block critical BCDR processes like replication if not monitored or sized correctly according to the protected VM growth.

An " Unplanned Failover " is triggered when the primary site is completely offline or unreachable due to a disaster. Because the primary site cannot be contacted to perform one last synchronization of data, the recovery must rely on the recovery points that were successfully replicated to the destination cluster before the outage occurred.

In this scenario, the worst-case data loss is equivalent to the Recovery Point Objective (RPO) defined in the Protection Policy. For example, if the RPO is set to 1 hour, and the disaster occurs 59 minutes after the last successful replication, the business will lose 59 minutes of data. By default, the Nutanix orchestration engine will automatically select and use the most recent recovery point available at the recovery site to restore the virtual machines. While an administrator can manually choose an older recovery point if needed (e.g., in the case of a ransomware attack), the default behavior is to minimize data loss by using the newest available point. This highlights why setting an appropriate RPO is the most important design decision for managing potential data loss in an unplanned failure event.

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.