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

According to the Nutanix Community1, users can authenticate using their Active Directory credentials when Active Directory support is enabled for Prism Central. To enable Active Directory support, you need to configure Role Mapping12, which defines how Active Directory groups map to Prism Central roles.

https://next.nutanix.com/ncm-intelligent-operations-formerly-prism-pro-ultimate-26/configuring-authentication-38051

Shadow Clones is a Nutanix feature that provides effective caching optimization in VDI environments. VDI stands for Virtual Desktop Infrastructure, which is a technology that allows users to access virtual desktops hosted on a centralized server. VDI environments typically have a high degree of similarity among desktop images, which means that many VMs access the same data blocks from the storage layer. Shadow Clones leverages this similarity by creating read-only copies of frequently accessed data blocks on each node’s SSD tier, reducing network traffic and improving performance. Shadow Clones works automatically and transparently without any configuration or intervention from the administrator.

References: : [Fault Tolerance - Nutanix Bible] : [Block Awareness - Nutanix Bible] : [Block Awareness - Nutanix Support & Insights] : [Shadow Clones - Nutanix Bible] : [Shadow Clones - Nutanix Support & Insights] : [Shadow Clones - Nutanix Community]

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.

Terminology

• Availability Zone – it is represented by all resources (Nutanix Clusters) connected to Prism Central or Xi Leap Availability zone. Depends on the architecture, Availability zone can represent geographic territory, datacenter or server room in the datacenter. Protection policies – in protection policies you set up (RPO, Retention), rules to auto-apply policies to virtual machines

https://vmware mine.com/2019/02/08/nutanix-leap-runbooks-part-1/#sthash.VwrzSzhQ.dpbs

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.

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 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 cluster12. This means that the Zookeeper component can tolerate two failures, as it can still operate with a quorum of three nodes out of five3.

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 34. 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 available5.

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.