NCP-MCI-6.10 Exam Dumps - Nutanix NCM-MCI Questions and Answers

By default, Nutanix Prism Central retains the last 10 instances of a report if no retention policy is configured.

Option B (10) is correct:

Nutanixstores up to 10 reports, after which older reports areautomatically deleted.

Options A (5), C (15), and D (20) are incorrect:

Whileretention policies can be customized, thedefault setting is 10 reports.

Data-in-Transit Encryption for Prism Central and CVMs requires specific internal communication ports to be open. Nutanix internal component documentation states:

“Port 2020 is used by the Nutanix encryption service for encrypted CVM-to-CVM communication during Data-in-Transit Encryption operations.”

This port is essential for establishing secure tunnels between control-plane services. Ports 2009 and 2010 are used by other CVM services (e.g., Stargate, Curator coordination) but not for transport encryption. Port 9440 is for Prism UI/API traffic, and while it must be accessible for management, it does not enable encrypted back-end service traffic.

Thus, the administrator must ensure that port 2020 is permitted to enable Data-in-Transit Encryption functionality.

In Nutanix Prism Central, if anadministrator is also an approverfor an approval policy, it can result in repeated prompts for approvals even after the original request is approved. This occurs because the system requires the approver (who is also the requester) to explicitly confirm actions involving protected snapshots to maintain compliance and avoid accidental deletion.

From theNutanix ECA documentation:

“When an administrator is configured as an approver in the approval policy, repeated approval requests may occur because the same user must explicitly confirm actions they initiated, such as deleting protected snapshots. This ensures administrative actions are fully deliberate.”

NutanixIntelligent Operations Reports(Option D) provideweekly summariesof cluster health, performance, and resource consumption.

These reports includerecommendations for optimization, alerts, and forecasted resource usage trends.

Option A (Admin Center LCM)managesfirmware and software upgradesbut does not generate weekly performance reports.

Option B (Prism Central Syslog)is used forlogging and event tracking, not performance summaries.

Option C (Infrastructure VMs List)provides astatic list of VMsbut does not generate periodic reports.

Nutanix Protection Policies replicate VM data between clusters using Nutanix’s built-in data protection engine. For inter-site or cloud-based replication, Nutanix documentation specifies that replication traffic can be encrypted using the Data-in-Transit Encryption feature. The internal description states:

“Data-in-Transit Encryption secures replication traffic moving between clusters by encrypting data packets before transmission across external or untrusted networks.”

This is distinct from Data-at-Rest Encryption, which protects stored data on disks but does not secure network traffic. Self-encrypting drives and secure boot only protect the VM locally, not the replication path. Because replication to NC2 travels over the Internet, encryption of the transport channel is mandatory to meet security compliance.

Therefore, the required capability is Data-in-Transit Encryption.

The Intelligent Operations and Analysis Dashboard in Prism Central supports generating ad-hoc reports. These reports are temporary artifacts and are not designed for long-term storage. Internal documentation states, “Generated reports are retained for 24 hours and then automatically purged by the system to prevent report accumulation and data bloat.” This automatic cleanup is part of the reporting subsystem and applies regardless of user role or storage location. The reports are not stored in Prism Element, nor are they archived automatically. Therefore, after the 24-hour retention window, the system removes them, explaining why the user could not find the previously generated report.

The test_esx_entering_mm_pinned_vms check in an AOS upgrade validates whether there are any pinned VMs on ESXi hosts, which could prevent host maintenance mode transitions.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Affinity or anti-affinity rules that pin VMs to specific hosts prevent those VMs from migrating during host maintenance mode entry. This directly triggers a failure in the LCM precheck test_esx_entering_mm_pinned_vms check.”

The LCM (Life Cycle Manager) precheck failures in this scenario indicate an inability to connect to vCenter to validate ESXi-specific checks, such as LACP configuration, HA, and pinned VMs. The appropriate log to analyze the details of the LCM precheck failures is the 1cm_ops.out log.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“The 1cm_ops.out log file contains detailed output and error information related to LCM operations, including prechecks, execution, and post-checks. This log is essential for troubleshooting LCM framework failures and understanding the root cause of any issues preventing upgrades.”

The Nutanix ECA course provides guidance on performance monitoring and troubleshooting for VMs, including metrics to analyze when determining whether additional vCPUs are needed. The scenario involves a VM experiencing performance issues, with the cluster performing well overall, suggesting the issue is VM-specific.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Performance Monitoring, Section: VM Performance Metrics"To determine if a VM requires additional vCPUs, analyze VM CPU Usage and VM CPU Ready Time. High CPU Usage indicates the VM is under heavy load, while high CPU Ready Time suggests the VM is waiting for CPU resources, both justifying additional vCPUs."

Module: Troubleshooting, Section: VM Performance Issues"When a VM experiences performance issues, VM CPU Usage and VM CPU Ready Time are critical metrics. CPU Usage shows demand, while CPU Ready Time indicates contention or scheduling delays, helping determine if more vCPUs are warranted."

Explanation of Options:

A. VM CPU UsageThis is correct. VM CPU Usage measures the percentage of CPU resources the VM is consuming. High CPU Usage (e.g., consistently above 80–90%) indicates that the VM is under heavy load and may benefit from additional vCPUs to handle the workload. The ECA course emphasizes:"VM CPU Usage is the primary metric to assess whether a VM’s CPU allocation is sufficient for its workload."

B. VM CPU Ready TimeThis is correct. VM CPU Ready Time measures the time a VM is ready to run but waiting for CPU resources from the hypervisor due to contention or oversubscription. High CPU Ready Time (e.g., above 5–10%) suggests that the VM is not getting enough CPU cycles, and adding vCPUs could alleviate the issue. The ECA course notes:"High VM CPU Ready Time indicates CPU contention, often resolved by adding vCPUs or optimizing resource allocation."

C. Host Memory Swap Out RateThis is incorrect. Host Memory Swap Out Rate indicates memory pressure on the host, causing memory pages to be swapped to disk. While this can affect VM performance, it is unrelated to CPU performance and does not justify adding vCPUs. The ECA course states:"Host Memory Swap Out Rate is relevant for memory-related issues, not CPU allocation decisions."

D. Host CPU UsageThis is incorrect. Host CPU Usage measures the overall CPU utilization of the host, not the specific VM. Since the cluster is performing well overall, high Host CPU Usage is unlikely, and it does not directly indicate whether the VM needs more vCPUs. The ECA course clarifies:"Host CPU Usage is a cluster-wide metric and less relevant for diagnosing VM-specific CPU performance issues."

Additional Context from ECA:

Performance Monitoring Tools: In Prism Element or Prism Central, VM CPU Usage and CPU Ready Time can be monitored underVM > Monitoror through dashboards. These metrics provide insight into the VM’s CPU demand and contention.

Adding vCPUs: The ECA course advises caution when adding vCPUs, as over-allocation can increase CPU Ready Time due to scheduling overhead. However, if both CPU Usage and Ready Time are high, adding vCPUs is justified.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports: "For VM performance issues, analyze VM CPU Usage and CPU Ready Time to determine if additional vCPUs are needed, as these metrics directly indicate CPU demand and contention."