Free Nutanix NCP-MCI Exam Dumps August 2026

Offset-based IP mapping in Nutanix Recovery Plans allows automatic subnet changes during DR failover.

Option D (Utilize Recovery Plan Offset-based IP mapping) is correct:

This method automatically adjusts the IP range while keeping the same last octet.

It eliminates the need for manual intervention after failover.

Option A (Custom script) is incorrect:

Scripting is an option, but Recovery Plan IP mapping is simpler and native to Nutanix.

Option B (Use IPAM) is incorrect:

IP Address Management (IPAM) is useful, but offset-based mapping provides more control.

Option C (Manually update IPs) is incorrect:

This would be time-consuming and error-prone.

Nutanix Disaster Recovery Guide Using Offset-Based IP Mapping

Nutanix KB Best Practices for Managing IP Addresses in DR

When a node is placed into Maintenance Mode, Nutanix follows a structured process to ensure service continuity and data integrity.

Option B (All eligible VMs on the host are migrated to other hosts) is correct:

Live Migration automatically moves VMs to other hosts to avoid downtime.

This ensures workloads remain operational during maintenance.

Option D (Non-migratable VMs are powered off) is correct:

Some VMs, such as those using GPU pass-through or local storage dependencies, cannot be live-migrated.

These VMs must be powered off before placing the host into Maintenance Mode.

Option A is incorrect:

Non-migratable VMs are not automatically restarted on other hosts---they remain powered off until manually restarted.

Option C is incorrect:

Eligible VMs are live-migrated, not powered off.

Nutanix AHV Best Practices Understanding Maintenance Mode Behavior

Nutanix KB VM Migration and Power-Off Scenarios in Maintenance Mode

For Metro Availability to work properly, the storage containers at both the primary and secondary sites must meet certain requirements:

The storage containers must have the same name (Option D). This ensures that replication and failover work seamlessly. If the names do not match, the storage containers will not be listed as compatible.

The destination storage container must be empty (Option C). Metro Availability requires a clean storage container at the secondary site to receive data. If the container already contains data, it cannot be used.

Option A is incorrect: Different vendor hardware does not affect Metro Availability compatibility.

Option B is incorrect: Compression does not affect Metro Availability compatibility. However, it is recommended to keep compression settings aligned between sites.

Nutanix Documentation: Metro Availability Deployment Guide

Nutanix Best Practices for Metro Availability

Nutanix KB 2093: Troubleshooting Metro Availability Storage Container Issues

Multicast traffic can generate unnecessary overhead if it is not properly managed. IGMP Snooping (Option C) ensures that multicast packets are only sent to VMs that have requested them, rather than broadcasting to all VMs.

Option C (IGMP Snooping) is correct:

It reduces unnecessary multicast traffic by ensuring that only subscribed VMs receive the packets.

It is supported natively in AHV networking.

Option A (LACP) is incorrect:

Link Aggregation Control Protocol (LACP) improves bandwidth and redundancy but does not control multicast traffic.

Option B (UDP) is incorrect:

UDP (User Datagram Protocol) is a transport protocol, not a network optimization feature.

Option D (Network Segmentation) is incorrect:

Segmentation (VLANs, VPCs) isolates networks but does not optimize multicast traffic specifically.

Nutanix AHV Networking Guide Enabling IGMP Snooping

Nutanix Bible Network Traffic Optimization in AHV

Nutanix KB Best Practices for Multicast Traffic in AHV

The task that needs to be performed when time is not synchronizing properly after deploying a cluster is NTP configuration. In the Nutanix Multicloud Infrastructure (NCP-MCI) 6.5, Network Time Protocol (NTP) is used to synchronize the system time across all the nodes in a cluster. If the time is not synchronizing properly, it indicates that there might be an issue with the NTP configuration. Therefore, checking and correcting the NTP configuration would be the appropriate action to resolve this issue. The other options like DNS configuration, HA configuration, and SMTP configuration are not directly related to time synchronization in a cluster.