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

According to the Prism Central User Guide (Analysis and Planning):

Analysis Sessions: Prism Central includes a feature called " Analysis " (or Performance Analysis). It allows administrators to create " Sessions " which are essentially saved workspaces.

Workflow: An administrator can select a specific metric (like Storage Controller IOPS), click " Add to Analysis, " and save it to a new or existing session. This allows them to " quickly review... at a later date " by simply opening the saved Analysis Session, which retrieves the data dynamically, rather than relying on static exports or reports.

For Virtual Machine operations involving vGPUs (NVIDIA GRID) on Nutanix AHV, it is a strict requirement that all GPU nodes must run the same version of the host driver .

To support VM mobility, live migration, and High Availability (HA) within the cluster, the source and destination hosts must have compatible GPU profiles and identical driver versions. If drivers are mismatched between nodes, the GPU state cannot be successfully transferred or re-initialized, preventing migration and potentially causing VM power-on failures. While a cluster can contain a subset of nodes with GPUs (heterogeneous cluster), the nodes that do have GPUs must be uniform in their driver configuration.

non-persistent VDI machines are deleted when they are rebooted, logged off, or shut down.  Therefore, Windows Update policy should be configured to prevent automatic updates that may trigger a restart on these machines 1 .

https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/onboarding-and-servicing-non-persistent-vdi-machines-with/ba-p/1360721

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

According to Nutanix AHV Administration Guide regarding GPU Pass-Through :

Hardware Binding: GPU Pass-Through (DirectPath I/O) binds a virtual machine to a specific physical PCIe device on the host. Unlike vGPU (which abstracts the hardware), passthrough creates a 1:1 dependency.

HA Behavior: Nutanix AHV supports High Availability (HA) for GPU-enabled VMs in the sense that if a host fails, the system attempts to restart the VM on another host (Cold Migration). Option C ( " Not HA-capable " ) is incorrect because the system attempts the restart; it does not simply abandon the VM by design.

Failure Cause: The restart fails (the " behavior " described) because the destination host must have the exact same GPU hardware resource available (free and matching the profile/addressing). If the other nodes in the cluster do not have a free GPU of the same type, or if they are already fully utilized, the VM cannot power on, resulting in the " Insufficient GPU resources " error.

Nutanix Files VDI Sync is a feature originally designed for active-active use cases where users might access data from either site, requiring bidirectional metadata scanning and locking. This process is resource-intensive.

For a Disaster Recovery (DR) purpose where the secondary site is passive (users only access it if the primary fails), full active-active bidirectional synchronization is unnecessary and wasteful. To reduce the high CPU and RAM utilization caused by the constant metadata comparison between sites, the administrator should configure one-way synchronization (or leverage standard Async DR protection). This ensures data replicates to the DR site without the overhead of checking the DR site for changes to replicate back to the source.

Nutanix Files Smart DR allows administrators to configure replication policies between file servers managed by different Prism Central (PC) instances (Multi-PC).4

According to the Nutanix Files Guide and Disaster Recovery documentation, a strict prerequisite for this configuration is that both Prism Central clusters must be in an availability zone (AZ) pair . 5 This pairing establishes the trust and replication channel required for the Files Manager to coordinate the disaster recovery policies between the source and target file servers across the different PC domains.

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

According to Nutanix AHV Best Practices for Virtual Desktop Infrastructure (VDI):

Power Management: The most critical " optimal " configuration for latency-sensitive EUC workloads is to ensure the host power management policy is set to High Performance . This prevents the CPU from entering power-saving states (C-states/P-states) which can introduce latency during user interaction.

Memory Configuration: While Nutanix AHV typically disables memory overcommit by default (or does not use it in the same way as other hypervisors for VDI), the active configuration step required by an administrator to guarantee optimal performance is the Power Management setting. Memory reservation should generally be 100% (not 50%) to avoid swapping, and CPU/Memory shares are usually left at default unless there is specific contention, but Power Management is the baseline requirement for EUC optimization.

Why not D? While memory overcommit should be disabled for VDI, in many AHV versions this is the default behavior or inherent architecture. " High performance power management " represents the specific tuning parameter that administrators must validate or configure (often in the BIOS or via AHV command) to ensure the environment is " optimized " for desktop workloads.

Prism Central Image Service allows you to upload and manage images through Prism Central by using the v3 API.  You can also choose where your images will be available across different clusters 1 2 3

https://next.nutanix.com/ncm-intelligent-operations-formerly-prism-pro-ultimate-26/prism-central-adding-images-to-prism-central-33759

In the Citrix Studio workflow, before a Machine Catalog can be created for a specific infrastructure, a Hosting Connection (or Host Connection) must be established. This connection links the Citrix control plane to the specific hypervisor (Nutanix AHV) and defines the resources (such as storage containers and networks) available for provisioning.

If the administrator is setting up a " new cluster " and attempts to create a catalog but finds that " no resources were found, " it indicates that either no Hosting Connection exists for that new cluster, or the existing connection does not include the storage/network resources of the new cluster. Therefore, the immediate resolution is to create a new hosting connection in Citrix Studio that points to the new AHV cluster, ensuring the appropriate networks and containers are selected as available resources.

According to Citrix DaaS (formerly Citrix Virtual Apps and Desktops Service) architecture on Nutanix, a Resource Location is defined by the presence of Cloud Connectors.2 These connectors serve as the communication proxy between the Nutanix AHV infrastructure and the Citrix Cloud control plane.

For Disaster Recovery (DR) planning, the DR site functions as a distinct Resource Location. To ensure the DR site is available and manageable by the Citrix Cloud service during an event, an administrator must deploy at least one Cloud Connector in every resource location (though two are recommended for high availability). Keeping connectors offline (Option A) is unsupported because they require continuous connectivity to receive automatic updates; if they are offline for too long (tombstone life), they become invalid. Recovering connectors during an event (Option D) increases RTO unnecessarily. Therefore, establishing the DR site as a valid resource location with active Cloud Connectors is the correct planning step.