NCP-MCI-7.5 Exam Dumps - Nutanix NCP-MCI Questions and Answers

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 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 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 networking guidance makes this distinction very clearly: balance-slb (Active-Active with MAC pinning) is the bond type used when the administrator wants multi-uplink utilization without additional physical-switch configuration. Nutanix also documents that LACP requires Active-Active / balance-tcp, and balance-slb must not be combined with link aggregation protocols such as LACP. If the switch team turns on LACP while the Nutanix side remains in balance-slb, the uplink behavior is mismatched and degraded throughput is the expected result. Therefore D is the correct answer.

This is a classic exam trap because both balance-slb and balance-tcp are Active-Active styles, but they are not interchangeable. One is switch-independent and the other is switch-dependent with LACP. The problem here is not MTU, uplink count, or support for vs0. It is the fact that the switch configuration and AHV bond mode no longer agree. In Nutanix, if LACP is enabled on the switches, the virtual switch must be configured for the LACP-compatible Active-Active mode, not MAC pinning. That is why D is the authentic answer.

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.

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 DR documentation for volume groups distinguishes replication types by RPO range. Nutanix documents Asynchronous Replication as the model for 1 hour or more RPO, while NearSync covers 1 minute to 15 minutes, and synchronous/Metro designs target near-zero or zero-RPO behavior with tighter latency expectations. Since the requirement here is 1 hour and the clusters are in different geographic regions, Asynchronous is the correct fit. That makes D the right answer.

The geography in the question is also a clue. Synchronous and Metro Availability are usually associated with low-latency links and more demanding network requirements, which are not implied by “different geographic regions.” NearSync is too aggressive for a 1-hour target and is documented for much shorter RPO windows. Nutanix’s own replication taxonomy places 1 hour or more squarely in the Asynchronous category, so D 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 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.