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

According to the Network File System web search result3, NFS (Network File System) is a distributed file system protocol that allows a user on a client computer to access files over a network in a manner similar to how local storage is accessed. NFS is one of the access protocols supported by Files. According to the [MS-WPO]: File Access Services Protocols web search result4, SMB (Server Message Block) is a Windows file sharing protocol that enables applications to discover, access, and share files that are hosted on or made available by a file server, using a network between them, in a secure and managed environment. SMB is another access protocol supported by Files. Therefore, SMB and NFS are two access protocols supported by Files.

According to the Dell Unity: Data Reduction Technical White Paper1, snapshots and clones on Dell Unity use the Copy-on-Write (CoW) algorithm to maximize efficiency and effectiveness. CoW is a technique that defers the copying of data until it is modified. This means that snapshots and clones only consume space when changes are made to the source or the clone, respectively. CoW also preserves the original data in case of a rollback or recovery operation.

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-Prism-v5_10:mul-pc-install-scratch-c.html

 According to the Nutanix Support & Insights web search result4, Prism Central can be installed manually on an AHV cluster by using three disk images: boot, home, and data. These disk images must be downloaded from the portal for the Prism Central VM and uploaded to an image service on the AHV cluster. The boot image contains the operating system and kernel for Prism Central. The home image contains the configuration files and logs for Prism Central. The data image contains the database and application files for Prism Central.

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.

"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

According to the Nutanix Support & Insights, in a two-node ROBO cluster with a witness VM, if one node goes down, the other node sends a leadership request to the witness VM and goes into single-node mode. The cluster remains available and can tolerate another failure of either the witness VM or the network link.

According to the web search results, the two actions that the administrator should perform to determine if the current cluster can accommodate the new VMs are:

• Utilize Optimize Resources for VM efficiency: Optimize Resources is a feature in Prism Central that helps the administrator improve the efficiency and performance of their VMs by identifying and resolving issues such as overprovisioning, inactivity, constraints, or bullying3. By using Optimize Resources, the administrator can reclaim unused resources and optimize the resource allocation for their VMs3.
• Determine utilization with Cluster Runway: Cluster Runway is a feature in Prism Central that helps the administrator estimate how long their cluster can continue to run normally based on the current consumption rate of CPU, memory, and storage resources4. By using Cluster Runway, the administrator can see how adding more VMs will affect the resource utilization and capacity of their cluster4.

According to the Nutanix Support & Insights web search result3, shadow clones are vDisk copies that are created by the cluster when a vDisk is read by multiple VMs. Shadow clones are immutable copies of a vDisk that are stored in different nodes in the cluster, and are used to improve read performance and reduce network traffic. Shadow clones are automatically created and deleted by the cluster, based on the demand and availability of resources.

Deploy the Move appliance and Import the .vmdk into the Image Service. These are two methods that can be used to migrate a VM from VMware ESXi to AHV2. The Move appliance is a tool that automates the migration process by converting the VM disks and configuration to AHV format and transferring them to the Nutanix cluster3. The Image Service is a feature that allows users to upload and manage disk images that can be used to create or clone VMs on AHV4. By importing the .vmdk file of the VMware VM into the Image Service, users can create a new AHV VM from that image.

According to the web search results, the policy that should be used to meet this requirement is an Isolation Environment Policy. An Isolation Environment Policy is a type of security policy that can be created in Prism Central using Flow Network Security, which is a feature that provides microsegmentation and network security for Nutanix environments1. An Isolation Environment Policy allows the administrator to isolate a group of VMs from another group of VMs based on their categories, and block all traffic between them regardless of direction2. This policy can be useful for creating isolated environments for testing, development, or compliance purposes2.

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

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

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.

Prism Element is a graphical user interface that allows you to manage Nutanix clusters1. You can use Prism Element charts to understand Nutanix cluster workloads and troubleshoot performance related issues2.

memory optimized virtual machine sizes offer the best performance for SQL Server workloads on Azure VMs. Adding more RAM to the user VM can help reduce paging and improve query execution times.

SQL Server performance can be affected by disk latency and throughput. By creating separate virtual disks for data and logs, you can spread activity across multiple spindles and reduce disk contention.

https://next.nutanix.com/how-it-works-22/differences-between-prism-element-prism-central-and-prism-pro-37137

Flow Networking is a feature that enables software-defined networking for AHV clusters. It allows users to create and manage virtual private clouds (VPCs), subnets, and network services such as NAT, DHCP, routing, and VPN. Flow Networking also supports service insertion and chaining, which enables integration with third-party network functions such as firewalls and load balancers. Flow Networking is built on top of the microservices infrastructure (MSP) in Prism Central, which provides the platform for running various Nutanix services such as Calm, Karbon, and Objects. Therefore, to enable Flow Networking, the MSP must be enabled first on Prism Central1. The MSP can be enabled from the Prism Central settings page or from the command line interface (CLI) of the Prism Central VM2. Enabling the MSP will also enable Flow Microsegmentation, which is another feature that provides network security and visibility for AHV clusters.

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.

https://portal.nutanix.com/page/documents/details/?targetId=Web-Console-Guide-Prism-v51:wc-block-services-c.html

According to the web search results, a consistency group is a group of related applications or services that must be recovered together in order to work properly, and this means more than being recovered at the same time67. They also typically need to be recovered to the same point in time6. Therefore, to meet the requirement of protecting all VMs of a multi-tier application at the same time, the administrator must create a consistency group for the application and place all VMs in it8. This way, the administrator can apply data protection policies and schedules to the entire consistency group as a single unit8.

According to the web search results, three storage optimizations that should be set on a dedicated storage container for a VDI solution with persistent desktops are compression, deduplication and erasure coding. Compression is a technique that reduces the size of data by removing redundant information. Deduplication is a technique that eliminates duplicate copies of data blocks and stores only unique blocks. Erasure coding is a technique that increases usable capacity by reducing the replication factor of data blocks and using parity information instead7. These three optimizations can improve performance and save storage space for VDI workloads, especially during a node failure event when data needs to be rebuilt from parity information8. The administrator can enable these optimizations by using Prism Element web console or ncli command-line interface9.

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.

Enable Memory Overcommit on the over-provisioned VMs is the most efficient resolution to enable additional VMs to be created. Memory overcommit allows VMs to use more memory than physically available on a host by compressing and swapping memory pages to storage1. This can improve memory utilization and increase VM density on a cluster1. However, memory overcommit is not supported when HA is configured to use reserved hosts, so you may need to disable HA reservation on the cluster before enabling memory overcommit1.

NGT is a software package that enables advanced VM management features provided by Nutanix, such as file-level restore, VM mobility, and application-consistent snapshots12. To use NGT, you need to enable the NGT feature for a VM in the Prism Element web console, mount the NGT installer (ISO disk file) in the VM, and install NGT in the VM1. However, before installing NGT, you need to ensure that the VM can communicate with the NGT-Controller VM service, which runs on the Controller VM (CVM) of each Nutanix node3. The NGT-Controller VM service listens on port 9943 for incoming requests from the guest VMs3. Therefore, you need to enable port 9943 on the ESXi-hosted VM to allow communication with the NGT-Controller VM service.

The best method to provide access for a user to view real-time performance metrics for all VMs on all clusters across the datacenter is to configure AD authentication create a custom role, assign the user to the role, and apply the role to all clusters and VMs. This method accomplishes this with the least effort and ongoing maintenance because:

• AD authentication allows Nutanix Prism Central to integrate with an existing Active Directory (AD) domain and use AD users and groups for authentication and authorization5. This simplifies user management and avoids creating local users on Prism Central.
• Creating a custom role allows Nutanix Prism Central to define granular permissions for different actions and entities based on specific needs6. This ensures that users only have access to what they need and nothing more.
• Assigning the user to the custom role allows Nutanix Prism Central to grant access rights for that user based on the role definition7. This avoids assigning permissions individually for each user.
• Applying the role to all clusters and VMs allows Nutanix Prism Central to propagate the access rights for that role across all entities in scope8. This ensures that users can view real-time performance metrics for all VMs on all clusters without having to configure each entity separately.

References: 1: Health Dashboard - Prism Element Guide 2: Understanding Native VLANs - Cisco 3: VMs may lose network connectivity if connected to virtual network with … - Nutanix Support & Insights 4: VLAN Configuration - AHV Networking Guide 5: Active Directory Authentication - Prism Central Guide 6: Create Custom Roles - Prism Central Guide 7: Assign Roles - Prism Central Guide 8: Apply Roles - Prism Central Guide

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

According to the Nutanix Support & Insights website1, 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 clusters23.

A Nutanix cluster requires a minimum of three nodes to maintain quorum and data availability. Removing a node from a 3-node cluster would violate the redundancy factor and cause data loss. Therefore, it is not possible to remove a host from a 3-node cluster using Prism or CLI. The only way to replace a node in a 3-node cluster is to use the Foundation tool, which will erase the existing cluster configuration and create a new cluster with the new node1.

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

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

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

A. This statement is incorrect because there is no static threshold set to trigger a critical alert at 6000 MB. The graph shows a peak that goes above 6000 MB, but the alert configuration below does not specify a static threshold at this value.

B. This is the correct statement. The configuration under "Behavioral Anomaly" is set to alert every time there is an anomaly, with a critical level alert set to trigger when the I/O working set size is between 0 MB and 4000 MB. The graph illustrates that the anomalies (highlighted in pink) occur when the working set size exceeds the normal range (blue band). Therefore, any anomaly detected above 4000 MB would trigger a critical alert.

C. This statement is incorrect because there is no indication that a warning alert is configured to trigger after 3 anomalies. The exhibit does not show any configuration that specifies an alert based on the number of anomalies.

D. This statement is incorrect as there's no indication that a warning alert will be triggered based on the I/O working set size exceeding the blue band. The alert settings are configured to ignore anomalies below 4000 MB and to trigger a critical alert for anomalies above this threshold.

The settings displayed in the exhibit are typically part of Nutanix's Prism infrastructure management platform, which can set various thresholds for performance metrics and trigger alerts based on those thresholds. The behavior is defined in the Prism documentation where the alert configuration is outlined.

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.

When a VM is connected to a Nutanix managed network, the IP address is assigned when the VM is powered on. A Nutanix managed network is a network that is created and managed by Prism Central using IP address management (IPAM). IPAM allows Prism Central to automatically assign IP addresses to VMs from a pool of available addresses in a subnet. IPAM also tracks the IP address usage and availability across clusters and networks4.

When a VM is connected to a Nutanix managed network, the administrator can choose one of the following assignment types for the IP address:

• Assign Static IP: This option allows the administrator to manually specify a static IP address for the VM from the subnet range. The IP address will not change unless the administrator changes it.
• Assign with DHCP: This option allows Prism Central to dynamically assign an IP address for the VM from the subnet range using DHCP. The IP address may change depending on the DHCP lease time and availability.
• No Private IP: This option allows the administrator to skip assigning an IP address for the VM. This option is useful for scenarios where the administrator wants to use an external IPAM solution or assign an IP address later5.

Regardless of the assignment type, the IP address is assigned when the VM is powered on. This is because Prism Central needs to communicate with the hypervisor (AHV or ESXi) to configure the virtual NIC (vNIC) of the VM with the IP address information. This communication can only happen when the VM is in a powered on state6.

References: 4: IP Address Management - Prism Central Guide 5: Creating a New Report - Prism Central Guide 6: IP Address Assignment - AHV Networking Guide

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 Kbps1. To provide adequate host resources, resize (increase) the constrained VMs1.