NCP-MCI-6.5 Exam Dumps - Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) v6.5 exam

According to the Migration to a different processor web search result2, live migration of VMs depends on the source and destination hosts having the same CPU functions (CPU flags). Live migration requires the source and destination hosts to have CPUs from the same manufacturer, and only CPU functions which both hosts support are provided (same CPU generation, or by using VMware Enhanced vMotion Compatibility (EVC)). If the administrator adds a node with older generation processors to an existing AHV cluster with newer generation processors, then live migration of VMs is prevented between newer and older processors, unless EVC is enabled.

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'.

The correct answer is C. The VLAN was not created on the upstream switches.

A VLAN (virtual local area network) is a logical segmentation of a physical network that allows devices on the same VLAN to communicate with each other, regardless of their physical location. A VLAN also isolates the devices on different VLANs from each other, unless there is a router or a layer 3 switch that can route traffic between VLANs. To create a VLAN, the administrator needs to configure the network devices that are involved in the VLAN, such as switches, routers, and hosts. The administrator also needs to assign a unique VLAN ID to each VLAN, which is a number between 1 and 4094 that identifies the VLAN1.

In Nutanix AHV, the administrator can create a Nutanix managed network with a specific VLAN ID for guest VMs. This network can be assigned to VM NICs using Prism Element or Prism Central. However, creating a Nutanix managed network does not automatically create the VLAN on the upstream switches that connect the AHV hosts. The administrator needs to manually configure the upstream switches to allow the VLAN traffic on the ports that connect to the AHV hosts. The administrator also needs to ensure that the upstream switches are interconnected physically or virtually and can forward traffic between different VLANs if needed2.

Therefore, if an administrator has created a Nutanix managed network with a VLAN ID of 512 and notices that the VMs on that network can only communicate with other VMs on the same host, but not with VMs on different hosts in the cluster, the most likely cause of this issue is that the VLAN was not created on the upstream switches. This means that the switches are dropping or blocking the traffic with VLAN ID 512 and preventing it from reaching other hosts or VMs. To resolve this issue, the administrator should create the VLAN on the upstream switches and allow it on the ports that connect to the AHV hosts3.

The critical alerts listed are indicating that the default passwords are still in use for IPMI, the host, and the Controller Virtual Machine (CVM). This suggests that the passwords for these components were not changed from the default during the initial cluster configuration and deployment process, which is a critical security practice.

A. CVM password changes: The alert for the CVM using the default password indicates that the CVM password has not been changed. It is a standard security measure to change default passwords to prevent unauthorized access.

C. Host password changes: Similarly, the alert for the host using the default password indicates that the default password for the host has not been updated. This applies to the passwords used to access the hypervisor host directly.

Changing default passwords is a critical step in securing the Nutanix environment. This is highlighted in Nutanix's best practices and security guidelines, which recommend changing default passwords as part of the initial configuration to ensure that the environment is not left vulnerable to unauthorized access due to known default credentials. This process is typically part of the initial setup procedures outlined in the Nutanix documentation for cluster deployment and security configuration.

The IPMI alert also points to the need for changing default passwords, but since IPMI (Intelligent Platform Management Interface) is not specifically mentioned in the provided options, it falls under the broader category of host-level password changes, which would be covered by option C.

BIOS password changes (Option B) and Password policy changes (Option D) are also important but were not directly flagged by the alerts mentioned. BIOS password changes are usually a separate task and not indicated by the alerts given, while password policy changes are related to the policies governing password complexity and rotation rather than the initial password setup.

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.

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.