NCP-MCI-7.5 Questions and Answers

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 )

Nutanix guidance for compression settings and current container behavior aligns with inline compression as the standard default, with an immediate (0-minute) delay model. Nutanix compression FAQ guidance also states that when deploying compression on a container, the recommended default delay for inline compression is 0, reinforcing the expected default posture for new storage containers. That makes A the correct answer. ( Nutanix )

This is one of those questions where older platform knowledge can cause confusion because historical versions and terminology evolved. The safest exam-oriented approach is to follow the current documented behavior and Nutanix’s own recommended default delay. Post-process compression with 60 minutes used to be a common mental model in older storage discussions, but the modern expected answer for a newly created container in Prism Central is inline compression with a 0-minute delay. Therefore A is the right choice. ( Nutanix )

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.

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 )

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 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.

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.

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 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 )

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 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 states that the default erasure coding window for write-cold data is seven days. That means newly written or recently modified data is not immediately converted into erasure-coded stripes. If there was a large increase in data usage over a weekend, the administrator might not yet see the expected space savings because the new data has not aged long enough to fall within the EC processing window. That is why D is the correct answer.

This is a timing question more than a configuration question. The issue is not that EC has failed or deactivated automatically; it is that the data may still be considered too “hot” for the erasure-coding policy to process under the default window. DSIP and Prism Central health are irrelevant to whether EC space savings appear on a storage container. Nutanix separates the eligibility window from the fact that EC is enabled. Therefore, after a sudden growth event, lower-than-expected savings are best explained by the default erasure coding window settings, which is option D.

Nutanix documentation describes Multicloud Snapshot Technology (MST/NMST) as a way to replicate native Nutanix snapshots directly to cloud object storage such as AWS S3 or Azure Blob, and specifically positions it as a cost-effective disaster recovery and data mobility approach. Nutanix best-practice content also says MST is especially suitable when an organization does not want to maintain a full secondary DR site and is looking for a low-cost recovery-point location in the cloud. That aligns exactly with the requirement in this question. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

Adding an NC2 recovery location or full DRaaS design can be valid but usually carries more infrastructure cost than simply replicating snapshots to object storage. A custom runbook to clone recovery points to S3 is not the native Nutanix DR method being tested. So for an external cloud-based recovery point location with cost efficiency as the deciding factor, A is the authentic answer.

Nutanix security and network-segmentation documentation clearly states that the segmented DSIP and the regular cluster DSIP are different entities, and that Prism Central needs a cluster DSIP in the same subnet to upgrade. In other words, placing the DSIP only in a secondary non-routable segment can break Prism Central’s ability to perform upgrades if Prism Central cannot reach the cluster using the expected subnet path. The documented fix is to maintain or configure a DSIP in the original communication subnet that Prism Central can use. That makes C the correct answer.

The other options are not the Nutanix-documented solution. Proxy ARP is not the prescribed remedy here, and disabling segmentation is unnecessary if the communication requirement can be satisfied by adding the proper DSIP. Uplink redundancy has nothing to do with the management-plane reachability issue in the question. So the authentic fix is to configure an additional DSIP in the original subnet used for Prism Central communication, which is C.

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 )

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 )

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 )

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.

The question is asking for the best balance of capacity efficiency, fault tolerance, and cost control. Nutanix documentation explains that erasure coding is the storage-efficiency mechanism that increases usable capacity by using parity instead of full-copy replication overhead, making it a strong fit when data is relatively cold or infrequently modified. Nutanix also documents that erasure coding requires a minimum of six nodes when using replication factor 3, which corresponds to Fault Tolerance 2 designs. That makes Erasure Coding with six nodes the correct answer.

Deduplication is valuable for certain duplicate-heavy data sets such as VDI or repeated blocks, but the question emphasizes business-critical cold data and a tight budget. In that context, erasure coding provides the more directly documented capacity-efficiency benefit. The five-node options are eliminated by Nutanix’s minimum-node requirement for RF3 erasure coding. Since FT2 implies the higher fault-tolerance design and Nutanix requires six nodes for EC with RF3, A is the correct answer.

Nutanix Move documentation states that when the administrator changes the preparation mode for only a subset of VMs under Change Settings, and there is now a mix of preparation modes across the migration plan, the overall preparation mode automatically switches to Mixed. That is exactly the condition described in the question: 10 VMs in the migration plan, two manually changed, which creates more than one preparation mode across the plan. Therefore the correct answer is D. Mixed. ( Nutanix Portal )

This is an important Nutanix Move behavior because it affects how the migration plan is displayed and managed. The administrator does not get a brand-new custom label such as “Hybrid”; Nutanix specifically uses the term Mixed to indicate that some VMs are prepared one way and others another way. It also means the plan must be reviewed carefully so each VM’s preparation setting aligns with guest OS requirements and migration prerequisites. Since the official Move documentation names this exact automatic state change, the authentic answer is D rather than Manual or Automatic. ( Nutanix Portal )

Nutanix does support exposing storage containers for hypervisor access patterns, but Nutanix also clearly recommends not using an AOS storage container as a general-purpose NFS or SMB share. For a temporary exception such as a migration host, the safer and more controlled approach is to whitelist only the exact host that needs access. Using a single host IP with a 255.255.255.255 netmask is the most restrictive option listed and follows the principle of least privilege. That reduces risk during the migration window and avoids broad, unnecessary exposure of the container to an entire subnet. ( Nutanix Portal )

This question is really about administration discipline, not just raw connectivity. Opening the whole subnet might be convenient, but it creates more attack surface and more chance of accidental mounting from unauthorized systems. Nutanix documentation steers administrators toward purpose-built file services, such as Nutanix Files, when they need true shared file access. Since this is only for a temporary migration, the best practice is a tightly scoped NFS allowlist entry for one external host. That makes B the strongest operational and security choice. ( Nutanix Portal )

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 supports storage policy–based encryption in Prism Central, which is exactly the right mechanism when only a subset of workloads needs encryption. Nutanix documentation explains that in addition to cluster-level encryption, administrators can configure storage policies to encrypt data at rest and apply those policies selectively. Since the PCI-DSS workloads are already logically groupable by category, the proper design is to create a storage policy with encryption enabled and then associate it with the category assigned to those VMs. That makes C correct. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

Cluster-level encryption would encrypt too much, which violates the requirement to leave general-purpose VMs unencrypted. Guest OS BitLocker is a separate operating-system control, not the Nutanix platform answer being tested here. Container-centric thinking is older and less flexible than policy-based encryption. Nutanix’s policy model is the authentic platform-aligned solution for category-scoped encryption using an external KMS.

For a standard AHV cluster deployment, each node typically requires one IP for the hypervisor host, one for the Controller VM (CVM), and one for IPMI or management access. Nutanix cluster-creation and expansion documentation repeatedly references entering host, CVM, and IPMI addresses for each node. If the administrator also wants a cluster virtual IP, that adds one additional IP for the cluster VIP. This results in three IPs per node plus one VIP, which is option C. ( Nutanix )

The answer choices with four IPs per node overstate the standard requirement, while the two-VIP choices add an extra VIP not requested in the question. Nutanix documentation for cluster details also distinguishes the per-node addresses from the optional virtual IP used for cluster access. So the clean way to think about this is: per node = host + CVM + IPMI, plus one shared VIP for the cluster. That aligns exactly with C. ( Nutanix )

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.

In Nutanix PD-based disaster recovery, when the source storage container name and the destination storage container name are different, the administrator must explicitly configure a vStore mapping. Nutanix documentation says that each vStores entry maps a local source storage container to a remote target storage container. Nutanix also documents that if you want replication from a local vStore to a remote vStore with different names, you provide the mapping between the local and target containers. That is exactly what this question is asking: source container Marketing, destination container Backups, and replication must know how those two names correspond. ( Nutanix Portal )

The other choices do not control storage-container placement for replicated data. Network mapping is about network connectivity for failover or recovery testing, not where the storage data lands. Network compression is unrelated to container targeting. vStore PD is not the Nutanix feature name that solves this requirement. Nutanix’s own remote-container best-practice guidance recommends establishing vStore mappings so the target container is deterministic and properly aligned to the protection design. Therefore, the correct and authentic Nutanix answer is C. vStore mapping. ( Nutanix Portal )

Nutanix documentation for creating a storage container with Replication Factor 1 shows the workflow in the Prism Element web console. The official steps begin with logging on to Prism Element, navigating to storage, and creating the RF1-enabled container there. This makes A the correct answer.

This question is really about administrative scope. RF1 is a specialized storage-container setting that is managed at the cluster level, and Nutanix documents it in Prism Element rather than Marketplace or Self-Service. Prism Central can manage many cluster-wide resources, but the specific documented RF1 container-creation workflow is rooted in Prism Element. For exam prep, when a question asks which interface is required to create an RF1 container, the safe and documentation-aligned answer is Prism Element. Therefore A is the authentic Nutanix answer.

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 )