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

Virtual NIC receive packet dropped is the most useful VM metric for isolating the cause of users being disconnected from remote desktop sessions to a specific VM. This metric shows the number of packets that are dropped by the virtual NIC of the VM due to insufficient buffer space or other reasons. Packet drops can indicate network congestion, misconfiguration, or performance issues that can affect the quality and availability of remote desktop sessions. Packet drops can also cause retransmissions, delays, and errors in TCP-based protocols such as RDP2. To view this metric in Prism, go to Entities > Compute & Storage > VMs > Summary View and select a VM. Then, in the Details View, go to Metrics > Performance and select Virtual NIC receive packet dropped from the drop-down menu3.

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

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 section 4 of the exam blueprint guide1, 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, one of the best practices for Nutanix AHV networking is to create a second bridge on each host and assign the 1GbE interfaces to it3. This way, the customer can use both 10GbE and 1GbE interfaces for VM traffic, and also benefit from network isolation and redundancy. 

Categories are key-value pairs that can be used to tag entities such as VMs, images, networks, and projects in Prism Central. Categories can be used to create dynamic groups of entities based on their attributes, and assign roles and permissions to those groups3. In this case, a category such as OS=Linux can be used to group all Linux VMs and grant access rights to the Linux administration team.

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

data size for flash mode exceeds 25% of the SSD capacity could cause the performance issues. Flash mode is a feature that allows vDisks to be pinned to SSDs for faster access, but it has a limit of 25% of the SSD capacity per node. If this limit is exceeded, some vDisks may be evicted from flash mode and cause disk latency2.

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]

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.

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.

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.

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

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

A Compute Only node is a node that does not have any local storage devices and only provides compute resources to the cluster2. A Compute Only node does not run a CVM, but instead relies on the CVMs of other nodes to access the distributed storage fabric2

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

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

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

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

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.

According to the Nutanix Prism Central Guide, to configure a syslog server in Prism Central, you need to specify the transport protocol (TCP or UDP) and the IP address/port of the syslog server.

Prism Element and NCC are two ways to run all NCC checks manually on a Nutanix cluster. Prism Element is the web console that provides management and monitoring capabilities for a single Nutanix cluster. Prism Element has a Health dashboard that shows the status of various components and services in the cluster, such as disks, nodes, CVMs, NCC, and alerts. The Health dashboard also allows the administrator to run NCC checks manually by using the Actions drop-down menu on the right side of the screen. The administrator can choose to run all NCC checks or specific checks based on the category or severity. The NCC checks will run in the background and generate a report that can be viewed or downloaded from the Summary tab. This method is easier and faster than running NCC from the command line on the CVM.

NCC stands for Nutanix Cluster Check, which is a framework of scripts that performs system checks and validations on Nutanix clusters. NCC can detect issues related to hardware, software, configuration, hypervisor, networking, and more. NCC can be run from the command line interface (CLI) of any CVM in the cluster by using the ncc command. To run all NCC checks manually, the administrator can use the command ncc health_checks run_all, which will execute all available checks and display the results on the screen. This method is more comprehensive and detailed than running NCC from Prism Element.

References: : [Health Dashboard - Prism Element Guide] : [Nutanix Cluster Check (NCC) - Nutanix Support & Insights] : [Running NCC Checks - Nutanix Support & Insights]

The correct answer is B. The existing and the expansion node are on different VLANs.

The output shows that the new node has a br0-up bond with four interfaces: eth0, eth1, eth2, and eth3. The bond is configured with LACP active and LACP fallback set to false. This means that the bond will only work if the upstream switch supports LACP and is configured to form an LACP group with the four interfaces. However, the output also shows that the bond has no IP address assigned to it, which indicates that the bond is not operational. One possible reason for this is that the existing and the expansion node are on different VLANs, and the upstream switch is not configured to allow the VLAN traffic on the LACP group. This would prevent the new node from communicating with the cluster and being discovered by the Expand Cluster function in Prism.

To verify this, the administrator can check the VLAN configuration on the upstream switch and compare it with the existing nodes. Alternatively, the administrator can use the “manage_ovs show_uplinks” command on an existing node and compare the output with the new node. If there is a VLAN mismatch, the administrator can either change the VLAN configuration on the switch or on the new node to match the existing nodes.

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 performance1. 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 OS2:

• 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

Nutanix provides two types of granular RBAC for AHV hosts: category based and cluster based3. 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 department4.

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

The best way for the administrator to limit the amount of storage space that data stored in a single container can consume is to set an advertised capacity for the container. This will ensure that the data stored in the container doesn't exceed the set limit, and it will also help prevent any potential performance issues due to resource contention. Additionally, the administrator should consider thick provisioning the container, which will pre-allocate the amount of storage space that can be used by the container. This will help ensure that the data stored in the container doesn't exceed the advertised capacity.

A GPU (graphics processing unit) is a specialized hardware device that can accelerate graphics rendering and computation for applications that use APIs such as DirectX, OpenGL, CUDA, and OpenCL. A GPU can also offload the CPU from encoding and decoding tasks for remote display protocols such as Frame Remote Desktop Protocol (FRP). A VM can use a GPU either by directly accessing a physical GPU (pGPU) on the host or by using a virtual GPU (vGPU) that shares a pGPU with other VMs. A user running a computer aided design (CAD) application may benefit from using a GPU or a vGPU to improve the performance and responsiveness of the application, especially when moving windows or rendering images. However, if the GPU or vGPU is not properly configured or provisioned, the user may experience slow response time within the VM. Therefore, to diagnose the problem, the administrator should monitor the GPU Usage metric for the VM. The GPU Usage metric shows the percentage of GPU resources that are consumed by the VM over time3. The administrator can use Prism Central to view the GPU Usage metric for each VM in a chart or a widget4. The administrator can also use Prism Central to view other metrics related to GPU performance, such as GPU Memory Usage, GPU Encoder Usage, and GPU Decoder Usage3. By analyzing these metrics, the administrator can determine if the VM is using the GPU efficiently and optimally, or if it needs more or less GPU resources.

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 use1. API Explorer is a tool that allows users to explore and test Nutanix REST APIs within Prism Element1.

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

To periodically send information about cluster efficiency via email to a set of users, the administrator can follow these steps:

• Create a report in Prism Central that contains the relevant information about cluster efficiency.
• Add a schedule to the report to generate and send the report via email to the set of users at a specified frequency.

This will ensure that the users receive regular updates about the cluster efficiency without the need for manual intervention.

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.

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

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

network segmentation on Nutanix clusters refers to creating a separate network for service-specific communication and isolating different types of traffic over selected VLANs or physical interfaces.

https://next.nutanix.com/ncm-intelligent-operations-formerly-prism-pro-ultimate-26/network-segmentation-isolating-service-specific-traffic-39463

https://next.nutanix.com/how-it-works-22/network-segmentation-basics-38414

 When a node with Erasure Coding fails, the cluster will automatically rebuild the missing data using replication factor (RF) 2 or 3, depending on the cluster configuration. This means that the data that was previously stored using Erasure Coding will now be stored using full copies, which may increase the amount of data stored in the SSD tier1.

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

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.

Answer: A. VM-VM anti-Affinity policy

A VM-VM anti-Affinity policy is a rule that ensures that two or more VMs don’t run on the same AHV host. It’s useful when an application provides HA and an AHV host can’t be an application’s single point of failure1. In this case, the SQL cluster VMs should have a VM-VM anti-Affinity policy configured to prevent them from running on the same host and causing an outage if that host fails. A VM-VM anti-Affinity policy can be created using the aCLI commands2. The other options are not relevant for this scenario.

References: 1: Affinity Policies - Nutanix Support & Insights 2: Affinity Policies Help | Nutanix Community

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.

Prism Central is a multi-cluster manager that provides a single, centralized management interface for Nutanix environments1. 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 device2. NAT can be used to enable communication between Prism Central and Prism Elements that are in different networks or subnets3. For example, Prism Central can be deployed in a public cloud and use NAT to access Prism Elements that are in a private data center3.
• 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 network4. Prism Elements and Prism Central can be in different subnets as long as they can communicate with each other through routing or NAT3. For example, Prism Central can be deployed in a management subnet and access Prism Elements that are in different application subnets3.
• 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.

The correct answer is A. Long term storage of data which is written once and read infrequently.

Erasure Coding is a feature that increases the usable capacity on a Nutanix cluster by reducing the amount of data replication. Instead of replicating data, Erasure Coding uses parity information to rebuild data in the event of a disk failure. The capacity savings of Erasure Coding is in addition to deduplication and compression savings1.

Erasure Coding is most beneficial for scenarios where the data is written once and read infrequently, such as long term storage of archival data, backup data, or cold data. This is because Erasure Coding has some trade-offs and limitations that may affect the performance and availability of the cluster. Some of these trade-offs and limitations are2:

• Erasure Coding requires more CPU and memory resources than replication, as it involves more complex calculations for encoding and decoding data.
• Erasure Coding increases the network bandwidth consumption, as it involves more data transfers between nodes for encoding and decoding data.
• Erasure Coding reduces the resiliency of the cluster, as it can tolerate fewer node failures than replication. For example, a cluster with redundancy factor 2 can tolerate one node failure with replication, but only two disk failures with Erasure Coding.
• Erasure Coding is not effective for workloads that have many overwrites or random writes, as it involves more overhead for updating the parity information.
• Erasure Coding is not supported for some features, such as volume groups, file server VMs, or Metro Availability.

Therefore, if an administrator needs to configure a container on a Nutanix cluster, they should enable Erasure Coding only if the container will store data that is written once and read infrequently. This way, they can maximize the capacity savings of Erasure Coding without compromising the performance and availability of the cluster.

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 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 follows1:

• 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 criteria2:

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

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 best way for the administrator to configure Prism to send encrypted messages to a set of recipients is to set the SMTP Security Mode to STARTTLS. This will ensure that all messages sent over SMTP are encrypted and secure. Additionally, the administrator should consider installing SSL certificates on Prism Central to ensure that the messages are being sent securely. Finally, the administrator should consider configuring Prism Central to use Cluster Lockdown, which will help ensure that the messages are only sent to the intended recipients.

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.

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 interface1.
• 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 consume2. The Nutanix Files clusters can be stopped by using the Prism Element web console or the ncli command-line interface3.