Deduplication is a process that eliminates duplicate data blocks and reduces the amount of storage space required for virtual desktops. Deduplication can be enabled at both cluster level and container level on Nutanix.

Deduplication can also work with VCAI (View Composer Array Integration), which is a feature that uses Nutanix native NFS snapshot technology to clone VMs 2 . VCAI can improve performance and reduce storage consumption for linked-clone desktop pools.

Another feature that can help with capacity issue is Shadow Clones, which is a distributed caching mechanism that allows multiple VMs to read from a single vDisk copy stored locally on each node 3 . Shadow Clones can reduce network traffic and improve boot times for virtual desktops.

https://www.nutanix.com/support-services/training-certification/certifications/certification-details-nutanix-certified-professional-ncp-euc-v6

non-persistent VDI  is a type of virtual desktop infrastructure (VDI) that does not save any changes made by the user on the virtual machine (VM) across sessions. Non-persistent VDI uses a master image to create and delete VMs as needed.

Therefore, if the administrator needs to manage a non-persistent deployment, they should avoid any requirements that involve modifying or installing applications on the VMs, as those changes would not be saved.

https://www.nutanix.com/support-services/training-certification/certifications/certification-details-nutanix-certified-professional-ncp-euc-v6

To achieve the requirement of bidirectional replication where a user can access their profile data locally at either site (Active-Active profile availability), the administrator should configure VDI Sync.

VDI Sync is a specialized configuration within the Nutanix Files ecosystem designed to synchronize User Profile directories across distributed file server instances. Unlike standard one-way Disaster Recovery (Smart DR) which is designed for failover, VDI Sync ensures that changes made to a profile at Site A are replicated to Site B, and vice-versa, allowing users to roam between physical locations while maintaining a consistent, local copy of their profile data.

https://www.nutanix.com/support-services/training-certification/certifications/certification-details-nutanix-certified-professional-ncp-euc-v6

https://docs.citrix.com/en-us/citrix-daas/install-configure/machine-catalogs-create.html

A gold image is a master image that contains the operating system, drivers, patches, and configurations for a virtual desktop. A non-persistent Citrix MCS environment is one where virtual desktops are created from a gold image and discarded after each user session.

Citrix Machine Creation Services (MCS) is a tool that uses a gold image to create and manage virtual machines for Citrix Virtual Apps and Desktops environments. MCS can create different types of machines, such as pooled random, static assigned, or dedicated 2 .

One of the challenges of using MCS is managing multiple gold images for different user groups or application needs. Updating multiple gold images can be time-consuming and error-prone. Therefore, it is recommended to use a single base image without any applications and leverage another tool such as Microsoft System Center Configuration Manager (SCCM) to deliver applications dynamically to the cloned virtual desktops 3 .

This approach can simplify image management, reduce storage consumption, improve performance, and enhance user experience. SCCM can also provide additional features such as patch management, compliance enforcement, inventory reporting, etc. 3

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

According to Nutanix AOS storage documentation and best practices regarding Data Efficiency:

Default Behavior (AOS 5.18+): Starting with AOS 5.18, Inline Compression is enabled by default on all newly created storage containers. 2 The system configures this with a compression delay of 0, meaning data is compressed immediately as it is written to the extent store. 3

Performance Impact: Enabling inline compression by default is designed to improve performance and increase effective storage capacity without significant overhead. 4 Nutanix recommends keeping this default setting for most workloads, including VDI and general server virtualization, as it reduces the amount of physical data written to the SSD tier. 5

Other Mechanisms:

Deduplication is not enabled by default. 6 It is typically reserved for specific use cases (like full clones or persistent desktops) and requires enabling both cache and capacity deduplication manually.

Erasure Coding (EC-X) is not enabled by default. It is a post-process feature that must be manually turned on for containers where data is " write cold " (not frequently overwritten), such as archives or backups.

Post-Process Compression was the historical default in older AOS versions (configured with a 60-minute delay) but has been superseded by Inline Compression as the standard default for new containers.

Summary: When an administrator creates a new container in a modern Nutanix environment, the system automatically checks the box for Compression and sets the delay to 0 minutes (Inline). 7

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 applications 1 .  Writable AppVolumes are stored as VMDK files on a datastore 2 .

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 sites 3 .

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

To achieve logical traffic separation while minimizing physical ports (using the same physical uplinks for multiple traffic types), Nutanix AHV networking best practices recommend the use of 802.1Q VLAN tagging.

The standard validated design is to:

Place the CVM and AHV Host management/storage interfaces on the Native VLAN (untagged) or a specific management VLAN.

Place User VM (Guest) traffic on Tagged VLANs .

This configuration allows storage replication traffic (CVM) and user traffic (VMs) to share the same physical cables (minimizing port usage) while remaining logically isolated at the switch level. Options like separate virtual switches (Option B) often require dedicated physical uplinks, which violates the requirement to minimize ports.

Nutanix storage best practices dictate that Encrypted Data should be stored in a container with compression disabled .

Data that is encrypted at the guest VM level or application level (before reaching the Nutanix storage controller) appears as random, high-entropy data. Compression algorithms (like LZ4) rely on finding repeated patterns in data to reduce its size. Because encrypted data has no discernible patterns, the compression algorithm will consume CPU cycles without achieving any storage savings (and potentially increasing latency).

While VM Templates and ISOs are often already compressed, they are not strictly required to have compression disabled in the same critical manner as Encrypted Data. VDI User Profiles often benefit significantly from compression.

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

According to Nutanix Storage Best Practices for Citrix/VDI :

Workload Type: The question specifies Persistent VDI , which typically uses Full Clones .

Deduplication: For Full Clones/Persistent Desktops, the data (OS and Apps) is identical across many VMs but stored independently. Deduplication (specifically Capacity Tier Deduplication) is Enabled to eliminate these redundant blocks and save significant capacity.

Compression: Inline Compression is Enabled by default and recommended for all VDI workloads to improve performance and capacity usage.

Erasure Coding (EC-X): Nutanix documentation explicitly states that Erasure Coding is Disabled for active VDI workloads. EC-X provides capacity savings for " write-cold " data (like backups or archives) but introduces a performance penalty (parity calculation overhead) on random writes, which are common in persistent desktop usage.

Correction: While option D suggests enabling everything, the specific best practice table for " Citrix MCS: Full Clone " lists Erasure Coding as Disabled to maintain optimal user experience.