Nutanix NCP-MCI-6.10 - Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10)

Understanding the Exhibit & Memory Allocation

Thehost has 128GB of physical RAM.

Thecurrent memory allocationacrossthree VMs (VM1, VM2, VM3) is 128GB, but only92GB is actually utilized.

This means there is36GB of unutilized memory available for allocation.

Step-by-Step Breakdown

Existing Memory Usage Before Adding VM4

Total Physical RAM:128GB

Used by running VMs (VM1, VM2, VM3):92GB

Unutilized Memory Available:36GB

After Creating and Running VM4

VM4 is allocatedmemory but only utilizes 28GB.

The table does not show VM4’s allocated RAM, but assuming it was given a reasonable allocation, it must have been taken from the36GB unutilized memory pool.

IfVM4 uses 28GB, theremaining unutilized memory is now (36GB - 28GB) = 8GB.

Maximum Memory Allocation for VM5

Sinceonly 8GB remains unutilized, the maximum memory VM5 can be allocated while still allowing it to power on is8GB.

Evaluating the Answer Choices

(A) 4GB❌(Incorrect)

More memory (8GB) is available, so limiting to 4GB is unnecessary.

(B) 8GB✅(Correct)

Theremaining unutilized memory after VM4 is 8GB, so VM5 can be allocated up to8GBwhile ensuring it can power on.

(C) 16GB❌(Incorrect)

Only8GB is left, so 16GB isnot possible.

(D) 32GB❌(Incorrect)

There isnot enough unutilized memoryto allocate 32GB.

Key Concept: Nutanix Memory Overcommit

Nutanix AHV supportsmemory overcommit, meaning VMs can be allocated more memory than physically available usingmemory ballooning and swapping.

However,to power on VM5 without impacting performance, it must fit within the available unutilized memory, which is8GB.

Nutanix storage containers allow administrators to configure capacity reservations and advertised limits for better resource management.

Option D (Set Reserved Capacity to 10 GiB and Advertised Capacity to 500 GiB) is correct:

Reserved Capacityensures that10 GiB is always available for this container and not consumed by other containers.

Advertised Capacitydefines alogical limit of 500 GiBto prevent over-allocation.

Option A is incorrect:

Advertised Capacity of 10 GiB is too lowand does not match the requirement of a500 GiB storage container.

Option B is incorrect:

Only setting Advertised Capacity does not guarantee Reserved Capacity, meaning other containers could consume the reserved space.

Option C is incorrect:

Setting only Reserved Capacity does not enforce an upper limit, which could lead to overprovisioning.

https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v6_10:mul-configure-data-in-transit-encryption-pc-t.html

"Ensure that port 2009 is open between the Prism Central instances for the KMS cluster to communicate."This is explicitly stated in the "Firewall rules for Data-in-Transit Encryption" section for Prism Central.

Technical Context:

Port 2009 is used by ZooKeeper (the coordination service for the KMS cluster) in Scale-Out Prism Central deployments.

DiTE in Prism Central relies on a dedicated KMS cluster that synchronizes encryption keys across PC instances using this port.

Firewall blocks on port 2009 break KMS quorum, preventing key exchange and causing DiTE to fail.

In a dark site deployment, LCM does not automatically fetch updates from the internet. The administrator must manually upload compatibility bundles.

Option B (The latest compatibility bundle has not been uploaded) is correct:

Thecompatibility bundlecontainsfirmware mappings, allowing LCM to detect the correct BIOS version.

Option A is incorrect:

AOSdoes not need to be upgraded firstfor a BIOS update.

Option C is incorrect:

TheBMC firmware does not always need updatingbefore BIOS updates.

Option D is incorrect:

In a dark site deployment,LCM does not rely on an internet connection, so webserver access is not required.

Upgrading an AHV host with GPUs requires that the correct GPU drivers be manually uploaded to LCM, as GPU firmware is not updated automatically.

Option C (Use Direct Uploads to upload appropriate driver bundles) is correct:

LCM does notautomatically fetch GPU drivers.

The administrator mustdownload and manually upload the appropriate firmware bundlebefore upgrading.

Option A is incorrect:

Agent VMs are not requiredfor GPU updates.

Option B is incorrect:

Running LCM indark site mode does not impact GPU firmware updates.

Option D is incorrect:

Updating NCCis a best practice but does not resolve GPU driver issues.

TheBully VMs Listview in Prism Central’sIntelligent Operationsidentifies VMs that are consumingexcessive resources(CPU, memory, or storage IO) and causing resource starvation for other VMs.

From theNutanix ECA documentation:

“Bully VMs List identifies virtual machines with high resource consumption, enabling administrators to investigate and take action to prevent performance degradation in other VMs.”

The other options:

A (Constrained VMs): Shows VMs that are being starved of resources.

C (Inactive VMs): Shows VMs that are using little to no resources.

D (Overprovisioned VMs): Shows VMs with allocated resources beyond actual usage.

The Nutanix Life Cycle Manager (LCM) is designed to manage and automate firmware and software upgrades across Nutanix clusters. However, firmware upgrades via LCM are not supported for single-node clusters. This limitation is documented in the ECA course as well as in LCM’s official release notes and guides.

From the Nutanix Enterprise Cloud Administration (ECA) course materials:

“LCM does not support performing firmware upgrades on single-node clusters. These clusters require manual upgrades, and LCM will not list any available firmware updates for them, regardless of the firmware revision state.”

The other options:

A is incorrect; single-node clusters don’t have this limitation specifically for “one-disk” firmware upgrades—it’s a complete limitation for all firmware tasks in LCM.

B is misleading; LCM is supported in general for Nutanix clusters, just not for firmware tasks in single-node clusters.

D is incorrect because lack of internet connectivity would typically show an error related to download or connectivity issues, not complete absence of firmware updates.

The NCC alert indicates connectivity failure to the remote site. Resolving this involves confirming network connectivity and re-establishing the remote site configuration if necessary.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“The primary ports used for replication between clusters are 2009 (for Prism Element API) and 2020 (for data replication). Ensuring these ports are open and reachable is critical for remote site connectivity.”

Also:

“If the remote site has been re-imaged or reconfigured, it may have a new cluster incarnation ID. In such cases, the remote site configuration must be recreated to align with the current cluster information.”

Steps like checking ping with MTU 9000 (D) are not directly related to remote site connectivity for replication, and NAT configurations (B) are generally not recommended unless explicitly required.