Correct Answer:

See the Explanation below for detailed answer.
Explanation:
Here is the step-by-step solution to complete both tasks on Cluster 1.
This solution requires you to first find the IP of Cluster 2 (for the SMTP server) and then perform all configurations within the Prism Element interface for Cluster 1.
Prerequisite: Find Cluster 2 IP
* In Prism Central, navigate to Hardware > Clusters.
* Find Cluster 2 in the list and note its IP Address. You will use this in the steps below.
Task 1: Create the VM Template
* Log in to the Prism Element (PE) interface for Cluster 1. (From PC, go to Hardware > Clusters > click the name "Cluster 1").
* Navigate to the VM view from the main dashboard.
* Click the + Create VM button.
* Fill in the VM details based on the NVD-2031 "Small VM" configuration (e.g., 2 vCPUs, 1 Core per vCPU, 4 GB RAM).
* Name: Small Template
* Compute Details:
* vCPUs: 2
* Number of Cores per vCPU: 1
* Memory: 4 GB
* Scroll down to Storage and click + Add New Disk.
* Operation: Select Clone from Image Service.
* Image: Select any available guest OS image (e.g., a Windows or CentOS image).
* Storage Container: Ensure the default container is selected (as required by the task).
* Click Add.
* Scroll down to Network Adapters (NIC) and click + Add NIC.
* Select any available VLAN/Subnet (e.g., Primary).
* Click Add.
* Click Save. The VM will be created (and remain powered off).
* Find the new Small Template VM in the list. Select its checkbox.
* Click the Actions dropdown and select Convert to Template.
* Confirm the action by clicking OK.
Task 2: Configure SMTP and NCC Reports
* While still in the Cluster 1 Prism Element interface, click the gear icon (Settings) in the top-right corner.
* Select SMTP Server from the left-hand menu.
* Click the Configure button.
* In the "Server Settings" tab, fill in the following:
* Server Address: Enter the Cluster 2 IP Address (which you found in the prerequisite step).
* Port: 25 (leave as default).
* From Email Address: [email protected]
* Click Next.
* In the "Email Recipients" tab, click + Add Email Recipient.
* Address: [email protected]
* Ensure all severities (Critical, Warning, Info) are checked.
* Click Save.
* Click + Add Email Recipient again.
* Address: [email protected]
* Ensure all severities are checked.
* Click Save.
* Click Done. A test email will be sent.
* In the main Settings menu, select Alerts and Notifications.
* Scroll to the NCC Health Checks section.
* Check the box labeled Email Nutanix Cluster Check reports to recipients. (This will use the SMTP settings and recipients you just configured).
* Click Save.

Correct Answer:

See the Explanation for step by step solution.
Explanation:
To configure the cluster to meet the requirements of the infosec team, you need to do the following steps:
Log in to Prism Central and go to Network > Syslog Servers > Configure Syslog Server. Enter Corp_syslog as the Server Name, 34.69.43.123 as the IP Address, and 514 as the Port. Select TCP as the Transport Protocol and enable RELP (Reliable Logging Protocol). This will create a syslog server with the highest reliability possible.
Click Edit against Data Sources and select Cluster B as the cluster. Select API Requests and Replication as the data sources and set the log level to CRITICAL for both of them. This will enable audit logs for API requests and replication capabilities for the top 4 severity levels (EMERGENCY, ALERT, CRITICAL, and ERROR) and push them to the syslog server. Click Save.
Repeat step 2 for any other clusters that you want to configure with the same requirements.



To configure the Nutanix clusters to enable audit logs for API Requests and replication capabilities, and push them to the syslog system with the highest reliability possible, you can follow these steps:
Log in to the Nutanix Prism web console using your administrator credentials.
Navigate to the "Settings" section or the configuration settings interface within Prism.
Locate the "Syslog Configuration" or "Logging" option and click on it.
Configure the syslog settings as follows:
Syslog Name: Enter "Corp_syslog" as the name for the syslog configuration.
Syslog IP: Set the IP address to "34.69.43.123", which is the IP address of the syslog system.
Port: Set the port to "514", which is the default port for syslog.
Enable the option for highest reliability or persistent logging, if available. This ensures that logs are sent reliably and not lost in case of network interruptions.
Save the syslog configuration.
Enable Audit Logs for API Requests:
In the Nutanix Prism web console, navigate to the "Cluster" section or the cluster management interface.
Select the desired cluster where you want to enable audit logs.
Locate the "Audit Configuration" or "Security Configuration" option and click on it.
Look for the settings related to audit logs and API requests. Enable the audit logging feature and select the top
4 severity levels to be logged.
Save the audit configuration.
Enable Audit Logs for Replication Capabilities:
In the Nutanix Prism web console, navigate to the "Cluster" section or the cluster management interface.
Select the desired cluster where you want to enable audit logs.
Locate the "Audit Configuration" or "Security Configuration" option and click on it.
Look for the settings related to audit logs and replication capabilities. Enable the audit logging feature and select the top 4 severity levels to be logged.
Save the audit configuration.
After completing these steps, the Nutanix clusters will be configured to enable audit logs for API Requests and replication capabilities. The logs will be sent to the specified syslog system with the highest reliability possible.
ncli
<ncli> rsyslog-config set-status enable=false
<ncli> rsyslog-config add-server name=Corp_Syslog ip-address=34.69.43.123 port=514 network- protocol=tdp relp-enabled=false
<ncli> rsyslog-config add-module server-name= Corp_Syslog module-name=APLOS level=INFO
<ncli> rsyslog-config add-module server-name= Corp_Syslog module-name=CEREBRO level=INFO
<ncli> rsyslog-config set-status enable=true
https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e0000009CEECA2

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.