Practice Free NCP-MCI-7.5 Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) 7.5 Exam Questions Answers With Explanation

This question is about CPU feature compatibility, not storage or networking uniformity. Nutanix documentation and KB guidance explain that VM migration can fail when clusters contain nodes with different CPU generations or different exposed CPU features. A VM that is already running with features negotiated on a newer-generation CPU may not live-migrate successfully to an older or feature-different node until it is power-cycled or configured with advanced processor compatibility. That makes C the correct answer. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

The important subtlety is that “same core count, memory, storage, subnet, and software version” does not guarantee CPU-feature equivalency. Firmware or ADS activity is not the primary issue described. Affinity rules can restrict placement, but the classic symptom after mixing repurposed nodes is CPU compatibility. Nutanix also documents that advanced processor compatibility settings persist across migrations and power cycles, reinforcing that CPU exposure is the real gating factor here.

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 VM revert behavior in Prism Central states that categories are preserved by default when a VM is reverted to a recovery point. Nutanix further notes that if an administrator wants categories to revert to the state captured in the recovery point, that must be done by using a V4 API override rather than the standard default behavior. That directly rules out choices A and B in the ordinary UI-based revert scenario. The expected default behavior is preservation of current categories, not rollback of categories to historical values.

The same recovery-point workflow also preserves present-day management context such as ownership rather than reconstructing all metadata exactly as it existed at the earlier capture point. The reason is practical: reverting the VM is primarily about workload state recovery, not about undoing every later governance assignment unless explicitly requested through advanced controls. From an administrator’s point of view, this is safer because access-control and ownership context is not unexpectedly rolled backward during a restore operation. Therefore the best answer is C: both the VM’s categories and ownership are preserved at their current state.

Nutanix separates storage resiliency reservation from compute high availability. For storage, the relevant setting is Rebuild Capacity Reservation, which reserves storage space so the cluster can self-heal and rebuild after node, block, or rack failure. For memory and compute, the relevant concept is High Availability, which reserves or accounts for host resources needed to restart workloads after a host failure. Putting those together gives the combination that best governs the remaining usable storage and memory capacity while preserving fault tolerance. That makes C the most correct answer.

The distractors either use non-standard phrasing or split the concepts incorrectly. “Memory Reservation” by itself is not the standard Nutanix answer when the exam is asking about cluster-wide restart capacity and usable memory after failure accounting. Nutanix administrators think in terms of HA for compute-memory protection and rebuild capacity reservation for storage protection. If the goal is to manage the usable remaining capacity for both storage and memory correctly, the right pair is Rebuild Capacity Reservation and High Availability. Therefore C is the authentic answer.

The key requirement here is that the playbook must fire based on a pattern of alert characteristics, not on one fixed alert policy name or ID. Nutanix Intelligent Operations documentation provides a trigger type specifically for this purpose: Alerts Matching Criteria. That trigger lets administrators filter alerts using criteria such as severity, type, title patterns, and similar attributes, which is exactly what is needed when policy identifiers vary across environments but the response logic should stay consistent. It avoids binding the playbook to one alert definition and instead binds it to the alert behavior that matters operationally. ( Nutanix )

A single Alert trigger would be too brittle because it ties the automation to one named alert policy. A Webhook trigger would move the matching logic outside Prism and add unnecessary external dependency when the requirement can already be met natively. An Event trigger is also too broad or mismatched because the question is explicitly about filtering alerts by performance-related characteristics. Nutanix created “Alerts Matching Criteria” to handle precisely this kind of cross-environment, pattern-based automation. Therefore, A is the best answer because it gives the administrator scalable, environment-agnostic remediation logic while still excluding unrelated alerts through filters. ( 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 for enabling load balancing of vDisks in a volume group states that vDisk load balancing is enabled by default for volume groups attached to VMs by using a Data Services IP address. That is the exact behavior this question asks about: how to make load balancing happen by default rather than managing it manually each time. Therefore D is the correct answer. ( portal.nutanix.com , portal.nutanix.com )

The other answers may relate to supported limits or guest best practices, but they do not describe the default-enablement mechanism. Nutanix intentionally ties this behavior to the DSIP-based attachment model, which simplifies pathing and discovery while automatically enabling the balancing behavior. So for a study guide aligned to Nutanix docs, D is the authentic answer.

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.

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.

For Prism Central–based DR between on-prem Availability Zones, Nutanix documentation states that the clusters participating in the protection workflow must be registered with Prism Central. In the standard same-management-plane deployment model, the primary and recovery clusters need to be available to the Prism Central instance orchestrating the policy and recovery objects. That is why B is the expected exam answer for successfully configuring asynchronous replication with a protection policy in this scenario. ( Nutanix )

The other options reflect common misconceptions. Identical storage-container naming is not a mandatory prerequisite because Nutanix supports vStore mapping to map source and destination containers when names differ. The strict less than 5 ms RTT requirement is associated with synchronous-style designs such as Metro Availability, not ordinary asynchronous replication. Matching Prism Central versions is good practice but is not the core requirement expressed in the documented prerequisites. Since the protection policy workflow depends on managed registration within the Prism Central DR architecture, B is the best answer. ( Nutanix )

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.

Nutanix documentation specifically identifies deduplication as providing the greatest benefit for common data sets, and it explicitly calls out full-clone VDI workloads as one of the strongest matches. In a full-clone desktop environment, many virtual desktops contain highly similar operating-system files, application binaries, and repeated data blocks. Capacity deduplication is designed to eliminate those repeated blocks and therefore reduce the total physical storage consumed by the environment. This is exactly why Nutanix recommends deduplication for such use cases.

The other answers are less targeted. Thin provisioning is useful generally but is not the signature optimization for repeated-content VDI storage. Erasure coding is powerful for write-cold data and capacity efficiency, but it is not the primary answer Nutanix recommends for full-clone VDI patterns. “Post-process map reduce” is not the standard storage-efficiency answer expected in this context. For exam purposes, whenever Nutanix asks about full-clone VDI, the important association is with capacity deduplication, because that feature directly exploits the high block similarity across cloned desktops. Therefore B is the correct and most authentic answer.

Nutanix documents Storage QoS as the correct mechanism to throttle VM I/O and prevent noisy-neighbor behavior. Nutanix also documents that storage policies in Prism Central apply to Categories, and that QoS settings such as throttled IOPS can be defined in the storage policy itself. That means the administrator can create one policy, set the IOPS cap, and apply it to the category assigned to Dev VMs. Current and future VMs with that category then inherit the same behavior without one-by-one configuration. That is exactly the scalable model described in option B.

The other options do not meet the requirement as cleanly. Replication factor affects resilience, not IOPS governance. Cloning one VM’s QoS is not a robust policy framework for future operations, especially when category-based automation already exists. Compression changes storage efficiency and sometimes performance characteristics, but it does not function as an enforceable per-VM IOPS cap. Because Nutanix explicitly ties QoS throttling to storage policies and category-based assignment, B is the documented and most maintainable answer.

Nutanix documentation for PD-based DR remote-site configuration states that if vStore mapping is not configured, replication occurs to the remote container with the same name as the source container. Nutanix further explains that this fallback relies on the existence of that matching destination container. Therefore, if same-name containers do not exist on the two sites and no explicit vStore mapping is defined, the replication target cannot be resolved correctly and the replication will fail. That makes A the correct answer.

This behavior is intentional. Nutanix does not randomly pick a destination container, nor does it silently force all replications into the default container. When administrators want different container names between source and target, the supported mechanism is vStore mapping. Skipping that mapping only works when identical container names already exist at both sites. Because the question explicitly removes that condition, replications fail to complete, which is why A is the authentic answer.

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 )

In Prism Central VM efficiency and behavioral-learning views, Nutanix groups inefficient VMs into categories such as over-provisioned, inactive, bully, and constrained. A constrained VM is one that does not have enough resources for its workload and is therefore experiencing pressure. Nutanix documentation ties constrained status to signs such as CPU readiness, memory swapping, or other stress indicators that show the VM is not adequately provisioned for what it is trying to do. That means the best interpretation is that those VMs are lacking sufficient resources, which is option B. ( Nutanix Portal )

This category is different from the other distractors. An inactive VM is mostly idle and not making meaningful use of its assigned resources. An over-provisioned VM is wasting capacity because it was allocated too much. A VM that is merely “consuming too much CPU” could be a bully VM or simply a busy VM, but that alone does not define the constrained classification. Nutanix uses the constrained label to signal a right-sizing opportunity in the direction of adding or adjusting resources, not reclaiming them. Therefore the most accurate answer is B, because constrained VMs are the ones that are short on sufficient resources for their workload behavior. ( 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.

Nutanix documents Logbay as the preferred and supported mechanism for efficient platform log collection. The AHV administration guide states that you can use Logbay only after the CVM is installed on the node or the AHV compute node has been added to the cluster, which directly matches the wording in option A. Nutanix’s web-console guidance also points administrators toward Logbay as the preferred collection method rather than relying only on manual UI collection.

The other options describe tools or behaviors that do not match Nutanix’s documented collection path for this scenario. Panacea is not the standard answer for supported cluster log-bundle collection in the way described. Storage policy reports are not substitutes for host/CVM diagnostic logs, and ADS does not function as an automatic diagnostic bundle exporter for arbitrary contention events. Because the question asks for both the supported approach and a key prerequisite, Logbay with the documented availability condition is the most precise Nutanix answer. Therefore A is correct.

Nutanix AHV documentation for Windows Defender Credential Guard support states that the VM must be configured with UEFI and Secure Boot enabled, and Nutanix security guidance for vTPM explains that vTPM is used to protect Windows credentials and is part of the trusted platform features required by modern Windows security functions. Together, these requirements map directly to option D: enable UEFI firmware, enable Secure Boot, and add a vTPM device.

The other options each contain a flaw. IDE is not the correct secure-boot bus choice in these workflows, legacy BIOS does not satisfy the modern secure boot requirement, and “Generation 2 firmware” is Hyper-V-oriented wording rather than the standard AHV requirement stated in Nutanix docs. The policy in the question explicitly mentions rootkit resistance and credential isolation, both of which are tied to Secure Boot and TPM-backed trust. Therefore Nutanix’s documented VM configuration that satisfies those requirements is exactly what is described in D.

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 )

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 )

The Nutanix setting designed to protect a portion of space for a particular container is Reserved Capacity (Logical). The role of this setting is to logically reserve capacity for that container so that other containers sharing the same storage pool cannot consume all the available space first. In exam language, this is the option that guarantees a minimum amount of usable headroom remains allocated for that container’s future growth, independent of the consumption behavior of neighboring containers. ( Nutanix Portal )

The distractors represent metrics or controls with different purposes. Advertised Capacity influences how much capacity is presented logically, but it does not reserve space. Throttled IOPS controls performance, not capacity isolation. Total Space (Physical) is simply a capacity measure and offers no reservation behavior. Nutanix separates storage efficiency, capacity reporting, and capacity reservation into different controls, so administrators need to choose the one aligned to the requirement. Because the question asks for a guarantee that one container retains a minimum amount of available storage even when others are consuming space, the correct answer is Reserved Capacity (Logical). ( Nutanix Portal )

When the requirement is to deploy multiple remote clusters efficiently from a central point, Nutanix’s intended tool is Foundation Central. Nutanix documentation describes Foundation Central as a way to manage several Foundation instances from a single pane of glass, allowing administrators to create clusters of remote nodes. That design matches the scenario perfectly: five newly purchased clusters, remote deployment, and a need for efficiency and centralized control. ( Nutanix Portal )

The other tools are more limited in scope. Foundation for Windows/Mac and a standalone Foundation VM are useful for imaging and cluster creation, but they do not provide the same centralized, multi-cluster orchestration model that Foundation Central provides. Phoenix ISO is a recovery or re-imaging tool and is not the normal answer for greenfield mass deployment. In short, this question is less about “which tool can build a cluster” and more about “which tool is purpose-built for remote, scaled deployment across many clusters.” Nutanix positions Foundation Central exactly for that use case, so B is the best answer. ( Nutanix Portal )

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 )

Nutanix documentation for Prism Central point-in-time backups states that the Recovery Point Objective (RPO) can be configured in values ranging from 1 hour to 24 hours. Since the question asks for the RPO time in hours for Prism Central backups, the expected exam answer is the maximum supported interval of 24 hours, which corresponds to option A.

This is not asking how long recovery takes or how long restore points are retained. Nutanix documents those separately. The RPO defines how often recovery points can be taken, and Prism Central’s backup framework allows choices up to a 24-hour interval. That is why values like 36, 48, or 72 hours are not supported answers in the documented PC backup workflow. So for an authentic Nutanix-aligned study sheet, A. 24 is correct.

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 )

For storage-dense nodes, Nutanix allocates CVM resources to ensure the Controller VM can handle storage services efficiently. Official Nutanix documentation shows the Controller VM requires a minimum of 12 vCPUs, and Foundation documentation describes CVM vCPU allocation ranges that increase based on platform characteristics and workload needs. In a dense-storage design with 100 TB per node, the exam-aligned answer is 12 logical cores for the CVM. ( Nutanix Portal )

The key concept here is not simply memorizing one number, but understanding why dense storage affects CVM sizing. The CVM runs critical storage-path services, metadata handling, and data services operations. As node capacity increases, Nutanix expects sufficient CPU to sustain those functions under load. Options 6 and 8 are too small for the documented baseline direction shown in official guidance, while 14 is not the standard answer expected for this scenario. For exam purposes, when the question frames a dense storage node with 100 TB, the supported sizing answer is 12. ( Nutanix Portal )

Nutanix LCM documentation for the pre-check test_ahv_entering_mm_pinned_vms explains that this check identifies VMs that block the host from entering maintenance mode. Nutanix also notes that during host updates, LCM automatically shuts down running non-migratable VMs before updating the host. In practice, VMs using certain pinned or non-migratable features—such as specific agent, passthrough, or unsupported migration cases—must be powered off if they cannot be moved safely. That makes D the best answer. ( portal.nutanix.com , portal.nutanix.com )

The key is that not every special VM can live-migrate in every environment. Credential Guard migration has CPU-generation limitations, and pinned or specialized VMs can still block maintenance. The safest supported action for the listed blocked VMs is to power them off, let the host enter maintenance mode, and then proceed. So D is the right operational answer.