Pass the Nutanix Certified Professional (NCP) NCP-MCI-6.5 Questions and answers with ValidTests

A Nutanix cluster requires a minimum of three nodes to maintain quorum and data availability. Removing a node from a 3-node cluster would violate the redundancy factor and cause data loss. Therefore, it is not possible to remove a host from a 3-node cluster using Prism or CLI. The only way to replace a node in a 3-node cluster is to use the Foundation tool, which will erase the existing cluster configuration and create a new cluster with the new node1.

First Preference:

Policy is applied to a specific entity

2nd Preference:

Policy is applied to an entity type in a category

3rd Preference:

Policy is applied to an entity type in a cluster

4th Preference:

Policy is applied to all entities of an entity type

Comprehensive Detailed Explanation with References:In Nutanix Prism, when multiple alert policies are created and applied to the same entities, the policies are evaluated based on their specificity. The order of precedence from highest to lowest is as follows:

Policy is applied to a specific entity: Custom alert policies that are applied to specific entities take precedence over those applied to broader categories. This is because the more specific policy is usually created with a particular context or requirement in mind for that entity.

Policy is applied to an entity type in a category: The next level of precedence is given to policies that are applied to all entities of a certain type within a specific category. Categories allow grouping of entities based on certain criteria, and policies applied here are more specific than to an entire cluster or entity type.

Policy is applied to an entity type in a cluster: This refers to policies that are applied to all entities of a certain type within a specific cluster. This is more general than the above two but still targets a specific cluster environment.

Policy is applied to all entities of an entity type: The lowest precedence is given to policies that are broadly applied to all entities of a particular type across the entire Nutanix environment.

This order ensures that the most specifically targeted policies are given priority, which allows for fine-tuned control and customization of alert policies. The details of alert policy precedence are typically covered in the Nutanix Prism Central Guide and the documentation related to Prism Central's alerting and policies.

According to the Nutanix Prism Central Guide, Prism Central allows you to apply storage policies on a per VM basis using Category, so that the VM uses the storage configuration defined in the storage policy. Using a storage policy, you can manage parameters of VMs, such as encryption, type of or lack of data compression, and IOPS or Throughput throttling values to be applied to the entities.

NTP service needs to be configured to ensure logs, alerts and information is consistent across clusters that are located in different countries. NTP stands for Network Time Protocol and it is used to synchronize the clocks of all the nodes in a cluster1. This helps to maintain accurate timestamps for logs, alerts and other information that are generated by Nutanix clusters1.

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.

The correct answer is D. Fewer than 30 I/Os and less than 1000 bytes per day of network traffic for the past 21 days.

A zombie VM is a type of inactive VM that is powered on but does very little activity. A zombie VM wastes host resources such as CPU, memory, disk, and network that could be used by other VMs. A zombie VM can be identified by using the VM Profile feature in Prism Central. The VM Profile feature analyzes the resource utilization of each VM and assigns it a profile based on its efficiency and impact on other VMs. The profiles are as follows1:

Efficient: The VM is well-provisioned and has optimal resource utilization.

Over-provisioned: The VM has more resources than it needs and has low resource utilization.

Constrained: The VM has less resources than it needs and has high resource utilization.

Inactive: The VM has no resource utilization and is idle or powered off.

Bully: The VM has high resource utilization and causes contention for other VMs.

A zombie VM is a subtype of an inactive VM that meets the following criteria2:

The VM is powered on for the past 21 days.

The VM does fewer than 30 read or write I/Os (total) per day for the past 21 days.

The VM receives or transfers fewer than 1000 bytes per day of network traffic for the past 21 days.

To identify a zombie VM, the administrator can use Prism Central to view the VM Profile dashboard and filter by profile type. The dashboard shows the number of VMs in each profile type, as well as their resource consumption and efficiency score. The administrator can also drill down into each VM to see its detailed metrics and recommendations for optimization.

Nutanix Move is a tool that allows you to migrate VMs from different sources to Nutanix AHV with minimal downtime and complexity. Nutanix Move supports migration from Hyper-V to AHV, including VMs configured for UEFI-boot. UEFI stands for Unified Extensible Firmware Interface, which is a standard for the software interface between the operating system and the firmware. UEFI-boot is a mode of booting that uses UEFI instead of BIOS (Basic Input/Output System) to load the operating system. UEFI-boot offers some advantages over BIOS-boot, such as faster boot time, larger disk support, and better security features1.

To migrate a VM configured for UEFI-boot from a Nutanix Hyper-V cluster to AHV, you need to use Nutanix Move and follow these steps2:

Download and deploy the Nutanix Move appliance on the AHV cluster.

Log in to the Nutanix Move web console and add the source Hyper-V environment and the target AHV environment.

Create a migration plan and select the VMs that you want to migrate. You can choose either automatic or manual preparation mode for the migration.

Start the migration plan and monitor the progress. The migration plan will perform data seeding, which is the process of copying the VM data from the source to the target in the background.

When the data seeding is complete, perform a cutover, which is the process of shutting down the source VMs and powering on the target VMs. The cutover will also configure the boot device for the UEFI-boot VMs on AHV.

Verify that the migrated VMs are working as expected on AHV.

References: 1: UEFI Boot - Nutanix Support & Insights 2: Hyper-V to AHV and Hyper-V to Nutanix Clusters on AWS VM Migration - Nutanix Support & Insights

https://next.nutanix.com/installation-configuration-23/nutanix-vlan-34170

A GPU (graphics processing unit) is a specialized hardware device that can accelerate graphics rendering and computation for applications that use APIs such as DirectX, OpenGL, CUDA, and OpenCL. A GPU can also offload the CPU from encoding and decoding tasks for remote display protocols such as Frame Remote Desktop Protocol (FRP). A VM can use a GPU either by directly accessing a physical GPU (pGPU) on the host or by using a virtual GPU (vGPU) that shares a pGPU with other VMs. A user running a computer aided design (CAD) application may benefit from using a GPU or a vGPU to improve the performance and responsiveness of the application, especially when moving windows or rendering images. However, if the GPU or vGPU is not properly configured or provisioned, the user may experience slow response time within the VM. Therefore, to diagnose the problem, the administrator should monitor the GPU Usage metric for the VM. The GPU Usage metric shows the percentage of GPU resources that are consumed by the VM over time3. The administrator can use Prism Central to view the GPU Usage metric for each VM in a chart or a widget4. The administrator can also use Prism Central to view other metrics related to GPU performance, such as GPU Memory Usage, GPU Encoder Usage, and GPU Decoder Usage3. By analyzing these metrics, the administrator can determine if the VM is using the GPU efficiently and optimally, or if it needs more or less GPU resources.