Nutanix NCM-MCI Dumps - Pass the Nutanix Certified Master - Multicloud Infrastructure v6.10 Exam in 2026

To create a report named VMs_Power_State that lists the VMs in the cluster and their basic details including the power state for the last month, you can follow these steps:

Log in to Prism Central and click on Entities on the left menu.

Select Virtual Machines from the drop-down menu and click on Create Report.

Enter VMs_Power_State as the report name and a description if required. Click Next.

Under the Custom Views section, select Data Table. Click Next.

Under the Entity Type option, select VM. Click Next.

Under the Custom Columns option, add the following variables: Name, Cluster Name, vCPUs, Memory, Power State. Click Next.

Under the Time Period option, select Last Month. Click Next.

Under the Report Settings option, select Monthly from the Schedule drop-down menu. Enter admin@syberdyne.net as the Email Recipient. Select CSV as the Report Output Format. Click Next.

Review the report details and click Finish.

To generate an instance of the report named VMs_Power_State as a CSV and save the zip file as Desktop\Files\VMs_Power_state.zip, you can follow these steps:

Log in to Prism Central and click on Operations on the left menu.

Select Reports from the drop-down menu and find the VMs_Power_State report from the list. Click on Run Now.

Wait for the report to be generated and click on Download Report. Save the file as Desktop\Files\VMs_Power_state.zip.

1. Open the Report section on Prism Central (Operations > Reports)

2. Click on the New Report button to start the creation of your custom report

3. Under the Custom Views section, select Data Table

4. Provide a title to your custom report, as well as a description if required.

5. Under the Entity Type option, select VM

6. This report can include all as well as a selection of the VMs

7. Click on the Custom Columns option and add the below variables:

a. Name - Name of the listed Virtual Machine

b. vCPUs - A combination of the vCores and vCPU's assigned to the Virtual Machine

c. Memory - Amount of memory assigned to the Virtual Machine

d. Disk Capacity - The total amount of assigned virtual disk capacity

e. Disk Usage - The total used virtual disk capacity

f. Snapshot Usage - The total amount of capacity used by snapshots (Excluding Protection Domain snapshots)

8. Under the Aggregation option for Memory and Disk Usage accept the default Average option

9. Click on the Add button to add this custom selection to your report

10. Next click on the Save and Run Now button on the bottom right of the screen

11. Provide the relevant details on this screen for your custom report:

12. You can leave the Time Period For Report variable at the default of Last 24 Hours

13. Specify a report output of preference (PDF or CSV) and if required Additional Recipients for this report to be mailed to. The report can also simply be downloaded after this creation and initial run if required

14. Below is an example of this report in a CSV format:

Here is the step-by-step solution to create and run the report, performed entirely within Prism Central.

1. Create the Analysis Session

First, we will build the charts and entities for the report using the Analysis tool.

From the Prism Central main menu, navigate to Operations > Analysis.

Click the + New Session button.

Add the required entities:

In the 'Entities' search box, type Cluster 1 and select Cluster: Cluster 1.

In the 'Entities' search box, type SQL01 and select VM: SQL01.

In the 'Entities' search box, type SQL02 and select VM: SQL02.

Click Add Charts > New Chart to add the Cluster CPU chart:

Title: Cluster 1 Max CPU Usage

Entity Type: Cluster

Metric: Cluster CPU Usage %

Aggregation: Select Maximum.

Click Add.

Click Add Charts > New Chart to add the VM CPU Ready Time chart:

Title: VM Max CPU Ready Time

Entity Type: VM

Metric: CPU Ready Time %

Aggregation: Select Maximum.

Click Add.

2. Save and Configure the Report

Now, save the session as a report and configure it to dynamically include all VMs with the SQL prefix.

Click the Save as Report icon (the bookmark icon in the upper right).

Name the report SQL_Batch_Saturday and click Save.

Navigate to Operations > Reports.

Find the SQL_Batch_Saturday report you just created and click its name to open the report editor.

In the Entities tile, click the Edit (pencil) icon.

By default, it will list 'Cluster 1', 'SQL01', and 'SQL02'.

Change the VM selection:

Select the radio button for All VMs prefixed with.

In the text box, enter SQL.

Ensure 'Cluster 1' is still listed under 'Clusters'.

Click Save.

3. Schedule the Report

While still in the report editor for SQL_Batch_Saturday, click the Schedule button.

Configure the schedule:

Recurrence: Weekly

Repeat on: Sunday

Start Time: 12:00 AM

Time Range: Previous 7 Days

Configure the notification (as SMTP is not available):

Expand the Notification Settings section.

Check the box for Notify when ready (this enables the bell icon notification).

Ensure 'Email Report' is not checked.

Click Save.

4. Generate and Save the CSV Instance

Finally, run the report now and download the CSV as requested.

Navigate back to the main Operations > Reports list.

Select the checkbox next to SQL_Batch_Saturday.

Click the Actions dropdown and select Run Now.

In the dialog, confirm the time range (e.g., 'Last 7 Days') and click Run.

Click the Report Instances tab.

Wait for the report instance 'SQL_Batch_Saturday' to finish running (the status will change from 'Running' to Succeeded).

Once it has succeeded, click the Download (arrow) icon for that instance.

Select the CSV format.

Save the file to the desktop.

Here is the step-by-step solution to apply the security requirements to Cluster 2.

1. Access Cluster 2 Prism Element

First, we must access the Prism Element (PE) interface for Cluster 2, as most security settings are cluster-specific.

From the Prism Central dashboard, navigate to Hardware > Clusters.

Find Cluster 2 in the list and click its name. This will open the Prism Element login page for that specific cluster in a new tab.

Log in to Cluster 2's Prism Element using the admin credentials.

2. Requirement: Update Node Root Password

This task syncs the root password for all AHV hypervisor nodes with the cluster's admin user password.

In the Cluster 2 PE interface, click the gear icon (Settings) in the top right corner.

Select Cluster Lockdown from the left-hand menu.

Click the Set Root Password on All Hosts button.

A dialog box will appear. Enter the current admin password (the one you just used to log in) into both the New Password and Confirm New Password fields.

Click Save. This will propagate the admin password to the root user on all nodes in Cluster 2.

3. Requirement: Add CVM SSH Key

This task adds the security team's public key to the admin user, which is required before we can disable password-based login.

On the desktop, navigate to the Files > SSH folder.

Open the id_rsa.pub file (or equivalent public key file) with Notepad.

Copy the entire string of text (e.g., ssh-rsa AAAA...).

In the Cluster 2 PE interface, go to Settings (gear icon) > User Management.

Select the admin user and click Modify User.

Paste the copied public key into the Public Keys text box.

Click Save.

4. Requirement: Apply SCMA Policies (All other requirements)

The remaining requirements are all applied via the command line on a CVM using Nutanix's Security Configuration Management Automation (SCMA).

Access the CVM:

Find a CVM IP for Cluster 2 by going to Hardware > CVMs in the PE interface.

Open an SSH client (like PuTTY) and connect to that CVM's IP address.

Log in with the username admin and the corresponding password.

Output Current Policy (Req 2):

Before making changes, run the following command to see the current policy:

ncli scma status

Copy the entire output from your SSH terminal.

Open Notepad on the desktop, paste the copied text, and Save the file to the desktop as output.txt.

Apply New Policies (Req 3, 4, 5):

Run the following commands one by one. The cluster will apply them immediately without a reboot.

Enable AIDE (Req 3):

ncli scma update aide-status=enabled aide-schedule=weekly

Enable High-Strength Passwords (Req 4):

ncli scma update password-policy=high

Require SSH Keys for CVMs (Req 5):

ncli scma update ssh-login=keys-only

Verification

You can verify all changes by running the status command again. The output should now reflect the new, hardened security posture.

ncli scma status

AIDE Status: should show Enabled

AIDE Schedule: should show Weekly

Password Policy: should show High

SSH Login: should show keys-only

Here is the step-by-step solution to create and export the capacity planning scenario. This task is performed within Prism Central.

1. Navigate to the Planning Dashboard

From the Prism Central main menu (hamburger icon), navigate to Operations > Planning.

2. Create and Define the Scenario

Click the + Create Scenario button.

In the dialog box:

Scenario Name: IaaS

Scenario Type: Select New Workload

Click Create. This will open the scenario editor.

3. Configure Cluster and Runway Settings

In the 'IaaS' scenario editor, find the Runway setting (top left) and set it to 12 Months.

Find the Cluster configuration tile and click Edit.

Set Number of Host Failures to Tolerate to 2.

Click Save.

4. Define the Workload Profile

In the Workloads section, click the + Add Workload button.

Select Create a new workload profile.

Fill in the VM specifications:

Workload Name: Customer-VM (or similar)

vCPU per VM: 4

Memory per VM: 16 GB

Storage per VM: 200 GB

Click Add.

5. Set the Workload Growth Plan (Waves)

You will be returned to the main scenario editor. In the timeline section ('Workload Plan'), add the VMs:

Wave One (Today):

Click + Add under the 'Today' column.

Select the Customer-VM profile.

Enter 100 VMs.

Click Add.

Wave Two (3 Months):

Click the + icon on the timeline itself.

Set the date to 3 Months from today.

Click + Add under this new '3 Months' column.

Select the Customer-VM profile.

Enter 50 VMs.

Click Add.

Wave Three (6 Months):

Click the + icon on the timeline.

Set the date to 6 Months from today.

Click + Add under this new '6 Months' column.

Select the Customer-VM profile.

Enter 20 VMs.

Click Add.

6. Select the Hardware

In the Hardware configuration tile, click Change Hardware.

In the 'Select Hardware' pane:

Model: Search for and select DX365-10-G11-NVMe.

Note: This model is full-flash by definition, satisfying the requirement.

Click Done. The planner will recalculate the required nodes.

7. Save and Export the Scenario

Click the Save icon (floppy disk) in the top-right corner to save the IaaS scenario.

Click the Export icon (arrow pointing down) in the top-right corner.

Select PDF from the dropdown menu.

A 'Save As' dialog will appear.

Navigate to the Desktop.

Set the file name to IaaS-requirement.pdf.

Click Save.

Here is the step-by-step solution to configure Disaster Recovery from the Cluster 1 Prism Element interface.

1. Add Cluster 2 as a Remote Site

First, you must register Cluster 2 as a DR target for Cluster 1.

From the Cluster 1 Prism Element dashboard, navigate to Data Protection from the main dropdown menu.

Click the Remote Site tab.

Click the + Remote Site button and select Physical Cluster.

In the 'Name' field, enter Cluster2_DR_Task3.

In the 'Address' field, enter the 172.30.0.x Virtual IP address of Cluster 2.

Click Save. The clusters will exchange credentials and connect.

2. Throttle Replication Bandwidth

Next, apply the 10 Mbps bandwidth limit for traffic going to Cluster 2.

On the same Remote Site tab, select the newly created Cluster2_DR_Task3.

Click the Update button.

In the dialog, set the Bandwidth Limit to 10 Mbps.

Click Save.

3. Create the Protection Domain

A Protection Domain (PD) is the top-level object that will manage the VMs and replication schedules.

In the Data Protection dashboard, click the Table tab.

Click the + Protection Domain button and select Async DR.

For the Name, enter App_PD_Task3.

Click Create.

4. Protect VMs in a Consistency Group

Now you will add the three application VMs to the new Protection Domain as a single Consistency Group (CG).

You will be taken to the dashboard for the new App_PD_Task3. In the Entities panel, click the Protect Entities button.

In the 'Protect Entities' dialog, search for and select the three VMs:

Web-Prod

App-Prod

DB-Prod

Click Next.

Select Create new consistency group and name it App_CG_Task3.

Click Protect.

5. Create the Replication Schedule

Finally, configure the schedule to meet the RPO and retention requirements.

In the App_PD_Task3 dashboard, click the Schedules tab.

Click the + New Schedule button.

Remote Site: Select Cluster2_DR_Task3.

RPO (Repeat every): Select NearSync. Set the RPO to 1 minute.

Note: This is the lowest possible RPO for an Async (>5ms latency) connection, fulfilling the 'as close to 0' requirement.

Local Retention: Set to 2 Days.

Remote Retention: Set to 2 Days.

Ensure the 'Store snapshots for 2-way replication' checkbox is enabled to allow failback from Cluster 2.

Click Create Schedule.