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

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

 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 image description, the exhibit shows a screenshot of a computer screen with a table of data. The table has 6 columns and 4 rows. The columns are labeled “Date”, “Time”, “Status”, “Details”, “Configuration”, and “Duration”. The rows contain information about different configurations and their statuses. The background is a light blue color. There is a pop-up message on the bottom right corner of the screen that reads “This question has been answered. Click here to enable the edit button.”

Based on the table data, it seems that the screenshot is taken from the Prism Central web console, showing the results of a cluster health check report. The report shows that there are four failed checks: Host Password Policy, CVM Password Policy, NTP Configuration, and Cluster Time Skew2. These checks indicate that some initial cluster configuration tasks were missed during the deployment process.

The Host Password Policy check verifies that the host passwords are not set to default values and are compliant with the password policy defined in Prism Central3. The CVM Password Policy check verifies that the CVM passwords are not set to default values and are compliant with the password policy defined in Prism Central4. These checks are important for ensuring the security and compliance of the cluster. Therefore, changing the host and CVM passwords from their default values and following the password policy guidelines are two initial cluster configuration tasks that were missed.

References: 1: VM Details View - Nutanix Support & Insights 2: Cluster Health - Nutanix Support & Insights 3: Host Password Policy - Nutanix Support & Insights 4: CVM Password Policy - Nutanix Support & Insights

Deploy the Move appliance and Import the .vmdk into the Image Service. These are two methods that can be used to migrate a VM from VMware ESXi to AHV2. The Move appliance is a tool that automates the migration process by converting the VM disks and configuration to AHV format and transferring them to the Nutanix cluster3. The Image Service is a feature that allows users to upload and manage disk images that can be used to create or clone VMs on AHV4. By importing the .vmdk file of the VMware VM into the Image Service, users can create a new AHV VM from that image.

Answer: A. VM-VM anti-Affinity policy

A VM-VM anti-Affinity policy is a rule that ensures that two or more VMs don’t run on the same AHV host. It’s useful when an application provides HA and an AHV host can’t be an application’s single point of failure1. In this case, the SQL cluster VMs should have a VM-VM anti-Affinity policy configured to prevent them from running on the same host and causing an outage if that host fails. A VM-VM anti-Affinity policy can be created using the aCLI commands2. The other options are not relevant for this scenario.

References: 1: Affinity Policies - Nutanix Support & Insights 2: Affinity Policies Help | Nutanix Community

This is because there is no GUI method to unregister a cluster from Prism Central, so the process requires SSH access to the PC VM as well as to a CVM of the cluster2. The unregistration process involves getting the UUID of the cluster from the CVM and then using that to trigger de-registration from PC command line2. The unregistration process also involves cleaning up any associated metadata and configuration on both PC and PE2. Therefore, the administrator needs to use a Host SSH session to perform this task.

The correct answer is C. Network latency.

The diagram shows a solution that uses synchronous replication between two remote protection domains, cluster site A and cluster site B. Synchronous replication is a feature that allows near-zero RPO (recovery point objective) by replicating data to the remote site before acknowledging writes to the local site. However, synchronous replication has some requirements and limitations that must be met for it to work properly. One of these requirements is that the network latency between the two sites must be less than or equal to 5 ms1. If the network latency is higher than 5 ms, the synchronous replication will fail and the protection policy will be suspended2.

Therefore, based on the diagram, the most likely cause of the issue is that the network latency between cluster site A and cluster site B is higher than 5 ms, which prevents the synchronous replication from working. To verify this, the administrator can use the “ncli cluster ping” command to measure the network latency between the two sites3. If the network latency is indeed higher than 5 ms, the administrator can either improve the network performance or switch to a different replication mode, such as near-synchronous or asynchronous.