NCP-BC-7.5 Dumps with Practice Exam Questions Answers

VM-VM Anti-Affinity rules are used in Nutanix to ensure that specific virtual machines (such as the nodes of a database cluster or redundant web servers) never run on the same physical host, thereby protecting the application from a single host failure. These rules are typically managed through Prism Central (PC) in a modern deployment.

However, in the context of Disaster Recovery (DR) between two different clusters or availability zones, there is a technical limitation regarding the replication of these affinity policies. While the virtual machine ' s data and primary metadata (CPU, RAM, Disks) are replicated by the Cerebro service, the affinity rules are often considered local cluster constraints. In many versions of Nutanix Disaster Recovery (specifically the initial iterations of Leap/Prism Central-based DR), these affinity policies are not natively " synchronized " or enforced at the recovery site during a failover. This means that when the VMs are recovered at the destination cluster, the hypervisor ' s dynamic scheduler (ADS) may place them on the same host if that host has the most available resources. To maintain anti-affinity at the recovery site, an administrator would typically need to manually recreate the affinity policies at the destination AZ or use specialized orchestration scripts. Understanding this limitation is vital for ensuring that high-availability requirements are still met after a disaster recovery event has occurred.

In a Nutanix Disaster Recovery context, choosing the right failover type is critical during a ransomware event. A " Planned Failover " is designed for maintenance scenarios. Its first step is to synchronize the current data state to the recovery site to ensure zero data loss. In a ransomware attack, the " current state " is encrypted or corrupted data. If an administrator performs a Planned Failover at 2:45 AM, the system will capture and replicate the encrypted files, effectively " backing up " the ransomware to the recovery site.

To successfully recover from ransomware, the administrator must perform an " Unplanned Failover. " Despite the name, this failover type is the correct choice for this scenario because it allows the administrator to manually select a historical recovery point from the destination cluster ' s storage. By choosing a recovery point from 1:00 AM (before the attack began), the administrator can restore the virtual machines to a known-good, unencrypted state. This is a primary use case for maintaining a multi-day or multi-week snapshot retention policy. While a " Test Failover " (Option A) could be used to verify the 1:00 AM snapshot in an isolated network first, the ultimate production recovery is achieved via an Unplanned Failover that specifically targets a point-in-time snapshot that predates the infection.

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.

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.