Pass the Nutanix Certified Professional (NCP) NCP-MCI-6.5 Questions and answers with ExamsMirror

This is because Nutanix uses a distributed storage fabric (DSF) that replicates data across multiple nodes and drives to ensure data resiliency. When a drive fails, the cluster detects the failure and initiates a data rebuild process to restore the replication factor (RF) of the affected containers. The data rebuild process does not affect the availability or performance of the VMs, as they can still access their data from other replicas on other nodes or drives. Therefore, there is no need to wait for 60 minutes, use a shared volume group, or trigger an HA event.

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.

The default network configuration for AHV hosts and CVMs is a bond named br0-up with two or more uplinks in active-backup mode. This means that only one uplink is active at a time, while the others are in standby mode. This provides high availability, but not load balancing or increased bandwidth. To increase the bandwidth available to the AHV host and the CVM, the administrator can change the bond mode to Active-Active, which allows all uplinks to be used simultaneously. This can be done using the manage-ovs commands on each AHV host. The steps are as follows1:

Log in to the AHV host using SSH.

Enter maintenance mode on the CVM by running allssh 'cluster status | grep -i cvm | grep -i down'.

Change the bond mode to Active-Active by running manage_ovs --bond_mode active-active update_uplinks br0-up , where  is a comma-separated list of uplink interfaces (for example, eth0,eth1).

Verify the bond mode by running manage_ovs show_uplinks.

Exit maintenance mode on the CVM by running allssh 'cluster start'.

According to the Nutanix Support & Insights, IPAM enables AHV to assign IP addresses automatically to VMs using DHCP. You can configure each virtual network and associated VLAN with a specific IP subnet, associated domain settings, and group of IP address pools available for assignment.

Curator is the process that runs on every node in a Nutanix cluster and is responsible for data management tasks such as deduplication, compression, erasure coding, and replication factor compliance. Curator also handles disk failure recovery by scanning Cassandra to find all data previously hosted on the failed disk, and all disks in that node. Curator then rebuilds the data on other nodes in the cluster using the distributed storage fabric1.

According to the Troubleshooting hosted disk I/O performance problems (1008885), when using VMware hosted products, consider that both the virtual machines and host operating system often share the same disk resources and hardware. If a hard disk fails, the virtual machines that have data on the failed device will experience an HA event, causing them to restart on a node that contains the replica data.

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.

According to the How to use the cvm_shutdown script web search result3, the cvm_shutdown script signals HA when shutting down the CVM (Controller VM) to forward the storage traffic to another healthy CVM. Instead of using sudo shutdown or sudo reboot commands, this script should be used to minimize I/O hits in user VMs running on the present hypervisor host. The cvm_shutdown -P now command will initiate the shutdown process on the CVM immediately. Therefore, if the administrator needs to perform an orderly shutdown of the CVM, they should execute this command from the CVM.

Configure VM-Host affinity for the nodes that meet the application’s GPU requirement. This is because VM-Host affinity allows the administrator to specify which nodes a VM can run on or must not run on1. By creating a VM-Host affinity rule that binds the application VM to the three nodes that have the physical GPU, the administrator can ensure that the VM will always run on a node that meets its requirement, regardless of any HA or migration events. This also allows the other nodes in the cluster to host other VMs without any restrictions.

The correct answer is A. Long term storage of data which is written once and read infrequently.

Erasure Coding is a feature that increases the usable capacity on a Nutanix cluster by reducing the amount of data replication. Instead of replicating data, Erasure Coding uses parity information to rebuild data in the event of a disk failure. The capacity savings of Erasure Coding is in addition to deduplication and compression savings1.

Erasure Coding is most beneficial for scenarios where the data is written once and read infrequently, such as long term storage of archival data, backup data, or cold data. This is because Erasure Coding has some trade-offs and limitations that may affect the performance and availability of the cluster. Some of these trade-offs and limitations are2:

Erasure Coding requires more CPU and memory resources than replication, as it involves more complex calculations for encoding and decoding data.

Erasure Coding increases the network bandwidth consumption, as it involves more data transfers between nodes for encoding and decoding data.

Erasure Coding reduces the resiliency of the cluster, as it can tolerate fewer node failures than replication. For example, a cluster with redundancy factor 2 can tolerate one node failure with replication, but only two disk failures with Erasure Coding.

Erasure Coding is not effective for workloads that have many overwrites or random writes, as it involves more overhead for updating the parity information.

Erasure Coding is not supported for some features, such as volume groups, file server VMs, or Metro Availability.

Therefore, if an administrator needs to configure a container on a Nutanix cluster, they should enable Erasure Coding only if the container will store data that is written once and read infrequently. This way, they can maximize the capacity savings of Erasure Coding without compromising the performance and availability of the cluster.