Nutanix NCP-MCI-6.5 Practice Test - Questions Answers, Page 9

The number of Prism Central instances required to deploy Leap is one per customer environment.Prism Central is a multi-cluster manager that provides a single, centralized management interface for Nutanix environments3.Leap is a native cloud extension that provides disaster recovery as a service (DRaaS) for Nutanix environments4.To use Leap, customers need to have one Prism Central instance deployed in their primary site, and register it with their Xi Cloud Services account5.This Prism Central instance can manage multiple Nutanix clusters across different physical sites or availability zones6.

The only option that requires iSCSI initiator configuration in the guest OS to use Volumes is Microsoft Windows Failover Cluster.Volumes is an enterprise-class, software-defined block storage solution that exposes storage resources directly to virtualized guest operating systems or physical hosts using the iSCSI protocol7. To use Volumes, customers need to configure iSCSI initiators on their hosts or guest OSes. However, some applications or services can use native storage adapters instead of iSCSI initiators when running on AHV VMs. These include:

SQL Server Always On Availability Group: This is a high availability and disaster recovery solution for SQL Server databases that uses Windows Server Failover Clustering (WSFC) and Availability Groups (AGs) as its core components. When running on AHV VMs, SQL Server Always On Availability Group can use native storage adapters instead of iSCSI initiators.

Oracle RAC: This is a clustered database system that provides high availability and scalability for Oracle databases. When running on AHV VMs, Oracle RAC can use native storage adapters instead of iSCSI initiators.

Exchange DAG: This is a group of up to 16 mailbox servers that hosts a set of databases and provides automatic database-level recovery from failures that affect individual servers or databases. When running on AHV VMs, Exchange DAG can use native storage adapters instead of iSCSI initiators.

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.

According to the Migration to a different processor web search result2, live migration of VMs depends on the source and destination hosts having the same CPU functions (CPU flags). Live migration requires the source and destination hosts to have CPUs from the same manufacturer, and only CPU functions which both hosts support are provided (same CPU generation, or by using VMware Enhanced vMotion Compatibility (EVC)). If the administrator adds a node with older generation processors to an existing AHV cluster with newer generation processors, then live migration of VMs is prevented between newer and older processors, unless EVC is enabled.

According to the How to use the cvm_shutdown script web search result3, the cvm_shutdown script signals HA when shutting down the CVM (Controller VM) to forward the storage traffic to another healthy CVM. Instead of using sudo shutdown or sudo reboot commands, this script should be used to minimize I/O hits in user VMs running on the present hypervisor host. The cvm_shutdown -P now command will initiate the shutdown process on the CVM immediately. Therefore, if the administrator needs to perform an orderly shutdown of the CVM, they should execute this command from the CVM.

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.

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.

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.