Nutanix NCP-EUC - Nutanix Certified Professional - End User Computing (NCP-EUC) v6.5Exam

one of the possible causes of slower logon and application load times for VMware Horizon-based virtual desktop users is Failed to create Native clone errors. This error occurs when there is a problem with cloning virtual machines using Nutanix Native Clones technology. To troubleshoot this issue, you can check the following:

The Nutanix cluster has enough free space to create clones

The Nutanix cluster has enough CPU and memory resources to handle cloning operations

The Nutanix cluster is running a compatible version of AOS and AHV with VMware Horizon

The VMware Horizon environment is configured correctly to use Nutanix Native Clones

The VMware Horizon agent is installed and updated on the master image

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

https://kb.vmware.com/s/article/1008360

The CPU usage percentage indicates how much of the allocated CPU resources the virtual desktop is consuming.

A high CPU usage percentage means that the virtual desktop is using a lot of CPU resources, which can affect the performance of other virtual desktops on the same host or cluster.

According to Nutanix best practices, the recommended CPU usage percentage for virtual desktops is less than 80%.

VM-0001 (99%)

VM-0002 (98%)

VM-0003 (97%)

VM-0004 (96%)

VM-0005 (95%)

VM-0010 (85%)

VM-0016 (81%)

These virtual desktops are likely contributing to the performance issue by consuming too much CPU resources and starving other virtual desktops from performing adequately.

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, applicationlogs, backups, and archives1. Nutanix Files also provides high availability and a unified single namespace for easy management2.

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.

Storage Efficiency features that will provide better storage efficiency and performance improvement for a mix of full clones and non-persistent desktops deployed via Citrix MCS on a three-node cluster are Compression and Deduplication. Compression is a technology that reduces the size of data blocks by removing redundant information. Deduplication is a technology that eliminates duplicate blocks of data and reduces storage consumption. Both Compression and Deduplication can be enabled on a per-container basis and can provide significant savings for Citrix virtual desktop deployments that use cloning technologies such as MCS2.

an action that the administrator should take to identify the virtual desktops in the environment that are using the most resources and causing resource contention is Filter the virtual desktops by Constrained: High. Constrained is a metric that indicates how often a virtual machine is unable to get its requested CPU resources. A high value means that the virtual machine is frequently starved for CPU and may experience performance degradation. By filtering the virtual desktops by Constrained: High, the administrator can see which ones are suffering from resource contention and take appropriate actions such as migrating them to less loaded hosts or increasing their CPU allocation.

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-Prism-v6_0:mul-tasks-view-page-pc-r.html

Based on the given information, the administrator is deploying 1000 instant clone virtual desktops, 500 full clone virtual desktops, and 150 applications. To support these workloads, the Nutanix solution will need multiple storage containers.

According to the Nutanix Certified Professional - End User Computing (NCP-EUC) v6 guide, for VDI workloads, it is recommended to create a separate storage container for each type of desktop (e.g. instant clone, full clone) and another container for AppStacks. It is also recommended to have at least one container for metadata and one container for replicas.

Therefore, for this scenario, a total of 3 storage containers should be created:

One container for 1000 instant clone virtual desktops

One container for 500 full clone virtual desktops

One container for 150 applications delivered via AppStacks

So the answer is C. 3.

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 changes1. To customize this user experience, administrators can use different solutions that manage user profiles and settings1.