Pass the Nutanix NCM-MCI NCP-MCI-6.10 Questions and answers with Dumpstech

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 “nutanix” user is a system-level account required by the platform for internal operations, automation, cluster communication, and support access. It cannot be deleted or renamed. Nutanix security guidelines state:

“The correct method to prevent password-based SSH access for system accounts is to use Cluster Lockdown mode, which disables password authentication and enforces key-based access for all system-level CVM accounts.”

Cluster Lockdown modifies SSH configuration across all CVMs, ensuring:

password authentication is disabled

only key-based authentication is permitted

privileged system accounts such as ‘nutanix’ cannot log in interactively

Blocking port 22 is not appropriate because it would block SSH entirely, including legitimate administrative access. The “nutanix” user cannot be renamed or removed due to system dependency.

Thus, enabling Cluster Lockdown is the proper Nutanix-approved method to remove password-based SSH access for system accounts.

Enabling "Cluster Lockdown" in Nutanix is the best security measure to prevent password-based SSH logins.

Option C (Enable Cluster Lockdown) is correct:

Cluster Lockdowndisables password-based SSHandrequires key-based authentication.

Option A (Rename the nutanix user) is incorrect:

The Nutanix useris a system accountand cannot be renamed.

Option B (Block port 22) is incorrect:

This wouldprevent all SSH connections, includingkey-based logins, making administration difficult.

Option D (Delete the nutanix user) is incorrect:

Thenutanix useris required for system operations and cannot be removed.

Storage Policies in Nutanix allow administrators to configuredata protection and performance settingsat thestorage container level.

Replication Factor (RF)definesthe number of copies of datastored across nodes for fault tolerance.

Encryptionensures thatdata at rest is protectedvia Nutanix-native encryption methods.

Option A (Storage Containers and Volume Groups)refers tostorage organization, not policies.

Option C (Shares and Object Stores)applies tofile and object storage services, not VM storage policies.

Option D (Data Protection and Security)is a broad term but does not definespecific policy attributes.

Nutanix Life Cycle Manager (LCM) relies on validated firmware and driver bundles for hardware components. For GPU-enabled hosts, LCM documentation states:

“GPU-enabled AHV hosts require GPU driver bundles to be uploaded manually via the Direct Uploads mechanism so that LCM can validate and upgrade the necessary GPU components during workflow execution.”

GPU drivers are vendor-specific and not always available in the standard catalog, so the administrator must upload them before LCM can orchestrate the upgrade.

Running in dark site mode does not provide missing GPU bundles. Creating agent VMs is unrelated to GPU driver operations. Updating NCC improves validations but does not provide GPU support files.

Therefore, Direct Uploads of GPU driver bundles is required.

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.

When performing aLife Cycle Manager (LCM) upgrade, therecommended way to stop the process is to use the “Stop Update” feature in LCM (Option D).

Option A (Cancel via Ergon ecli)is not a recommended approach since manually interfering with running tasks can cause inconsistencies.

Option B (lcm_task_cleanup.py script)is used for post-upgrade cleanup but does not stop ongoing updates.

Option C (Restarting Genesis)does not stop an LCM upgrade and can cause instability.

Duringfailover in Nutanix Disaster Recovery, VMs retain theirstatic IPsbut maylose DNS settingsif the network configuration at the DR site is different from the primary site.

Option B (Create custom in-guest scripts) is correct:

Custom scriptsallowWindows or Linux VMs to restore DNS settings automaticallyafter failover.

These scripts can be executed usingpost-failover automationin Nutanix DR policies.

Option A (Self-Service Restore) is incorrect:

Self-Service Restore is used forend-user recovery of deleted files, not for network settings.

Option C (nncli tool) is incorrect:

Thenncli toolis used fornetwork troubleshooting, but it does not automatically restore DNS settings.

Option D (Configure a Protection Domain) is incorrect:

Protection Domains definereplication policies, but they do not fix DNS settings after failover.

Port mirroring requires the source and target VMs to be on the same host to efficiently copy network traffic without additional routing overhead.

Option B (Source VM and Target VM are on the same host) is correct:

AHV’s port mirroringonly works within a single hostbecause network packets are intercepted before leaving the hypervisor.

If the VMs are on different hosts,mirroring cannot be configured without additional network tools.

Option A (Same VLAN) is incorrect:

VLAN membership isnot a requirementfor port mirroring.

Option C (Same subnet) is incorrect:

Port mirroring happens atthe virtual switch level, which does not require VMs to be in the same subnet.

Option D (Same VPC) is incorrect:

While VPCs provide network isolation,they do not control port mirroring availability.