Free Practice Questions for Nutanix NCP-MCI-6.5 Exam

The correct answer is B. The existing and the expansion node are on different VLANs.

The output shows that the new node has a br0-up bond with four interfaces: eth0, eth1, eth2, and eth3. The bond is configured with LACP active and LACP fallback set to false. This means that the bond will only work if the upstream switch supports LACP and is configured to form an LACP group with the four interfaces. However, the output also shows that the bond has no IP address assigned to it, which indicates that the bond is not operational. One possible reason for this is that the existing and the expansion node are on different VLANs, and the upstream switch is not configured to allow the VLAN traffic on the LACP group. This would prevent the new node from communicating with the cluster and being discovered by the Expand Cluster function in Prism.

To verify this, the administrator can check the VLAN configuration on the upstream switch and compare it with the existing nodes. Alternatively, the administrator can use the “manage_ovs show_uplinks” command on an existing node and compare the output with the new node. If there is a VLAN mismatch, the administrator can either change the VLAN configuration on the switch or on the new node to match the existing nodes.

NTP service needs to be configured to ensure logs, alerts and information is consistent across clusters that are located in different countries. NTP stands for Network Time Protocol and it is used to synchronize the clocks of all the nodes in a cluster1. This helps to maintain accurate timestamps for logs, alerts and other information that are generated by Nutanix clusters1.

Categories are key-value pairs that can be used to tag entities such as VMs, images, networks, and projects in Prism Central. Categories can be used to create dynamic groups of entities based on their attributes, and assign roles and permissions to those groups3. In this case, a category such as OS=Linux can be used to group all Linux VMs and grant access rights to the Linux administration team.

https://next.nutanix.com/installation-configuration-23/nutanix-vlan-34170

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 failure1. 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 commands2. The other options are not relevant for this scenario.

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

Port 389 is the default port for LDAP without SSL encryption. Port 636 is used for LDAP over SSL (LDAPS). Port 3268 and 3269 are used for Global Catalog (GC) and Global Catalog over SSL (GCSSL), respectively2.

According to the web search results, two steps that should be taken to prepare for relocating an AHV cluster to a new datacenter during a maintenance window are:

Shut down all user VMs in the cluster: This step is necessary to ensure that there is no data loss or corruption during the relocation process. The user VMs can be shut down either individually or in bulk by using the Prism Element web console or the acli command-line interface1.

Stop all Nutanix Files clusters: If the AHV cluster hosts any Nutanix Files clusters, they should be stopped before relocating the cluster. Nutanix Files clusters are composed of one or more virtual machines that provide file services to clients. Stopping a Nutanix Files cluster will stop all the file server VMs and release the resources they consume2. The Nutanix Files clusters can be stopped by using the Prism Element web console or the ncli command-line interface3.

According to section 4 of the exam blueprint guide1, one of the topics covered is AHV networking components and configuration settings. One of these components is Open vSwitch (OVS), which is a software switch that provides network connectivity between VMs and physical networks. OVS has two types of ports:

Uplink ports: These are physical ports that connect to external networks or switches.

Internal ports: These are virtual ports that connect to VMs or other internal networks.

To view the uplink state of all AHV nodes in the cluster, an administrator can use the manage_ovs command with the show_uplinks option. This command displays information such as port name, link state, speed, duplex mode, MTU size, bond mode, and bond status. However, this command only works on a single node. To run the command on all nodes in the cluster, an administrator can use the allssh command, which executes a command on all CVMs in parallel. Therefore, the correct command is:

allssh manage_ovs show_uplinks

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.