Pass the Nutanix Certified Professional (NCP) NCP-EUC Questions and answers with Dumpstech

alert policies are rules that define the conditions for generating alerts on Nutanix clusters1. You can create custom alert policies based on your specific needs and preferences2Playbooks are automated workflows that perform actions based on triggers such as alerts3. You can create playbooks using predefined alerts or alerts matching criteria3.

To ensure that the vice president of IT infrastructure has the best possible experience and to be notified if any CPU resource constraints on the virtual desktop, one possible solution is to create a new alert policy to alert if the CPU on the virtual desktop is over a certain threshold (for example, 80%) and configure a playbook to send a notification (for example, via email or Slack) to the administrator23. This way, the administrator can monitor the performance of the virtual desktop and take appropriate actions if needed.

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2022_6:mul-alert-policies-customize-system-pc-t.html

In Nutanix AHV networking, the default bond mode for a virtual switch is Active-Backup. In this mode, all traffic flows through a single active physical uplink, while other uplinks remain in standby mode to be used only in the event of a failure. This explains the observation that "only one of the physical NICs... is carrying VM traffic."

To utilize multiple physical uplinks simultaneously and balance the traffic, the administrator must change the bond mode to an Active-Active configuration. In AHV, this is achieved by configuring the bond mode to Balance-SLB (Source Load Balancing) or Balance-TCP (LACP). These modes distribute VM traffic across all available physical interfaces in the bond, thereby balancing the load.

According to Nutanix "Omnissa Horizon on Nutanix Best Practices" (formerly VMware Horizon), Windows system services that create excessive background I/O must be optimized for VDI environments. Specifically, the Windows Search (Indexing) Service is a common cause of high CPU and disk I/O. In a non-persistent environment, if the indexing service is active, it continuously attempts to crawl the file system and update the index database during the user session. This generates a large number of small, random writes (IOPS) which land in the Flash Tier (Hot Tier/Oplog).

The behavior described—usage ramping up during business hours (as users create data/emails) and coming down during off-hours—aligns with the Curator process. Curator scans the cluster periodically (typically every 6 hours or during low load) to perform Tiering (moving cold data from SSD to HDD) and cleanup. If indexing is enabled, the "hot" index data fills the SSD tier during the day; Curator then destages this data or consolidates it during the scan. To resolve the performance impact and unnecessary flash consumption, the administrator must disable the Windows Search service or configure it correctly in the Golden Image.

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.

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

According to the installation guide for the Nutanix AHV Plug-in for Citrix:

Plugin Registration: The Nutanix AHV plug-in functions as a Hardware Compatibility Layer (HCL) plugin within the Citrix architecture. This allows the Citrix Provisioning (PVS) Streamed VM Setup Wizard to communicate with the AHV hypervisor.

Service Restart: After installing the plug-in on the PVS Console machine (or the DDC where the wizard is being run), the administrator must restart the specific Citrix services that load these HCL plugins. The Citrix Remote HCL Server service (often associated with the proxying of hypervisor calls in PVS/DDC environments) must be restarted to register the new Nutanix connection type.

Resolution: Without restarting this service, the PVS wizard cannot enumerate the Nutanix AHV connection or resources, rendering the integration unusable until the service reload picks up the new plugin dlls.

A Mandatory Profile is a read-only user profile (.man) that is pre-configured by an administrator.9 When a user logs in, the system copies this profile to create the session environment.

Crucially, any changes the user makes during the session (such as wallpaper, icons, or settings) are discarded when the user logs off. This ensures that every time the user logs in, they receive the exact same standard user configuration ("at the beginning of each session"), preventing configuration drift. Roaming and Container profiles are designed to retain user settings, which contradicts the requirement for a standardized start state.

persistent virtual desktops are virtual desktops that retain their state and configuration across sessions.

This means that users can customize their virtual desktops with their own applications, settings, and data, and have them available every time they log on.

Persistent virtual desktops are suitable for users who need a consistent and personalized experience, such as developers.

According to Nutanix best practices2, one of the recommended migration paths for persistent virtual desktops is to convert the physical computers to virtual desktops.

This can be done by using a tool such as VMware Converter or Microsoft Disk2vhd to create a virtual disk image of the physical computer’s hard drive.

Then, this image can be imported into Nutanix Cloud Platform and used as a base image for creating persistent virtual desktops.

This migration path can preserve the existing applications, settings, and data of the physical computers and minimize the disruption for the users.

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/