Free Practice Questions for Nutanix NCP-BC-7.5 Exam

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.

Self-Service Restore (SSR) is designed to be a temporary recovery operation. When a user uses the SSR agent to mount a historical snapshot disk, that disk is attached to the VM via the hypervisor ' s virtual controller. While it is a best practice for the user to " unmount " and " detach " the disk once they have recovered their files, the Nutanix system includes a safety mechanism to prevent these temporary disks from being left attached indefinitely.

Nutanix enforces a built-in automatic detachment timeout of 24 hours. If a disk remains attached via the SSR workflow for longer than 24 hours, the Nutanix orchestration engine will automatically trigger a detachment task to clean up the VM ' s configuration. This is essential for maintaining cluster " hygiene, " as stale snapshots attached to VMs can interfere with future backup operations, prevent VM migrations (vMotion), or lead to unnecessary storage overhead if the snapshots are kept " locked " by the attachment. Understanding this 24-hour timeout helps administrators reassure users that they have a full day to perform their recovery tasks while ensuring the infrastructure team that the environment will automatically revert to a clean state without manual intervention. This balance of user flexibility and system automation is a hallmark of the Nutanix BCDR design.

Here are questions 81 through 100 from the Nutanix Certified Professional - Business Continuity (NCP-BC) 7.5 exam set, formatted strictly as requested with detailed technical explanations for each.

Nutanix Cloud Clusters (NC2) on AWS or Azure allows for flexible disaster recovery models, including " Pilot Light " and " Zero Compute " . " Zero Compute " is a cost-effective model where data is replicated to cloud storage (like S3 or Azure Blob) without needing a running cluster at the recovery site. Multi-Site Tooling (MST) or Nutanix Disaster Recovery orchestration can be used to manage this process.

In a " Zero Compute " setup, the orchestration of an automated failover is technically complex because there is no active cluster management plane at the recovery site until the failover is triggered. A key technical requirement for successful automated failover in this model is the management of networking and IP addresses. Because the VMs are being brought up in a cloud environment that likely has a different network subnet than the on-premises environment, the system must be able to dynamically assign and manage IP addresses. Therefore, configuring an external IPAM (IP Address Management) system is a strict requirement to ensure that when VMs are restored, they receive valid networking configurations that allow them to communicate with external users and other services. Without a properly configured IPAM and network mapping in the Recovery Plan, the restored workloads would be isolated and non-functional. This highlights the need for careful network planning when designing DR strategies that utilize cloud-native storage and on-demand compute resources.

The Nutanix architecture relies on specialized services running on each Controller VM (CVM) to handle specific cluster operations. The " Cerebro " service is the primary engine responsible for data protection and replication tasks across the Nutanix cluster. It manages recovery points, snapshot schedules, and the actual transfer of data between the local cluster and remote sites. Consequently, the cerebro.INFO log file is the most vital resource for an administrator troubleshooting replication health or site-to-site connectivity. This log records critical events such as the start and completion of replication jobs, handshake failures between clusters, and timeout errors during snapshot transfers. If an administrator notices that replication is " hung " or failing consistently, cerebro.INFO provides the granular detail needed to see if the issue is a network timeout, a remote service unavailability, or a metadata synchronization error. Reviewing this log helps ensure that the connection stability is maintained and that any deviations in replication performance are identified before they impact the Recovery Point Objective (RPO). Other logs like genesis.out (Option B) are more focused on service startup and configuration rather than the ongoing health of the BCDR replication stream.

Nutanix Volume Groups (VGs) provide block-level storage to virtual machines, often used for high-performance databases or shared storage clusters. Unlike standard vDisks, which are managed directly as part of the VM ' s hardware definition, VGs are presented as iSCSI targets. In a Disaster Recovery scenario, when a VM is recovered at a new site, it must be able to " find " and re-attach these Volume Groups to resume operation.

For this attachment to succeed, especially across different clusters or into a Nutanix Cloud AZ, both the source and recovery clusters must have a " Data Services IP Address " configured. The Data Services IP acts as the cluster-wide iSCSI target portal. When a VM fails over, the Nutanix orchestration engine uses this IP to coordinate the iSCSI login and mapping of the Volume Group to the guest OS. If this IP is missing on either cluster, the internal iSCSI redirection and handoff mechanisms will fail, even if the general management networking and Protection Policies are perfectly healthy. This is a common " Day 1 " configuration error because management connectivity (Prism) works without a Data Services IP, but block-level services like VGs and certain NGT features strictly require it. Verifying and configuring the Data Services IP at both availability zones is the primary fix for Volume Group attachment failures during DR failover.

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.

Synchronous replication environments (like Metro Availability) allow for zero-RPO failover, but the performance of the workload is highly dependent on " Data Locality " . Nutanix architecture is built on the principle that a VM ' s compute (vCPU/RAM) should ideally reside on the same host or cluster that serves its primary storage I/O.

During a storage failover, the " Active " container role may move to the recovery site, but the virtual machines might still be running on the primary site ' s compute nodes. This causes " Remote I/O, " where every read and write must traverse the network link to reach the active storage container at the other site, resulting in the reported higher latency and degraded performance. To resolve this, the administrator must " realign " the compute and storage by performing a vMotion (or live migration) of the VMs to the cluster that is now hosting the active storage role. While the Acropolis Dynamic Scheduler (ADS) (Option D) eventually attempts to rebalance, a manual realignment ensures that performance is restored immediately after the failover stabilization. Reconfiguring schedules (Option C) or retention (Option A) has no impact on real-time I/O latency, highlighting the critical role of data locality in high-performance BCDR designs.

Nutanix Self-Service Restore (SSR) allows end-users to recover files from snapshots without needing assistance from a cluster administrator. This functionality is enabled by Nutanix Guest Tools (NGT), which mounts a snapshot disk to the guest VM. For SSR to function, the Nutanix Guest Agent (NGA) must be able to recognize and mount the file systems present on the snapshots.

For Linux-based virtual machines, Nutanix SSR supports standard, modern journaling file systems. EXT4 is the most widely supported and common file system used across modern Linux distributions like RHEL, CentOS, and Ubuntu, and it is natively supported by the Nutanix SSR agent. While other file systems like XFS or older EXT versions might be supported by the OS itself, EXT4 is the primary validated target for SSR operations. NTFS (Option B) is primarily a Windows file system, though it can be mounted on Linux, it is not the native standard for Linux SSR. Supporting the native file system of the guest OS is critical because it ensures that file permissions and ownership (UID/GID) are preserved during the recovery process. This compatibility allows users to seamlessly mount the snapshot, navigate to the required directory, and restore deleted or corrupted files directly to their production environment.

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.

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.