Get Nutanix NCP-MCA Exam Practice Questions - Real and Updated

Answer : D

The administrator needs to add AWS as a provider in Calm. A provider is a cloud platform or infrastructure that hosts the application VMs or services. Calm supports various providers such as Nutanix, AWS, Azure, GCP, VMware, and Kubernetes. To add a provider, the administrator needs to go to the Providers page in the Calm UI and click on the +Create Provider button. Then, the administrator needs to select the AWS provider type and enter the required information such as name, access key, secret key, and regions.Reference:Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 11; Nutanix Calm User Guide, section 3.1.

Answer : B, D

Calm can be deployed as a VM on ESXi or AHV hypervisors and leverage calm functionality without the Nutanix infrastructure. Calm can also be enabled inside of Prism Central, which is a VM that can run on any Nutanix supported hypervisor, including ESXi and AHV. However, Calm cannot be enabled inside of Prism Element, which is the management interface for each Nutanix cluster. Calm also cannot be deployed as a VM on Hyper-V, as this is not a supported hypervisor for Calm.Reference:Nutanix Calm Configuration and Training,Calm on ESXi Deployment | Nutanix Community,Nutanix Support & Insights

Answer : A, C

From the exhibit, it is clear that Prism Central needs to communicate with Calm managed target Linux VMs via SSH and with Calm managed target Windows VMs via PowerShell or Shell scripts. The appropriate ports to open for these communications are:

TCP 22: This port is used for SSH, which is necessary for managing Linux VMs.

TCP 5985 and 5986: These ports are used for PowerShell remoting, which is essential for managing Windows VMs.

Nutanix Calm documentation on Network Ports.

Best practices for Nutanix Network Configuration.

Answer : C

The Playbook is designed to manually reduce the vCPU count on any selected VM within the environment. However, it failed during a test run on VM2 because there was a running snapshot of the VM.According to Nutanix Multicloud Automation (NCP-MCA) principles, you cannot reduce the vCPU count on a VM that has an active snapshot1.This is because the snapshot captures the state of the VM configuration and data, and reverting to a snapshot will restore both the guest OS and the virtual hardware2. Therefore, changing the vCPU count while a snapshot is running will cause inconsistency and error. The other options are incorrect because:

A .The Playbook can be executed against a VM on AHV, as long as there is no snapshot running3.

B .The VM does not need to be powered off before vCPU can be reduced, as this can be done using hot-plug CPU feature4.

D . The play will not cause the VM to go below the minimum vCPU, as the minimum number of vCPUs is set to 1 in the Playbook, and the VM has 4 vCPUs initially.Reference:Nutanix Support & Insights,Solved: Snapshot query !! - VMware Technology Network VMTN,Calm on ESXi Deployment | Nutanix Community,Virtual CPU Configuration and Limitations - VMware Docs

Answer : A

A Category in Nutanix is a grouping of entities (such as VMs, hosts, clusters, etc.) into a key-value pair. Categories are used to organize and manage resources more effectively by tagging them with meaningful identifiers.

Nutanix documentation on Categories.

Nutanix Best Practices for Using Categories.