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 web search results, the cluster redundancy factor (RF) determines how many copies of the cluster metadata and configuration data are stored on different nodes. By default, the cluster RF is 2, which means that there are three copies of the Zookeeper and Cassandra data on the cluster.  If the cluster RF is increased to 3, then there will be five copies of the Zookeeper and Cassandra data on the cluster 1 2 .  This means that the Zookeeper component can tolerate two failures, as it can still operate with a quorum of three nodes out of five 3 .

However, the container replication factor (RF) determines how many copies of the VM data and oplog are stored on different nodes. The container RF can be set independently for each container, and it can be different from the cluster RF.  For example, a container can have RF 2 even if the cluster has RF 3 4 . In this case, the container will only have two copies of the VM data and oplog on the cluster, regardless of the cluster RF.  This means that the Extent Groups component can only tolerate one failure, as it needs at least one copy of the VM data and oplog to be available 5 .

Therefore, if the administrator increases the cluster RF to 3, but does not modify the containers, then the new values in the data resiliency dashboard will be Zookeeper = 2 and Extent Groups = 1.

According to the image description, the exhibit shows a screenshot of a computer screen with a table of data. The table has 6 columns and 4 rows. The columns are labeled “Date”, “Time”, “Status”, “Details”, “Configuration”, and “Duration”. The rows contain information about different configurations and their statuses. The background is a light blue color. There is a pop-up message on the bottom right corner of the screen that reads “This question has been answered. Click here to enable the edit button.”

Based on the table data, it seems that the screenshot is taken from the Prism Central web console, showing the results of a cluster health check report.  The report shows that there are four failed checks: Host Password Policy, CVM Password Policy, NTP Configuration, and Cluster Time Skew 2 . These checks indicate that some initial cluster configuration tasks were missed during the deployment process.

The Host Password Policy check verifies that the host passwords are not set to default values and are compliant with the password policy defined in Prism Central 3 .  The CVM Password Policy check verifies that the CVM passwords are not set to default values and are compliant with the password policy defined in Prism Central 4 . These checks are important for ensuring the security and compliance of the cluster. Therefore, changing the host and CVM passwords from their default values and following the password policy guidelines are two initial cluster configuration tasks that were missed.

References:  1 :  VM Details View - Nutanix Support & Insights   2 :  Cluster Health - Nutanix Support & Insights   3 :  Host Password Policy - Nutanix Support & Insights   4 :  CVM Password Policy - Nutanix Support & Insights

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.

An agent VM is a special type of VM that is used for running services or applications that are not affected by high availability (HA) events or host maintenance. An agent VM is never migrated to any other host in the cluster. If an HA event occurs or the host is put in maintenance mode, agent VMs are powered off and are powered on on the same host once that host returns to a normal state.  This behavior is different from regular VMs, which are migrated to another host in the cluster if possible, or restarted on the same host if not possible 1 .

Therefore, during an AHV upgrade, an administrator may find that a critical VM was powered off rather than migrated to another host if the VM was marked as an agent VM.  This can be done either from the Prism web console by selecting the Use this VM as an agent VM option in the Update VM dialog box, or from the aCLI by using the vm.create or vm.update commands with the agent_vm=true parameter 2 . To avoid this situation, the administrator should ensure that any critical VMs are not marked as agent VMs before starting the AHV upgrade.

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 fabric 1 .

To periodically send information about cluster efficiency via email to a set of users, the administrator can follow these steps:

Create a report in Prism Central that contains the relevant information about cluster efficiency.

Add a schedule to the report to generate and send the report via email to the set of users at a specified frequency.

This will ensure that the users receive regular updates about the cluster efficiency without the need for manual intervention.

According to the Nutanix Support & Insights web search result 2 , VM NICs on AHV can operate in two modes: Access and Trunked. Access NICs are the default, and allow one VLAN on the NIC. Trunked NICs allow multiple VLANs on a single NIC for VMs that are VLAN aware.  If you must use trunked NICs, follow the steps described in the web search result 2 . Therefore, the most efficient way to have a VM on an AHV cluster with access to multiple VLANs is to update a vNIC on the VM to operate in trunked mode for all desired VLANs.

Answer: A. VM-VM anti-Affinity policy

A VM-VM anti-Affinity policy is a rule that ensures that two or more VMs don’t run on the same AHV host. It’s useful when an application provides HA and an AHV host can’t be an application’s single point of failure 1 . In this case, the SQL cluster VMs should have a VM-VM anti-Affinity policy configured to prevent them from running on the same host and causing an outage if that host fails. A VM-VM anti-Affinity policy can be created using the aCLI commands 2 . The other options are not relevant for this scenario.

References: 1 : Affinity Policies - Nutanix Support & Insights 2 : Affinity Policies Help | Nutanix Community