Nutanix ' s Shadow Clones feature is used to create linked clones or snapshots of base VMs, which can improve VM provisioning time and storage efficiency by reducing the amount of duplicated data.

If an administrator disables Shadow Clones within a company ' s VDI environment, it is likely that deployment times would increase as the number of deployed desktops increases. This is because linked clones or snapshots would no longer be used, so each new desktop deployment would require creating a full copy of the base VM.

Nutanix Shadow Clones allow for distributed caching of a particular disk or VM data, which are in a ‘multi-reader’ scenario.  This can help in scenarios such as VDI or private clone boot storms, where VMs on multiple nodes read from the same set of base disks 1 2

This is because this option will enable the administrator to add a Nutanix cluster as a new connection by installing and registering the plugin on the Delivery Controllers that manage the connection type menu.

https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2079-Citrix-Virtual-Apps-and-Desktops:BP-2079-Citrix-Virtual-Apps-and-Desktops

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

According to Citrix on Nutanix Reference Architectures :

Simplicity of MCS: Machine Creation Services (MCS) is integrated directly into the Citrix Studio console and communicates natively with the Nutanix AHV APIs. It creates clones (Linked or Full) effortlessly without requiring extra infrastructure.

Comparison with PVS: PVS (Provisioning Services) (Option D) requires a separate PVS infrastructure (Provisioning Servers, SQL database, TFTP/DHCP configuration, Network Streaming Setup).

Conclusion: For a " Dedicated VDI " requirement, using MCS to provision full or fast clones requires significantly less administrative effort and infrastructure setup than implementing a PVS environment.

In a non-persistent VDI environment, changes to the operating system should only occur within the Golden Image (or Master Image), not on the individual provisioned VMs. If the Windows Update policy is set to Automatic within the Gold Image, the clones generated from that image will independently check for updates, download them, and attempt to install them during the user ' s session.

This behavior often triggers a " Restart Required " prompt to the end-user to finish installing the updates. To prevent this disruption and ensure version consistency, Nutanix and VDI best practices dictate that the Windows Update service should be disabled or set to Manual in the Gold Image. Updates should be applied administratively to the Gold Image during a maintenance window, followed by a recompose/update of the machine catalog.

Nutanix is the only vendor that supports replication of linked clones. This means that option A is correct. However, I cannot guarantee the accuracy or validity of this information, so please verify it with other sources before using it.

Users may expect some level of personalization and consistency across their virtual desktop sessions, even if they do not save any changes 1 .  To customize this user experience, administrators can use different solutions that manage user profiles and settings 1 .

Nutanix Prism Central features the Security Dashboard (previously known as Security Planner), which is the designated interface for monitoring and managing the security posture of the environment.

This dashboard specifically scans and reports on Common Vulnerabilities and Exposures (CVEs), including CPU and memory-related vulnerabilities (such as Spectre, Meltdown, and L1TF) affecting the AHV hosts and CVMs. It provides a consolidated view of the " Protection Status " across all registered clusters and guides the administrator on the necessary software versions (LTS/STS) or Life Cycle Manager (LCM) updates required to remediate these specific hardware-level security risks.