NCM-MCI: Nutanix Certified Master - Multicloud Infrastructure

A node added during cluster expansion must run an AOS version compatible with and matched to the existing cluster. An older AOS version on the G7 node is incompatible with the cluster running AOS 5.10 and prevents the expansion. Mixed G5 and G7 hardware is supported when the applicable hardware and software compatibility requirements are met; EVC applies to VMware vSphere rather than AHV.

A four-vCPU VM at roughly 25% total CPU utilization has the equivalent of only one vCPU fully utilized. That pattern is consistent with a workload that is not using multiple execution threads, rather than a VM-wide CPU-resource constraint. The reported storage I/O latency of 2.33 ms and zero controller IOPS do not indicate that the workload is waiting for storage access.

Soft image-placement enforcement allows images to be placed on clusters other than those matched by the policy's identified cluster set. Hard enforcement instead restricts image placement to the clusters enforced by that policy.

An average VM CPU wait time of 11% indicates CPU contention: virtual machines are waiting to be scheduled on physical CPU resources. Adding CPU capacity to the cluster reduces that contention and improves application responsiveness. The reported memory and SSD utilization levels do not identify those resources as the limiting factor.

In Metro Availability Automatic Resume Mode, an unplanned failover requires manual promotion of the protection domain at the surviving site before protected VMs can restart. The mode does not require the administrator to unwitness Site B before promoting its protection domains.