Free Practice Questions for Nutanix NCP-MCI-6.5 Exam

According to the CPU (%) - VMware Docs web search result2, one of the possible causes of high CPU ready % is over-provisioning vCPUs for a VM or having too many VMs on a host. CPU ready % indicates the percentage of time that the VM was ready, but could not get scheduled to run on the physical CPU. High CPU ready % can lead to VM performance problems, such as slow response time or application latency. To improve VM performance, the administrator should reduce the number of vCPUs assigned to VMs or reduce the number of VMs on the hosts, so that there is less contention for CPU resources.

This is because there is no GUI method to unregister a cluster from Prism Central, so the process requires SSH access to the PC VM as well as to a CVM of the cluster2. The unregistration process involves getting the UUID of the cluster from the CVM and then using that to trigger de-registration from PC command line2. The unregistration process also involves cleaning up any associated metadata and configuration on both PC and PE2. Therefore, the administrator needs to use a Host SSH session to perform this task.

Active-Active is a bond mode that allows all uplinks in the bond to be used simultaneously for traffic transmission and reception. This bond mode provides load balancing and increased bandwidth for the AHV host and its VMs. Active-Active bond mode uses a hashing algorithm based on source MAC addresses to distribute traffic across different uplinks in the bond. Each individual VM NIC uses only a single bond member interface at a time, but multiple VM NICs are spread across different bond member interfaces. As a result, it is possible for a Nutanix AHV node with two 10 Gb interfaces to use up to 20 Gbps of network throughput, while individual VMs have a maximum throughput of 10 Gbps6.

Therefore, if an administrator needs to optimize for maximum single VM throughput, they should select Active-Active bond mode for their AHV cluster. This bond mode can be configured using Prism Element UI or manage-ovs commands on each AHV host7. No additional configuration is required on the upstream switch side, as long as the switches are interconnected physically or virtually and both uplinks trunk the same VLANs8.