Pass the Nutanix NCP-MCI NCP-MCI-7.5 Questions and answers with ExamsMirror

Nutanix documentation for Windows VM creation on AHV clearly states that when deploying the Nutanix VirtIO ISO for a VM using Secure Boot and UEFI, the SATA bus type must be used. Nutanix also documents that IDE is not supported when Secure Boot is enabled for UEFI mode, which reinforces the correct bus choice. This makes C. SATA the correct answer directly from the official procedure. ( Nutanix )

This is a compatibility question, not a performance question. It can be tempting to choose SCSI because it is common in virtual machine storage design, but Nutanix’s secure-boot provisioning guidance is explicit about the VirtIO ISO attachment method. The exam often checks whether the administrator remembers that the driver ISO itself has a required bus type in secure-boot scenarios. Since the supported method in the Nutanix documentation is to mount the VirtIO ISO on SATA, C is the correct answer. ( Nutanix )

Nutanix AHV networking documentation identifies Active-Active with MAC pinning, also known as balance-slb, as the bond mode that can increase host and VM bandwidth utilization across multiple adapters without requiring additional physical-switch configuration. That makes D the correct answer. By contrast, balance-tcp is associated with LACP and therefore depends on switch-side configuration. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

This is one of the most fundamental AHV bond-type questions. Active-Backup gives redundancy but not simultaneous bandwidth use. No Uplink Bond provides neither aggregation nor redundancy. Because the requirement explicitly says “across multiple physical adapters” and “without additional switch configuration,” the answer must be balance-slb.

The requirement is not to keep the mission-critical VMs together or apart from each other; it is to prevent them from running on a specific set of older hosts. In Nutanix Prism Central policy terms, that is a VM-Host Anti-Affinity Policy. Anti-affinity at the VM-host level allows administrators to mark selected hosts as unsuitable targets for selected VMs, which is exactly what the scenario requires. Therefore C is the correct answer.

The distractors all target the wrong relationship. VM-VM affinity and anti-affinity control how VMs are placed relative to other VMs, not whether they can run on particular hosts. VM-Host Affinity would express a positive preference or requirement to run on a chosen host group, but the question is framed negatively: the VMs must never run on the older hosts. Nutanix’s policy model supports this exact exclusion use case through VM-Host Anti-Affinity. In a long refresh delay scenario, this is the safest operational control to keep sensitive workloads off weaker or undesirable hardware without removing those hosts from the cluster immediately. Therefore C is the authentic answer.