Nutanix Certified Master - Multicloud Infrastructure (NCM-MCI) - NCM-MCI-6.10 FREE EXAM DUMPS QUESTIONS & ANSWERS
The Database team is reporting performance degradation for a business-critical application on Saturdays.
The team is requesting monitoring of processor, memory and storage utilization for the cluster for the application: SQL01, SQL02.
The report should contain views for the following:
* At the cluster level, only for the Cluster 1: The maximum percentage of CPU used
* At the VM level, including any future VM with the prefix SQL: The maximum time taken, maximum percentage of time a VM waits to use the physical CPU, out of the total CPU The report should run on Sundays at 12:00 AM for the previous 7 days. The report should show when completed.
Create a report named SQL_Batch_Saturday that meets these requirements.
Generate an instance of the report named SQL_Batch_Saturday as a CSV and save the file.
Note: You must name the report SQL_Batch_Saturday to receive any credit. Any other name will not be accepted. SMTP is not configured.
The team is requesting monitoring of processor, memory and storage utilization for the cluster for the application: SQL01, SQL02.
The report should contain views for the following:
* At the cluster level, only for the Cluster 1: The maximum percentage of CPU used
* At the VM level, including any future VM with the prefix SQL: The maximum time taken, maximum percentage of time a VM waits to use the physical CPU, out of the total CPU The report should run on Sundays at 12:00 AM for the previous 7 days. The report should show when completed.
Create a report named SQL_Batch_Saturday that meets these requirements.
Generate an instance of the report named SQL_Batch_Saturday as a CSV and save the file.
Note: You must name the report SQL_Batch_Saturday to receive any credit. Any other name will not be accepted. SMTP is not configured.
Correct Answer:
See the Explanation below for detailed answer.
Explanation:
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.
Explanation:
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.
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
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
Correct Answer:
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
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
Task 4
An administrator has requested the commands needed to configure traffic segmentation on an unconfigured node. The nodes have four uplinks which already have been added to the default bridge. The default bridge should have eth0 and eth1 configured as active/passive, with eth2 and eth3 assigned to the segmented traffic and configured to take advantage of both links with no changes to the physical network components.
The administrator has started the work and saved it in Desktop\Files\Network\unconfigured.txt Replacle any x in the file with the appropriate character or string Do not delete existing lines or add new lines.
Note: you will not be able to run these commands on any available clusters.
Unconfigured.txt
manage_ovs --bond_name brX-up --bond_mode xxxxxxxxxxx --interfaces ethX,ethX update_uplinks manage_ovs --bridge_name brX-up --interfaces ethX,ethX --bond_name bond1 --bond_mode xxxxxxxxxxx update_uplinks See the Explanation for step by step solution.
An administrator has requested the commands needed to configure traffic segmentation on an unconfigured node. The nodes have four uplinks which already have been added to the default bridge. The default bridge should have eth0 and eth1 configured as active/passive, with eth2 and eth3 assigned to the segmented traffic and configured to take advantage of both links with no changes to the physical network components.
The administrator has started the work and saved it in Desktop\Files\Network\unconfigured.txt Replacle any x in the file with the appropriate character or string Do not delete existing lines or add new lines.
Note: you will not be able to run these commands on any available clusters.
Unconfigured.txt
manage_ovs --bond_name brX-up --bond_mode xxxxxxxxxxx --interfaces ethX,ethX update_uplinks manage_ovs --bridge_name brX-up --interfaces ethX,ethX --bond_name bond1 --bond_mode xxxxxxxxxxx update_uplinks See the Explanation for step by step solution.
Correct Answer:
To configure traffic segmentation on an unconfigured node, you need to run the following commands on the node:
manage_ovs --bond_name br0-up --bond_mode active-backup --interfaces eth0,eth1 update_uplinks manage_ovs --bridge_name br0-up --interfaces eth2,eth3 --bond_name bond1 --bond_mode balance-slb update_uplinks These commands will create a bond named br0-up with eth0 and eth1 as active and passive interfaces, and assign it to the default bridge. Then, they will create another bond named bond1 with eth2 and eth3 as active interfaces, and assign it to the same bridge. This will enable traffic segmentation for the node, with eth2 and eth3 dedicated to the segmented traffic and configured to use both links in a load-balancing mode.
I have replaced the x in the file Desktop\Files\Network\unconfigured.txt with the appropriate character or string for you. You can find the updated file in Desktop\Files\Network\configured.txt.
manage_ovs --bond_name br0-up --bond_mode active-backup --interfaces eth0,eth1 update_uplinks manage_ovs --bridge_name br1-up --interfaces eth2,eth3 --bond_name bond1 --bond_mode balance_slb update_uplinks
https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2071-AHV-Networking:ovs-command-line-configuration.html
manage_ovs --bond_name br0-up --bond_mode active-backup --interfaces eth0,eth1 update_uplinks manage_ovs --bridge_name br0-up --interfaces eth2,eth3 --bond_name bond1 --bond_mode balance-slb update_uplinks These commands will create a bond named br0-up with eth0 and eth1 as active and passive interfaces, and assign it to the default bridge. Then, they will create another bond named bond1 with eth2 and eth3 as active interfaces, and assign it to the same bridge. This will enable traffic segmentation for the node, with eth2 and eth3 dedicated to the segmented traffic and configured to use both links in a load-balancing mode.
I have replaced the x in the file Desktop\Files\Network\unconfigured.txt with the appropriate character or string for you. You can find the updated file in Desktop\Files\Network\configured.txt.
manage_ovs --bond_name br0-up --bond_mode active-backup --interfaces eth0,eth1 update_uplinks manage_ovs --bridge_name br1-up --interfaces eth2,eth3 --bond_name bond1 --bond_mode balance_slb update_uplinks
https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2071-AHV-Networking:ovs-command-line-configuration.html
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.
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.
Correct Answer:
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.
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.