According to section 5 of the exam blueprint guide1, one of the topics covered is live migration. Live migration is the process of moving a running VM from one host to another without any downtime or interruption of service. To perform live migration, there are some prerequisites that must be met, such as:
* All AHV hosts have IP addresses in the same subnet
* All VMs are configured for the same VLAN
* The source and destination hosts have enough resources to accommodate the VM
* The VM does not have any PCI devices attached

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.

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

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.

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.