Exactprep NCP-EUC Questions

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.

Citrix NetScaler VPX is a virtual appliance that provides web and application load balancing, secure and remote access, acceleration, security and offload features1. To set up and configure a Citrix NetScaler VPX appliance, you need to download it from the Citrix website, install it on a hypervisor such as Citrix XenServer or Microsoft Azure23, and log on to the console using the nsroot credentials2.

To expose the Citrix NetScaler VPX private VIP to the internet in order for users to be able to access the Citrix VDI desktops upon a DR failover, one possible solution is to use a floating IP address. A floating IP address is an IP address that can be dynamically assigned to an instance by using API calls. It allows you to redirect network traffic from one instance to another without changing any DNS settings or client configuration.

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.