Nutanix Certified Professional - Multicloud Infrastructure v6.5 Exam Questions

https://portal.nutanix.com/page/documents/details/?targetId=Web-Console-Guide-Prism-v50:wc-block-services-enabling-t.html

Provision storage on the Nutanix cluster by creating a volume group. Create a client whitelist to enable access to the volume group by using the IP addresses or client initiator IQNs in a whitelist (as part of the volume group configuration). Create a secret for the volume group if you are using CHAP authentication.

According to the CPU (%) - VMware Docs web search result2, one of the possible causes of high CPU ready % is over-provisioning vCPUs for a VM or having too many VMs on a host. CPU ready % indicates the percentage of time that the VM was ready, but could not get scheduled to run on the physical CPU. High CPU ready % can lead to VM performance problems, such as slow response time or application latency. To improve VM performance, the administrator should reduce the number of vCPUs assigned to VMs or reduce the number of VMs on the hosts, so that there is less contention for CPU resources.

The storage policy value that can be inherited from a cluster is Compression. In the Nutanix Multicloud Infrastructure (NCP-MCI) 6.5, compression is a storage optimization feature that can be configured at the cluster level and inherited by all the entities within the cluster. This feature helps in reducing the storage footprint by compressing the data before writing it to the disk. The other options like IO performance, Storage Container, and QoS are not inherited from the cluster. They are configured and managed separately for each entity as per the requirements.

The output in the exhibit indicates that the node's network interfaces (eth0-eth3) are bonded together using LACP (Link Aggregation Control Protocol) with 'balance-tcp' as the bonding mode and LACP speed set to 'fast'. For LACP to function correctly, the switch ports to which the node is connected must also be configured to support LACP. If the ports on the upstream switch are not configured for LACP, the bond will not be able to establish properly, and the node will not communicate effectively on the network, making it undiscoverable when attempting to expand the cluster.

The absence of an operational LACP configuration could prevent the new node from joining the existing cluster as the node's network interfaces would not be able to pass traffic correctly. This can be verified by checking the switch configuration to ensure that the ports are set to participate in an LACP bond.

The other options, such as a firewall blocking discovery traffic (Option A) or the node being on different VLANs (Option C), are possible causes for a node not being discovered, but given the specific command output provided, the most likely cause is related to the switch port configuration for LACP. Option D, regarding completing LACP configuration after cluster expansion, is not correct because LACP needs to be operational for the node to communicate with the cluster during the expansion process.

Proper LACP configuration is critical for network communication in a Nutanix AHV cluster, and this is covered in detail in the Nutanix AHV and Networking documentation. It outlines the steps for configuring network bonds and LACP on both the AHV hosts and the connecting network infrastructure.

The storage policy value that can be inherited from a cluster is Compression. In the Nutanix Multicloud Infrastructure (NCP-MCI) 6.5, compression is a storage optimization feature that can be configured at the cluster level and inherited by all the entities within the cluster. This feature helps in reducing the storage footprint by compressing the data before writing it to the disk. The other options like IO performance, Storage Container, and QoS are not inherited from the cluster. They are configured and managed separately for each entity as per the requirements.