Pass Nutanix NCM-MCI-6.10 With GuideTorrent Exam Dumps - Updated on Apr-2026
Fully Updated NCM-MCI-6.10 Dumps - 100% Same Q&A In Your Real Exam
NEW QUESTION # 18
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.
Answer:
Explanation:
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
NEW QUESTION # 19
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.
Answer:
Explanation:
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.
NEW QUESTION # 20
Task 14
An administrator has been asked to configure a storage for a distributed application which uses large data sets across multiple worker VMs.
The worker VMs must run on every node. Data resilience is provided at the application level and low cost per GB is a Key Requirement.
Configure the storage on the cluster to meet these requirements. Any new object created should include the phrase Distributed_App in the name.
Answer:
Explanation:
See the Explanation for step by step solution.
Explanation:
To configure the storage on the cluster for the distributed application, you can follow these steps:
Log in to Prism Element of cluster A using the credentials provided.
Go to Storage > Storage Pools and click on Create Storage Pool.
Enter a name for the new storage pool, such as Distributed_App_Storage_Pool, and select the disks to include in the pool. You can choose any combination of SSDs and HDDs, but for low cost per GB, you may prefer to use more HDDs than SSDs.
Click Save to create the storage pool.
Go to Storage > Containers and click on Create Container.
Enter a name for the new container, such as Distributed_App_Container, and select the storage pool that you just created, Distributed_App_Storage_Pool, as the source.
Under Advanced Settings, enable Erasure Coding and Compression to reduce the storage footprint of the data.
You can also disable Replication Factor since data resilience is provided at the application level. These settings will help you achieve low cost per GB for the container.
Click Save to create the container.
Go to Storage > Datastores and click on Create Datastore.
Enter a name for the new datastore, such as Distributed_App_Datastore, and select NFS as the datastore type.
Select the container that you just created, Distributed_App_Container, as the source.
Click Save to create the datastore.
The datastore will be automatically mounted on all nodes in the cluster. You can verify this by going to Storage > Datastores and clicking on Distributed_App_Datastore. You should see all nodes listed under Hosts.
You can now create or migrate your worker VMs to this datastore and run them on any node in the cluster.
The datastore will provide low cost per GB and high performance for your distributed application.
NEW QUESTION # 21
Task 9
The application team has requested several mission-critical VMs to be configured for disaster recovery. The remote site (when added) will not be managed by Prism Central. As such, this solution should be built using the Web Console.
Disaster Recovery requirements per VM:
Mkt01
RPO: 2 hours
Retention: 5 snapshots
Fin01
RPO: 15 minutes
Retention: 7 days
Dev01
RPO: 1 day
Retention: 2 snapshots
Configure a DR solution that meets the stated requirements.
Any objects created in this item must start with the name of the VM being protected.
Note: the remote site will be added later
Answer:
Explanation:
See the Explanation for step by step solution.
Explanation:
To configure a DR solution that meets the stated requirements, you can follow these steps:
Log in to the Web Console of the source cluster where the VMs are running.
Click on Protection Domains on the left menu and click on Create Protection Domain.
Enter a name for the protection domain, such as PD_Mkt01, and a description if required. Click Next.
Select Mkt01 from the list of VMs and click Next.
Select Schedule Based from the drop-down menu and enter 2 hours as the interval. Click Next.
Select Remote Site from the drop-down menu and choose the remote site where you want to replicate the VM.
Click Next.
Enter 5 as the number of snapshots to retain on both local and remote sites. Click Next.
Review the protection domain details and click Finish.
Repeat the same steps for Fin01 and Dev01, using PD_Fin01 and PD_Dev01 as the protection domain names, and adjusting the interval and retention values according to the requirements.
NEW QUESTION # 22
Task 1
An administrator needs to configure storage for a Citrix-based Virtual Desktop infrastructure.
Two VDI pools will be created
Non-persistent pool names MCS_Pool for tasks users using MCS Microsoft Windows 10 virtual Delivery Agents (VDAs) Persistent pool named Persist_Pool with full-clone Microsoft Windows 10 VDAs for power users
20 GiB capacity must be guaranteed at the storage container level for all power user VDAs The power user container should not be able to use more than 100 GiB Storage capacity should be optimized for each desktop pool.
Configure the storage to meet these requirements. Any new object created should include the name of the pool (s) (MCS and/or Persist) that will use the object.
Do not include the pool name if the object will not be used by that pool.
Any additional licenses required by the solution will be added later.
Answer:
Explanation:
See the Explanation for step by step solution.
Explanation:
To configure the storage for the Citrix-based VDI, you can follow these steps:
Log in to Prism Central using the credentials provided.
Go to Storage > Storage Pools and click on Create Storage Pool.
Enter a name for the new storage pool, such as VDI_Storage_Pool, and select the disks to include in the pool.
You can choose any combination of SSDs and HDDs, but for optimal performance, you may prefer to use more SSDs than HDDs.
Click Save to create the storage pool.
Go to Storage > Containers and click on Create Container.
Enter a name for the new container for the non-persistent pool, such as MCS_Pool_Container, and select the storage pool that you just created, VDI_Storage_Pool, as the source.
Under Advanced Settings, enable Deduplication and Compression to reduce the storage footprint of the non- persistent desktops. You can also enable Erasure Coding if you have enough nodes in your cluster and want to save more space. These settings will help you optimize the storage capacity for the non-persistent pool.
Click Save to create the container.
Go to Storage > Containers and click on Create Container again.
Enter a name for the new container for the persistent pool, such as Persist_Pool_Container, and select the same storage pool, VDI_Storage_Pool, as the source.
Under Advanced Settings, enable Capacity Reservation and enter 20 GiB as the reserved capacity. This will guarantee that 20 GiB of space is always available for the persistent desktops. You can also enter 100 GiB as the advertised capacity to limit the maximum space that this container can use. These settings will help you control the storage allocation for the persistent pool.
Click Save to create the container.
Go to Storage > Datastores and click on Create Datastore.
Enter a name for the new datastore for the non-persistent pool, such as MCS_Pool_Datastore, and select NFS as the datastore type. Select the container that you just created, MCS_Pool_Container, as the source.
Click Save to create the datastore.
Go to Storage > Datastores and click on Create Datastore again.
Enter a name for the new datastore for the persistent pool, such as Persist_Pool_Datastore, and select NFS as the datastore type. Select the container that you just created, Persist_Pool_Container, as the source.
Click Save to create the datastore.
The datastores will be automatically mounted on all nodes in the cluster. You can verify this by going to Storage > Datastores and clicking on each datastore. You should see all nodes listed under Hosts.
You can now use Citrix Studio to create your VDI pools using MCS or full clones on these datastores. For more information on how to use Citrix Studio with Nutanix Acropolis, see Citrix Virtual Apps and Desktops on Nutanix or Nutanix virtualization environments.
https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2079-Citrix-Virtual-Apps-and- Desktops:bp-nutanix-storage-configuration.html
NEW QUESTION # 23
An administrator wants to increase the performance of their Database virtual machine.
Database_VM has a database that is spread across three vDisks in the volume group Database_VM. The volume group is directly attached to the virtual machine. Previous performance analysis has indicated all storage requests are going to the same node. While this test environment has 1 node, the production environment has 3 nodes.
Configure the Volume Group Database_VM so that it's optimized for the user's VM and the production environment. The virtual machine has been powered off and moved to this test cluster for the maintenance work.
Note: Do not power on the VM.
Answer:
Explanation:
See the Explanation below for detailed answer.
Explanation:
Here is the step-by-step solution to configure the Volume Group for optimized performance in the production environment.
This task is performed in Prism Central.
* From the main dashboard, navigate to Compute & Storage > Volume Groups.
* Find the Volume Group named Database_VM in the list.
* Select the checkbox next to Database_VM.
* Click the Actions dropdown menu and select Update.
* In the "Update Volume Group" dialog, scroll to the bottom of the "Basic Configuration" section.
* Find the checkbox labeled Enable Client Side Load Balancing and check it.
Note: This setting allows the iSCSI initiator within the guest VM to connect to all CVMs in the cluster, distributing the storage load from the three vDisks across all three nodes in the production environment instead of focusing all I/O on just one.
Click Save.
NEW QUESTION # 24
TASK 1
A newly created Windows VM "SQL02" is experiencing poor storage performance when compared to
"SQL01" running within the same cluster, on the same storage container.
The cluster is in a healthy state.
Create a new session named Monitor SQL02 with meaningful metrics. Right click on the session page and click Select All then paste this into Notepad and save it as Task 1.txt on the desktop.
Also, save the analysis as a report named MonitorSQL02 and send the report as a PDF on a daily basis to [email protected]. Reports should not be retained. If any new objects need to be created, use monitovm2 in the name.
Finally, correct the issue within "SQL02".
Notes:
* Do not power on the VMs.
* While you will be creating a session, you will need to examine the VM configurations to determine the issue.
* Do not delete the VM to resolve the issue, any other destructive change is acceptable.
Answer:
Explanation:
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.
NEW QUESTION # 25
An administrator regularly sees a WARN for backup_schedule_check and also receives alerts for Pulse not being enabled on Cluster 1.
Detailed information for backup_schedule_check:
Node xx.xx.xx.xx:
WARN: Backup schedule(s) exist for protection domain NoVMs; however, there are no entities in the protection domain.
Refer
to KB 1910 (http://portal.nutanix.com/kb/1910) for details on backup_schedule_check or Recheck with: ncc health_checks data_protection_checks protection_domain_checks backup_schedule_check.
This shows up in NCC, however, it is something set up by the company and they do not want the NCC check to be run.
Configure Cluster 1 to no longer have messages in NCC about the backup_schedule_check.
Turn off the alert for Pulse not being enabled, and resolve the alert. They would like messages about Pulse to be recorded, but do not want an alert.
Note: You may need to run the "Pulse is not enabled" check in order to have one to resolve.
Answer:
Explanation:
See the Explanation below for detailed answer.
Explanation:
Here is the step-by-step solution to configure Cluster 1 from its Prism Element interface.
1. Disable the backup_schedule_check NCC Check
This will prevent the WARN message for the NoVMs protection domain.
* Log in to the Cluster 1 Prism Element (PE) interface.
* Navigate to the Health dashboard (click the "heart" icon in the top-left).
* In the left-hand menu, select NCC.
* In the search bar for the checks, type backup_schedule_check to find the specific check.
* Select the checkbox next to the backup_schedule_check in the list.
* Click the Disable button that appears above the table. This will stop this check from running during NCC health reports.
2. Configure and Resolve Pulse Alerts
This process involves two parts: disabling the alerting policy, and then enabling Pulse itself to resolve the underlying condition.
A. Disable the Alert Policy
This stops the system from generating a new alert if Pulse is ever disabled, satisfying the "do not want an alert" requirement.
* Click the gear icon (Settings) in the top-right corner.
* From the left-hand menu, select Alert Policies.
* In the search bar, type Pulse to find the policy.
* Select the checkbox for the alert policy named Pulse is not enabled (or pulse_disabled_alert).
* Click the Update button.
* Uncheck the Enable box for the policy.
* Click Save.
B. Enable Pulse (to Resolve the Condition)
This enables the Pulse service to record messages (as requested) and fixes the root cause of the alert, allowing it to be resolved.
* Click the gear icon (Settings) in the top-right corner.
* From the left-hand menu, select Pulse.
* Click the Enable Pulse button (or "Update" if it's already partially configured).
* Check the box for Enable Pulse.
* (Note: Any "Enable alerts for Pulse" boxes would remain unchecked or be ignored, as the main Alert Policy itself is now disabled.)
* Click Save.
C. Resolve the Active Alert
* Navigate to the Alerts dashboard (click the "bell" icon in the top-left).
* Find the active alert: Pulse is not enabled.
* (Note: If the alert is not present, you would first go to the Health dashboard, run the check_pulse NCC check to generate it, and then return to the Alerts dashboard.)
* Select the checkbox next to the "Pulse is not enabled" alert.
* Click the Resolve button that appears at the top of the list. Since the underlying condition (Pulse being disabled) is now fixed, the alert will be successfully resolved.
NEW QUESTION # 26
Create a VM template on Cluster 1 named Small Template that matches the small VM Configuration in NVD-2031 (see the Files\Documentation 6.10 folder) however, you will use default storage container.
Configure SMTP Alerting and NCC reports per NVD-2031 for Cluster 1.
Settings:
* SMTP: Use Cluster 2 IP address
* Cluster email: [email protected]
* Alert emails: [email protected], [email protected]
Answer:
Explanation:
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.
NEW QUESTION # 27
Task 16
An administrator is working to create a VM using Nutanix V3 API calls with the following specifications.
* VM specifications:
* vCPUs: 2
* Memory: BGb
* Disk Size: 50Gb
* Cluster: Cluster A
* Network: default- net
The API call is falling, indicating an issue with the payload:
The body is saved in Desktop/ Files/API_Create_VM,text
Correct any issues in the text file that would prevent from creating the VM. Also ensure the VM will be created as speeded 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.
Answer:
Explanation:
See the Explanation for step by step solution.
Explanation:
https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000LLEzCAO
https://jsonformatter.curiousconcept.com/#
acli net.list (uuid network defult_net)
ncli cluster info (uuid cluster)
Put Call: https://Prism Central IP address : 9440/api/nutanix/v3vms
Edit these lines to fix the API call, do not add new lines or copy lines.
You can test using the Prism Element API explorer or PostMan
Body:
{
{
"spec": {
"name": "Test_Deploy",
"resources": {
"power_state":"OFF",
"num_vcpus_per_socket": ,
"num_sockets": 1,
"memory_size_mib": 8192,
"disk_list": [
{
"disk_size_mib": 51200,
"device_properties": {
"device_type":"DISK"
}
},
{
"device_properties": {
"device_type":"CDROM"
}
}
],
"nic_list":[
{
"nic_type": "NORMAL_NIC",
"is_connected": true,
"ip_endpoint_list": [
{
"ip_type": "DHCP"
}
],
"subnet_reference": {
"kind": "subnet",
"name": "default_net",
"uuid": "00000000-0000-0000-0000-000000000000"
}
}
],
},
"cluster_reference": {
"kind": "cluster",
"name": "NTNXDemo",
"uuid": "00000000-0000-0000-0000-000000000000"
}
},
"api_version": "3.1.0",
"metadata": {
"kind": "vm"
}
}
https://www.nutanix.dev/2019/08/26/post-a-package-building-your-first-nutanix-rest-api-post-request/ Reference
NEW QUESTION # 28
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.
Answer:
Explanation:
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
NEW QUESTION # 29
Task 11
Running NCC on a cluster prior to an upgrade results in the following output FAIL: CVM System Partition /home usage at 93% (greater than threshold, 90%) Identify the CVM with the issue, remove the fil causing the storage bloat, and check the health again by running the individual disk usage health check only on the problematic CVM do not run NCC health check Note: Make sure only the individual health check is executed from the affected node
Answer:
Explanation:
See the Explanation for step by step solution.
Explanation:
To identify the CVM with the issue, remove the file causing the storage bloat, and check the health again, 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 find the NCC health check output file from the list.
You can use the date and time information to locate the file. The file name should be something like ncc- output-YYYY-MM-DD-HH-MM-SS.log.
Open the file and look for the line that says FAIL: CVM System Partition /home usage at 93% (greater than threshold, 90%). Note down the IP address of the CVM that has this issue. It should be something like X.X.X.
X.
Log in to the CVM using SSH or console with the username and password provided.
Run the command du -sh /home/* to see the disk usage of each file and directory under /home. Identify the file that is taking up most of the space. It could be a log file, a backup file, or a temporary file. Make sure it is not a system file or a configuration file that is needed by the CVM.
Run the command rm -f /home/<filename> to remove the file causing the storage bloat. Replace <filename> with the actual name of the file.
Run the command ncc health_checks hardware_checks disk_checks disk_usage_check --cvm_list=X.X.X.
X to check the health again by running the individual disk usage health check only on the problematic CVM.
Replace X.X.X.X with the IP address of the CVM that you noted down earlier.
Verify that the output shows PASS: CVM System Partition /home usage at XX% (less than threshold, 90%).
This means that the issue has been resolved.
#access to CVM IP by Putty
allssh df -h #look for the path /dev/sdb3 and select the IP of the CVM
ssh CVM_IP
ls
cd software_downloads
ls
cd nos
ls -l -h
rm files_name
df -h
ncc health_checks hardware_checks disk_checks disk_usage_check
NEW QUESTION # 30
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.
Answer:
Explanation:
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.
NEW QUESTION # 31
......
Latest NCM-MCI-6.10 Exam Dumps - Valid and Updated Dumps: https://torrentpdf.guidetorrent.com/NCM-MCI-6.10-dumps-questions.html