NCP-MCI-6.5 Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) v6.5 exam Free Practice Exam Questions (2025 Updated)

Step 1 ---> Login into Prism Element.

Step 2 ---> Select the Gear Icon at top right of the page.

Step 3 ---> Click Upgrade Software.

Step 4 ---> Select the component to upgrade.

Step 5 ---> Click download.

Step 6 ---> Once the download completes, select upgrade.

Invalid:-

1 - Select Prism Central.

2 - Select user login.

3 - On left select upgrade Prism Central.

According to the web search results, the policy that should be used to meet this requirement is an Isolation Environment Policy. An Isolation Environment Policy is a type of security policy that can be created in Prism Central using Flow Network Security, which is a feature that provides microsegmentation and network security for Nutanix environments1. An Isolation Environment Policy allows the administrator to isolate a group of VMs from another group of VMs based on their categories, and block all traffic between them regardless of direction2. This policy can be useful for creating isolated environments for testing, development, or compliance purposes2.

NGT is a software package that enables advanced VM management features provided by Nutanix, such as file-level restore, VM mobility, and application-consistent snapshots12. To use NGT, you need to enable the NGT feature for a VM in the Prism Element web console, mount the NGT installer (ISO disk file) in the VM, and install NGT in the VM1. However, before installing NGT, you need to ensure that the VM can communicate with the NGT-Controller VM service, which runs on the Controller VM (CVM) of each Nutanix node3. The NGT-Controller VM service listens on port 9943 for incoming requests from the guest VMs3. Therefore, you need to enable port 9943 on the ESXi-hosted VM to allow communication with the NGT-Controller VM service.

Enable Memory Overcommit on the over-provisioned VMs is the most efficient resolution to enable additional VMs to be created. Memory overcommit allows VMs to use more memory than physically available on a host by compressing and swapping memory pages to storage1. This can improve memory utilization and increase VM density on a cluster1. However, memory overcommit is not supported when HA is configured to use reserved hosts, so you may need to disable HA reservation on the cluster before enabling memory overcommit1.

According to the Troubleshoot high memory issues on Azure virtual machines web search result2, one of the common factors in a low memory situation is over-provisioning memory for a VM. Over-provisioning memory can cause memory pressure, which leads to swapping and degraded performance. Therefore, to fix this issue, the administrator should reduce the amount of memory assigned to the VM, based on the average hardware requirements for that operating system and application load.

According to the web search results, one recommended configuration change to improve throughput for a custom backup application that requires a 2TB disk and runs on Windows is to span the 2TB disk across four vDisks. Spanning is a technique that allows you to create a single logical disk from multiple physical disks. Spanning can improve throughput by distributing I/O requests across multiple disks and reducing contention5. To span a disk across four vDisks, the administrator should create four vDisks of equal size (500 GB each) and attach them to the VM. Then, in Windows Disk Management, create a spanned volume from the four vDisks and format it as NTFS6.

In this case, the administrator wants to investigate the performance of a core banking system that consists of application servers and database servers. The application servers have high CPU utilization during business hours, which may indicate a bottleneck or a resource contention issue. The administrator needs to review multiple metrics in Prism Analysis Graphs to identify the root cause and determine if there is a problem with the app servers only, or with other components as well.

The metrics that are relevant for this analysis are:

Cluster IO: This metric shows the input/output operations per second (IOPS) and throughput (MBps) of the cluster. It can help to understand if there is a high demand for disk IO from the VMs or if there is any latency or congestion in the storage layer.

Cluster CPU: This metric shows the CPU utilization (%) and load average of the cluster. It can help to understand if there is enough CPU capacity in the cluster to handle the workload or if there is any imbalance or contention among hosts.

Cluster Memory: This metric shows the memory utilization (%) and available memory (GB) of the cluster. It can help to understand if there is enough memory capacity in the cluster to support the VMs or if there is any pressure or swapping in the memory layer.

Network: This metric shows the network throughput (MBps) and packets per second (pps) of the cluster. It can help to understand if there is enough network bandwidth in the cluster to transfer data between hosts and VMs or if there is any congestion or packet loss in the network layer.

App Server CPU: This metric shows the CPU utilization (%) and load average of each application server VM. It can help to understand if there is any variation or anomaly in the performance of each app server or if there is any correlation with other metrics.

Database Server CPU: This metric shows the CPU utilization (%) and load average of each database server VM. It can help to understand if there is any variation or anomaly in the performance of each database server or if there is any correlation with other metrics.

According to the web search results, a consistency group is a group of related applications or services that must be recovered together in order to work properly, and this means more than being recovered at the same time67. They also typically need to be recovered to the same point in time6. Therefore, to meet the requirement of protecting all VMs of a multi-tier application at the same time, the administrator must create a consistency group for the application and place all VMs in it8. This way, the administrator can apply data protection policies and schedules to the entire consistency group as a single unit8.

An agent VM is a special type of VM that is used for running services or applications that are not affected by high availability (HA) events or host maintenance. An agent VM is never migrated to any other host in the cluster. If an HA event occurs or the host is put in maintenance mode, agent VMs are powered off and are powered on on the same host once that host returns to a normal state. This behavior is different from regular VMs, which are migrated to another host in the cluster if possible, or restarted on the same host if not possible1.

Therefore, during an AHV upgrade, an administrator may find that a critical VM was powered off rather than migrated to another host if the VM was marked as an agent VM. This can be done either from the Prism web console by selecting the Use this VM as an agent VM option in the Update VM dialog box, or from the aCLI by using the vm.create or vm.update commands with the agent_vm=true parameter2. To avoid this situation, the administrator should ensure that any critical VMs are not marked as agent VMs before starting the AHV upgrade.

The storage policy value that can be inherited from a cluster is Compression. In the Nutanix Multicloud Infrastructure (NCP-MCI) 6.5, compression is a storage optimization feature that can be configured at the cluster level and inherited by all the entities within the cluster. This feature helps in reducing the storage footprint by compressing the data before writing it to the disk. The other options like IO performance, Storage Container, and QoS are not inherited from the cluster. They are configured and managed separately for each entity as per the requirements.

A GPU (graphics processing unit) is a specialized hardware device that can accelerate graphics rendering and computation for applications that use APIs such as DirectX, OpenGL, CUDA, and OpenCL. A GPU can also offload the CPU from encoding and decoding tasks for remote display protocols such as Frame Remote Desktop Protocol (FRP). A VM can use a GPU either by directly accessing a physical GPU (pGPU) on the host or by using a virtual GPU (vGPU) that shares a pGPU with other VMs. A user running a computer aided design (CAD) application may benefit from using a GPU or a vGPU to improve the performance and responsiveness of the application, especially when moving windows or rendering images. However, if the GPU or vGPU is not properly configured or provisioned, the user may experience slow response time within the VM. Therefore, to diagnose the problem, the administrator should monitor the GPU Usage metric for the VM. The GPU Usage metric shows the percentage of GPU resources that are consumed by the VM over time3. The administrator can use Prism Central to view the GPU Usage metric for each VM in a chart or a widget4. The administrator can also use Prism Central to view other metrics related to GPU performance, such as GPU Memory Usage, GPU Encoder Usage, and GPU Decoder Usage3. By analyzing these metrics, the administrator can determine if the VM is using the GPU efficiently and optimally, or if it needs more or less GPU resources.

Terminology

Availability Zone – it is represented by all resources (Nutanix Clusters) connected to Prism Central or Xi Leap Availability zone. Depends on the architecture, Availability zone can represent geographic territory, datacenter or server room in the datacenter. Protection policies – in protection policies you set up (RPO, Retention), rules to auto-apply policies to virtual machines

https://vmware mine.com/2019/02/08/nutanix-leap-runbooks-part-1/#sthash.VwrzSzhQ.dpbs

According to the Nutanix Community1, host maintenance mode is used to safely migrate all the user virtual machines (VMs) in the host and make sure no VMs are running on the node. If a VM can’t be migrated to another host, you need to shut down the VM for the host to enter into maintenance mode.

According to The Virtualist2, a storage container is a logical segmentation of a storage pool that can be mounted as an NFS datastore on ESXi hosts. You can choose a replication factor (RF) for each storage container, which determines how many copies of data are stored across different nodes.

According to the Nutanix Support & Insights web search result2, VM NICs on AHV can operate in two modes: Access and Trunked. Access NICs are the default, and allow one VLAN on the NIC. Trunked NICs allow multiple VLANs on a single NIC for VMs that are VLAN aware. If you must use trunked NICs, follow the steps described in the web search result2. Therefore, the most efficient way to have a VM on an AHV cluster with access to multiple VLANs is to update a vNIC on the VM to operate in trunked mode for all desired VLANs.

switch ports are configured with different VLANs could be the cause of this error. If the switch ports are not configured with the same VLANs as the network interfaces on each node, then there could be a mismatch in network connectivity when one interface is disconnected1. This could affect the guest VMs that are using a different VLAN than the hypervisor.

 According to the Nutanix Support & Insights web search result1, the name of the internal bridge used by AHV nodes and CVMs is br0. The internal bridge is an Open vSwitch (OVS) bridge that connects the AHV host management interface, the CVM interface, and the VM vNICs. The internal bridge also acts as a gateway for the CVM and VM traffic to reach the external network through the host physical NICs.

An Application Security Policy is a security feature in Nutanix AHV that can be used to restrict network communication between virtual servers based on a variety of criteria, such as IP address, port, and protocol. By creating a policy that restricts communication to authorized hosts and applying it to the servers in enforce mode, the administrator can prevent unauthorized communication between virtual servers.

https://www.nutanix.com/products/ahv