Nutanix NCP-MCI-6.5 Practice Questions

Explanation: According to the Nutanix Support & Insights web search result1, the administrator can change the frequency of checks and alerts for the System Non-Root Partition Usage in Prism Element by going to the Health Dashboard > Manage Checks > Schedule. The administrator can select the check name, such as disk_usage_check, and click on Edit Schedule. The administrator can then choose the desired frequency, such as every 15 minutes, every hour, or every day, and click on Save. This will change how often the check runs and alerts are generated.

Explanation: Data locality is the capability of storing VM data on the node where the VM is running and ensuring that the read I/O does not have to traverse the network. Data locality is a unique feature of Nutanix that provides high performance and low latency for VMs by minimizing network traffic and crosstalk. Data locality works by writing one copy of the data local to the VM and the other copy (or copies) on other nodes. When a VM migrates to another node, Nutanix also moves its data to the new node and serves all I/O requests locally. Data locality also adapts to changing workloads and access patterns by dynamically moving data to where it is needed most1.

Explanation:
A. This statement is incorrect because there is no static threshold set to trigger a critical alert at 6000 MB. The graph shows a peak that goes above 6000 MB, but the alert configuration below does not specify a static threshold at this value.
B. This is the correct statement. The configuration under "Behavioral Anomaly" is set to alert every time there is an anomaly, with a critical level alert set to trigger when the I/O working set size is between 0 MB and 4000 MB. The graph illustrates that the anomalies (highlighted in pink) occur when the working set size exceeds the normal range (blue band). Therefore, any anomaly detected above 4000 MB would trigger a critical alert.
C. This statement is incorrect because there is no indication that a warning alert is configured to trigger after 3 anomalies. The exhibit does not show any configuration that specifies an alert based on the number of anomalies.
D. This statement is incorrect as there's no indication that a warning alert will be triggered based on the I/O working set size exceeding the blue band. The alert settings are configured to ignore anomalies below 4000 MB and to trigger a critical alert for anomalies above this threshold.
The settings displayed in the exhibit are typically part of Nutanix's Prism infrastructure management platform, which can set various thresholds for performance metrics and trigger alerts based on those thresholds. The behavior is defined in the Prism documentation where the alert configuration is outlined.

Explanation: Configure VM-Host affinity for the nodes that meet the application’s GPU requirement. This is because VM-Host affinity allows the administrator to specify which nodes a VM can run on or must not run on1. By creating a VM-Host affinity rule that binds the application VM to the three nodes that have the physical GPU, the administrator can ensure that the VM will always run on a node that meets its requirement, regardless of any HA or migration events. This also allows the other nodes in the cluster to host other VMs without any restrictions.