Nutanix NCP-MCI-7.5 Dumps

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 documents guest customization profiles as reusable operating-system customization definitions that can be applied during VM deployment. This is precisely what makes them the most efficient answer when a Windows VM will be cloned repeatedly and each clone requires OS-level customization such as naming, identity settings, or first-boot configuration. Instead of creating a separate template each time or manually editing each deployed clone, the administrator creates one reusable customization profile and applies it across deployments. That makes C the correct answer.

This is especially important at scale. Manual post-clone configuration is error-prone and time-consuming, while per-deployment templates create management sprawl. Nutanix’s design encourages reusable policy- or profile-based standardization so that repeated deployments remain consistent and secure. For Windows, that typically means Sysprep-oriented OS customization combined with reusable deployment logic. In other words, the question is asking for the most efficient method, and Nutanix’s documented answer to repeatable OS customization is the guest customization profile. Therefore C is the authentic choice.

Nutanix documentation is very clear on this point: Secure Boot is not supported if the VM uses IDE disks. Nutanix also states that for AHV, if Secure Boot is enabled for UEFI mode, the IDE interface is not supported and SATA should be used for the VirtIO ISO in that configuration. So an IDE-attached disk is a direct blocker to enabling Secure Boot. ( Nutanix Portal )

This is one of those areas where the exam expects you to know compatibility rules, not just feature names. UEFI is actually part of the supported Secure Boot path, so option D is not the blocker. The CVM’s RAM and node cache storage are unrelated to whether the VM’s firmware and bus configuration can support Secure Boot. The administrative fix is usually to convert the VM to a supported configuration using UEFI and non-IDE bus types where required. Therefore, among the listed options, the condition that prevents completion of the task is the presence of IDE disks, making C correct. ( Nutanix Portal )

For AHV, when enabling LACP, Nutanix documentation specifies the Active-Active bond type, also described as balance-tcp. Nutanix explicitly ties LACP and link aggregation behavior to the Active-Active configuration and notes that this configuration sets LACP fallback to Active-Backup on AHV hosts. That makes C the correct bond type for an LACP-enabled design. ( Nutanix Portal )

It is also important to understand why Active-Active with MAC Pinning is wrong here. Nutanix documentation states that the MAC-pinning / balance-slb style must not be used with link aggregation protocols such as LACP. So even though both options sound like they distribute traffic, only one is compatible with LACP. Active-Backup provides redundancy, but not the LACP behavior being requested. “No Uplink Bond” obviously does not meet the requirement. Even without the missing exhibit from the uploaded file, the Nutanix networking documentation makes the intended answer clear: Active-Active is the bond type used when enabling LACP on AHV. ( Nutanix Portal )

Nutanix security guidance is explicit on this point. After adding an SSH public key and verifying connectivity, Nutanix recommends disabling password authentication for all CVMs and AHV hosts to reduce interactive access risk. The Security Guide notes that after the SSH key inclusion and connectivity validation are complete, password authentication should be disabled as the next hardening step. That makes B the correct answer.

This is a straightforward hardening sequence question. The administrator has already completed the prerequisite—public-key access is working—so the next step is to remove the weaker interactive method. Core dumps, login banners, and UI session settings do not address SSH authentication exposure. Nutanix’s security model favors moving from password-based remote shell access to key-based access only. Therefore B is the authentic and recommended next step.

In Prism Central, Runway Analysis is not a simple reading of current utilization; it is a forecast based on historical consumption trends. Nutanix documentation explains that capacity planning and runway use machine learning and historical resource behavior to estimate when CPU, memory, or storage will run out. That means a cluster can still show only 60% memory used today and yet have a short memory runway if the memory-consumption trend has been climbing steadily and rapidly over recent history. In this scenario, the most likely reason for only 12 days of runway is sustained growth in memory use over the historical observation period. ( Nutanix )

The distractors do not fit the documented behavior as well. Nutanix does support scenario modeling, but a low runway in the standard view is primarily a forecast outcome, not a default penalty for missing history or a result of guaranteed HA mode by itself. HA reservations can reduce available effective capacity, but the wording of the question points to forecasting logic rather than static reservation math. Since Nutanix runway is based on actual consumption trends, the answer that best explains a low runway despite moderate present-day utilization is that memory usage has been continuously increasing, which is option B. ( 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 documentation for Prism Central point-in-time backup states that the system supports one point-in-time backup target at a time. Nutanix further documents that Prism Central can be backed up to registered clusters, Nutanix Objects, AWS S3, or generic S3-compliant storage, but the platform still supports only one active point-in-time backup target concurrently. Therefore the correct answer is A. 1.

This question is easy to overthink because the product supports multiple target types, but that is different from supporting multiple simultaneous configured S3 targets for one Prism Central instance. Nutanix’s wording is explicit and leaves little ambiguity: one backup target at a time. That means answers B, C, and D are not consistent with the documented PC backup design. So for a study guide grounded in current official Nutanix documentation, the authentic answer is A.

Nutanix documentation for multisite disaster recovery states that a protection policy can include multiple replication schedules across up to three different recovery clusters, and Nutanix also documents the ability to configure multisite replication schedules for up to three recovery clusters with different schedules. That means a source site can protect workloads to multiple destinations without requiring separate, duplicated protection policies for each site. Given the options, the most efficient approach is therefore one protection policy from the source cluster covering all three sites, which is option D.

The answer choices that create multiple separate protection policies are less efficient and introduce avoidable administrative duplication. Cloning policies across sites also misses the point of Nutanix’s native multisite capability. Even though the sites are managed by different Prism Central instances, Nutanix documents DR support between clusters registered to different Prism Central instances as well. So the most scalable and documentation-aligned answer is D.

The error message is tied to resilience requirements. Nutanix documentation states that Replication Factor 3 requires at least five nodes so data remains online even if two nodes fail concurrently. If removing a node would drop the cluster below the minimum usable-node requirement, Nutanix blocks the operation. The safest and supported way to proceed during a hardware refresh is to add the replacement node first, restore compliant cluster capacity, and then remove the original node. ( Nutanix Portal )

The wrong answers all involve bypassing or weakening resilience inappropriately. Changing cluster or container RF to RF2 just to remove a node would reduce fault tolerance and is not the right answer for a SQL environment where resilience matters. Force-removal is also not the supported operational answer in a healthy refresh workflow. This question tests whether the administrator understands that node lifecycle actions are constrained by Nutanix fault-tolerance rules. When the cluster says it needs at least five usable nodes, the correct action is not to override the rule but to satisfy it by adding capacity first. Therefore A is the correct answer. ( Nutanix Portal )

Foundation Central is about deployment centralization, not backup, lifecycle upgrades, or automatic registration workflows as its main value proposition. Nutanix documentation describes Foundation Central as a tool that can manage several Foundation instances from a single pane of glass, allowing administrators to create clusters of remote nodes. That statement maps directly to option D. ( Nutanix Portal )

The subtle point here is that the question mentions Marketplace only as the method used to deploy Foundation Central, not as the capability being tested. Once deployed, Foundation Central’s job is to simplify remote cluster creation at scale. It does not replace LCM for software upgrades, nor is its primary role to perform backup and recovery of cluster configurations. Automatic cluster registration may happen as part of broader operational workflows, but it is not the core capability Nutanix emphasizes in the product description. In the context of imaging and deploying many branch-office clusters from a central team, the defining capability is centralized cluster creation and management visibility. That is why D is the right answer. ( Nutanix Portal )

Nutanix documentation explains that Projects in Prism Central provide logical groupings of infrastructure resources and user access, and that you can add users and user groups to a project while also allowing clusters and subnets in that project. That is exactly the mechanism used when a user group needs controlled access to resources drawn from multiple clusters. The project becomes the governance boundary that ties users, roles, and infrastructure scope together. Therefore A. Configure Nutanix Projects is the correct answer. ( Nutanix Portal )

The other choices are unrelated to access scoping across clusters. Advanced Network Controller deals with networking services and policy capabilities, not user resource assignment. Micro Services Platform is not the RBAC/governance feature for multi-cluster access. Availability Zone is relevant for placement and DR topologies, not for delegating cluster resources to user groups. Nutanix’s governance guidance is clear that Projects are the construct used to organize infrastructure resources and assign them to users or groups with the proper RBAC controls. So for a user group that needs access to resources from multiple clusters, the authentic Prism Central action is A. ( Nutanix Portal )

Nutanix networking documentation is explicit that LACP on AHV requires the Active-Active bond type, also described as balance-tcp. Nutanix further explains that this mode increases host and VM bandwidth utilization beyond a single uplink by balancing VM NIC TCP and UDP sessions across multiple physical adapters. That directly addresses both parts of the requirement in the question: maximizing per-host throughput and per-VM throughput while also providing LACP support. For that reason, B is the correct answer.

The other options do not satisfy the stated requirement. Active-Backup gives redundancy but does not aggregate active bandwidth. Active-Active with MAC pinning (balance-slb) can use multiple adapters without switch configuration, but Nutanix documents that it must not be used with LACP. “No Uplink Bond” obviously cannot maximize throughput or provide aggregation. This question is testing a core AHV networking distinction: if the user explicitly wants LACP, then the answer is always the Active-Active / balance-tcp model. That is why B is the authentic Nutanix answer.

Nutanix documentation on rebuild capacity reservation and resilient capacity emphasizes that some storage space must remain effectively protected so the cluster can recover from failures and maintain resiliency. If a cluster consumes all capacity beyond that protected threshold, it can reach a point where it no longer safely accepts writes because continuing to do so would violate resiliency guarantees. The symptoms in the question—stopped accepting writes and VM outages—align with a cluster hitting its resilient capacity limit, not merely an EC optimization limit. ( Nutanix )

This distinction matters. Erasure coding limits affect efficiency opportunities, but they do not by themselves explain the cluster refusing writes. A degraded container after a node failure may contribute to pressure, but the wording centers on cluster-wide behavior after rebuild-capacity reservation is enabled. Nutanix’s resiliency logic is designed to protect the cluster from entering an unsafe state, and one enforcement mechanism is to stop admitting additional writes when resilient capacity has been exhausted. Therefore, the most likely cause is C: the cluster has reached its resilient capacity limit. ( Nutanix )

Nutanix documentation for Prism Central deployment states that single Prism Central VM deployments are supported in Small, Large, or X-Large sizes, and that a single-VM deployment can later be scaled out. Since X-Small is not the supported minimum deployment size in this documented model, the minimum supported size is Small. That makes A correct.

This question is really checking whether the administrator understands the starting point for a scale-out-capable Prism Central design. The existence of larger sizes does not change the minimum supported entry point. Nutanix’s documentation is explicit that a single Prism Central VM can begin at Small and later be expanded if more scale or resiliency is needed. Therefore, for a single-node Prism Central deployment with future scale-out potential, the correct answer is Small.

Nutanix documentation for Erasure Coding is explicit: a cluster must have a minimum of four nodes to enable erasure coding, and for RF2 the minimum remains four nodes. Nutanix further explains that RF3 with erasure coding requires six nodes, which helps distinguish the two thresholds clearly for exam purposes. Since the question asks specifically about Replication Factor 2 and Erasure Coding, the minimum supported node count is 4. ( Nutanix )

This question is testing one of the most common node-count rules in Nutanix storage efficiency. A three-node cluster can provide RF2 storage, but that does not automatically mean erasure coding is available there. Erasure coding introduces its own resiliency and stripe-width requirements, and Nutanix sets the minimum at four nodes for RF2. The values 5 and 6 are distractors meant to confuse RF2 and RF3 rules. Because the official requirement is four nodes for RF2 EC, the correct answer is B. ( Nutanix )

The requirement is not to keep the mission-critical VMs together or apart from each other; it is to prevent them from running on a specific set of older hosts. In Nutanix Prism Central policy terms, that is a VM-Host Anti-Affinity Policy. Anti-affinity at the VM-host level allows administrators to mark selected hosts as unsuitable targets for selected VMs, which is exactly what the scenario requires. Therefore C is the correct answer.

The distractors all target the wrong relationship. VM-VM affinity and anti-affinity control how VMs are placed relative to other VMs, not whether they can run on particular hosts. VM-Host Affinity would express a positive preference or requirement to run on a chosen host group, but the question is framed negatively: the VMs must never run on the older hosts. Nutanix’s policy model supports this exact exclusion use case through VM-Host Anti-Affinity. In a long refresh delay scenario, this is the safest operational control to keep sensitive workloads off weaker or undesirable hardware without removing those hosts from the cluster immediately. Therefore C is the authentic answer.

Nutanix documentation for Performing Failover in PD-based DR includes the exact error message quoted in the question: “Protection domain is already active on source site ... Please trigger migrate from source site to activate the protection domain.” Nutanix shows this message when the protection domain is still active on the source cluster and the proper action is a planned migrate from the source, not an activate at the target. In other words, the source cluster is still reachable and authoritative, so trying to activate the protection domain on the other side is the wrong operation. That makes D the correct answer. ( Nutanix Portal )

This is a classic Nutanix DR distinction between planned migration and unplanned failover/activation. If the primary cluster is still available, Nutanix expects the administrator to use migrate from the source site. Activation at the destination is reserved for failover conditions when the source cannot safely coordinate the move. The error itself tells you the reason if you read it carefully: the protection domain is still active on the source site. Therefore the root cause is that the administrator is trying to activate the PD while the primary cluster is still reachable and still owns the active copy, which is exactly option D. ( Nutanix Portal )

Nutanix security hardening guidance explains that SSH Whitelisted Addresses control which client IPs are allowed to reach the CVM over SSH. If IP restriction is enabled and the new jump box is not on the allowlist, the SSH connection is expected to be refused. In that locked-down state, the correct recovery path is to access the CVM through a local or serial console and update the whitelist to include the new jump box IP. That makes C the correct answer. ( portal.nutanix.com , portal.nutanix.com )

Cluster Lockdown disabling password-based SSH is not the same setting as the SSH allowlist. Prism Central security views can help with visibility, but the key documented mechanism is the whitelist itself. Restarting the CVM does not reset the hardened configuration. Nutanix’s intent is that trusted-source access must be explicitly permitted, and once it is blocked, you need console-level access to make the change safely.

For database workloads, Nutanix documentation distinguishes between crash-consistent and application-consistent recovery points. If the Take App-Consistent Recovery Points option is not selected, the recovery point may capture storage in a crash-consistent state only. For transactional databases, that can lead to corruption, incomplete writes, or recovery issues after restore. Nutanix specifically documents that selecting the app-consistent option creates application-consistent recovery points; if you do not select it, the recovery points are crash-consistent. That makes D the most likely root cause. ( portal.nutanix.com , portal.nutanix.com )

The mention that NGT was checked is important because NGT participation is commonly part of quiesced and app-consistent protection workflows. A high RPO can increase data loss, but it does not by itself explain logical corruption inside the restored database. Category choice and roll-up schedule are also not the primary issue. Nutanix best practice for databases is to ensure application-consistent protection is enabled wherever supported. Therefore D is the correct answer.

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 )

In Nutanix Elastic VM Storage and shared-storage workflows, the container used across clusters must be created as a Shared storage container. Nutanix documentation for storage container management and container creation in Prism Central explicitly references Creating a Shared Storage Container and Creating a VM with Shared Storage from another HCI Cluster. If the container is not defined as Shared, it will not be eligible for the remote-storage VM placement workflow, so it will not appear as a valid target in the dropdown. ( Nutanix Portal )

The distractors are there to pull attention toward naming and capacity details, but those are not the gating requirement for remote shared-storage presentation. A reservation setting affects capacity planning, not whether the container is exposed as a remote shared-storage option. Hyphens in names and the specific length shown are not the documented reason the container would be absent from this workflow. Nutanix treats shared cross-cluster storage as a specific container type and workflow. Therefore, if the remote container is missing during provisioning, the most likely explanation is that the container type was not configured as Shared. ( Nutanix Portal )

Nutanix documentation for Active Directory authentication in Prism Element states that the default LDAP port is 389, while port 636 is used for LDAPS, which provides encrypted LDAP traffic. Because the question explicitly says the administrator wants all traffic encrypted, the correct port is 636. That is the standard LDAPS answer and the one Nutanix documents directly.

The missing exhibit is not actually necessary to answer the question because the encryption requirement itself is enough. Ports 443 and 9440 are associated with web interfaces or management access, not LDAP directory authentication transport. Port 389 is unencrypted LDAP unless other mechanisms are layered on top. Nutanix’s own directory-authentication docs make the intended answer clear: use LDAPS on port 636. Therefore C is the authentic Nutanix answer.

Nutanix documentation for Updating Capacity Configurations explains that the Reserve Capacity For Failure option determines whether runway analysis should account for the impact of a node failure, and when Auto Detect is selected, Prism Central automatically uses the cluster’s failure assumptions rather than the full unconstrained cluster total. In practical runway terms, that means the calculation reflects the loss of the node whose failure would have the greatest effect on usable capacity. Among the provided options, the best match for that documented logic is D: the runway analysis excludes the resources of the largest node so estimates account for a node failure. ( Nutanix Portal )

This behavior is important because runway is intended to answer “how long until I run out of safe usable capacity,” not just “how long until all raw resources are consumed.” Nutanix therefore lets administrators model capacity while preserving headroom for failure scenarios. The fixed 10% answer is too generic and not how Nutanix documents the option. Storage-only reservation also misses the fact that runway tracks CPU, memory, and storage dimensions. So, based on Nutanix’s Auto Detect wording and the resilience-oriented design of runway planning, D is the most authentic answer. ( Nutanix Portal )

For CHAP-protected volume groups, Nutanix documentation is explicit that when the target password is changed, the administrator must also update the associated recovery plan. Nutanix states that if the new target password is not updated in the recovery plan, it is not retained after failover. That makes the recovery plan the place where the failover-side credential continuity is preserved. In other words, protection policies create and replicate recovery points, but the recovery plan contains the information needed for the recovered application workflow, including CHAP details needed after recovery. ( Nutanix Portal )

This is an important exam distinction: protection policy controls snapshot and replication behavior, while recovery plan controls recovery orchestration and the settings needed when workloads are actually brought online at the target site. Recovery points themselves are snapshots of protected entities; they are not the administrative mechanism Nutanix documents for persisting an updated CHAP target password through failover. So even though the uploaded file says option D, the official Nutanix guidance supports A. For failover success with CHAP-enabled VGs, always synchronize password changes with the recovery plan. ( Nutanix Portal )

Nutanix Volumes documentation explains that external iSCSI clients use the iSCSI Data Services IP address for target discovery and connection. Nutanix specifically documents creating or updating the ISCSI Data Services IP Address on the cluster as part of enabling access to Volumes. If that step is missing, an external initiator can fail to discover or connect to the volume group correctly. Therefore B is the correct answer.

The other options are unrelated to the direct connectivity requirement. Microservices Infrastructure and Prism Central registration are not the necessary cluster-side prerequisites for an external iSCSI connection. LDAP directory configuration is also not the primary dependency being tested here. The key Nutanix platform requirement is that the cluster exposes the Volumes service via the configured Data Services IP. Without that, the initiator connection workflow breaks. So B is the authentic answer.

In PD-based DR, Nutanix distinguishes between planned migration and unplanned failover/activation. When the source side is unstable or unreachable, the administrator cannot rely on a clean migration workflow initiated from the source. In that case, the correct recovery action is to activate the protection domain on the destination cluster. This is the classic unplanned failover behavior: bring the replicated workload online at the target because the source cannot be trusted to participate in a coordinated handoff. That makes A the correct answer. ( portal.nutanix.com , portal.nutanix.com )

The exam distinction is simple: Migrate is for planned movement when both sides cooperate; Activate is for disaster-style recovery at the target. Since the question explicitly says the source has intermittent network issues, it is pointing you toward the unplanned-failover path. Therefore the administrator should perform Activate on the destination.

Nutanix volume groups support attaching storage to one or more VMs. Nutanix documentation for creating volume groups states that if you want to attach a volume group to multiple VMs, you select the Shared option. That is the key requirement when building an application-level high-availability configuration where two database VMs need shared access to the same block storage construct. ( Nutanix Portal )

The other options either describe different capabilities or are not the documented mechanism for this requirement. External client access is used when exposing the volume group to external iSCSI initiators, which is not what the question asks. Storing vDisks on different containers does not create shared access semantics. “Multi-writer mode via storage policy” is not the standard Nutanix answer here; Nutanix’s documented configuration language for this use case is the Shared setting on the volume group itself. So if the requirement is two VMs, same application data path, and application-level HA, the correct Nutanix configuration is to create the VG in shared mode. ( Nutanix Portal )

Nutanix documentation states that when you perform an LCM inventory, Life Cycle Manager first checks and updates its own framework before presenting other upgrade options. Nutanix’s guidance for framework updates and recommended upgrade order repeatedly references Perform Inventory as the step that ensures the system discovers and updates the LCM framework itself. That is why A is the correct answer when the goal is specifically to guarantee LCM is upgraded to the latest version. ( Nutanix )

The other actions may be valid parts of broader maintenance, but they do not ensure the LCM framework itself is brought to the latest version. Upgrading AHV or AOS addresses platform components, not the LCM service logic. Running NCC is good pre-upgrade hygiene, but it is not the mechanism that causes LCM to update. Nutanix intentionally ties framework currency to the inventory process, so the correct operational answer is to perform an inventory first. ( Nutanix )

Nutanix documentation for enabling Marketplace in Prism Central explicitly states that a unique data services IP address (DSIP) must be configured on the Prism Element cluster that hosts Prism Central. This is a hard prerequisite for Marketplace enablement and application deployment workflows. In exam terms, the presence of DSIP is not optional convenience; it is a setup requirement Nutanix calls out directly before Marketplace can be used. ( Nutanix )

The other answers are not Marketplace prerequisites in the same direct sense. SMTP is useful for email notifications, LDAP for external authentication, and LACP for network design, but none of those is the documented enabling requirement for Marketplace. Nutanix separates platform application management prerequisites from general infrastructure best practices, and DSIP falls into the former category. So when the exam asks what must already be in place on the Prism Element cluster before enabling Marketplace, the correct answer is A: Data services IP must be configured. ( Nutanix )

The key clue is the mismatch between the VM being slow under memory overcommit and the guest OS pagefile usage remaining low. If the guest itself were under strong memory pressure, you would expect higher pagefile or swap-file activity inside the OS. Instead, the symptoms suggest memory reclamation is happening outside the guest, which points to hypervisor swapping. In Nutanix AHV terms, that means the platform is reclaiming memory at the virtualization layer, causing performance degradation even though the guest does not show heavy internal paging. Therefore C is the most likely cause.

The distractors are weaker. “CVM swapping” would indicate pressure in the storage/control path VM, not necessarily this guest’s memory experience. Ballooning and swapping are not mutually exclusive, and the question’s evidence does not specifically prove ballooning is disabled. This is a troubleshooting pattern-recognition question: slow VM, full memory use, low guest pagefile use, and overcommit enabled usually indicates the hypervisor is swapping, so C is the best answer.

A Nutanix vDisk live migration moves the VM’s virtual disks into a new storage container while the VM remains online. For that to complete, the destination container must have enough available capacity to receive the migrated vDisk objects. If the target container lacks space, the migration can stall or fail because Nutanix cannot fully place the destination copy and complete the handoff. This makes insufficient storage space in the target storage container the most direct explanation. Nutanix migration and storage workflows consistently rely on adequate target-side capacity before the move can finish successfully. ( portal.nutanix.com )

The distractors are less precise. Source-side snapshots can be part of protection or internal workflow behavior, but the question is specifically about moving to a new container, so target capacity is the key gating factor. “Local storage container” is too vague and is not the normal object referenced in this workflow. Operationally, the right next step is to confirm free space, reservations, and any capacity constraints on the destination container before retrying the migration. That is why B is the best answer.

Nutanix’s NCC ec_enablement_check identifies containers where erasure coding could save space, but administrators still need to apply judgment based on workload behavior. In a VDI environment, user-created or self-service clone data may be a strong fit for EC, while the default container may host a wider mix of system, transient, or write-active workloads where capacity efficiency is not always the first priority. Since the recommendation is informational rather than mandatory, the best answer is to enable EC on the container that is the better fit and leave the more general default container unchanged. That makes D the most balanced answer.

This question is testing operational discretion. “Enable EC everywhere NCC mentions” is too simplistic. Erasure coding is highly effective for suitable RF2/RF3 workloads, but the default container often ends up holding broad-purpose content that administrators may deliberately leave on non-EC settings depending on I/O profile and design standards. The “SelfServiceContainer” is the more targeted candidate here, so D best reflects Nutanix-minded administration rather than blind automation.