Free NCP-MCI-6.5 Questions Attempt

According to the web search results, the most efficient action an administrator should take to ensure a supported state when adding a node with a higher AOS release to an existing cluster is to perform a standalone reimage of the new node and then add it to the cluster1. This way, the new node will have the same AOS version as the existing nodes, and there will be no compatibility issues or downtime. Therefore, option C is correct, while options A, B, and D are not.

According to section 6 of the exam blueprint guide1, one of the topics covered is VM placement options. When creating a new VM on an AHV cluster, there are two ways to determine its initial placement:

• Automatic placement: The Acropolis Dynamic Scheduler (ADS) selects a host that provides adequate resources for the VM’s configuration, such as CPU, memory, disk space, and network bandwidth. ADS also considers factors such as host load, power state, availability domains, and affinity rules.
• Manual placement: The administrator can specify a host or a host group where they want to place the VM.

According to the Nutanix Volumes - Recommendations And Best Practices web search result3, two actions that the administrator should take when designing the Volume Group are:

• Distribute workload across multiple virtual disks: Use multiple disks rather than a single large disk for an application. Consider using a minimum of one disk per Nutanix node to distribute the workload across all nodes in a cluster. Multiple disks per Nutanix node may also improve an application’s performance. For performance-intensive environments, we recommend using between four and eight disks per CVM for a given workload.
• Enable RSS (Receive Side Scaling): Receive-side scaling (RSS) allows the system to use multiple CPUs for network activity. With RSS enabled, multiple CPU cores process network traffic, preventing a single CPU core from becoming a bottleneck. Enabling RSS within hosts can be beneficial for heavy iSCSI workloads. For VMs running in ESXi environments, RSS requires VMXNET3 VNICs. For Hyper-V environments, enable VMQ to take full advantage of Virtual RSS.