Nutanix Updated NCP-BC-7.5 Exam Questions and Answers by amna

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.

In a Nutanix environment, " Advertised Capacity " is a logical limit (a quota) that an administrator can set on a specific storage container. Even if the physical storage pool has terabytes of free space, if a container ' s advertised capacity is reached, the hypervisor and the Nutanix services will perceive the container as being 100% full.

In this troubleshooting scenario, the " nfs status 28 " error code is a standard indicator for " No space left on device " . Since the administrator confirmed the pool is healthy, the logical limit on the container is the only remaining bottleneck. Replication jobs will " hang " because the destination Stargate service cannot write the incoming data blocks to a container that reports zero free space. To resolve this, the administrator must either increase the advertised capacity value in Prism or remove the limit entirely to allow the container to consume the available physical space in the pool. This highlights a common configuration " trap " where logical quotas—intended for multi-tenant management—can inadvertently block critical BCDR processes like replication if not monitored or sized correctly according to the protected VM growth.

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.

The fundamental purpose of a " Test Failover " in Nutanix Disaster Recovery is to provide a non-disruptive way to validate the recovery process. During this test, virtual machines are cloned from their most recent snapshots and powered on at the recovery site. If an administrator incorrectly maps the " Test Network " to the actual " Production Network " (VLAN/Subnet) at the recovery site, they create two significant risks.

First, this configuration can lead to immediate IP address conflicts. Because the test VMs have the exact same IP addresses as the live production VMs, having them active on the same logical production network will disrupt routing and potentially cause service outages for real users. Second, it defeats the " isolation " between production and test workflows. A valid DR test should occur in a " sandbox " where test applications can crash or exhibit errors without any possibility of affecting the live environment. By using the production network, the administrator is effectively running a " live " test on the production infrastructure, which is a dangerous violation of standard BCDR best practices. To avoid these outcomes, the administrator must map the test network to a dedicated, isolated VLAN or overlay network at the recovery AZ that has no physical or logical path back to the production segment.