An administrator is working to create a VM using Nutanix V3 API calls with the following specifications.
VM specifications:
* vCPUs: 2
* Memory: 8Gb
* Disk Size: 50Gb
* Cluster: Cluster 1
* Network: default-net
* Branding must be disabled on the VM
The API call is failing, indicating an issue with the payload:
"": [
"'metadata' is a required property",
"'spec' is a required property"
],
"message": "Request could not be processed.",
"reason": "INVALID_REQUEST"
The body is saved in desktop\API_Create_VM.txt.
Correct any issues in the text file that would prevent it from creating the VM. Also ensure the VM will be created as specified and make sure it is saved for re-use using that filename.
Deploy the VM through the API.
Note: Do not power on the VM.

See the Explanation below for detailed answer.
Explanation:
Here is the step-by-step solution to correct the API payload and deploy the VM.
This task is performed using the REST API Explorer within Prism Central.
1. Get Required UUIDs
To create a VM, you first need the unique IDs (UUIDs) for the target cluster and network.
* From the Prism Central dashboard, click the question mark (?) icon in the top-right corner and select REST API Explorer.
* Find Cluster 1 UUID:
* In the API Explorer, search for and select the clusters/list (POST) endpoint.
* In the Body field, paste a simple filter: { "kind": "cluster" }
* Click Send.
* In the "Response" body, find the entry for Cluster 1 and copy its metadata.uuid value.
* Find default-net UUID:
* Search for and select the subnets/list (POST) endpoint.
* In the Body field, paste: { "kind": "subnet" }
* Click Send.
* In the "Response" body, find the entry where spec.name is default-net and copy its metadata.uuid value.
2. Correct the API Payload File
The error message "'metadata' is a required property" and "'spec' is a required property" indicates the JSON in the file is malformed and missing the required root-level objects. The file content also does not match the VM specifications.
* On the desktop, open API_Create_VM.txt in Notepad.
* Delete all existing text in the file (including the POST Call and Body: lines).
* Paste the following corrected and complete JSON payload into the file.
* Replace <UUID_for_Cluster_1> and <UUID_for_default-net> with the actual UUIDs you copied in the previous step.
JSON
{
"spec": {
"name": "API_VM_Task15",
"resources": {
"power_state": "OFF",
"num_sockets": 2,
"num_vcpus_per_socket": 1,
"memory_size_mib": 8192,
"disk_list": [
{
"disk_size_mib": 51200,
"device_properties": {
"device_type": "DISK"
}
}
],
"nic_list": [
{
"subnet_reference": {
"kind": "subnet",
"uuid": "<UUID_for_default-net>"
}
}
],
"guest_customization": {
"is_overridable": true,
"override_branding": true
}
},
"cluster_reference": {
"kind": "cluster",
"uuid": "<UUID_for_Cluster_1>"
}
},
"metadata": {
"kind": "vm"
}
}
* Save and close the API_Create_VM.txt file.
Correction Summary:
* JSON Structure: The original file was malformed. The new payload provides the required spec and metadata objects at the root level.
* vCPUs: Set to 2 sockets (2 vCPUs total).
* Memory: Set to 8192 MiB (8 GB).
* Disk: Set to 51200 MiB (50 GB) and removed the unneeded CDROM.
* Cluster/Network: Placeholders are added for the required UUIDs.
* Branding: guest_customization.override_branding: true is added to disable branding for the VM.
3. Deploy the VM via API
* Return to the REST API Explorer.
* Search for and select the vms (POST) endpoint (the one with the description "Create a new vm").
* Open the corrected API_Create_VM.txt file, copy its entire contents (which now includes your specific UUIDs).
* Paste the complete JSON payload into the Body field of the vms (POST) endpoint.
* Click Send.
The API will return a 202 Accepted response, and the VM will be created (and remain powered off) on Cluster 1.

Task 12
The application team is reporting performance degradation for a business-critical application that runs processes all day on Saturdays.
The team is requesting monitoring or processor, memory and storage utilization for the three VMs that make up the database cluster for the application: ORA01, ORA02 and ORA03.
The report should contain tables for the following:
At the cluster level, only for the current cluster:
The maximum percentage of CPU used
At the VM level, including any future VM with the prefix ORA:
The maximum time taken to process I/O Read requests
The Maximum percentage of time a VM waits to use physical CPU, out of the local CPU time allotted to the VM.
The report should run on Sundays at 12:00 AM for the previous 24 hours. The report should be emailed to [email protected] when competed.
Create a report named Weekends that meets these requirements
Note: You must name the report Weekends to receive any credit. Any other objects needed can be named as you see fit. SMTP is not configured.

See the Explanation for step by step solution.
Explanation:
To create a report named Weekends that meets the requirements, 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 Weekends 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 Cluster. Click Next.
Under the Custom Columns option, add the following variable: CPU Usage (%). Click Next.
Under the Aggregation option for CPU Usage (%), select Max. Click Next.
Under the Filter option, select Current Cluster from the drop-down menu. Click Next.
Click on Add to add this custom view to your report. Click Next.
Under the Custom Views section, select Data Table again. Click Next.
Under the Entity Type option, select VM. Click Next.
Under the Custom Columns option, add the following variables: Name, I/O Read Latency (ms), VM Ready Time (%). Click Next.
Under the Aggregation option for I/O Read Latency (ms) and VM Ready Time (%), select Max. Click Next.
Under the Filter option, enter ORA* in the Name field. This will include any future VM with the prefix ORA.
Click Next.
Click on Add to add this custom view to your report. Click Next.
Under the Report Settings option, select Weekly from the Schedule drop-down menu and choose Sunday as the day of week. Enter 12:00 AM as the time of day. Enter [email protected] as the Email Recipient.
Select CSV as the Report Output Format. Click Next.
Review the report details and click Finish.

Your security team is working on automation to manage Security Policies.
They have exported some of the existing rules to the file "Security Policy.txt" located on the desktop. This file needs to be modified for the test environment.
* All rules except the quarantine rule should be logged.
* Only the Quarantine rule should be enforced, the other rules will only be logged.
* The quarantine rule should affect the SecOps environment.
* The SMB rule should only affect VMs with the "smbhost" and "smbclient" tags.
* The "DN test" policy should allow ipv6 and should not restrict any protocols between the included tiers.
There are three rules in the file, do not delete, add or copy lines. Only replace xxxx with the correct value as appropriate. It is possible that not all "xxxxx" will be replaced.
Save the file with the same name.
Possible values to replace the "xxxxx":
8080
ALL
APPLY
false
MONITOR
Non-Prod
SecOps
smbhost
smbclient
TCP
True

See the Explanation below for detailed answer.
Explanation:
Here is the step-by-step solution to modify the security policy file as required.
Navigate to the desktop and open the file Security Policy.txt (which corresponds to the provided Security Policy.bak content) using a text editor like Notepad.
Modify the file content by replacing the xxxxx and xxxx placeholders according to the security requirements.
Modifications by Rule
Here are the specific changes to make within the file:
1. Quarantine Rule
Requirement 1 (No Logging): The quarantine rule should not be logged.
Change "is_policy_hitlog_enabled": "xxxxx" to "is_policy_hitlog_enabled": "false" Requirement 2 (Enforce): This rule must be enforced.
Change "action": "xxxxx" (under quarantine_rule) to "action": "APPLY"
Requirement 3 (Environment): The rule must affect the "SecOps" environment.
Change "Environment": ["xxxxx"] to "Environment": ["SecOps"]
2. SMB-block Rule
Requirement 1 (Logging): This rule must be logged.
Change "is_policy_hitlog_enabled": "xxxxx" to "is_policy_hitlog_enabled": "True" Requirement 2 (Monitor): This rule must not be enforced, only logged.
Change "action": "xxxxx" (under isolation_rule) to "action": "MONITOR"
Requirement 4 (Tags): The rule must affect the "smbhost" and "smbclient" tags.
Change "SMBv1": ["xxxxx"] to "SMBv1": ["smbhost"]
Change "SMRv1": ["xxxxx"] to "SMRv1": ["smbclient"]
3. DN test (dn-policy1) Rule
Requirement 2 (Monitor): This rule must not be enforced, only logged.
Change "action": "xxxx" (under app_rule) to "action": "MONITOR"
Requirement 5 (Allow IPv6): This policy must allow IPv6 traffic.
Change "allow_ipv6_traffic": "xxxx" to "allow_ipv6_traffic": "True"
Final Step
After making all the replacements, Save the file, overwriting the original Security Policy.txt on the desktop.
Example of completed rules (replace xxxxx accordingly):
Rule Name: Quarantine Rule
Logged: false
Action: APPLY
Environment: SecOps
Protocols: TCP
Ports: 8080
Rule Name: SMB Rule
Logged: True
Action: MONITOR
Tags: smbhost, smbclient
Protocols: TCP
Ports: 8080
Rule Name: DN Test Policy
Logged: True
Action: MONITOR
Environment: Non-Prod
Protocols: ALL
Ports: 8080

The Infosec team has requested that all operational tasks performed within Cluster 1 be properly logged to include the top 4 severity levels and pushed to their syslog system using highest reliability possible for analysis. This is to include any Virtual Machine changes only.
The Infosec team has also requested that monitor logs for the given RSyslog Server Module be included for now. No extra logs should be included.
No other clusters should connect to this syslog server.
Syslog configuration:
* Syslog Name: Corp_Syslog
* Syslog IP: 34.142.155.231
* Port: TCP/514
Ensure only Cluster 1 is configured to meet these requirements.

See the Explanation below for detailed answer.
Explanation:
Here is the step-by-step solution to configure syslog for Cluster 1.
1. Access Cluster 1 Prism Element
Since the requirement is to only configure Cluster 1 and not other clusters, this task must be performed in the Prism Element (PE) interface for Cluster 1.
* From the main Prism Central dashboard, navigate to Hardware > Clusters.
* Find Cluster 1 in the list and click its name. This will open the specific Prism Element login page for that cluster.
* Log in to Cluster 1's Prism Element interface.
2. Add the Syslog Server
* In the Cluster 1 PE interface, click the gear icon (Settings) in the top-right corner.
* From the left-hand menu, select Syslog.
* In the "Remote Syslog Server" section, click the + Add Syslog Server button.
* Fill in the server details as required:
* Name: Corp_Syslog
* IP Address: 34.142.155.231
* Port: 514
* Protocol: TCP (This provides the highest reliability, as requested).
* Click Save.
3. Configure Log Modules and Severities
Now, we must specify which logs to send to the new server.
* On the same Syslog settings page, find the "Syslog Configuration" section and click the Configure button (or Modify if a default is present).
* A dialog box "Select Modules and Levels" will appear.
* Uncheck all modules to ensure no extra logs are sent.
* Check the box for the RSyslog Server Module (or rsyslog_forwarder).
* For this module, check the boxes for the severities: Critical, Warning, and Info.
* Check the box for the ApiServer module.
* This module logs all operational tasks and audit trails, which includes all Virtual Machine changes.
* For this module, check the boxes for the top severity levels: Critical, Warning, and Info.
* Ensure no other modules (like Stargate, Cerebro, Zookeeper, etc.) are checked.
* Click Save.
Cluster 1 is now configured to send its audit logs (including VM changes) and its own syslog monitoring logs to the Corp_Syslog server via TCP, fulfilling all security requirements.
Topic 2, Performance Based Questions Set 2
Environment
You have been provisioned a dedicated environment for your assessment which includes the following:
Workstation
* windows Server 2019
* All software/tools/etc to perform the required tasks
* Nutanix Documentation and whitepapers can be found in desktop\files\Documentation
* Note that the workstation is the system you are currently togged into Nutanix Cluster
* There are three clusters provided. The connection information for the relevant cluster will be displayed to the high of the question Please make sure you are working on the correct cluster for each item Please ignore any licensing violations
* Cluster A is a 3-node cluster with Prism Central 2022.6 where most questions will be performed
* Cluster B is a one-node cluster and has one syslog item and one security item to perform
* Cluster D is a one-node duster with Prism Central 5.17 and has a security policy item to perform Important Notes
* If the text is too small and hard to read, or you cannot see an of the GUI. you can increase/decrease the zoom of the browser with CTRL + ,and CTRL + (the plus and minus keys) You will be given 3 hours to complete the scenarios for Nutanix NCMMCI Once you click the start button below, you will be provided with:
- A Windows desktop A browser page with the scenarios and credentials (Desktop\instructions) Notes for this exam delivery:
The browser can be scaled lo Improve visibility and fit all the content on the screen.
- Copy and paste hot-keys will not work Use your mouse for copy and paste.
- The Notes and Feedback tabs for each scenario are to leave notes for yourself or feedback for
- Make sure you are performing tasks on the correct components.
- Changing security or network settings on the wrong component may result in a falling grade.
- Do not change credentials on an component unless you are instructed to.
- All necessary documentation is contained in the Desktop\Files\Documentation directory