Ace Your NCP-MCI-6.5 NCP-MCI Exam

According to the Nutanix Prism Central Guide, role-based access control (RBAC) in Prism Central allows you to create custom roles and assign them to users or groups based on the categories of the entities they need to manage1. Categories are key-value pairs that you can assign to entities such as VMs, hosts, clusters, images, etc. to group them logically2. For example, you can create a category key called “OS” and assign values such as “Linux” or “Windows” to different VMs based on their operating system.

In the exhibit, the Linux Admin role has been created with the following settings:

• The role has the “VM Admin” permission, which allows the user to perform all actions on VMs3.
• The role has been assigned to the admin1 user.
• The role has been scoped to the entities that have the category key “OS” and the value “Linux”.

However, the admin1 user does not have access to all Linux VMs in the environment. This means that some of the Linux VMs do not have the proper category assigned to them. To grant the proper access, the administrator should add the category key “OS” and the value “Linux” to each Linux VM that needs to be managed by the Linux Admin role. This can be done either individually or in bulk through Prism Central4. Once the categories are added, the admin1 user will be able to see and manage all Linux VMs in the environment.

Answer: D. Load the Virtual SCSI pass-through controller.

The error message shown in the image indicates that Windows 10 setup cannot find any drives to install the OS. This is because the Nutanix AHV hypervisor uses a virtual SCSI pass-through controller to present disks to the VMs, and Windows 10 does not have a built-in driver for this device. Therefore, the administrator needs to load the Nutanix VirtIO driver for the virtual SCSI pass-through controller during the OS installation process. The Nutanix VirtIO driver package contains various drivers that are specifically used by Windows VMs hosted in the Nutanix environment to enhance their stability and performance1. The administrator can download the latest Nutanix VirtIO driver package from the VirtIO downloads page of the Nutanix support portal. The administrator can then follow these steps to load the driver and install the OS2:

• On the Windows 10 setup screen, click Load driver.
• Insert a USB drive or mount an ISO image that contains the Nutanix VirtIO driver package.
• Browse to the location of the driver package and select the folder that matches the OS architecture (32-bit or 64-bit).
• Select the vioscsi.inf file and click Next.
• Wait for the driver to load and then click Refresh.
• Select the disk where you want to install Windows 10 and click Next.

References: 1: VirtIO Driver Versions for Windows 2: Installing Windows on AHV

Fault tolerance (FT) is the ability of a cluster to withstand node failures and maintain data availability. FT is determined by the replication factor (RF) of the data, which is the number of copies of each data block stored on different nodes. FT = RF - 1, meaning that the cluster can tolerate as many node failures as one less than the RF. Block awareness is a feature that enhances fault tolerance by ensuring that data copies are distributed across different blocks, which are groups of nodes that share a power source and network switch. Block awareness requires a minimum of three blocks and a minimum of six nodes in the cluster.

In this scenario, the administrator has been asked to enable block awareness and increase the fault tolerance to FT2 on a Nutanix AHV cluster with the following configuration: Four blocks, One node per block. The administrator will not be able to accomplish these tasks because:

• To enable block awareness, the cluster needs at least six nodes, but it only has four nodes.
• To increase the fault tolerance to FT2, the cluster needs at least five nodes per RF3 or seven nodes per RF4, but it only has four nodes.

Therefore, the administrator will need to add more nodes to the cluster before enabling block awareness and increasing the fault tolerance to FT2.

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.