Nutanix Certified Professional - Multicloud Infrastructure v6.10 NCP-MCI-6.10 Exam Practice Test

Answer : B

BMC (Baseboard Management Controller) updates can be applied per-node in Nutanix LCM, unlike AOS or AHV, which require cluster-wide upgrades.

Option B (BMC) is correct:

BMC firmware controls remote management and power cycling of individual nodes.

Updating BMC does not impact the entire cluster and can be done per node.

Option A (AOS) is incorrect:

AOS upgrades affect the entire cluster and require cluster-wide consistency.

Option C (NCC) is incorrect:

NCC updates apply across all nodes simultaneously, ensuring uniformity in checks.

Option D (AHV) is incorrect:

AHV updates require coordinated upgrades across hosts to maintain VM availability.

References:

Nutanix LCM User Guide Per-Node Firmware Updates

Nutanix KB How to Upgrade BMC Using LCM

Answer : B

VMs using GPU pass-through cannot be live-migrated because they are directly tied to a physical GPU on a specific host.

Option B (VMs use GPU pass-through) is correct:

Pass-through devices (such as GPUs) are directly assigned to VMs, making migration impossible unless the VM is powered off first.

Option A (VMs use a Volume Group) is incorrect:

Volume Groups support live migration unless they are configured incorrectly.

Option C (VM-VM anti-affinity) is incorrect:

Anti-affinity rules prevent two specific VMs from running together, but do not prevent migration.

Option D (VMs use external NAS) is incorrect:

Using NAS does not block VM migration, as Nutanix supports shared storage across hosts.

References:

Nutanix AHV Best Practices GPU Pass-through and VM Migration Limitations

Nutanix KB Why Can't I Live Migrate a VM with GPU Passthrough?

Answer : D

For cross-hypervisor DR failover (e.g., ESXi to AHV), Nutanix Guest Tools (NGT) must be installed on VMs to ensure proper configuration and recovery.

Option D (NGT must be installed on source guest VMs) is correct:

NGT ensures correct reconfiguration of VM devices and networking settings during failover.

It handles disk and driver reassignments between ESXi and AHV.

Option A (Utilize delta disks) is incorrect:

Delta disks are used in snapshot optimization, not DR failover.

Option B (Deploy Legacy BIOS boot) is incorrect:

AHV prefers UEFI boot mode, and Legacy BIOS is not a requirement.

Option C (Use raw device mappings) is incorrect:

RDMs are VMware-specific and are not used in AHV failover scenarios.

References:

Nutanix Disaster Recovery Guide Cross-Hypervisor Failover Best Practices

Nutanix KB Ensuring VM Compatibility During ESXi to AHV DR

Answer : A

Agent VMs, such as CVMs (Controller VMs) or Witness VMs, have strict affinity and anti-affinity rules to ensure they remain on specific hosts and maintain data consistency and high availability. If an agent VM is powered off and then manually started on another host, it becomes unresponsive because it breaks these rules.

From the Nutanix Enterprise Cloud Administration (ECA) course materials:

''Agent VMs have specific configuration and affinity constraints. Manually starting them on another host violates these constraints, resulting in the agent VM becoming unresponsive to the cluster.''

Further clarification:

''The cluster expects the agent VM to be on a particular host. Moving it manually to another host breaks this expectation and causes the VM to be unable to properly join the cluster services, leading to an unresponsive state.''

Therefore, it is essential to avoid manually starting agent VMs on different hosts, as doing so can disrupt cluster services.

Answer : D

Nutanix Intelligent Operations Reports (Option D) provide weekly summaries of cluster health, performance, and resource consumption.

These reports include recommendations for optimization, alerts, and forecasted resource usage trends.

Option A (Admin Center LCM) manages firmware and software upgrades but does not generate weekly performance reports.

Option B (Prism Central Syslog) is used for logging and event tracking, not performance summaries.

Option C (Infrastructure VMs List) provides a static list of VMs but does not generate periodic reports.

References:

Nutanix Prism Central Intelligent Operations and Reports

Nutanix Bible Automated Insights for Cluster Health Monitoring

Nutanix KB Using Intelligent Operations Reports for Capacity Planning

Answer : A

Answer : B

To automate the deployment of a large number of Linux VMs (such as 100), each with similar base configurations but unique hostnames, local configurations, and additional package installations, Cloud-Init is the most appropriate approach. Cloud-Init is a widely supported industry-standard tool for automating the initialization and configuration of Linux instances at first boot.

From the Nutanix Enterprise Cloud Administration (ECA) course materials:

''Cloud-Init is the recommended method for configuring Linux virtual machines during deployment in Prism Central. It allows administrators to inject configuration scripts and user data that customize the VM at boot time, including hostname, network settings, user creation, and package installations.''

Specifically:

''Using Cloud-Init, you can create a template or base image for the Linux VMs and then customize each VM deployment by passing individualized configuration parameters, ensuring that while the base configuration remains consistent, each VM has unique settings such as hostname or installed software.''

This method is far superior to manual configuration, which is impractical for 100 VMs, and it's not suitable to use SysPrep (which is for Windows-based customization). VM templates alone would provide only the base image; they do not address unique per-VM settings.

Therefore, Cloud-Init ensures a repeatable, scalable, and fully automated deployment process that aligns with the Nutanix best practices for deploying large numbers of Linux VMs with unique configurations.