Correct Answer:

See the Explanation below for detailed answer.
Explanation:
Here is the step-by-step solution to create the category and the corresponding storage encryption policy within Prism Central.
1. Create the Category
First, you must create the category and the two values requested.
* In Prism Central, navigate to Administration > Categories.
* Click New Category.
* In the Name field, enter VM-Storage.
* In the Add a Value field, type softwareencrypted and click the Add (plus) button.
* In the Add a Value field again, type SEDencrypted and click the Add (plus) button.
* Click Save.
2. Create the Encryption Policy
Next, you will create the security policy that uses the new category.
* In Prism Central, navigate to Security > Data-at-Rest Encryption.
* Click the + Create Security Policy button.
* In the Policy Name field, enter Encrypted-Storage.
* Ensure the Encryption Type is set to Software-based.
* For Target VMs, select the radio button for VMs matching a category.
* In the Select Category dropdown, choose the VM-Storage category you just created.
* In the Select Value dropdown, choose softwareencrypted.
* Click Save.
This policy will now automatically apply software-based encryption to any new or existing VMs that are assigned the VM-Storage: softwareencrypted category.

Correct Answer:

See the Explanation below for detailed answer.
Explanation:
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: [email protected]
* 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.

Correct Answer:

See the Explanation below for detailed answer.
Explanation:
Here is the step-by-step solution to reconfigure the sql3532 virtual machine.
This task is performed from the Prism Element interface for the cluster the VM is on (e.g., Cluster 1).
1. Locate and Update the VM
* From the Prism Element main dashboard, navigate to the VM view.
* Find the VM named sql3532 in the VM table.
* Select the checkbox next to sql3532 and click the Update button.
2. Configure HA Priority and Flash Mode
In the "Update VM" dialog, configure the HA and SSD performance settings:
* HA Priority:
* Find the VM High Availability section.
* Select the High Priority radio button. This ensures it is one of the first VMs to power on during an HA event.
* Flash Mode (SSD Performance):
* Scroll down to the Flash Mode section.
* Check the box to Enable Flash Mode. This pins the VM's vDisks to the SSD tier, satisfying the requirement to keep as much of the VM as possible on SSDs, especially since it's on the default (hybrid) container.
3. Reconfigure Disks (per KB-3532)
While still in the "Update VM" dialog, scroll to the Disks section to add the new data and log disks. The key to "best performance" (KB-3532) is to place Data and Logs on separate vSCSI controllers.
* (The VM already has an OS disk, which we will assume is on scsi.0.)
* Add Data Disk:
* Click the + Add New Disk button.
* Storage Container: default (as required).
* Size: 80 GB (for the 4 x 20 GB databases).
* Bus Type: SCSI.
* Device Index: 1. (This creates a new vSCSI controller, scsi.1, for the data disk).
* Click Add.
* Add Log Disk:
* Click the + Add New Disk button.
* Storage Container: default (as required).
* Size: 20 GB.
* Bus Type: SCSI.
* Device Index: 2. (This creates a third vSCSI controller, scsi.2, for the log disk).
* Click Add.
4. Save Configuration
* After adding the disks and setting HA/Flash Mode, click the main Save button at the bottom of the
"Update VM" dialog.
The VM is now configured with high availability, its storage is pinned to SSD, and its disk layout follows performance best practices by separating the OS, Data, and Log I/O paths onto three different controllers.