Nutanix Updated NCP-MCI-7.5 Exam Questions and Answers by sulayman

Nutanix documentation for updating a VM through Prism Central states explicitly: “BIOS mode: You cannot modify the BIOS mode after the VM is created.” That wording directly answers the question and makes A the correct option. By contrast, vCPU count and memory allocation are common VM settings that administrators can adjust as part of lifecycle management, and boot priority can also be changed in supported conditions. The only one Nutanix calls out as restricted after creation is the BIOS mode. ( Nutanix Portal )

This reflects how foundational firmware mode is to VM identity and boot architecture. Once the VM is created using Legacy BIOS or UEFI, many guest-OS assumptions, boot-device structures, and security options depend on that original firmware model. Nutanix therefore locks this parameter after creation instead of treating it as an ordinary runtime edit. For exam preparation, this is a classic item to memorize: CPU and memory can generally be changed, but BIOS mode cannot be modified after VM creation. So the authentic Nutanix answer here is A. BIOS mode. ( Nutanix Portal )

Nutanix documentation for Prism Central point-in-time backups states that the Recovery Point Objective (RPO) can be configured in values ranging from 1 hour to 24 hours. Since the question asks for the RPO time in hours for Prism Central backups, the expected exam answer is the maximum supported interval of 24 hours, which corresponds to option A.

This is not asking how long recovery takes or how long restore points are retained. Nutanix documents those separately. The RPO defines how often recovery points can be taken, and Prism Central’s backup framework allows choices up to a 24-hour interval. That is why values like 36, 48, or 72 hours are not supported answers in the documented PC backup workflow. So for an authentic Nutanix-aligned study sheet, A. 24 is correct.

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 documentation is very clear on this point: Secure Boot is not supported if the VM uses IDE disks. Nutanix also states that for AHV, if Secure Boot is enabled for UEFI mode, the IDE interface is not supported and SATA should be used for the VirtIO ISO in that configuration. So an IDE-attached disk is a direct blocker to enabling Secure Boot. ( Nutanix Portal )

This is one of those areas where the exam expects you to know compatibility rules, not just feature names. UEFI is actually part of the supported Secure Boot path, so option D is not the blocker. The CVM’s RAM and node cache storage are unrelated to whether the VM’s firmware and bus configuration can support Secure Boot. The administrative fix is usually to convert the VM to a supported configuration using UEFI and non-IDE bus types where required. Therefore, among the listed options, the condition that prevents completion of the task is the presence of IDE disks, making C correct. ( Nutanix Portal )