Nutanix's recommended migration tool for moving VMs into AHV is Nutanix Move. Official Nutanix guidance and migration material specifically recommend Move as the preferred mechanism for migrating VMs to AHV, especially when the goal is to reduce disruption compared with coarse methods like backup- and-restore. Move is purpose-built for this scenario and supports migration workflows from platforms such as VMware into Nutanix AHV with minimized downtime during cutover. ( Nutanix ) The distractors highlight common confusion between the overall product and helper components. Move Agent may be involved in certain source-platform workflows, but the question asks what should be used to minimize downtime at the solution level. The correct answer is the migration platform itself: Nutanix Move. Backup and restore is usually more disruptive and manual. CCLM is unrelated here. Nutanix positioning is very clear that the standard, supported, low-downtime migration path from a third-party virtual environment to AHV is Move, so D is correct. ( Nutanix )

Nutanix Move documentation states that when migrating VMs from Hyper-V to AOS/AHV, a Nutanix Move agent service is deployed on the Hyper-V host. Nutanix provides dedicated procedures for deploying the Move Agent on Hyper-V, both manually and automatically. That makes D the correct answer.
This is a common migration-tool distinction. Nutanix Move is the migration platform, but the question asks what specifically must be deployed on the Hyper-V host. The answer is not VirtIO drivers or NGT, because those serve different purposes. Nutanix explicitly documents the Move Agent as the source-host component used for Hyper-V migrations. Therefore the authentic exam answer is D. Nutanix Move Agent.

Nutanix does support exposing storage containers for hypervisor access patterns, but Nutanix also clearly recommends not using an AOS storage container as a general-purpose NFS or SMB share. For a temporary exception such as a migration host, the safer and more controlled approach is to whitelist only the exact host that needs access. Using a single host IP with a 255.255.255.255 netmask is the most restrictive option listed and follows the principle of least privilege. That reduces risk during the migration window and avoids broad, unnecessary exposure of the container to an entire subnet. ( Nutanix Portal ) This question is really about administration discipline, not just raw connectivity. Opening the whole subnet might be convenient, but it creates more attack surface and more chance of accidental mounting from unauthorized systems. Nutanix documentation steers administrators toward purpose-built file services, such as Nutanix Files, when they need true shared file access. Since this is only for a temporary migration, the best practice is a tightly scoped NFS allowlist entry for one external host. That makes B the strongest operational and security choice. ( Nutanix Portal )

The decisive metric in the iostat output is %iowait = 83.20. In Linux performance interpretation, such a high iowait value means the CPU is spending most of its time waiting for disk I/O operations to complete rather than actively executing user or system work. On a Nutanix CVM, that strongly suggests the storage path is the bottleneck at that moment, whether due to backend disk saturation, contention, or broader storage subsystem latency. Since user CPU and steal are both low, the issue is not primarily compute pressure or hypervisor scheduling contention. Therefore, A is the most accurate description. ( Nutanix ) This is a classic Nutanix troubleshooting interpretation question. If the output had shown high %steal, then hypervisor contention would be a stronger candidate. If %system and %user were both very high, compute load from services would be more likely. But with the overwhelming majority of time in iowait, the signal points toward delayed storage completion. In operational terms, the next steps would usually involve checking CVM disk metrics, Stargate performance, storage latency, and possibly the health of the underlying drives.
The evidence in the output supports a storage wait condition, which is exactly what option A says. ( Nutanix )