NCP-BC-7.5 Nutanix Certified Professional - Business Continuity (NCP-BC) 7.5 Questions and Answers

Nutanix offers several ways to recover data, ranging from full VM reverts to granular file-level access. In this scenario, the key requirement is to access historical data (from four days ago) without modifying or destroying the current production VM ' s state. Self-Service Restore (SSR) is the most efficient and least disruptive method to achieve this. SSR, which requires Nutanix Guest Tools (NGT) to be installed, allows an administrator or user to mount a historical snapshot disk directly to the existing VM as a new, temporary volume. This allows the QA team to browse the file system of the " four-day-old " state and copy the specific older browser version they need while the production application continues to run undisturbed with its new code and patches. An " In-place Restore " (Option C) would be disastrous here because it would roll back the entire VM, overwriting the new patches. A " Clone " (Option D) would work but is less efficient as it consumes additional vCPU, RAM, and full storage overhead for an entirely new VM. SSR provides the surgical precision needed for file-level testing while maintaining the integrity of the live production environment.

An In-place Restore (Revert) is the fastest way to roll back a VM because it overwrites the current vDisks with the data from the snapshot. However, this operation has strict requirements regarding the consistency of the VM ' s hardware configuration. The most common technical blocker for an in-place revert is a change in the disk topology between the time the snapshot was taken and the time of the restore.

If the administrator added a new 50GB data disk (Option D) after taking the snapshot, the VM ' s current configuration now includes a vDisk that does not exist in the snapshot ' s metadata. Nutanix AOS cannot " revert " a disk that has no point-in-time reference in the recovery point. In this situation, the " In-place Restore " button is typically disabled or will throw an error, forcing the administrator to use the " Clone " (Out-of-place) option. Cloning creates a new VM based exactly on the snapshot ' s metadata, effectively ignoring the newly added disk. While changing memory (Option B) or NGT versions (Option A) might affect performance or guest features, they do not usually prevent the storage-level revert operation. Being forced into a " Clone " restore increases the RTO slightly, as the administrator must then delete the corrupted VM and ensure the new clone has the correct network settings.

Nutanix Disaster Recovery to the Cloud is built on the principle of automation and resource optimization. When a failover to a Nutanix Cloud Availability Zone (AZ) occurs, the orchestration engine can dynamically provision virtual networks to ensure recovered VMs have immediate connectivity. These networks are temporary infrastructure components required only while the workloads are running in the cloud. Once the primary on-premises site is restored and a failback is successfully executed, the VMs are migrated back to their original home. At this point, the dynamically created virtual networks at the cloud recovery site no longer host any active entities. The Nutanix orchestration engine is designed to automatically clean up these ephemeral resources (Option B) to prevent " infrastructure sprawl " and to ensure the customer is not billed for unused networking components in the cloud. This automated cleanup is a core feature of the Nutanix Cloud AZ workflow, allowing administrators to focus on stabilizing production rather than performing manual housekeeping tasks on the recovery site. This cycle of dynamic provisioning and automated cleanup ensures that the DR environment is always " right-sized " and ready for the next event.

In Nutanix Protection Domains, the relationship between a virtual machine and a snapshot is tied to the metadata at the time the snapshot was created . When an administrator removes a VM from a PD (Option B), the cluster stops taking new snapshots, but the historical snapshots (recovery points) remain in the storage system until their retention period expires .

If a disaster or corruption occurs (Option Wednesday), the administrator can still use those historical snapshots to perform a " Revert " operation. The Nutanix AOS engine can successfully roll back the VM ' s vDisks to the Monday state because the data exists. However, the " Revert " operation only impacts the data on the disks; it does not re-establish the logical configuration of the Protection Domain. Because the VM was explicitly removed from the PD on Tuesday, the system treats it as an " unprotected " VM after the restore is finished. It will not be included in the next scheduled snapshot cycle of PD_Production. To resume ongoing protection, the administrator must manually add the Inventory-VM back into the PD_Production Protection Domain. This scenario illustrates a critical operational point: restoring data does not automatically restore the protection schedule, and administrators must verify the " Protection Status " of VMs following any manual recovery task to ensure they are not left vulnerable to future failures.

In a Business Continuity strategy, " downtime " can be categorized as either unexpected (disaster) or controlled (maintenance). When an administrator knows that a disruption is coming, such as scheduled network maintenance on a primary cluster, they should utilize the " Planned Failover " mechanism within the Nutanix Recovery Plan.

A Planned Failover is a graceful, orchestrated migration. It first shuts down the virtual machines at the primary site to ensure all data is flushed and no new writes occur. It then performs a final synchronization to the recovery site to ensure zero data loss (Zero RPO), and finally powers the VMs on at the destination site according to the plan ' s sequence. This differs significantly from an " Unplanned Failover " (Option A), which assumes the primary site is already offline and may result in minor data loss depending on the last successful replication. A " Test Failover " (Option D) merely validates the process in an isolated environment and does not move the actual production workload. By executing a Planned Failover before the maintenance begins, the administrator ensures that the services are safely running on the target cluster, maintaining application availability and meeting the objective of zero downtime during the maintenance window.

Virtual GPUs (vGPUs) are hardware-dependent resources that are tied to specific physical GPU cards installed in the Nutanix nodes. While Nutanix Disaster Recovery can replicate the VM ' s virtual disks and general configuration, the specific mapping to a physical vGPU profile is often not automatically preserved across clusters due to potential differences in hardware availability or GPU generations at the recovery site.

When the VM fails over and boots up at the secondary site, the guest OS may see the NVIDIA driver but will find that the " backed " hardware resource is missing or incorrectly mapped, leading to a failure in hardware acceleration. To resolve this, the administrator must manually edit the VM ' s hardware settings at the recovery site and re-assign a compatible vGPU profile from the local cluster ' s available GPU resources. This post-failover cleanup task is essential for workloads like VDI (Virtual Desktop Infrastructure) or CAD applications that depend on GPU processing. Relying on NGT (Option A) or reinstalling the OS (Option B) will not fix the underlying missing hardware assignment in the hypervisor, highlighting the need for specialized knowledge when protecting VMs with specialized hardware pass-through or vGPU requirements.

Nutanix supports software-based data-at-rest encryption for AHV workloads. This encryption is typically managed through " Storage Policies " in Prism Central, which are applied to virtual machines based on their " Categories " . For example, a policy might state that any VM in the Compliance:Encrypted category must have its data encrypted on the disk.

When a failover occurs, the VM moves to the recovery cluster. While the data that was replicated is already encrypted, the " Active " Storage Policy at the recovery site must be verified. If the recovery cluster does not have the same Storage Policy configuration or if the VM-to-Policy association was lost during the transition, the AOS storage engine at the recovery site will treat the VM as a standard, non-encrypted workload. This results in " newly written data " (writes occurring after the failover) being stored in plain text. To fix this, the administrator must " reassign " or refresh the Storage Policies and Categories at the recovery site. This ensures that the encryption rules are actively enforced on the new cluster, maintaining the organization ' s security posture post-disaster. This cleanup step is vital for compliance-heavy environments where encryption-at-rest is a mandatory requirement.

Application-consistent snapshots are critical for ensuring data integrity for transactional workloads, such as databases. In a Nutanix AHV or ESXi environment, the cluster achieves application consistency by communicating with the guest operating system ' s Volume Shadow Copy Service (VSS). This communication is facilitated exclusively through Nutanix Guest Tools (NGT). When NGT is installed and enabled, it provides a VSS hardware provider that Nutanix uses to " quiesce " (pause/stabilize) the application ' s I/O and flush pending writes to the disk before the snapshot is taken. If crash-consistent snapshots are working but application-consistent ones are failing, it is a primary indicator that the VSS hooks provided by NGT are either missing, outdated, or not communicating correctly with the Nutanix cluster services. Without NGT, the system cannot verify the internal state of the guest OS, leading to VSS processing errors in third-party backup solutions like Veeam or Commvault. Ensuring NGT is installed and the NGT agent is running within the guest VM is the mandatory first step to resolving any snapshot failure involving application-level consistency.

Migrating from legacy Protection Domain (PD) based management to the modern Prism Central (PC) based Protection Policies is a recommended best practice for scaling Nutanix Disaster Recovery. This migration involves moving VMs from a " Prism Element " centric management model to a centralized, category-based model in Prism Central.

To ensure that no data is lost during this transition, the most critical prerequisite is to verify that a successful, full replication (backup) of the Protection Domain has recently completed. This ensures that the recovery site already possesses a complete and consistent set of data for the VMs before they are unlinked from the old policy and attached to the new one. While adding VMs to a category (Option A) is a step in the process, it is not the first verification step required for data safety. If an administrator attempts to migrate while a replication is incomplete or failing, the transition to the new policy might leave the VMs unprotected for an extended period, or recovery points might be missing if a disaster occurs mid-migration. By completing a full backup of the PD first, the administrator creates a " safety net " of recovery points that can be used if the migration itself encounters issues. This ensures that the transition to modern DR is performed with minimal risk to the business ' s data protection objectives.

Hardening a Nutanix cluster for Business Continuity involves implementing security controls that protect recovery data from unauthorized destruction. In many modern cyberattacks, specifically ransomware, the goal is not just to encrypt production data but also to delete the snapshots and backups that would allow for recovery. To satisfy the requirement that only authorized modifications occur, the administrator must move beyond simple Role-Based Access Control (RBAC) and implement an " Approval Policy " .

The Approval Policy feature in Prism Central forces a secondary layer of validation for sensitive operations like snapshot deletion. When a user tries to delete a recovery point, the Nutanix orchestration engine captures the request and holds it in a " Pending " state. The request must be reviewed and approved by a designated person with approval authority. This ensures that even if an administrator ' s account is compromised, the attacker cannot immediately wipe out the snapshots needed to restore the environment. This " multi-person control " is a recognized security best practice for protecting mission-critical data. While cluster lockdown (Option C) prevents unauthorized SSH access, it does not manage the logical management of data through the Prism UI. An Approval Policy provides the specific " modification and deletion " control requested, ensuring that the cluster ' s recovery points remain a reliable " source of truth " following a security incident or administrative error.

Network segmentation is a powerful Nutanix feature used to isolate replication and storage traffic from standard management traffic. However, implementing this in a " brownfield " environment—where replication is already active—requires careful coordination. In this scenario, the replication failure coincides with the implementation of network segmentation and new firewall rules. The administrator ' s first action must be to verify if segmentation was enabled while replication was actively running. If segmentation is enabled on one site without a matching configuration on the remote cluster, or if the services (Cerebro/Stargate) were not properly restarted to bind to the new interfaces, the replication stream will " hang " . Furthermore, enabling segmentation changes the source and destination IP addresses used for replication traffic. If these new segmented IP addresses were not whitelisted in the recent firewall hardening effort, all " Snapshot-on-wire " traffic will be dropped. By verifying the segmentation state first, the administrator can determine if the network plumbing is consistent across both sites. Recreating policies (Option A) or triggering failover (Option C) would not resolve an underlying network isolation issue and would likely result in further failures until the segmentation and firewall rules are properly aligned.

Single Root I/O Virtualization (SR-IOV) allows a virtual machine to bypass the hypervisor ' s virtual switch and communicate directly with a physical network adapter ' s virtual functions. This is commonly used for high-performance applications that require extremely low latency and high throughput. However, SR-IOV creates a " hard " dependency between the virtual machine and the specific physical hardware (NIC) of the host it is running on.

Disaster Recovery involves moving a VM to an entirely different cluster, which likely has different physical network adapters or a different SR-IOV configuration. Nutanix Disaster Recovery orchestration is designed to ensure that VMs can always boot at the recovery site, even if specialized hardware resources are unavailable. For VMs configured with SR-IOV, the recovery process includes a built-in fallback mechanism. During failover, the system will recover the VM and power it on, but it will disable the SR-IOV attachment. To ensure connectivity, it automatically adds or falls back to a standard virtio-net virtual adapter. This allows the VM to have network access immediately, though at a potentially lower performance level. The administrator must then manually re-configure SR-IOV at the recovery site if the local hardware supports it. This design prioritizes service availability (powering on and communicating) over specialized hardware performance during a disaster recovery event.

Migrating from legacy Protection Domains to modern Prism Central Protection Policies involves transitioning the management of virtual machine snapshots. During this process, the historical snapshots created by the Protection Domain are often intended to be " claimed " or utilized by the new PC-based system as valid recovery points.

Snapshots are point-in-time references to data on the storage tier. If a snapshot is deleted from the cluster before the migration to Protection Policies is finalized, the underlying data blocks associated with that specific point in time may be reclaimed by the system ' s garbage collection process. Consequently, the recovery points that were associated with that deleted snapshot will no longer be available for use within the new deployment. The system cannot " automatically recreate " (Option A) a deleted snapshot because the exact historical state of the data is lost once the snapshot is purged. The migration itself typically continues for the remaining valid data, but the loss of historical recovery points could impact the business ' s ability to restore to specific past dates. This highlights the importance of data retention awareness during management-plane migrations.

Replication in a Nutanix environment always begins with an " initial seed " . This first replication task is a full, 1-to-1 copy of all the data blocks currently occupied by the virtual machines on the source cluster. Unlike subsequent incremental snapshots—which only transfer the changed blocks—the initial seed requires sufficient physical or logical space at the destination to hold the entire data set of the protected VMs.

In this scenario, the administrator attempted to protect 4TB of virtual machine data but restricted the destination container ' s capacity to a mere 200GB. Because the destination container reports only 200GB of available space, the replication job will immediately stall or fail to progress as soon as the incoming data stream exceeds that limit. Nutanix replication requires a " landing zone " that can accommodate the full size of the initial snapshot before it can begin the process of data reduction (like compression or deduplication) at the remote site. To fix this, the administrator must increase the advertised capacity of the VMData container on Cluster B to at least 4TB (plus overhead for future growth and snapshots) to allow the initial full seed to complete successfully, thereby establishing the baseline for the BCDR protection schedule.

Replication between Nutanix clusters involves the transfer of both actual data blocks and the metadata required to manage the consistency and scheduling of those snapshots. Two specific services running on the Controller VMs (CVMs) are responsible for these tasks: Stargate and Cerebro.

Port TCP 2009 is used by the Stargate service. Stargate is the primary I/O manager for the Nutanix cluster, and in a BCDR context, it handles the " Snapshot-on-wire " data transfer. This is the port where the actual bits of the virtual disks are sent from the source cluster to the destination cluster. Port TCP 2020 is used by the Cerebro service. Cerebro is the replication engine that handles protection domain orchestration, snapshot scheduling, and cross-site handshake operations. Without port 2020, the clusters cannot synchronize their schedules or confirm that a recovery point has been successfully stored at the remote site. While other ports like 9440 (Prism management) and 22 (SSH) are used for administrative tasks, ports 2009 and 2020 are the mandatory " data path " and " control path " ports required for the continuous and successful replication of workloads between availability zones.

Nutanix supports two main types of snapshots: crash-consistent and application-consistent. A crash-consistent snapshot is taken at the storage layer without any awareness of the guest OS state; it is equivalent to pulling the power plug on a server. An application-consistent snapshot is more complex because it requires the Nutanix cluster to " quiesce " the applications (such as SQL Server or Exchange) inside the guest OS, flushing pending writes to disk to ensure data integrity.

To perform this quiescence on Windows VMs, the Nutanix cluster must communicate with the Windows Volume Shadow Copy Service (VSS). This communication is handled exclusively by Nutanix Guest Tools (NGT). If NGT is not installed on the VM, or if the NGT agent is not running/communicating with the cluster, the system cannot trigger the VSS hardware provider. In this situation, any request for an " application-consistent " snapshot from a third-party backup solution will fail because the cluster lacks the necessary hooks into the guest OS. However, a " crash-consistent " snapshot will still succeed because it does not require any guest-level interaction. Therefore, when app-consistent backups fail but crash-consistent ones succeed, the most likely root cause is a missing or broken NGT installation on the affected virtual machines.

Security and compliance are critical components of a Business Continuity strategy, particularly regarding the integrity of backups and snapshots. To prevent accidental or malicious deletion of critical recovery points, Nutanix Prism Central allows administrators to configure " Approval Policies " . These policies enforce a " four-eyes " principle where certain high-risk actions require validation by a second authorized user.

When an Approval Policy is active for DR snapshots, and a user attempts a deletion, the system does not execute the command immediately. Instead, the Nutanix orchestration engine captures the request and creates a " Pending Approval " task. The user who initiated the request will see the status update in the Task console, and an notification is sent to the designated " Approvers " . The snapshot remains fully protected and available for recovery until an authorized approver reviews and explicitly grants permission for the deletion. This mechanism provides a vital layer of defense against ransomware or administrative errors that could otherwise lead to the loss of a known-good recovery state. By integrating approval workflows into the storage management layer, Nutanix ensures that data destruction is a deliberate and verified process, meeting the strict control requirements of modern enterprises.

The Nutanix Cerebro service manages replication by scheduling snapshots and transferring the delta changes to the remote site. In an asynchronous replication schedule, if a new snapshot is taken before the previous one has finished replicating, the system faces a choice. To ensure that the most current data is available at the recovery site as quickly as possible, Nutanix may " skip " the replication of an older pending snapshot in favor of starting the replication of the newest one.

In this scenario, all infrastructure components (bandwidth, ports, hardware) are verified as healthy and have supported successful replication for months. This points toward a data-level issue rather than a connectivity issue. A " significant one-time surge in change rate " (Option D) means the VM generated a massive amount of new data blocks (churn) in a short period. Because the " Snapshot-on-wire " transfer size is directly tied to the number of changed blocks, this specific snapshot would take much longer than usual to replicate. If the transfer time exceeds the RPO interval, the next scheduled snapshot will trigger. The Cerebro service will see that it has a newer recovery point ready to go and will skip the " stuck " or slow-moving older snapshot to maintain the most recent RPO possible at the target. This behavior generates the " Replication was skipped " warning to notify the administrator that the historical sequence was interrupted due to a temporary imbalance between data churn and available throughput.

Storage consumption in a BCDR environment is directly governed by two factors: the frequency of recovery points (RPO) and the length of time those points are kept (Retention). When a third-party backup solution integrates with Nutanix Protection Policies, it often takes over the management of the snapshot lifecycle.

If storage utilization is increasing unexpectedly at both sites, the most likely cause is that recovery points are not being expired or purged at the expected rate. The administrator should first review the retention settings within the backup solution. If the retention period is set too long, or if the backup software is failing to send the " delete " command to Prism after its local catalog is updated, snapshots will accumulate on both the primary and recovery Nutanix clusters, leading to a steady growth in storage consumption. Other factors like network segmentation (Option C) or encryption (Option B) affect traffic paths and security but do not directly influence the quantity of data stored on the disks. Recovery validation (Option A) might use temporary storage but should not cause a continuous, long-term increase. Therefore, aligning the retention policy of the backup software with the available cluster capacity is the primary troubleshooting step.

Self-Service Restore (SSR) is a Nutanix feature that allows end-users to recover individual files by mounting a recovery point as a local drive within the guest VM. NearSync replication provides high-frequency protection with Recovery Point Objectives (RPOs) as low as 1 minute using Lightweight Snapshots (LWS). However, there is a technical distinction in how these high-frequency points are handled for end-user recovery.

In a NearSync configuration, the system generates dozens of LWS throughout an hour. While these are available for full VM disaster recovery, Nutanix limits the " granularity " available for Self-Service Restore to manage metadata overhead and guest agent performance. By default, SSR in a NearSync environment typically supports recovery point intervals of 1 hour. This means that while an administrator can restore the entire VM to a state from 5 minutes ago, an end-user using the SSR browser inside the VM will see recovery points at 1-hour increments (the " consolidated " points). This design balances the need for high-frequency disaster protection with the operational efficiency of file-level recovery. If a user needs a file from a point between the hourly intervals, an administrator may need to perform a full VM clone or an " Out-of-place " restore to provide access to those more granular lightweight recovery points.

Preserving IP addresses during a failover is a common requirement for applications with hardcoded IP references or complex inter-service dependencies. In a standard multi-site DR setup, the source and destination sites reside on different Layer 3 subnets, meaning a VM would naturally require a new IP address to be routable at the recovery site. To achieve " IP Preservation, " the underlying network infrastructure must support Layer 2 (L2) stretching.

L2 stretching (often implemented via VXLAN or specialized VPN tunnels like Nutanix Flow Virtual Networking) allows a single logical subnet to span multiple physical locations. When a VM fails over to a cluster on a stretched subnet, it effectively stays on the same network broadcast domain. As a result, its IP address, default gateway, and subnet mask remain valid and unchanged. If the subnets are not stretched, the administrator must rely on the Recovery Plan ' s " IP Mapping " feature to assign a new, valid IP at the destination—which does not " preserve " the original address. While preserving IPs simplifies application recovery, it requires more complex network engineering to ensure that traffic is correctly routed to the active site during a disaster, highlighting the trade-off between application simplicity and infrastructure complexity in BCDR design.

In a complex BCDR environment, replication failures that affect only a specific subset of virtual machines—while others on the same cluster succeed—usually point to a configuration mismatch rather than a general network or storage issue. Since the ports (2009 and 2020) are confirmed open and storage is available, the transport layer is functional. The fact that Linux VMs are succeeding while Windows (Marketing) VMs are failing suggests that the two groups may be mapped to different destination storage containers. In Nutanix replication, if a container mapping is explicitly set for one set of entities (the Linux VMs) but not for another (the Marketing VMs), the second group might be defaulting to a destination container that is either missing, misconfigured, or has restricted permissions. This specific scenario implies that the successful Linux VMs are benefiting from a correctly configured container mapping on the remote site, whereas the Marketing VMs are likely attempting to replicate to a location where mapping is invalid or non-existent. Troubleshooting this requires an administrator to verify the Prism Central container mapping settings to ensure that the storage targets for all protected categories are reachable and correctly associated with the destination storage pool.

When a replication job is marked as " ongoing " but the progress (bytes completed) is stagnant, it typically indicates a mismatch in the configuration or a failure in the orchestration logic rather than a total network blackout, especially when virtual IPs are confirmed reachable. In a " new setup, " a very common root cause is an incorrectly configured Protection Policy.

This can include issues such as mismatched category assignments, incorrect target site selection, or an invalid replication schedule that the system is unable to initialize properly. If the policy itself is misconfigured—for instance, if it is attempting to replicate to a storage container that hasn ' t been mapped or lacks permissions—the Cerebro service may initiate the task but then fail to progress the data transfer. While blocked ports (Options C and D) are common culprits in replication failures, they usually result in immediate " unreachable " alerts or job failures rather than a " stuck " status where connectivity is otherwise reported as healthy. If the Acropolis service were down at the remote site (Option A), the cluster would likely report the site as disconnected or show a critical service alert in Prism. Therefore, the most logical first area to investigate in a new, non-progressing setup is the logic and settings defined within the Protection Policy itself.

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.

Nutanix NearSync replication provides a middle ground between traditional asynchronous replication and synchronous mirroring, offering RPOs as low as 1 minute using Lightweight Snapshots (LWS). However, the LWS mechanism and the high-frequency metadata operations required to maintain a 1-to-15 minute RPO have specific hardware and cluster-level requirements.

One of the strict prerequisites for enabling NearSync is the cluster size. Nutanix requires a minimum of a three-node cluster for NearSync replication. This is because the system must have enough resources to distribute the LWS metadata and handle the increased I/O overhead without compromising the cluster ' s availability or performance. In a two-node cluster (which is common for small ROBO deployments), the system does not meet the minimum redundancy and resource thresholds required for the NearSync engine to operate reliably. While two-node clusters support standard Asynchronous replication (with a 60-minute RPO or higher), they are restricted from using the NearSync lightweight snapshot engine. An administrator attempting to set a 5-minute RPO on a two-node cluster will find the option either grayed out or the task will fail validation. To achieve a 5-minute RPO, the organization would need to expand the remote office cluster to at least three nodes or settle for a higher RPO supported by standard asynchronous replication on the existing hardware.

Nutanix manages data recovery operations differently depending on whether a virtual machine is in an asynchronous or synchronous replication state. For a standard Asynchronous VM like " REPORTING-DEV, " the local cluster takes periodic snapshots. If data corruption occurs, the administrator can perform an " In-place Restore " or " Revert " using a local recovery point. This is a standard procedure where the current vDisks are overwritten by the point-in-time data from the snapshot.

However, " ERP-PROD " is part of a Synchronous replication policy (0 RPO). This means the storage container it resides on is effectively " stretched " and locked in an active-active relationship with a remote cluster. Every write must be identical at both sites. If an administrator attempts to " Revert " a synchronous VM to a local snapshot, it would cause an immediate data mismatch between the primary and recovery sites, breaking the zero-RPO guarantee and potentially causing cluster-wide consistency issues. To protect data integrity, Prism Central typically grays out or blocks the " Revert " option for VMs currently in an active synchronous " Sync " state. To recover such a VM, an administrator would generally need to either " Clone " the snapshot to a new VM or temporarily move the VM into an asynchronous state by modifying the policy, thereby unlocking the ability to revert the data disks locally before re-enabling synchronization.

Nutanix Disaster Recovery is designed to be bi-directional, supporting both failover and failback . In an unplanned failover, the primary site (AZ1) is assumed to have crashed. Once AZ1 is brought back online, the system must synchronize any data changes that occurred while the VMs were running at AZ2.

Statement C is correct because once the VMs are powered on at AZ2, the Nutanix Cerebro service automatically reverses the protection policy. New recovery points are created at AZ2 and replicated back to AZ1. For a successful, modern failback with zero data loss from the cloud session, the administrator must wait for these recovery points to replicate back to AZ1 before initiating the failback.

Statement B is also correct and describes a specific " recovery of last resort " scenario. If AZ1 is restored but connectivity to AZ2 is permanently lost (e.g., the cloud provider has an issue), an administrator can still " Unplanned Failover " back to AZ1 using the historical snapshots that existed locally on AZ1 before the original outage. This would result in data loss equal to the time the VMs were running at AZ2, but it allows for service restoration when the recovery site itself fails. These two statements highlight the flexibility of the Nutanix DR architecture in handling both controlled failback and emergency local restoration.

In a Nutanix Synchronous Replication or Metro Availability setup, data is mirrored in real-time, but the " intelligence " required to automate a failover resides outside of the two primary clusters. Without a Witness VM (Option C), the secondary cluster cannot distinguish between a total primary site failure and a simple network partition between the two data centers. If the clusters lose communication but there is no Witness to act as an independent tie-breaker, the secondary cluster will stay in a " Standby " state and will not automatically " promote " its storage to " Active " or power on the VMs. This is a safety mechanism to prevent " split-brain " where two clusters might try to serve the same data, leading to corruption. To enable automatic failover, a Witness VM must be deployed at a third, independent site and registered to both clusters. The Witness allows the secondary site to verify that the primary site has indeed failed; once verified, the Witness grants the " lock " to the secondary site, allowing the automated failover process to begin. Thus, the lack of a Witness is the " most likely cause " for why a failover test would fail to trigger automatically during a storage or site outage.

This question evaluates the administrator ' s ability to map business RPO (Recovery Point Objective) requirements to the appropriate Nutanix technology. A requirement for " maximum 15 minutes of data loss " means the system must replicate data at least every 15 minutes. Nutanix offers two primary ways to achieve this: traditional Asynchronous replication and Nearsync replication. While Async (Option D) can technically be configured for a 15-minute interval, it relies on standard, full snapshots which can be heavy and resource-intensive, potentially leading to performance lag if the data churn is high. Nearsync Replication (Option B) is specifically designed for these low-RPO scenarios (from 20 seconds up to 15 minutes) by using " Lightweight Snapshots " (LWS). LWS minimize the storage and I/O overhead compared to traditional snapshots, making Nearsync the more reliable and robust choice for Tier-1 applications. Furthermore, Nearsync is built to handle the constant, high-frequency data transfers required to maintain a strict 15-minute window without impacting application performance. Therefore, Nearsync with a 15-minute RPO is the " best " configuration because it is the purpose-built solution for the stated performance and data protection goals.