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 methodautomatically adjusts the IP rangewhile keeping the same last octet.
* It eliminates the need formanual interventionafter failover.
* Option A (Custom script) is incorrect:
* Scripting is an option, butRecovery Plan IP mapping is simpler and native to Nutanix.
* Option B (Use IPAM) is incorrect:
* IP Address Management (IPAM) is useful, butoffset-based mapping provides more control.
* Option C (Manually update IPs) is incorrect:
* This would betime-consuming and error-prone.
References:
* Nutanix Disaster Recovery Guide #Using Offset-Based IP Mapping
* Nutanix KB #Best Practices for Managing IP Addresses in DR

A cluster runway below 365 days does not necessarily indicate an issue if Intelligent Operations determines that workloads are sustainable.
Option B (Because new workloads are sustainable) is correct:
Nutanixanalyzes resource trendsand marks clusters as healthyif new workloads are within projected capacity.
Option A (Storage Runway is still good) is incorrect:
Storage isone component, butCPU and memoryalso affect runway calculations.
Option C (Recommended resources) is incorrect:
Recommendations help optimize capacity, butdo not define cluster health.
Option D (Target is 1 month) is incorrect:
The scenario's target window does not impact the actual runway calculation.
References:
Nutanix Prism Central Guide #Capacity Planning & Runway Analysis
Nutanix KB #Understanding Capacity Runway and Workload Sustainability

Data-in-Transit Encryption for Prism Central and CVMs requires specific internal communication ports to be open. Nutanix internal component documentation states:
"Port 2020 is used by the Nutanix encryption service for encrypted CVM-to-CVM communication during Data-in-Transit Encryption operations." This port is essential for establishing secure tunnels between control-plane services. Ports 2009 and 2010 are used by other CVM services (e.g., Stargate, Curator coordination) but not for transport encryption. Port 9440 is for Prism UI/API traffic, and while it must be accessible for management, it does not enable encrypted back- end service traffic.
Thus, the administrator must ensure that port 2020 is permitted to enable Data-in-Transit Encryption functionality.

Within Nutanix VM classification, Agent VMs are special-purpose system VMs designated for infrastructure tasks. The internal definition states:
"Agent VMs are not live-migratable and do not participate in high-availability evacuation; they are excluded from standard host maintenance operations." If a VM is mistakenly marked as an Agent VM, the hypervisor will block all migration attempts. Disabling the Agent VM flag returns the VM to standard workload treatment, making it eligible for live migration.
Updating LLDP has no relevance to VM migration. Backplane port groups affect CVM networking only.
ADS influences workload placement but not migration eligibility.
Therefore, removing the Agent VM designation is required to allow migration.