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

Capacity Runway analytics in Prism Central rely on historical usage data to generate forward-looking projections. Nutanix documentation specifies:

“Capacity runway forecasts require a minimum of 30 days of historical utilization data to build growth rate baselines and trending models.”

The modeling engine uses CPU, memory, and storage trends over time to estimate depletion dates. Insufficient historical data prevents generating meaningful predictions.

Prism Central will display “Not enough data” or simply omit runway metrics until the minimum time window is met.

The 21-day threshold applies to anomaly detection, not runway calculations.

The 3-month and 6-month options refer to optimal historical windows for accuracy but are not required.

Thus, the correct requirement is 30 days of history.

Within Nutanix VM classification, Agent VMs are special-purpose system VMs designated for infrastructure tasks. The internal definition states:

“Agent VMs are not live-migratable and do not participate in high-availability evacuation; they are excluded from standard host maintenance operations.”

If a VM is mistakenly marked as an Agent VM, the hypervisor will block all migration attempts. Disabling the Agent VM flag returns the VM to standard workload treatment, making it eligible for live migration.

Updating LLDP has no relevance to VM migration. Backplane port groups affect CVM networking only. ADS influences workload placement but not migration eligibility.

Therefore, removing the Agent VM designation is required to allow migration.

The Nutanix data protection guide specifies that NearSync replication provides an RPO between 1 and 15 minutes, which is the lowest RPO available for standard asynchronous-based replication models. The documentation further states that NearSync is the supported method for achieving sub-hour RPO on one- and two-node clusters. Asynchronous replication has a minimum RPO of 60 minutes and therefore cannot be used for lowest RPO requirements. While scheduling intervals such as 1–15 minutes appear similar, Nutanix notes that these intervals are only achievable under the NearSync replication mode. Therefore, selecting NearSync is the required configuration to meet the goal of achieving the lowest RPO.

Nutanix High Availability (HA) determines the order in which VMs are restarted after a host failure or during host start sequences. Documentation states:

“VM restart priority levels defined in the High Availability policy determine which VMs are restarted first during node recovery or host power-on events.”

Nutanix HA allows administrators to assign priority levels such as High, Medium, or Low. The system ensures VMs with higher priority power on before other workloads.

Host affinity simply pins VMs to physical hosts and does not control boot order. Agent VMs are infrastructure components and not involved in workload priority. Recovery plans apply only to DR workflows, not standard host restart behavior.

Thus, the correct answer is High Availability.

Nutanix describes a special process for updating golden images or templates without modifying the original source object directly. The documentation states:

“Complete Guest OS Update creates a temporary, cloned instance of the template, boots it, and allows administrators to patch or update the operating system. Once updates are applied, the system recomposes the template with the modifications.”

This process ensures that templates remain clean and version-controlled while still allowing regular OS patching operations. Other options such as Create VM from Template merely instantiate running VMs and do not update the template source. Update Guest OS and Update Configuration refer to VM-level settings but do not create a temporary working copy for template lifecycle management.

Thus, Complete Guest OS Update is the correct feature.

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.