Explanation: According to the Nutanix Support & Insights web search result1, the name of the internal bridge used by AHV nodes and CVMs is br0. The internal bridge is an Open vSwitch (OVS) bridge that connects the AHV host management interface, the CVM interface, and the VM vNICs. The internal bridge also acts as a gateway for the CVM and VM traffic to reach the external network through the host physical NICs.

Explanation: Prism is the central service control used by Nutanix to manage the clusters. It provides a unified view of the entire system, and it is used to control the HTML5 UI, the nCLI, and the REST API. Prism is used to manage the resources of the system, such as the nodes, storage, and networks, as well as to monitor the performance of the system and the applications running on it.

PrismKey Role: UI and API

·Prism is the management gateway for components and administrators to configure and monitor the Nutanix cluster.This includes Ncli, the HTML5 UI, and REST API.
·Prism runs on every node in the cluster and uses an elected leader like all components in the cluster. All requests are forwarded to the leader using Linux Iptables. This allows access to PRISM using any CVM Ip address.
·Prism communicates with Zeus for cluster configuration data and Cassandra for statistics to present to the user. It also communicates with the ESXi hosts for VM status and related information
These are only some of the essential services that make up the CVM functionality. For more information on all the services and various Nutanix Cluster components, refer to the portal documentation.

Explanation: According to section 6 of the exam blueprint guide1, one of the topics covered is VM placement options. When creating a new VM on an AHV cluster, there are two ways to determine its initial placement:
Automatic placement: The Acropolis Dynamic Scheduler (ADS) selects a host that provides adequate resources for the VM’s configuration, such as CPU, memory, disk space, and network bandwidth. ADS also considers factors such as host load, power state, availability domains, and affinity rules.
Manual placement: The administrator can specify a host or a host group where they want to place the VM.

Explanation: VirtIO drivers are device drivers that are specifically designed for virtualized environments. They allow the guest operating system to communicate directly with the underlying hardware, bypassing the emulation layer. This improves the performance and efficiency of the virtual machines. VirtIO drivers are supported by various hypervisors, including Nutanix AHV1.
Nutanix AHV uses SCSI disks for VMs by default. However, Windows does not have native support for SCSI disks and requires VirtIO drivers to recognize them. Therefore, if an administrator is installing Windows 2019 on a new VM on an AHV cluster, they need to install the VirtIO drivers before selecting the destination disk for the installation. Otherwise, they will not see any drives listed for the install2.
To install the VirtIO drivers during Windows installation, the administrator can use one of the following methods3:
Use a VirtIO ISO image that contains the driver files. The administrator can download the VirtIO ISO image from the Nutanix support portal and upload it to the AHV image service. Then, they can attach the VirtIO ISO image to the VM as a CD-ROM device and load the driver from it during Windows installation.
Use a Nutanix Guest Tools (NGT) ISO image that contains the driver files and other tools. The administrator can download the NGT ISO image from Prism Element or Prism Central and attach it to the VM as a CD-ROM device. Then, they can load the driver from it during Windows installation.
Use a floppy disk image that contains only the driver files. The administrator can create a floppy disk image using tools such as WinImage or WinRAR and upload it to the AHV image service. Then, they can attach the floppy disk image to the VM as a floppy device and load the driver from it during Windows installation.

Explanation: According to the CPU (%) - VMware Docs web search result2, one of the possible causes of high CPU ready % is over-provisioning vCPUs for a VM or having too many VMs on a host. CPU ready % indicates the percentage of time that the VM was ready, but could not get scheduled to run on the physical CPU. High CPU ready % can lead to VM performance problems, such as slow response time or application latency. To improve VM performance, the administrator should reduce the number of vCPUs assigned to VMs or reduce the number of VMs on the hosts, so that there is less contention for CPU resources.

Explanation: According to the web search results, the most efficient action an administrator should take to ensure a supported state when adding a node with a higher AOS release to an existing cluster is to perform a standalone reimage of the new node and then add it to the cluster1. This way, the new node will have the same AOS version as the existing nodes, and there will be no compatibility issues or downtime. Therefore, option C is correct, while options A, B, and D are not.

Explanation: Nutanix provides two types of granular RBAC for AHV hosts: category based and cluster based3. Category based RBAC allows administrators to assign roles to users or groups based on categories, which are key-value pairs that can be applied to various entities in Prism Central, such as clusters, hosts, VMs, images, and networks. Categories can be used to group entities by different criteria, such as department, project, environment, or location. For example, an administrator can create a category key named Department and assign different values to it, such as Finance, Marketing, or Engineering. Then, the administrator can apply this category to different clusters or hosts and assign roles to users or groups based on this category. This way, users or groups can have different levels of access to different clusters or hosts depending on their department4.
Cluster based RBAC allows administrators to assign roles to users or groups based on specific clusters registered in Prism Central. For example, an administrator can create a role named Cluster Admin and assign it to a user or group for a particular cluster. This way, the user or group can have full access to that cluster and its hosts and VMs, but not to other clusters5.