Free Nutanix NCM-MCI Exam Dumps April 2026

To configure a DR solution that meets the stated requirements, you can follow these steps:

Log in to the Web Console of the source cluster where the VMs are running.

Click on Protection Domains on the left menu and click on Create Protection Domain.

Enter a name for the protection domain, such as PD_Mkt01, and a description if required. Click Next.

Select Mkt01 from the list of VMs and click Next.

Select Schedule Based from the drop-down menu and enter 2 hours as the interval. Click Next.

Select Remote Site from the drop-down menu and choose the remote site where you want to replicate the VM. Click Next.

Enter 5 as the number of snapshots to retain on both local and remote sites. Click Next.

Review the protection domain details and click Finish.

Repeat the same steps for Fin01 and Dev01, using PD_Fin01 and PD_Dev01 as the protection domain names, and adjusting the interval and retention values according to the requirements.

To restore the VM and ensure it is reachable on the network, you can follow these steps:

Log in to the Web Console of the cluster where the VM is running.

Click on Virtual Machines on the left menu and find Cent_Down from the list. Click on the power icon to power off the VM.

Click on the snapshot icon next to the power icon to open the Snapshot Management window.

Select a snapshot from the list that was taken before the network stack was corrupted. You can use the date and time information to choose a suitable snapshot.

Click on Restore VM and confirm the action in the dialog box. Wait for the restore process to complete.

Click on the power icon again to power on the VM.

Log in to the VM using SSH or console with the username and password provided.

Run the commandping 172.31.0.1to verify that the VM is reachable on the network. You should see a reply from the destination IP address.

Go to VMS from the prism central gui

Select the VMand go to More -> Guest Shutdown

Go to Snapshots tab and revert to latest snapshot available

power on vm and verify if ping is working

This is a classic Nutanix performance troubleshooting scenario. The issue is almost certainly that the VM was created using the wrong Disk Bus Type (IDE or SATA instead of SCSI).

Here is the step-by-step solution to complete Task 1.

Part 1: Analysis and Reporting

Create the Session

Log in to Prism Central (or Prism Element, depending on the exam environment, but Analysis is usually a PC feature).

Navigate to Operations -> Analysis.

Click New Session.

Name: Monitor SQL02

Entity: Search for and select the VM named SQL02.

Metrics: Since the issue is storage performance, search for and add these specific metrics:

Hypervisor IOPS (or Controller IOPS)

Hypervisor IO Latency (or Controller IO Latency)

Hypervisor IO Bandwidth

Click Save.

Save Session Data (Task 1.txt)

Open the 'Monitor SQL02' session you just created.

(Per instructions): Right-click anywhere on the chart/data area -> Click Select All.

Copy the selected text (Ctrl+C).

Open Notepad on the provided desktop.

Paste the data.

Save the file as Task 1.txt on the Desktop.

Create and Schedule the Report

While still in the Analysis session, click the Create Report (or 'Add to Report') button.

Report Name: MonitorSQL02

Report Settings:

Format: PDF

Frequency: Daily

Email Recipient: perf_group@ACME.org

Retention: 0 (or 'Do not retain', as requested).

Note: If the system forces you to create a new Report object and MonitorSQL02 is rejected, use monitorvm2 as the name per the instructions.

Save/Schedule the report.

Part 2: Diagnose and Fix the Issue

The Issue:

VM SQL02 was likely created with its data disks set to IDE or SATA.

Why this causes poor performance: IDE/SATA are emulated hardware with high CPU overhead and low queue depths (single-threaded).

The Standard: SQL01 (the healthy VM) is using SCSI, which is multithreaded and optimized for virtualization.

The Fix (Steps):

Navigate to the VM list in Prism.

Select SQL02 and click Update (or Edit).

Scroll down to the Disks section.

Identify the data disk(s). You will see the Bus Type listed as IDE or SATA.

Do not delete the VM. instead, perform a disk conversion (destructive change to the disk is allowed, but we want to keep the data).

Method to Convert (Clone to SCSI):

Hover over the IDE/SATA disk to see the path/filename of the vDisk (or write it down).

Click Add New Disk.

Operation: select Clone from ADSF file.

Path: Browse to the storage container and select the file associated with the current IDE disk.

Bus Type: Select SCSI (This is the critical fix).

Index: Ensure it doesn't conflict with existing disks (usually index 1 or higher for data).

Click Add.

Once the new SCSI disk is added, find the original IDE/SATA disk and click the X to remove it.

Click Save.

Note: You do not need to power on the VM to verify. The change from IDE to SCSI allows the VM to use the Nutanix VirtIO drivers for maximum storage performance.