Nutanix Nutanix Certified Professional - End User Computing (NCP-EUC) 6.10 Exam NCP-EUC Exam Dumps: Updated Questions & Answers (January 2026)

https://next.nutanix.com/community-blog-154/new-x-play-actions-in-prism-central-2021-7-40005

The Prism Central Playbook Action is a tool that allows you to automate tasks based on triggers, such as events, alerts, or webhooks. You can define a series of actions (called a playbook) that perform operations on your infrastructure, such as adding or reducing resources on a VM2.

To use the Playbook Action for VMs, you need to meet some prerequisites, such as:

The Prism Central version must be 2020.11 or later.

The AOS version must be 5.15 LTSR or later.

The hypervisor must be AHV or ESXi.

The VMs must have Nutanix Guest Tools (NGT) installed and enabled3.

One of the possible reasons why the Playbook Action is no longer being triggered is that the virtual desktop CPU Usage alerts were not cleared. According to the Prism Central guide3, “If an alert has been triggered once and has not been cleared yet, then it will not trigger any action again until it has been cleared”. Therefore, if the CPU Usage alert remains active for a virtual desktop, it will prevent the Playbook Action from adding more vCPUs to it.

Frame is a cloud-native desktop-as-a-service platform that delivers virtual apps and desktops from multiple public clouds1. Frame allows administrators to manage various components of their cloud accounts easily from the Frame console1.

A cloud account is a logical grouping of resources that are associated with a specific cloud provider (such as AWS, Azure, or Google) and region1. A cloud account can have multiple virtual networks, master images, and instance types that can be used to create and run virtual apps and desktops1.

To configure AWS, Azure, and Google accounts within Frame, an administrator needs to go to the Cloud Accounts section of the Frame console1. There, the administrator can add new cloud accounts or edit existing ones by providing the required credentials and settings for each cloud provider12.

https://docs.frame.nutanix.com/platform/infrastructure/byo/cloud-accounts/

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

According to Citrix Virtual Apps and Desktops architecture documentation utilized in Nutanix EUC designs:

VDA Functionality: The Virtual Delivery Agent (VDA) is the essential software component that must be installed on every machine (virtual or physical) that delivers applications or desktops.

FMA Role: The VDA registers with the Delivery Controller (Broker) and manages the FMA (FlexCast Management Architecture) connection between the machine and the user device. It establishes and manages the HDX connection, allowing the Citrix Workspace app (on the client side) to connect directly to the desktop session.

Distinction:

Citrix Workspace app is installed on the client device (endpoint), not the virtual desktop.

VirtIO drivers are lower-level drivers for disk/network I/O virtualization on AHV, not FMA connection brokers.

NGT provides Nutanix-specific fabric features (SSR, FLR), not Citrix session connectivity.

Nutanix offers a solution that delivers virtual apps and desktops in one click. Nutanix supports both persistent and non-persistent VDI deployments, as well as RDSH-based VMs and AppStacks.

Storage containers are logical units that group vDisks and apply storage policies such as replication factor, encryption, compression, deduplication and erasure coding3. Nutanix recommends using compression and deduplication to reduce storage usage and avoid duplicate data4.

In a Nutanix AHV environment integrated with Citrix Provisioning (PVS), the XenDesktop Setup Wizard (or Citrix Virtual Desktops Setup Wizard) is responsible for creating the Write Cache disk for target VMs during the provisioning process.

According to Nutanix Knowledge Base articles regarding PVS on AHV, a common cause for the failure of the write-cache disk creation is the presence of an attached virtual disk on the snapshot used as the template. The wizard expects to create and attach the write-cache disk itself. If the template snapshot already has a hard disk attached (other than the potential CD-ROM, which is generally supported if single), the wizard's logic for disk slot assignment or disk creation conflicts with the existing disk, causing the "creation of the VM's write-cache disk failed" error. The supported procedure explicitly states that the VM template snapshot must be created without any hard disks attached.

The optimal storage configuration aligns the container settings with the specific I/O patterns of the workload types:

Non-Persistent Desktops: These are typically linked clones (MCS/Instant Clones) with high write churn and little data commonality in the delta disks. Compression Only is best. Deduplication adds overhead with no benefit.

Persistent Full Clones: These are full copies of the OS. Because there are hundreds of copies of the same OS files, Deduplication (Capacity or Performance tier) is highly effective at saving space. Compression is always recommended.

Therefore, creating two separate containers—one configured with Compression Only (for the non-persistent pools) and one with Compression and Deduplication (for the persistent full clone pools)—provides the best balance of performance and capacity efficiency (Option D).

Writable AppVolumes are a feature of VMware App Volumes that provides users with a dedicated virtual disk for storing user profile data and user-installed applications1. Writable AppVolumes are stored as VMDK files on a datastore2.

To protect Writable AppVolumes during a disaster in a Nutanix environment, one possible solution is to use asynchronous DR between two sites. Asynchronous DR allows you to replicate VMs and their associated data from one site to another at regular intervals using protection domains and remote sites3.

https://www.nutanix.com/blog/vmware-app-volumes-on-nutanix

The performance statistics indicate that the SSD Cache tier is 85% full, which is the primary bottleneck. In a Nutanix cluster, the SSD tier serves as the high-performance "Hot Tier" (Extent Store and Oplog) for active data. When the SSD tier utilization exceeds recommended thresholds (typically above 75-80%), the system must aggressively destage data to the slower HDD Capacity tier to free up space for incoming writes.

This destaging process and the lack of available SSD space for the active working set (WS) force read and write operations to be served from the slower Capacity tier (HDD), resulting in significantly higher latency and "sluggish" desktop performance. The vCPU ratio (4:1) and Host CPU (< 40%) are well within healthy limits, ruling out CPU contention.

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.

regarding replicating AppStacks between Nutanix clusters, it is likely that the correct answer would involve configuring some form of replication or disaster recovery technology on the Nutanix clusters themselves.

https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2135-VMware-App-Volumes:BP-2135-VMware-App-Volumes