Free and Premium Nutanix NCP-MCI-7.5 Dumps Questions Answers

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.

Nutanix Foundation documentation explains that Standalone Foundation can be used for imaging or re-imaging nodes, including bare-metal imaging scenarios where the target nodes do not already have a host operating system. This matches the scenario exactly: the new node has no operating system, and the administrator needs a deployment tool to image it into the cluster. Since IPMI is not configured, a centrally managed remote bare-metal workflow like Foundation Central is less appropriate than directly using Standalone Foundation for node imaging. ( Nutanix )

The other options fit different situations. Phoenix ISO is generally associated with recovery and low-level reinstallation paths rather than the normal first-choice imaging workflow for adding a new node in an expansion scenario. Discovery OS is not the intended answer for cluster imaging itself. Foundation Central is designed to orchestrate many deployments at scale, but the question is about imaging a specific new bare-metal node without existing out-of-band configuration. Nutanix documentation describes Standalone Foundation as a supported answer for exactly this type of node imaging task, so D is correct. ( Nutanix )

Nutanix security documentation is clear that vTPM data includes crucial encryption keys and that those keys must be protected through the Nutanix-supported mechanisms. Nutanix also states that encryption keys must be backed up, and third-party-style backup approaches do not protect vTPM device data correctly. If the required key backup material is missing during recovery, the restored environment cannot reconstruct the vTPM-backed trust context for those VMs. In practical terms, that means the VMs cannot be started successfully in the expected protected state because the vTPM keys cannot be recovered without the backup file. That makes D the best answer. ( Nutanix Portal )

This is why Nutanix treats vTPM-enabled workloads as a special class in protection and recovery planning. The issue is not that a new blank vTPM can simply be attached during restore, and it is not that the external KMS alone automatically recreates the VM’s vTPM identity. The trust chain depends on the protected key material. Without that backup information, Windows BitLocker and other vTPM-dependent security features cannot be restored to their original usable state. So even though the environment uses an external KMS for software encryption, the Nutanix-documented principle still applies: without the necessary key backup, the vTPM-enabled VMs cannot be recovered successfully, which is exactly what option D states. ( Nutanix Portal )

Nutanix documentation for Protection Policies supports protecting entities by category, which is the most scalable and administratively efficient method when many current and future VMs share the same RPO requirement. By assigning the marketing VMs to a category and then associating that category with the policy, the administrator avoids one-by-one maintenance and also ensures new VMs can inherit protection simply by category assignment. ( Nutanix Portal )

This is exactly the kind of pattern Nutanix encourages across Prism Central: use categories for dynamic grouping and policy application. Adding each VM individually works, but it is not the easiest or most maintainable approach for a large VM set. Templates are not the unit used here for attaching data protection to running workloads. A category-based protection model gives consistency, scale, and easier future operations, particularly when teams like Marketing may continuously create or receive new VMs. Since the question asks for the easiest way, the category-based workflow in option A is the cleanest answer and aligns directly with official Nutanix policy design. ( Nutanix Portal )

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 )

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 on capacity reservation explains that a storage container can reserve a portion of storage so that a minimum amount of capacity remains available for that specific container. When reservations are configured, one container may retain protected usable space while other containers in the same storage pool can run out of usable capacity first, even though the pool still shows free space overall. That exactly matches the scenario in the question, which is why C is the correct answer. ( Nutanix )

This is a subtle storage-administration concept. The question is not saying the pool itself is full; it says all but one container are out of space while the single pool still has free space. That pattern is much more consistent with reservation policy than with hardware failure. Failed nodes or drives would usually surface additional health symptoms and would not neatly explain one container still having preserved capacity while the others are exhausted. Nutanix intentionally allows reservation for predictable capacity control, and that is the feature responsible here. Hence A, B, and D are distractors, while C is correct. ( Nutanix )

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 service accounts states that authentication is done using a shared secret key generated and managed through IAM. The same service-account framework is designed so the account can perform actions according to assigned privileges rather than inheriting unrestricted administrator rights. In practical terms, that means a service account is meant for automation, API use, and non-interactive authentication, while still being controlled through the RBAC model. That matches D exactly.

The incorrect options reflect common misunderstandings. A service account does not simply log in with the cluster admin password, and it does not automatically inherit full administrator privileges. It is not an external-KMS construct, and certificate-based auth is not how Nutanix documents this service-account mechanism. The exam clue is the phrase “without an interactive user password” combined with “granular permissions.” Nutanix’s answer to that requirement is a service account authenticated by an IAM-managed shared secret with assignable permissions. Therefore D is the authentic Nutanix answer.

The requirement is very specific: the organization wants a single place to review security posture and compliance across on-prem Nutanix plus public cloud environments, and the output should support security operations workflows, not just basic cluster health views. Nutanix documents Security Central as the product designed for exactly this purpose. The official guide states that Security Central provides a unified view of security posture across Nutanix private cloud and AWS and Azure public clouds, and it is positioned as a multi-cloud security and compliance capability rather than just a local Prism view.

The other answers are narrower than what the question asks. Flow Network Security policy views focus on segmentation and policy state, not full multi-cloud posture management. Prism Central alerts and events are useful operational signals, but they do not replace a posture-and-compliance platform. The standard Prism Central security dashboard is not the same as Security Central’s broader cloud-security scope. Because Nutanix explicitly documents Security Central as covering Nutanix, AWS, and Azure with posture and compliance visibility, D is the authentic answer.

Nutanix documentation describes guest customization profiles as reusable configuration settings that can be applied during VM deployment from a template and also during certain clone operations. For Linux-based cloud-init workflows, Nutanix explicitly shows that when deploying a VM from a template with Cloud-Init guest customization, administrators can apply or override the customization settings at deployment time. That makes option A the cleanest and most documentation-aligned answer. ( portal.nutanix.com , portal.nutanix.com )

Why not the others? Nutanix does support guided setup and clone scenarios, but the wording “create a VM template for reusability” points most strongly to the template deployment workflow rather than one-off cloning. Cloud-init is also the Nutanix-native customization method for Linux initialization at first boot, which makes it especially suitable for standardized reusable templates. So if the goal is simple repeatable management with a template-driven lifecycle, the correct point to apply the guest customization profile is when deploying a VM with Cloud-Init guest customization, which is A. ( portal.nutanix.com )

Nutanix Flow Network Security provides built-in Quarantine category values, including Strict and Forensic. Nutanix documentation states that Strict blocks all inbound and outbound traffic, while Forensic is specifically intended for situations where you want to quarantine the VM but still allow connectivity for forensic access. The documentation also notes that you can configure the allow behavior for forensic mode, which is exactly what this incident-response scenario requires. Therefore A is the correct answer.

This is a strong example of why built-in categories matter operationally. The organization wants a change that can be applied quickly during an incident and does not require redesigning existing policies. Assigning the VM to the Quarantine: Forensic category accomplishes both goals: it uses an existing system-defined control and preserves investigator access. Strict mode would over-isolate the VM and block the forensic tooling too. Thus the most authentic Nutanix response is A.

If the organization has changed naming conventions and needs VM disks placed into containers that comply with the new standard, the direct operational method is to move the VM’s virtual disks to the correct container. In Nutanix, that action is done through live vDisk migration. This preserves workload availability while relocating storage placement to the new destination container that matches policy. The question is really about correcting existing placement, not just defining intent for future objects. ( Nutanix Portal )

The other options do not solve the immediate placement problem. A storage policy can influence behavior, but it does not retroactively relocate already placed vDisks unless that policy is tied to an action that changes their storage location. Image placement policy affects images, not existing VM disk residency. Renaming storage containers is not the right operational answer here because naming policy changes usually result in a need to place workloads into the correct containers, and administrators do not rely on renaming alone to change where current VM data lives. Nutanix’s management model supports live movement of VM storage, so A is the practical and technically correct answer. ( Nutanix Portal )

Nutanix DR documentation for test failover states that recovered test VMs are brought up in a test virtual network at the recovery AZ, separate from production. Nutanix also documents that when multiple recovery directions or multiple recovery AZs are involved, recovery planning should be created per target direction and the required production and test network mappings need to exist for the recovery plan being tested. If recovery must be tested in both directions between the two clusters, each side effectively needs a production network and a test network. That makes two production networks and two test networks the most complete and correct answer.

This question is really about symmetry. One-direction failover testing can be done with a simpler mapping set, but the moment the requirement says test recovery in both directions, each cluster must be able to act as a recovery site and provide an isolated test-recovery network. That is why a single shared test network is not the best answer here. Nutanix’s recovery-plan structure and test-failover guidance support this interpretation. Therefore C is the correct and most practical answer.

Nutanix documentation confirms that a Prism Element cluster can be registered with only one Prism Central at a time, so option B is false. Nutanix also documents support for deploying multiple Prism Central instances on the same Prism Element cluster, so option A is false as well. The presence of a dedicated Nutanix doc for deploying multiple Prism Central instances on one PE cluster directly disproves option A. ( Nutanix Portal )

That leaves C and D. Nutanix documentation does not position Marketplace as the standard mechanism described in this context for deploying additional Prism Central instances. By contrast, Nutanix clearly documents registration and unregistration workflows, including the fact that clusters can be unregistered when no longer needed and later registered again. Since a cluster can only be attached to one Prism Central at a time, repeating register/unregister operations is a valid administrative action in supported workflows. Therefore D is the best valid statement among the given options. This question is mostly testing whether you know the difference between deployment support and registration exclusivity. Multiple PC instances may exist on the cluster, but registration to management is still one-at-a-time. ( Nutanix Portal )

Here the uploaded answer key says C, but official Nutanix documentation supports D. Nutanix documents that the Recycle Bin retains deleted VMs and volume groups for up to 24 hours by default, and space is not immediately reclaimed while those deleted entities are still being retained. Nutanix also provides a specific workflow to clear space used by the Recycle Bin immediately. That behavior matches the question perfectly: the VMs were deleted earlier today, yet space has not come back. The most likely reason is that the deleted VMs are still in the recycle bin. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

The answer mentioning “Medusa once every 24 hours” is not the correct interpretation for this symptom. Nutanix’s documented retention mechanism is the recycle bin, not a once-daily reclaim cycle as the main reason space stays consumed immediately after deletion. So based on the official docs, D is the authentic answer.

Nutanix documentation clearly states that guest VMs with GPU passthrough cannot be migrated to other hosts in the cluster. By contrast, Nutanix does support live migration for some vGPU- enabled VMs under supported conditions, but not for passthrough GPUs. That distinction is exactly what this question is testing. Therefore the correct answer is D. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

This is a high-value exam distinction: vGPU and GPU passthrough are not interchangeable in migration behavior. Memory overcommitment and vNUMA may affect placement or performance, but they are not the documented hard stop presented here. If a VM uses GPU passthrough, live migration is not supported, so the administrator cannot evacuate it the way they can with ordinary VMs.

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 )

Here the uploaded answer key says B, but Nutanix documentation recommends at least five stable time sources that have a high degree of accuracy and are reachable over a reliable network. That exact wording appears in Nutanix time synchronization guidance and related KB material. Because the question specifically asks for the minimum number that constitutes a good configuration ensuring a high degree of accuracy, the Nutanix documentation supports 5, which is option C. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

Three servers is a common generic IT answer, but the Nutanix wording in its own docs is more specific and recommends five. For an NCP-MCI study document meant to stay authentic to Nutanix guidance, C is the correct answer.

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 explicitly states that in Prism Central, when you are using more than 80% of Prism Central capacity, a red PC Under-provisioned warning icon appears. That means this alert is not describing the managed cluster’s resilient capacity, nor is it about a storage over-provisioning ratio on the Prism Central VM. It is specifically tied to the Prism Central instance itself approaching its own capacity limit. ( Nutanix Portal )

This is a good example of monitoring terminology that can be misleading on the exam. Because the administrator is looking at future resource needs for clusters, it is easy to assume the warning is about the cluster being under-provisioned. However, Nutanix labels this condition as PC Under-provisioned, and the documentation ties it to Prism Central consumption, not the cluster’s resilience threshold or a failed scale-out event. Operationally, the response is to review Prism Central sizing and determine whether scale-out or resizing is required to support the monitored environment. Based on the Nutanix documentation wording, B is the correct answer. ( Nutanix Portal )

Moving a running VM between hosts in the same cluster without downtime is the exact purpose of live migration in AHV. Nutanix AHV administration guidance treats live migration as the supported mechanism for relocating active workloads between hosts while maintaining service continuity, subject to any migration restrictions such as passthrough devices or CPU compatibility constraints. Because the VM must remain powered on and operating during the move, D. Live migrate within the cluster is the correct answer.

The other options are all recovery or duplication workflows, not mobility workflows. Restoring from a backup or recovery point creates interruption and changes the task from migration to recovery. Cloning from a snapshot creates another copy rather than moving the currently running VM. Nutanix intentionally distinguishes VM recovery operations from VM mobility operations. Since the requirement is in-place movement of a live workload within the cluster, the correct and most direct method is live migration. Therefore D is the authentic Nutanix answer.

A required RPO of 5 minutes immediately points to NearSync replication, because Nutanix documents NearSync protection policies as supporting recovery points in 1–15 minute intervals. The second requirement—automatically protect new mission-critical VMs—points to a Protection Policy approach in Prism Central, because protection policies can use categories and policy-based assignment to scale protection dynamically as new matching VMs are added. Combining those two requirements makes Protection Policy with NearSync replication the correct answer. ( Nutanix )

Protection Domains can support NearSync in older or alternate workflows, but the phrase “new mission critical VMs should be automatically protected” is the clue that pushes this question toward policy-based protection rather than manually maintained membership. Asynchronous replication also fails the first requirement because its RPO target is not the 5-minute class represented by NearSync. Nutanix’s modern DR design encourages policy-driven protection for scalable, category-based administration. Therefore B is the best fit for both the RPO and automatic-inclusion requirements. ( Nutanix )

To receive an alert earlier, the administrator must lower the threshold at which the alert’s warning state is triggered. Nutanix alerting works by comparing utilization against configured warning and critical thresholds. If the threshold is lowered, the system reaches it sooner, which gives the administrator more lead time before the environment becomes capacity-constrained. Among the given options, the one that directly performs that function is decreasing the Storage Container Space Usage Exceeded alert Warning threshold, which is option C.

The other choices are weaker or misaligned. There is no meaningful “increase frequency” adjustment that changes when capacity is considered low; it would only change how often checks occur, not the trigger point. Changing the critical threshold does not provide earlier warning notice, which is what the question asks for. The wording also points more naturally to a threshold-based action rather than enabling a different alert family. In Nutanix monitoring, earlier warnings come from making the warning trigger more conservative. Therefore C is the best answer because it causes the alert to fire at a lower usage percentage and provides earlier operational notice.

Here the uploaded answer key says C, but current Nutanix documentation says the opposite. Nutanix’s Live vDisk Migration Across Storage Containers documentation explicitly states that during an ongoing vDisk migration you cannot perform operations such as clone the VM, resize the VM, or take a snapshot. Nutanix also states, under DR considerations, that you should remove the VM from the protection domain or protection policy, migrate the vDisks, and then add the VM back afterward. That means the actions listed in option C are specifically blocked during vDisk live migration. ( Nutanix Portal )

Because all four answer choices are problematic against the current documentation, this is one of the questions I would flag as flawed in the source bank. The most accurate real-world Nutanix answer is: you should not perform snapshot, clone, resize, or DR policy/protection-domain operations during the migration. So although the uploaded key marks C, the official docs indicate that C is not actually allowed. For your final study document, this question should ideally be corrected or rewritten because the documented AHV behavior does not cleanly support any listed option as a valid “can perform during migration” task. ( Nutanix Portal )

Nutanix documentation confirms that Prism Element supports both NCC execution and log collection from the web console, so options A and B are incorrect. However, Nutanix also distinguishes running checks from collecting logs as separate actions. Operationally, if the administrator is actively running NCC at that moment, log collection is not available until that task is no longer in progress. That is why the most likely explanation is that logs cannot be collected while NCC is running. ( Nutanix )

This is a classic UI workflow question. Nutanix does allow log bundle collection from the web console, and newer NCC/Logbay capabilities even extend collection options further. But that does not mean every action is available concurrently. The supported mental model is: run checks, review output, then collect logs as needed. Since the question specifically says the administrator is running NCC and is not able to collect logs, the best explanation is the conflict between those two operations at the same time. Therefore, D is the correct answer. ( Nutanix )

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 documentation for log collection in Prism Central and related Logbay guidance supports collecting logs for a specific time range, which is exactly what this question requires to minimize noise and capture only the relevant 30-minute incident window. Nutanix also documents that when sending logs to Nutanix Support FTP, the administrator can enter a support case number, allowing the bundle to be attached to the case without manual repackaging. That makes D the strongest answer: use the alert details to identify the impacted entities and timestamps, collect the logs for that time window, and upload them using the support-case workflow. ( Nutanix Portal )

The other options do not produce the right diagnostic artifact. Auto-resolve only affects alert state, not log quality. Tightening thresholds may generate more alerts, but it does not replace collecting platform logs. Exporting a CSV of alerts can help summarize incidents, but it is not the primary evidence Nutanix Support needs for performance troubleshooting. Nutanix’s supported model is very clear: identify the incident timing, collect the appropriate logs for that window, and upload the bundle in a support-compatible way. Therefore D is the authentic answer from a Nutanix troubleshooting workflow perspective. ( Nutanix Portal )

When Prism Central is scaled out for resiliency, the design goal is not only to have multiple Prism Central VMs, but also to ensure they are not placed together in a way that creates a common point of failure. Nutanix documentation around anti-affinity policies explains that VM-VM anti-affinity is used to keep selected VMs from running on the same host. In a scaled-out Prism Central deployment, this placement separation is the logical next step to strengthen resiliency, because it prevents the Prism Central instances from collapsing onto the same physical host and failing together during a node outage. ( Nutanix )

The other options are either unrelated or not the primary required follow-up. Witness Service is associated with Metro Availability and DR designs, not with the baseline requirement of distributing Prism Central VMs after scale-out. Protection Domain protection may be useful in some cases, but it does not solve co-location risk. HA reservations on the hosting Prism Element cluster address restart capacity, not placement diversity. The most direct resiliency improvement after scaling out Prism Central is to enforce separation between the Prism Central VMs. That is why D is the best answer. ( Nutanix )

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.

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.

Here the uploaded answer key says D, but current Nutanix documentation says that when a cluster is created, the system automatically creates one storage pool and one storage container. Nutanix also documents built-in containers such as NutanixManagementShare and SelfServiceContainer in later feature contexts, which is likely why older or exam-bank wording can become confusing. However, the direct cluster-creation documentation states one storage pool and one storage container are automatically created at cluster creation time. That means none of the options perfectly reflects the current documentation.

Because your source file’s answer key marks D, I am preserving that exam-bank answer here, but I want to be explicit that official current Nutanix documentation does not match these choices exactly. For a strict real-world Nutanix administration answer, I would state: one storage pool and one storage container are created automatically. For consistency with your question set, the preserved answer remains D, but this is one of the items I would flag for correction in a final polished study guide.

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 )