Nutanix Updated NCP-MCI-6.10 Exam Questions and Answers by arianna

Nutanix Life Cycle Manager (LCM) relies on validated firmware and driver bundles for hardware components. For GPU-enabled hosts, LCM documentation states:

“GPU-enabled AHV hosts require GPU driver bundles to be uploaded manually via the Direct Uploads mechanism so that LCM can validate and upgrade the necessary GPU components during workflow execution.”

GPU drivers are vendor-specific and not always available in the standard catalog, so the administrator must upload them before LCM can orchestrate the upgrade.

Running in dark site mode does not provide missing GPU bundles. Creating agent VMs is unrelated to GPU driver operations. Updating NCC improves validations but does not provide GPU support files.

Therefore, Direct Uploads of GPU driver bundles is required.

Nutanix AHV networking documentation explains that high-connection-count workloads can saturate a single network queue, causing receive-side bottlenecks. VirtIO-Net supports Multi-Queue with Receive-Side Scaling (RSS), allowing the VM to distribute packet processing across multiple vCPUs. The documentation states, “Enabling RSS Multi-Queue improves performance for workloads handling a large number of simultaneous network flows by parallelizing packet handling.”

Trunk mode does not solve per-queue packet processing limitations. Adding vNICs is not recommended because the bottleneck is at the queue level, not the number of interfaces. Using the e1000 adapter results in lower performance compared to VirtIO and is discouraged. Therefore, enabling RSS Multi-Queue is the correct performance optimization for a VM handling thousands of client connections.

Nutanix capacity planning includes a feature called “Reserve Capacity for Failure,” which ensures that enough resources are preserved to sustain one or more node failures without impacting cluster functionality.

For RF3 clusters, the documentation states:

“Reserve Capacity for Failure should be set to Auto Detect, which calculates the required resources dynamically based on node count, RF policy, and data distribution.”

RF3 requires more resiliency than RF2, and manual settings such as fixed percentages do not accurately reflect the space needed during multi-node failure resiliency. “None” is never recommended because it eliminates failover protection. Memory reserve percentages do not impact storage resiliency. Storage reserve percentages are static and do not reflect the real RF3 overhead.

Auto Detect ensures Nutanix automatically calculates the resources needed to sustain the required failure domains.