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

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.

Nutanix Intelligent Operations documentation for behavioral learning and VM right-sizing identifies several thresholds used to detect resource pressure, including CPU ready time > 5% and memory swap rate > 0 Kbps. Those are direct indicators that the VM is experiencing contention rather than simply being oversized or idle. A VM in that state is not comfortably provisioned; it is operating under resource pressure. Nutanix uses the term constrained VM for workloads that are lacking sufficient resources and therefore show signs of stress such as CPU wait, memory swapping, or storage-path pressure. That makes C the correct answer.

The high Host I/O Stargate CPU usage strengthens the case that this is an under-served or stressed workload rather than an inactive or over-provisioned one. An inactive VM would not show these pressure signals. An over-provisioned VM typically wastes allocated resources but does not struggle for them. A bully VM consumes disproportionate resources and affects others, but the threshold clues given in Nutanix right-sizing guidance map more directly to a VM that is constrained. Therefore the most accurate category for these observed characteristics is C. Constrained VM.

In Prism Central, Runway Analysis is not a simple reading of current utilization; it is a forecast based on historical consumption trends. Nutanix documentation explains that capacity planning and runway use machine learning and historical resource behavior to estimate when CPU, memory, or storage will run out. That means a cluster can still show only 60% memory used today and yet have a short memory runway if the memory-consumption trend has been climbing steadily and rapidly over recent history. In this scenario, the most likely reason for only 12 days of runway is sustained growth in memory use over the historical observation period. ( Nutanix )

The distractors do not fit the documented behavior as well. Nutanix does support scenario modeling, but a low runway in the standard view is primarily a forecast outcome, not a default penalty for missing history or a result of guaranteed HA mode by itself. HA reservations can reduce available effective capacity, but the wording of the question points to forecasting logic rather than static reservation math. Since Nutanix runway is based on actual consumption trends, the answer that best explains a low runway despite moderate present-day utilization is that memory usage has been continuously increasing, which is option B. ( Nutanix )

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 )

The uploaded answer key lists B, and that is the safest supported choice among the options because it preserves the cluster’s all-NVMe storage profile rather than introducing mixed media tiers or an all-SSD design that changes the storage architecture. In Nutanix cluster expansion planning, keeping node media type aligned with the existing cluster profile is the normal supported design principle, especially when the existing cluster is already Full-NVMe. Nutanix storage documentation also emphasizes a single storage-pool-per-cluster model and consistent cluster design so that performance and capacity are optimized predictably across the nodes.

The alternative answers introduce obvious design mismatches. Mixed NVMe+HDD or SSD+NVMe nodes would materially change latency and tier behavior, while adding an all-SSD node into a Full-NVMe cluster would also break architectural consistency. Although the exact public expansion-matrix wording was not surfaced in the search results, the answer set itself strongly points to the only media-aligned option: one All NVMe node with 96 TiB RAW capacity. So for an exam-prep answer aligned with Nutanix design logic and the provided key, B is the correct choice.

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

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.