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

Disaster recovery orchestration in the Nutanix environment often involves the pairing of two separate Availability Zones (AZs), each managed by its own Prism Central instance. For these two management planes to communicate, exchange metadata, and synchronize Protection Policies and Recovery Plans, specific firewall ports must be open between them.

Port 9440 is the standard port used for all Prism Central and Prism Element web interface and API traffic. During the AZ pairing process, the primary Prism Central must reach the recovery Prism Central ' s API to establish the trust relationship and pair the sites. Other ports mentioned, such as 2009 (Option A) and 2020 (Option B), are used for data replication between Controller VMs (CVMs) but are not used for the initial management-plane pairing between Prism Central instances. Port 2074 (Option C) is typically used for Nutanix Guest Tools (NGT) communication with the cluster. Therefore, ensuring port 9440 is open between the two Prism Central instances is a mandatory prerequisite for successful disaster recovery site pairing.

Nutanix Disaster Recovery offers several replication tiers to meet varying business Recovery Point Objectives (RPOs). NearSync replication is a specific technology designed to fill the gap between traditional Asynchronous replication and zero-RPO Synchronous replication.

NearSync replication supports a minimum RPO of 1 minute. It achieves this by using Lightweight Snapshots (LWS), which are highly efficient and can be taken much more frequently than standard full snapshots without causing significant I/O overhead on the system. While some versions of Nutanix software allow NearSync to reach RPOs as low as 20 seconds, the standard minimum RPO recognized in the context of the NCP-BC 7.5 evaluation for minutes-based intervals is 1 minute. Option A (0 RPO) is only achievable through Synchronous replication. Option C (15 minutes) is the typical maximum RPO for NearSync before it transitions to Async, and Option D (60 minutes) is the standard interval for Asynchronous replication. Understanding these thresholds is essential for administrators when designing protection policies for mission-critical workloads.

Disaster recovery success depends on the stability of the network link and the health of the services responsible for data replication. Nutanix Cluster Check (NCC) is the primary native health-monitoring tool for the Nutanix environment. NCC includes a comprehensive suite of checks specifically designed for Data Protection and BCDR.

During disaster recovery setup or testing, an administrator can run NCC to verify that the clusters are correctly paired, that remote site connectivity is functional, and that the required ports (such as 2009 and 2020) are open and reachable. Specific NCC checks like remote_site_connectivity_check or replication_health_check provide granular insights into whether the " handshake " between the primary and recovery sites is succeeding. While acli (Acropolis CLI) or ecli (Erasure Coding CLI) are used for managing VMs or storage disks, they do not provide the high-level diagnostic capabilities of NCC. By regularly running NCC, an administrator can proactively identify connectivity issues—such as firewall changes or routing failures—that could otherwise lead to replication failures and compromise the organization ' s recovery objectives.

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.

In Nutanix Disaster Recovery using Protection Domains (PDs), " Activate " is a high-level command used to promote a remote site to an active state. This is typically reserved for an unplanned failover scenario when the primary site is completely offline. If an administrator mistakenly uses " Activate " for a test instead of the proper " Test Failover " workflow, the secondary cluster will begin treating the replicated snapshots as active, live virtual machines. This process involves promoting the storage and registering the VMs to the local hypervisor.

To return to a steady state where the production cluster is the only active site, the administrator must perform a cleanup on the DR cluster. The " Deactivate " command on the DR cluster serves two main purposes: it changes the Protection Domain status from " Active " back to " Standby " and provides an option to " Destroy VMs " associated with that PD. Choosing to destroy the VMs on the DR cluster is essential to prevent duplicate VM instances or IP address conflicts when production resumes. Simply deleting the VMs manually (Option C) is insufficient because it does not reset the PD ' s metadata status in the Nutanix Cerebro service. By deactivating the PD and destroying the VMs at the DR site, the administrator ensures that the DR site returns to its role as a passive replication target, allowing the primary production cluster to continue its operations without being impacted by the accidental activation.

Nutanix Asynchronous (Async) replication is a foundational data protection technology that allows for the periodic transfer of virtual machine snapshots from a primary cluster to a remote site. When using Async replication between two ESXi-based Nutanix clusters, the primary objective is data persistence rather than deep integration with the vSphere management hierarchy. Because Async replication operates at the storage level, it captures the virtual disk (vDisk) data and the VM ' s configuration files (.vmx) but does not natively synchronize the logical inventory metadata maintained by the vCenter Server, such as VM folders, resource pools, or specific vApp configurations.

When a failover is executed, the Nutanix cluster registers the VM to the remote ESXi host and vCenter. Since the inventory mapping details (original folder and resource pool) are not part of the standard Async replication payload, the vCenter Server treats the failing-over VM as a new registration and places it into the default root folder and the default cluster resource pool. To maintain consistent organizational structures during a disaster recovery event, administrators typically rely on Prism Central-based " Recovery Plans. " Recovery Plans offer advanced orchestration that allows for the manual definition of inventory mappings, ensuring that VMs are placed in the correct folders and resource pools upon recovery. Understanding this limitation of legacy Async replication is crucial for administrators designing BCDR solutions that require high levels of organizational consistency post-failover.

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.

Nutanix Guest Tools (NGT) is a software bundle that must be installed on the guest virtual machine (VM) to enable advanced management and data protection features within the Nutanix ecosystem. For the specific functionality of Self-Service Restore (SSR), NGT provides the necessary communication drivers and the Nutanix SSR agent. This agent allows end-users or administrators to mount recovery point snapshots as local drives directly within the guest operating system. Without NGT, the cluster lacks the specialized hooks into the guest OS required to perform granular file-level recovery without restoring the entire VM. Furthermore, NGT facilitates the creation of application-consistent snapshots by interacting with the Windows Volume Shadow Copy Service (VSS), which is often a prerequisite for high-integrity backups of Tier-1 applications like SQL Server or Exchange. By installing NGT, the VM is granted the intelligence to browse and attach historical vDisks, effectively enabling the SSR workflow and reducing the operational burden on the infrastructure team for simple file recovery requests.

Maintaining " predictable and consistent " IP addresses during a failover to a public cloud environment like Nutanix Cloud Clusters (NC2) on Azure is a common requirement for multi-tier applications that rely on static IP references.

To achieve this level of precision, the administrator should configure " Custom VM IP Mapping " within the Nutanix Recovery Plan. This feature allows the administrator to explicitly define the exact IP address that each VM should receive upon recovery at the destination site. While some Nutanix network configurations attempt to preserve the " last octet " of an IP address (Option C), this is not always possible or predictable in a cloud environment with existing subnets. Relying on default IPAM behavior (Option A) often results in dynamic, unpredictable assignments. Using in-guest NGT scripts (Option D) is an overly complex and manual workaround that is natively superseded by the Recovery Plan ' s IP mapping feature. By using custom IP mapping, the administrator ensures that the database, application, and web tiers all come up with the exact addresses required for the application to function immediately without manual intervention.

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.