NCP-MCI v6.10: Nutanix Certified Professional - Multicloud InfrastructureDemo

AOS provides the cluster software and compatibility baseline used by Nutanix Lifecycle Manager. Updating AOS first ensures that the LCM workflow and the target software or firmware versions are supported before subsequent LCM-managed updates are applied.

High CPU Ready Time indicates that virtual machines are waiting for physical CPU scheduling time, which can result from host CPU contention. Reviewing host CPU utilization confirms whether contention on the underlying hosts is causing the performance problem.

LCM cannot perform hardware firmware upgrades on a single-node cluster because firmware updates require taking the only node out of service and there is no cluster redundancy for a rolling upgrade. LCM support is not categorically absent for single-node clusters; the restriction is specific to firmware upgrades.

In a Nutanix Metro Availability deployment, a data_locality_check warning indicating a VM is reading and writing across the metro link from a remote cluster means the VM's compute is currently running at a site opposite from where the active copy of its data resides; because Metro Availability resolves I/O against the local copy for optimal performance while synchronously mirroring to the standby site, the corrective action is to migrate the VM back onto a host at the site holding its data and then configure appropriate DRS/affinity rules so future placement stays aligned with the protection domain's active site.

AHV uses SCSI as the preferred virtual-disk bus type for most workloads, with the VirtIO drivers installed in the guest OS. IDE, SATA, and PCI bus types are primarily compatibility options and can have performance implications. Comparing the vDisk bus type can therefore identify whether the lower-performing VM is using a less performant disk controller configuration.