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

According to the Nutanix Community1, host maintenance mode is used to safely migrate all the user virtual machines (VMs) in the host and make sure no VMs are running on the node. If a VM can’t be migrated to another host, you need to shut down the VM for the host to enter into maintenance mode.

According to The Virtualist2, a storage container is a logical segmentation of a storage pool that can be mounted as an NFS datastore on ESXi hosts. You can choose a replication factor (RF) for each storage container, which determines how many copies of data are stored across different nodes.

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.

Automated live migration is a feature of Nutanix that allows the cluster to automatically move VMs from one host to another without any downtime, in order to optimize the performance and availability of the cluster. According to the Nutanix documentation1, automated live migration can occur in the following scenarios:

Cluster resource hotspot: When a host or a group of hosts experience high resource utilization, such as CPU, memory, or network, the cluster can automatically migrate some VMs to other hosts with lower utilization, in order to balance the load and avoid performance degradation.

AOS upgrade: When upgrading the Nutanix software (AOS), the cluster can automatically migrate the VMs from the host that is being upgraded to another host in the same availability zone, in order to maintain the VM availability and minimize the impact of the upgrade process.

AHV host maintenance mode: When putting an AHV host into maintenance mode, the cluster can automatically migrate all the VMs from that host to another host in the same availability zone, in order to prepare the host for maintenance operations such as hardware replacement or firmware update.

A native VLAN is a VLAN that is assigned to untagged traffic on a trunk port of a switch. A trunk port can carry traffic from multiple VLANs, but it needs to have a native VLAN to handle traffic that does not have a VLAN tag. The native VLAN is usually VLAN 1 by default on most switches, but it can be changed to any other VLAN number2. When creating a network profile on Nutanix, the administrator needs to specify the VLAN ID that matches the VLAN configuration on the physical switch. However, if the network profile uses the same VLAN ID as the native VLAN on the switch, it will cause network connectivity issues for the VMs connected to that network profile. This is because Nutanix AHV uses 802.1Q tagging for all network traffic, including traffic in the native VLAN. The switch will expect untagged traffic in the native VLAN and will drop any tagged traffic in that VLAN3. To fix this issue, the administrator needs to change the VLAN field from vlan. 1 to vlan. 0 in the network profile on Nutanix. This will tell Nutanix AHV to send untagged traffic for that network profile and match the native VLAN configuration on the switch4.

A managed network is a type of network that can be created on an AHV cluster and allows VMs to automatically be assigned an IP address at creation time. A managed network uses the Nutanix IP Address Management (IPAM) service, which provides DHCP and DNS functionality for the VMs on the network. A managed network can be configured with a subnet range, a default gateway, and DNS servers. The IPAM service will allocate IP addresses from the subnet range to the VMs and register their hostnames in the DNS servers. The IPAM service will also release the IP addresses when the VMs are deleted or moved to another network1.

To create a managed network on an AHV cluster, the administrator can use Prism Element or Prism Central. The steps are as follows2:

In Prism Element, go to the Network Configuration page and click Create Network.

In Prism Central, go to the Networks page and click Create.

Enter a name and description for the network.

Select Managed as the network type.

Enter the subnet range, default gateway, and DNS servers for the network.

Optionally, enable VLAN tagging and enter a VLAN ID for the network.

Click Save.

One node hosts two VMs while the node being upgraded is in maintenance mode. This is because Nutanix supports a feature called Rolling Upgrade that allows upgrading AHV on a cluster without any downtime or impact to the VMs. The Rolling Upgrade feature performs the upgrade one node at a time, by putting the node in maintenance mode, evacuating the VMs to other nodes, upgrading AHV, and then bringing the node back online. The VM-VM anti-affinity policy ensures that the four VMs are not placed on the same node during the evacuation process, so one node will host two VMs temporarily while the other node is being upgraded.

According to the Nutanix Support & Insights web search result1, if the owner Controller VM becomes unavailable, the address moves to another Controller VM, ensuring that it is always available. This IP address is also used as a cluster-wide address by clients configured as part of Nutanix Files and other products. Therefore, the host will automatically redirect I/O and VMs will continue running without any interruption.

https://portal.nutanix.com/page/documents/details/?targetId=Web-Console-Guide-Prism-v50:wc-bl ock-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.

The only option that requires iSCSI initiator configuration in the guest OS to use Volumes is Microsoft Windows Failover Cluster. Volumes is an enterprise-class, software-defined block storage solution that exposes storage resources directly to virtualized guest operating systems or physical hosts using the iSCSI protocol7. To use Volumes, customers need to configure iSCSI initiators on their hosts or guest OSes. However, some applications or services can use native storage adapters instead of iSCSI initiators when running on AHV VMs. These include:

SQL Server Always On Availability Group: This is a high availability and disaster recovery solution for SQL Server databases that uses Windows Server Failover Clustering (WSFC) and Availability Groups (AGs) as its core components. When running on AHV VMs, SQL Server Always On Availability Group can use native storage adapters instead of iSCSI initiators.

Oracle RAC: This is a clustered database system that provides high availability and scalability for Oracle databases. When running on AHV VMs, Oracle RAC can use native storage adapters instead of iSCSI initiators.

Exchange DAG: This is a group of up to 16 mailbox servers that hosts a set of databases and provides automatic database-level recovery from failures that affect individual servers or databases. When running on AHV VMs, Exchange DAG can use native storage adapters instead of iSCSI initiators.

According to the web search results, the most efficient action an administrator should take to ensure a supported state when adding a node with a higher AOS release to an existing cluster is to perform a standalone reimage of the new node and then add it to the cluster1. This way, the new node will have the same AOS version as the existing nodes, and there will be no compatibility issues or downtime. Therefore, option C is correct, while options A, B, and D are not.