2V0-51.23 Exam Dumps and Practice Questions

Roles and permissions are a way of controlling the access and actions of administrators and users in Horizon. By default, Horizon provides two predefined roles: Administrators and Read Only Administrators. However, a high-level administrator can create custom roles with specific privileges to suit different needs and scenarios. To create a custom role, the administrator needs to follow these steps:

In the navigation pane under the Settings section, click on Administrators > Roles and Permissions.

In the Roles and Permissions page, click on Add.

In the Add Role pane, enter a name for the role in the Role Name text box.

In the Privileges section, select the checkboxes for the privileges that you want to assign to the role. You can expand or collapse the categories to view or hide the sub-privileges. You can also use the Select All or Deselect All buttons to select or clear all the privileges in a category.

Click on Save to create the custom role.

The custom role will appear in the Roles and Permissions page, where you can edit or delete it as needed. You can also assign the custom role to users or groups in the Users and Groups page.Reference: [Create Custom Roles] and [VMware Horizon 8.x Professional Course]

On a VMware vCenter managed virtual machine, the VMware Horizon Agent knows which Connection Server it should register with during the Instant Clone pool creation process by querying VMware Tools for a Guestlnfo Variable during the cloning process. The Guestlnfo Variable is a custom property that is set on the parent virtual machine and contains the FQDN of the Connection Server. When the parent virtual machine is cloned, the Guestlnfo Variable is copied to the clone and read by the Horizon Agent.The Horizon Agent then registers with the Connection Server specified in the Guestlnfo Variable12.

The other options are not correct for this scenario:

Administrator provides this information in the ''Add Pool'' creation wizard. This option is not correct because the administrator does not need to provide the Connection Server information in the ''Add Pool'' creation wizard. The administrator only needs to select the vCenter Server, data center, cluster, resource pool, datastore, network, and snapshot of the parent virtual machine.The Connection Server information is already embedded in the parent virtual machine as a Guestlnfo Variable3.

Horizon Agent retrieves this information from an DNS SRV record. This option is not correct because the Horizon Agent does not use DNS SRV records to find the Connection Server during the Instant Clone pool creation process. DNS SRV records are used by Horizon Client devices to discover Connection Servers when they connect to a Horizon environment.DNS SRV records are optional and can be configured by the administrator to simplify client connections4.

Administrator provides this information in the Horizon Agent Installation Wizard on the master image. This option is not correct because the administrator does not need to provide the Connection Server information in the Horizon Agent Installation Wizard on the master image. The administrator only needs to select the features and options that are required for the desktop pool, such as VMware Horizon Instant Clone Agent, VMware Dynamic Environment Manager, VMware App Volumes, and so on.The Connection Server information is set on the master image after it is converted to a parent virtual machine by using a PowerShell script5.

Instant Clones: How Does It Work?

Instant Clone Domain Administrator Account

Create an Automated Instant-Clone Desktop Pool

Configuring DNS Service Records for Horizon Connection Server

Install Horizon Agent on a Virtual Machine

[VMware Horizon 8.x Professional]

[VMware Horizon Architecture Planning]

Single sign-on (SSO) is a feature that allows users to log in to Horizon Client once and launch remote desktops and applications without being prompted for credentials again. SSO is enabled by default and can be configured in the Global Settings of Horizon Administrator. One of the settings is SSO Timeout, which determines how long the user's credentials are cached before they expire. If the SSO Timeout is too short, users might be frequently asked for credentials when opening additional apps. To resolve this issue, the administrator can increase the SSO Timeout value or set it to -1, which means that no SSO timeout limit is set.Reference:Global Settings for Client Sessions in Horizon Consoleand [VMware Horizon 8.x Professional Course]

https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-console-administration/GUID-E2A7CA32-193D-43D9-B08E-DD20CAE9CA28.html

VMware Horizon Cloud on Microsoft Azure is the only deployment solution that meets all the requirements.VMware Horizon Cloud on Microsoft Azure supports Windows 10 Enterprise multi-session desktops, which are a new Remote Desktop Session Host exclusive to Azure Virtual Desktop on Azure1. It also supports App Volumes, which is a real-time application delivery system that enables IT to instantly provision applications to users or desktops. VMware Horizon Cloud on Microsoft Azure supports centralized brokering, which means that the Horizon Cloud Service acts as a single point of entry for end users to access their virtual desktops and applications. VMware Horizon Cloud on Microsoft Azure also supports automatic routing of end-users to the most appropriate virtual workspace, using the Universal Broker feature. Universal Broker is a cloud-based brokering service that provides a unified user experience across multiple Horizon pods and clouds.

VMware vSphere Desktop Edition does not support Windows 10 Enterprise multi-session desktops, as they are only available on Azure Virtual Desktop1. VMware Workspace ONE Unified Endpoint Management does not support App Volumes, as it is a different solution for managing devices and applications. VMware Horizon On-Premises does not support automatic routing of end-users to the most appropriate virtual workspace, as it requires manual configuration of load balancing and global entitlements.Reference:

Profile production applications in Azure with Application Insights Profiler1

Using Application Profiler - VMware Docs2

First look at profiling tools - Visual Studio (Windows)3

App Volumes Overview

Horizon Cloud Service on Microsoft Azure Architecture

Universal Broker Overview

Workspace ONE UEM Overview

Load Balancing Across Pods and Sites in a Cloud Pod Architecture Environment

To enable debug logging for a single user in VMware Dynamic Environment Manager, the administrator needs to create an empty FlexDebug.txt file in the same folder as the standard log file for this user.This will trigger FlexEngine to switch to debug logging for this particular user1.Debug logging is useful for troubleshooting purposes, as it provides more detailed information about the FlexEngine operations and actions1.

The other options are not correct because:

Updating the FlexEngine registry to DEBUG will not enable debug logging for a single user, but for all users who log on to the same computer.This option can only be set through Group Policy settings and applies to all users1.Moreover, this option is not recommended, as it can cause performance issues and disk space consumption due to the large size of the log files1.

Creating an empty FlexDebug.log file in the log folder will not enable debug logging for a single user, as the file name must be exactly FlexDebug.txt.The file extension must be .txt, not .log1.

Configuring the FlexEngine GPO to DEBUG will not enable debug logging for a single user, but for all users who are affected by the GPO.This option can only be set through Group Policy settings and applies to all users1.Moreover, this option is not recommended, as it can cause performance issues and disk space consumption due to the large size of the log files1.

Enabling debug logging for a single user in VMware Dynamic Environment Manager1