Score Higher on Verified NCP-BC-7.5 | Nutanix Certified Professional - Business Continuity (NCP-BC) 7.5 Exam Questions with Answers

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 storage is often accessed by external backup solutions (like Veeam, Commvault, or HYCU) using the iSCSI protocol. This allows the backup server to mount snapshots and read data directly from the storage tier. The error message " iscsiadm... discovery... timeout " specifically indicates that the backup server ' s iSCSI initiator is unable to communicate with the Nutanix Data Services IP or the Controller VMs (CVMs) over the network.

When a Nutanix cluster is expanded, it is essential that all networking and firewall configurations applied to the existing nodes are also applied to the new nodes. The iSCSI protocol relies on specific TCP ports: port 3260 is the standard port for iSCSI traffic, and port 3205 is often used for iSCSI discovery and metadata operations within Nutanix. If these ports are not open in the physical firewall or the host-based security rules for the newly added nodes, the backup server will be unable to discover the targets on those specific nodes, leading to the timeout errors . This highlights a common " Day 2 " operational trap: cluster expansion requires careful auditing of network security groups and firewall whitelists to ensure that external integrations—especially BCDR and backup services—continue to have uninterrupted access to the expanded storage fabric. Verifying and opening ports 3205 and 3260 for the new node IPs is the first step to resolving this timeout issue.

Cross-Cluster Live Migration (CCLM) is an advanced Nutanix feature that allows a running virtual machine to move between two geographically separated clusters without downtime. When migrating between on-premises and a public cloud Nutanix Cloud Cluster (NC2), maintaining the VM ' s network identity (IP address) is often a critical requirement for application continuity.

Standard routing across different networks would require the VM to change its IP to match the destination subnet. To avoid this, an administrator must implement " Layer 2 (L2) stretching " . L2 stretching (often achieved using Nutanix Flow Virtual Networking and VXLAN/VPN tunnels) creates a unified broadcast domain that spans both the on-premises and cloud sites. This allows the VM to move to the cloud while remaining on the same logical subnet, meaning its default gateway and IP address remain valid. Without L2 stretching, a " Live Migration " would fail the moment the VM moved to the new cluster because its network connections would drop. This configuration is a prerequisite for seamless hybrid cloud mobility, enabling businesses to leverage cloud burst capacity or perform zero-downtime maintenance across sites.