Nutanix NCP-MCI-7.5 - Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) 7.5

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

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 )

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.

The uploaded source file shows the answer key as B, but the supporting exhibit or calculation context is missing from the provided document, so a full mathematical derivation cannot be verified from the question bank itself. Because of that missing context, the safest exam-faithful response is to preserve the source answer of 1125 IOPS while being transparent that the exact intermediate values used to reach that number are not visible in the provided material.

From a Nutanix policy perspective, IOPS throttling is implemented through storage policies to control or cap workload consumption and prevent noisy-neighbor impact. The conceptual goal is to set a value high enough to accommodate the intended steady-state workload while still enforcing policy boundaries. In practice, administrators usually choose a value above the observed average to allow normal variance, bursts, and scheduler overhead rather than matching the average exactly. That design logic is consistent with an answer larger than 800 IOPS. Given the choices and the source key, 1125 is the preserved answer for this batch, but this is one of the questions where the missing exhibit should ideally be restored before using it as a final study reference. ( Nutanix )

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

The wording “security drift” points to SCMA rather than AIDE. In Nutanix security hardening guidance, SCMA scheduling is the control that determines how often SCMA runs, with schedule options such as hourly, daily, weekly, and monthly. That makes the SCMA schedule the setting that changes the cadence of security drift checking without changing the underlying controls themselves. ( Nutanix Portal )

AIDE is a file-integrity mechanism and has its own role, but the question is specifically asking about how often the platform checks for drift in a broader security-configuration sense. Changing the list of entities inspected or baseline enforcement behavior would alter scope or enforcement semantics, not merely frequency. The most direct administrative answer is to change the schedule for SCMA. From an exam perspective, Nutanix often separates what runs, how it is enforced, and when it runs into different settings. Here the requirement is only about “how often,” so option B is the precise match. ( Nutanix Portal )

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

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

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.