Answer : A
Here is the step-by-step solution to all three tasks, performed within the Nutanix Prism interface.
Task 1: Create Monitoring Session & Save Metrics
From the Prism Central dashboard, navigate to Operations > Analysis.
Click the + New Session button.
Name the session Monitor SQL02.
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.
Title: Storage IOPS
Metric: Storage Controller IOPS
Click Add.
Click Add Charts > New Chart.
Title: Storage Latency
Metric: Storage Controller Latency
Click Add.
Click Add Charts > New Chart.
Title: Storage Bandwidth
Metric: Storage Controller Bandwidth
Click Add.
Click Save Session.
With the 'Monitor SQL02' session open, right-click anywhere on the page and click Select All.
Right-click again and select Copy.
Open Notepad, paste the content, and save the file to the desktop as Task 1.txt.
(The content pasted into Task 1.txt would be the session's chart configurations, showing metrics for SQL01 and SQL02.)
Task 2: Create and Schedule the Report
While still in the 'Monitor SQL02' analysis session, click the Save as Report button (it looks like a bookmark icon).
Name the report MonitorSQL02 and click Save.
Navigate to Operations > Reports.
Find the MonitorSQL02 report in the list. Select its checkbox.
Click the Actions dropdown and select Schedule.
Configure the schedule with the following settings:
Schedule Name: monitovm2_daily_report
Recurrence: Daily
Start Time: (Set to a time, e.g., 8:00 AM)
Repeat every: 1 day(s)
Retention Policy: Uncheck the 'Retain a copy of the report' box. (This ensures reports are not retained).
Email Report: Check this box.
Format: PDF
Recipients: perf_group@ACME.org
Click Save.
Task 3: Identify and Correct the Performance Issue
This task is performed without powering on the VMs, indicating a configuration error.
Investigation
Navigate to VMs > Table view.
Click on the SQL01 (the good VM) and select the Configuration tab.
Expand the Disks section. Observe that the primary disk is attached to a SCSI bus (e.g., scsi.0). This is the high-performance standard.
Return to the VM list and click on SQL02 (the problem VM).
Expand the Disks section.
Root Cause
You discover that the primary disk for SQL02 is attached to an IDE bus. The IDE bus has significant performance limitations and is not suitable for a database server, causing the poor storage performance.
Correction
With the SQL02 VM selected, click the Update button.
In the 'Update VM' dialog, scroll down to the Disks section.
Find the disk attached to the IDE bus. Click the Edit (pencil) icon for that disk.
Change the Bus Type dropdown from IDE to SCSI.
The Device Index will automatically populate (e.g., scsi.0).
Click Save in the 'Update Disk' dialog.
(Note: A 'VirtIO SCSI Controller' will be automatically added to the VM configuration if one was not already present.)
Click Save in the 'Update VM' dialog.
The VM SQL02 is now configured to use the high-performance VirtIO-SCSI controller, which will resolve the storage performance discrepancy once the VM is powered on.
All Official Question Types