The performance issue is caused by Host CPU overcommitment , specifically regarding CPU scheduling (Ready Time) rather than total utilization.

While the Host CPU utilization is below 80% (meaning the processor has idle cycles), the configuration of 8 vCPUs per VM combined with a high 9:1 vCPU-to-pCPU ratio creates a bottleneck known as " Co-stop " or high " CPU Ready " time. The hypervisor scheduler must wait until 8 physical cores are available simultaneously to execute a single clock cycle for one VM. In a dense VDI environment, finding 8 free cores at the exact same moment is difficult, causing the VMs to pause (freeze) while waiting for the scheduler, even if the overall CPU usage of the host appears moderate. Reducing the vCPU count per VM would likely resolve the performance issues.

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:

According to Nutanix EUC Troubleshooting Guides :

Tool Capabilities: RDAnalyzer (Remote Display Analyzer) is the specific tool recommended to view real-time statistics regarding the Display Protocol (Blast/ICA/PCoIP), Frames Per Second (FPS) , Bandwidth , Network Latency , and GPU Utilization in a single overlay window.

Why not GPUView? NVIDIA GPUView (Option D) is a deep-dive performance trace tool used for analyzing complex rendering pipelines and driver lag (DPCs/ISRs). It does not provide a live dashboard of " Network Latency " or " Bandwidth " for the display protocol, nor is it used for quick " real-time " monitoring by administrators in the same way RDAnalyzer is.

Note on Exam Key: While some older exam dumps might incorrectly flag D, RDAnalyzer is the only tool in the list that provides the protocol-specific network metrics (bandwidth/latency) requested in the scenario.

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:

According to Citrix on Nutanix Best Practices for Profile Management:

Legacy Roaming Profiles: A " Legacy Roaming Profile " (Windows Roaming User Profiles) functions by downloading the entire profile (files, folders, AppData, etc.) from the network share to the local VM at logon, and uploading changes back at logoff.

Impact on Performance: If a user has a large existing profile (common in legacy migrations), this copy process creates massive network and disk I/O activity during the logon/logoff phase, resulting in extended wait times (the " Applying User Settings " or " Waiting for User Profile Service " screens).

Contrast with Modern Solutions: Modern VDI solutions use Profile Containers (like FSLogix or Citrix Profile Management containers) which mount the profile as a virtual disk (VHDX) almost instantly, rather than copying files.

Why not Home Folder (C)? A home folder is typically a mapped network drive . It does not copy data to the desktop at logon; it simply maps a pointer. Therefore, having " too much data " in a mapped drive does not slow down the logon process itself.

For non-persistent VDI environments where speed and personalization are required, Container-based profiles (such as FSLogix Profile Containers or Citrix Profile Management containers) are the industry standard and Nutanix recommended solution.

Unlike Roaming Profiles (Option D), which must copy thousands of files over the network at login (causing slow logins and " bloat " ), Container-based profiles encapsulate the entire user profile into a single virtual disk (VHD/VHDX). This disk is mounted instantly over the network when the user logs in. This provides the user with their personalized settings immediately—mimicking a local profile—without the performance penalty of file copying, ensuring the fast and consistent sign-in experience requested by management.

A Mandatory Profile is a read-only user profile (.man) that is pre-configured by an administrator.9 When a user logs in, the system copies this profile to create the session environment.

Crucially, any changes the user makes during the session (such as wallpaper, icons, or settings) are discarded when the user logs off. This ensures that every time the user logs in, they receive the exact same standard user configuration ( " at the beginning of each session " ), preventing configuration drift. Roaming and Container profiles are designed to retain user settings, which contradicts the requirement for a standardized start state.

Nutanix Files is a software-defined, scale-out file storage solution that provides a repository for unstructured data, such as home directories, user profiles, departmental shares, application logs, backups, and archives 1 .  Nutanix Files also provides high availability and a unified single namespace for easy management 2 .

In a Nutanix AHV cluster, resource management and Admission Control ensure that VMs are only powered on if there are sufficient physical resources (specifically Memory) available to back them.

A cluster designed to run an " average " of 800 VMs likely has its physical memory sized to accommodate that workload plus some buffer (HA). Attempting to power on 1400 VMs simultaneously (almost double the average load) on the same 6-node cluster will likely exhaust the available physical RAM. Once the cluster memory capacity is full, AHV will refuse to power on additional VMs, resulting in the state observed in Citrix Studio where many VMs remain off. Citrix network issues (Directory/Storefront) would typically result in registration failures or connection errors, not the inability of the hypervisor to power on the VM.

  Frame utility server  is a stand-alone, general purpose Windows server that can be helpful for a variety of use cases, including:

License server: Install a network licensing manager for your software on a Frame utility server. Your production instances can then connect to this server to get the licenses.

Backend for a client-server application: Install a database or other backend service on a Frame utility server. Your production instances can then connect to this server to run your client-server application.

Shared file server: Install a file sharing service on a Frame utility server. Your production instances can then access shared files from this server.

Test and develop virtual desktops: Use a Frame utility server as a sandbox environment to test and develop your virtual desktops before publishing them to your production account.

https://docs.frame.nutanix.com/platform/admin/utility-servers/

The default load balancing configuration in Nutanix AHV is Balance-SLB (Source Load Balancing). This setting utilizes all available uplinks by assigning VM traffic to specific uplinks based on source MAC address hashing. To optimize bandwidth usage, the Balance-SLB algorithm periodically evaluates link utilization and may rebalance traffic by moving a VM ' s assignment from one uplink to another.

According to Nutanix AHV Networking documentation, this rebalancing action involves sending a gratuitous ARP (RARP) to update the physical switch. During this split-second transition, real-time sensitive traffic—such as streaming video or VoIP—may experience dropped packets or out-of-order delivery, resulting in symptoms like " hung/frozen display frames. " For environments prioritizing connection consistency over aggregate bandwidth for single VMs (like VDI with streaming requirements), Active-Backup is often recommended to eliminate the potential for rebalancing interruptions. (Note: Option A is a VMware ESXi terminology, not AHV).

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:

According to Citrix App Layering on Nutanix reference architectures:

Minimizing Storage: Citrix App Layering allows an administrator to capture applications in separate virtual disks ( " App Layers " ) that are stored once and then dynamically merged with a base OS layer to create layered images. 2 This avoids the storage bloat of installing every application into a single " Gold Image " or creating dozens of unique images for every department.

ELM Role: The Enterprise Layer Manager (ELM) is the virtual appliance required to manage this layering environment. 3 It orchestrates the creation of layers and the publishing of images.

Targeting User Groups: By using Elastic Layering (a feature of App Layering), specific app layers can be delivered to users based on their Active Directory group membership at login, fulfilling the requirement to deploy " different applications to different user groups " without installing them permanently in the base image.