NCP-MCI-6.5 Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) v6.5 exam Questions and Answers

According to the  Nutanix Prism Central Guide , you can click on any chart in a widget to expand it and view more details about the data elements.

According to the  Nutanix Files Guide , Nutanix Files instances are composed of a set of VMs (called FSVMs). Files requires at least three FSVMs running on three nodes to satisfy a quorum for high availability. By default, Files deploys three FSVMs when you create a file server instance.

A constrained VM is one that does not have enough resources for the demand and can lead to performance bottlenecks.  A VM is considered constrained when it exhibits one or more of the following baseline values, based on the past 21 days: CPU usage > 90% (moderate), 95% (severe) CPU ready time > 5%, 10% Memory usage > 90%, 95% Memory swap rate > 0 Kbps 1 .  To provide adequate host resources, resize (increase) the constrained VMs 1 .

Configure VM-Host affinity for the nodes that meet the application’s GPU requirement.  This is because VM-Host affinity allows the administrator to specify which nodes a VM can run on or must not run on 1 . By creating a VM-Host affinity rule that binds the application VM to the three nodes that have the physical GPU, the administrator can ensure that the VM will always run on a node that meets its requirement, regardless of any HA or migration events. This also allows the other nodes in the cluster to host other VMs without any restrictions.

According to the Nutanix Support & Insights web search result 1 , erasure coding is a data savings technique that utilizes stripes and parity calculation in a Nutanix cluster. Erasure coding increases the usable capacity on a cluster by reducing the replication factor of data blocks. Instead of replicating data, erasure coding uses parity information to rebuild data in the event of a disk or node failure.  Erasure coding can save up to 50% of storage space compared to replication factor 2, and up to 75% compared to replication factor 3 2 .

Prism Central is a multi-cluster manager that provides a single, centralized management interface for Nutanix environments 1 . Prism Central can be deployed in different configuration scenarios, depending on the network and security requirements of the environment. Some of the valid scenarios are:

Environments use Network Address Translation (NAT): NAT is a method of mapping one IP address space to another by modifying network address information in IP datagram packet headers while they are in transit across a traffic routing device 2 .  NAT can be used to enable communication between Prism Central and Prism Elements that are in different networks or subnets 3 .  For example, Prism Central can be deployed in a public cloud and use NAT to access Prism Elements that are in a private data center 3 .

Prism Elements and Prism Central are in different subnets: A subnet is a logical subdivision of an IP network that allows multiple networks to share a single physical network 4 .  Prism Elements and Prism Central can be in different subnets as long as they can communicate with each other through routing or NAT 3 .  For example, Prism Central can be deployed in a management subnet and access Prism Elements that are in different application subnets 3 .

Environments do not have Internet access: Internet access is not required for the deployment of Prism Central, as long as the environment meets the prerequisites and considerations for installing or upgrading Prism Central. For example, Prism Central can be deployed in a dark site, which is an environment that does not have Internet access or has restricted Internet access. In this case, the administrator needs to manually enable microservices infrastructure and download the required software packages from another source.

According to the Nutanix Support & Insights web search result 1 , 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.

LCM (Life Cycle Manager) is a feature that allows Nutanix administrators to perform one-click firmware and software upgrades for Nutanix clusters and components. LCM fetches inventory and update information from a pre-configured URL that contains the latest versions of firmware and software packages. However, upgrading Nutanix AOS does not automatically update the fetch URL. To update the fetch URL, the administrator needs to update the LCM framework.  The LCM framework is the core component of LCM that provides the logic and functionality for inventory, download, and upgrade operations 1 .

To upgrade the LCM framework, the administrator needs to perform an LCM inventory. An LCM inventory is a process that scans the cluster and its components for their current firmware and software versions and compares them with the available versions from the fetch URL. If there is a newer version of the LCM framework available, it will be shown as an update option under Cluster Software Component in the Available Updates page.  The administrator can then select and apply the LCM framework update to upgrade it to the latest version 2 .

The administrator can perform an LCM inventory using Prism Element or Prism Central.  The steps are as follows 3 :

In Prism Element, go to the Network Configuration page and click Life Cycle Management.

In Prism Central, go to the Services page and click Life Cycle Management.

Click Inventory in the toolbar and select Perform Inventory from the drop-down menu.

Wait for the inventory process to complete and check for any available updates.

https://portal.nutanix.com/page/documents/details/?targetId=Web-Console-Guide-Prism-v50:wc-bl ock-services-enabling-t.ht ml

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.

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]

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.

First Preference:

Policy is applied to a specific entity

2nd Preference:

Policy is applied to an entity type in a category

3rd Preference:

Policy is applied to an entity type in a cluster

4th Preference:

Policy is applied to all entities of an entity type

Comprehensive Detailed Explanation with References: In Nutanix Prism, when multiple alert policies are created and applied to the same entities, the policies are evaluated based on their specificity. The order of precedence from highest to lowest is as follows:

Policy is applied to a specific entity : Custom alert policies that are applied to specific entities take precedence over those applied to broader categories. This is because the more specific policy is usually created with a particular context or requirement in mind for that entity.

Policy is applied to an entity type in a category : The next level of precedence is given to policies that are applied to all entities of a certain type within a specific category. Categories allow grouping of entities based on certain criteria, and policies applied here are more specific than to an entire cluster or entity type.

Policy is applied to an entity type in a cluster : This refers to policies that are applied to all entities of a certain type within a specific cluster. This is more general than the above two but still targets a specific cluster environment.

Policy is applied to all entities of an entity type : The lowest precedence is given to policies that are broadly applied to all entities of a particular type across the entire Nutanix environment.

This order ensures that the most specifically targeted policies are given priority, which allows for fine-tuned control and customization of alert policies. The details of alert policy precedence are typically covered in the Nutanix Prism Central Guide and the documentation related to Prism Central ' s alerting and policies.

According to the Nutanix Support & Insights website 1 , you can configure alert emails through Prism Central by enabling or disabling customer email notification for each alert.  You can also modify or create custom alert policies for different entities and clusters 2 3 .

The number of Prism Central instances required to deploy Leap is one per customer environment.  Prism Central is a multi-cluster manager that provides a single, centralized management interface for Nutanix environments 3 .  Leap is a native cloud extension that provides disaster recovery as a service (DRaaS) for Nutanix environments 4 .  To use Leap, customers need to have one Prism Central instance deployed in their primary site, and register it with their Xi Cloud Services account 5 .  This Prism Central instance can manage multiple Nutanix clusters across different physical sites or availability zones 6 .

According to section 4 of the exam blueprint guide 1 , 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 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 interface 1 .

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 consume 2 .  The Nutanix Files clusters can be stopped by using the Prism Element web console or the ncli command-line interface 3 .

API Explorer page will launch  when an administrator presses the letter A on the keyboard after logging into Prism Element.  This is one of the keyboard shortcuts that Prism Element provides for accessibility and ease of use 1 .  API Explorer is a tool that allows users to explore and test Nutanix REST APIs within Prism Element 1 .

https://www.nutanixbible.com/3b-book-of-prism-navigation.html

According to the Nutanix Support & Insights web search result 3 , advertised capacity is an advanced container setting that allows the administrator to reserve an advertised storage space for a storage container. An advertised capacity setting gives the hypervisor a maximum storage size that the storage container can use. This setting can be any arbitrary value greater than or equal to the resiliency required. The hypervisor ensures that the storage container storage doesn’t go beyond the advertised capacity. If the administrator wants a container to be displayed and limited to 1TB in the hypervisor, they should set the advertised capacity to 1TB.

According to the How to use the cvm_shutdown script web search result 3 , the cvm_shutdown script signals HA when shutting down the CVM (Controller VM) to forward the storage traffic to another healthy CVM. Instead of using sudo shutdown or sudo reboot commands, this script should be used to minimize I/O hits in user VMs running on the present hypervisor host. The cvm_shutdown -P now command will initiate the shutdown process on the CVM immediately. Therefore, if the administrator needs to perform an orderly shutdown of the CVM, they should execute this command from the CVM.

According to the web search results, one possible cause of inter-VM communication failure between hosts is that the switch is not configured to allow VLAN 15 traffic. VLAN 15 is the default VLAN ID used by AHV for internal communication between CVMs and hosts.  If the switch blocks or drops VLAN 15 packets, it will prevent inter-VM communication across hosts 4 . To enable full inter-VM communication, the administrator should update the switch to specifically allow VLAN 15 traffic on the ports connected to the AHV hosts.

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 .

Answer: D. Load the Virtual SCSI pass-through controller.

The error message shown in the image indicates that Windows 10 setup cannot find any drives to install the OS. This is because the Nutanix AHV hypervisor uses a virtual SCSI pass-through controller to present disks to the VMs, and Windows 10 does not have a built-in driver for this device. Therefore, the administrator needs to load the Nutanix VirtIO driver for the virtual SCSI pass-through controller during the OS installation process. The Nutanix VirtIO driver package contains various drivers that are specifically used by Windows VMs hosted in the Nutanix environment to enhance their stability and performance 1 . The administrator can download the latest Nutanix VirtIO driver package from the VirtIO downloads page of the Nutanix support portal. The administrator can then follow these steps to load the driver and install the OS 2 :

On the Windows 10 setup screen, click Load driver.

Insert a USB drive or mount an ISO image that contains the Nutanix VirtIO driver package.

Browse to the location of the driver package and select the folder that matches the OS architecture (32-bit or 64-bit).

Select the vioscsi.inf file and click Next.

Wait for the driver to load and then click Refresh.

Select the disk where you want to install Windows 10 and click Next.

References: 1 : VirtIO Driver Versions for Windows 2 : Installing Windows on AHV

switch ports are configured with different VLANs  could be the cause of this error.  If the switch ports are not configured with the same VLANs as the network interfaces on each node, then there could be a mismatch in network connectivity when one interface is disconnected 1 . This could affect the guest VMs that are using a different VLAN than the hypervisor.

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2023_3:mul-cluster-storage-policy-pc-c.html

According to the  Red Hat Customer Portal , to use RELP with Rsyslog, you need to install the rsyslog-relp package on both the server and the client. If the remote server does not have rsyslog-relp installed, RELP logging will not work as expected.

This is because Nutanix uses a distributed storage fabric (DSF) that replicates data across multiple nodes and drives to ensure data resiliency. When a drive fails, the cluster detects the failure and initiates a data rebuild process to restore the replication factor (RF) of the affected containers. The data rebuild process does not affect the availability or performance of the VMs, as they can still access their data from other replicas on other nodes or drives. Therefore, there is no need to wait for 60 minutes, use a shared volume group, or trigger an HA event.

The change password at next logon attribute is a setting that forces a user to change their password when they log on to a domain for the first time or after their password has expired.  This attribute is enabled by default for new Active Directory user accounts or when an administrator resets a user’s password 4 .

However, Prism Central does not support this attribute for Active Directory authentication. Users with this attribute enabled will not be able to log on to Prism Central using their Active Directory credentials.  They will receive an error message saying “Invalid credentials” or “Authentication failed” when they try to log on 5 .

Therefore, if an administrator is not able to log on to Prism Central using a new Active Directory user account, the most likely cause of this issue is that the change password at next logon attribute is set for that user account.  To resolve this issue, the administrator should disable this attribute for the user account or log on to a domain workstation first and change their password before accessing Prism Central 6 .

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

inline compression  is a technique that compresses all incoming write I/O operations over 4 KB inline in the persistent write buffer (oplog) 2 3 .  This approach enables you to use oplog capacity more efficiently and helps drive sustained performance 2 .  From AOS 5.18 onward, inline compression (compression delay=0) is enabled by default for all new containers 2 4 .

https://portal.nutanix.com/page/documents/solutions/details?targetId=TN-2032-Data-Efficiency:TN-2032-Data-Efficiency

According to the web search results, Distributed Storage Fabric (DSF) is the scale-out storage technology that makes HCI and cloud possible 4 5 .  DSF pools the storage devices that are directly attached to a cluster of servers and presents them to applications across a variety of storage protocols 4 .  DSF also manages and protects data by a fine-grained, distributed metadata system that ensures uniform distribution of data throughout the cluster to eliminate hot spots and speed up rebuilds

Nutanix provides two types of granular RBAC for AHV hosts: category based and cluster based 3 . Category based RBAC allows administrators to assign roles to users or groups based on categories, which are key-value pairs that can be applied to various entities in Prism Central, such as clusters, hosts, VMs, images, and networks. Categories can be used to group entities by different criteria, such as department, project, environment, or location. For example, an administrator can create a category key named Department and assign different values to it, such as Finance, Marketing, or Engineering. Then, the administrator can apply this category to different clusters or hosts and assign roles to users or groups based on this category.  This way, users or groups can have different levels of access to different clusters or hosts depending on their department 4 .

Cluster based RBAC allows administrators to assign roles to users or groups based on specific clusters registered in Prism Central. For example, an administrator can create a role named Cluster Admin and assign it to a user or group for a particular cluster.  This way, the user or group can have full access to that cluster and its hosts and VMs, but not to other clusters 5 .

According to the web search results, Prism Central is a multi-cluster manager that provides a single, centralized management interface for Nutanix environments 1 2 .  One of the features of Prism Central is multi-cluster Single Sign On (SSO), which allows users to log in once and access multiple clusters without re-entering credentials 3 .

Nutanix leverages a method for determining the bands called ‘Generalized Extreme Studentized Deviate Test’. A simple way to think about this is similar to a confidence interval where the values are between the lower and upper limits established by the algorithm.

Another web source 3  shows an example of how anomaly detection works in Nutanix Prism Central. In the video, you can see that when the observed value of a metric deviates significantly from the predicted value based on historical data, an anomaly event is triggered and displayed on a chart.

Therefore, by comparing the observed values with the predicted values based on historical data, Nutanix anomaly detection can identify abnormal behavior and alert you accordingly.

The correct answer is D. Fewer than 30 I/Os and less than 1000 bytes per day of network traffic for the past 21 days.

A zombie VM is a type of inactive VM that is powered on but does very little activity. A zombie VM wastes host resources such as CPU, memory, disk, and network that could be used by other VMs. A zombie VM can be identified by using the VM Profile feature in Prism Central. The VM Profile feature analyzes the resource utilization of each VM and assigns it a profile based on its efficiency and impact on other VMs. The profiles are as follows 1 :

Efficient: The VM is well-provisioned and has optimal resource utilization.

Over-provisioned: The VM has more resources than it needs and has low resource utilization.

Constrained: The VM has less resources than it needs and has high resource utilization.

Inactive: The VM has no resource utilization and is idle or powered off.

Bully: The VM has high resource utilization and causes contention for other VMs.

A zombie VM is a subtype of an inactive VM that meets the following criteria 2 :

The VM is powered on for the past 21 days.

The VM does fewer than 30 read or write I/Os (total) per day for the past 21 days.

The VM receives or transfers fewer than 1000 bytes per day of network traffic for the past 21 days.

To identify a zombie VM, the administrator can use Prism Central to view the VM Profile dashboard and filter by profile type. The dashboard shows the number of VMs in each profile type, as well as their resource consumption and efficiency score. The administrator can also drill down into each VM to see its detailed metrics and recommendations for optimization.

" An administrator has been tasked with increasing security on Nutanix cluster by disabling password authentication when accessing the CVM and AHV hosts and instead moving to key-based SSH, What is the easiest way for the administrator to meet these needs? Enable Cluster Lockdown and provide an RSA key. "

 Cluster Lockdown mode disables password authentication when accessing the CVM and AHV hosts and instead requires key-based SSH. To enable Cluster Lockdown mode, you need to provide an RSA key.

Therefore, by enabling Cluster Lockdown mode and providing an RSA key, you can increase security on Nutanix cluster by disabling password authentication when accessing the CVM and AHV hosts and instead moving to key-based SSH with minimal effort.

https://next.nutanix.com/how-it-works-22/streamlined-login-and-increase-security-key-based-ssh-login-37397

" Playbook allows you to define a trigger that results in the execution of an action or a series of actions. A trigger may be an event that occurs in the system, such as an alert or a request made by you. The resultant actions that you configure can be VM actions, communication actions, alert actions, or report actions. " https://portal.nutanix.com/page/documents/details?targetId=Intelligent-Operations-Guide-vpc_2023_3:ssp-report-management-ssp-pc-c.html#:~:text=The%20environment%20summary%20report%20provides,is%20registered%20to%20Prism%20Central.

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.

when you create a custom alert policy, you can choose between two types of thresholds: Static Threshold and Behavioral Anomaly. Static Threshold allows you to set a fixed value for the metric that triggers the alert. Behavioral Anomaly allows you to use machine learning to detect abnormal behavior based on historical data.

If you select Behavioral Anomaly as the threshold type, you cannot set a warning level for the alert. You can only set a critical level that indicates how much deviation from normal behavior is considered an anomaly 3 . Therefore, the Alert warning if field is greyed out when you select Behavioral Anomaly.

According to the CPU (%) - VMware Docs web search result 2 , one of the possible causes of high CPU ready % is over-provisioning vCPUs for a VM or having too many VMs on a host. CPU ready % indicates the percentage of time that the VM was ready, but could not get scheduled to run on the physical CPU. High CPU ready % can lead to VM performance problems, such as slow response time or application latency. To improve VM performance, the administrator should reduce the number of vCPUs assigned to VMs or reduce the number of VMs on the hosts, so that there is less contention for CPU resources.

The issue described pertains to the inability to ping the IPMI IPs after moving the IPMI network links to the actual switches with specific VLAN configurations. The two changes that the administrator needs to make are:

A. SSH to AHV and set the VLAN ID using IPMI Tool : Since all VLANs are tagged in the new network configuration, the IPMI network interface needs to be aware of the VLAN it’s supposed to communicate on. This can be achieved by setting the VLAN ID using the IPMI Tool on the AHV.

C. SSH to AHV and change the IP address using IPMI tool : If the IPMI IP addresses were initially set in a different subnet that is not routable in the new network configuration, the administrator would need to change the IPMI IP addresses to match the new network configuration. This can be done by SSHing to the AHV and using the IPMI Tool to change the IP address.

One of the NICs needs to be configured on the internal VLAN. This is because the VMs that are isolated need to communicate with the firewall VM through a private network, and the firewall VM needs to communicate with the external network through a public network.  The internal VLAN is a logical network that can be created and managed by AHV 1 . If the firewall VM does not have a NIC on the internal VLAN, it will not be able to route traffic between the isolated VMs and the outside world.