[May 23, 2024] New 2024 VMware 2V0-51.23 Exam Dumps with PDF from TestSimulate (Updated 90 Questions) [Q23-Q47]

Q23. What are the steps to create a custom role?

In the navigation pane under the Settings section dick on Administrators > Roles and Permission > Add.
Once the Add Role pane opens, add a name for the role and select the specific privileges.

In the navigation pane under the Settings section click on Administrators > Roles and Permission > Users and groups > Add. Once the Add Role pane opens, add a name for the role and select the specific privileges.

In the navigation pane under the Settings section click on Administrators > Entitlements > Add. Once the add Role pane opens, add a name for the role and select the specific privileges.

In the navigation pane under the Settings section click on Administrators > Users and Groups > Add. Once the Add Role pane opens, add a name for the role and select the specific privileges.

Q24. An end-user is experiencing a black screen when connecting to their virtual desktop. After a few seconds, the connection closes. Which could be the cause of the issue? (Choose three.)

There is a vRAM shortage on the Horizon virtual machine.

The Client machine video memory is too high.

The incorrect video driver version is installed on the Horizon virtual machine.

The Horizon Virtual Machine video memory is too high.

There is an incorrect firewall configuration.

Explanation
A black screen when connecting to a Horizon virtual desktop can be caused by various reasons, such as network issues, hardware issues, Horizon tunnel issues, or underlying guest operating system issues. Based on the options given, the following could be the cause of the issue:
A vRAM shortage on the Horizon virtual machine. This can affect the display performance and cause a black screen or a disconnect. To resolve this issue, you should configure the pool to provide enough video memory for the resolutions you plan to present to the clients1.
The incorrect video driver version installed on the Horizon virtual machine. This can cause compatibility issues and prevent the display protocol from working properly. To resolve this issue, you should verify that the View desktop is using the correct video driver and that it is compatible with the VMware Tools and Horizon Agent versions installed23.
An incorrect firewall configuration. This can block or misroute the display protocol traffic and cause a connection failure. To resolve this issue, you should verify that the required ports are open between the client, UAG/Security server/Connection server, and VDI machine4 .
The other options are not likely to cause a black screen when connecting to a Horizon virtual desktop:
The client machine video memory is too high. This should not affect the display protocol performance or cause a black screen. The client machine video memory is only used to render the display on the local device, not on the remote desktop.
The Horizon virtual machine video memory is too high. This should not cause a black screen or a disconnect either. The Horizon virtual machine video memory is used to allocate resources for the display protocol on the server side, not on the client side.
References:
Dual monitors configured using PCoIP does not span both the monitors for VMware View and Connecting to a VDI desktop with PCoIP displays a black screen and disconnects after 10 seconds Error attaching to SVGADevTap, error 4000: EscapeFailed reported by PCoIP server Interoperability Matrices Configuring PCoIP Secure Gateway in VMware View
[Network Ports in VMware Horizon]

Q25. An administrator needs to enable Session Collaboration in the VMware Horizon environment. What will be used as a requirement to enable Session Collaboration?

floating Instant Clone pool

dedicated Instant Clone pool

PCoIP protocol

BLAST protocol

Q26. An administrator has added a supported PCI graphics accelerator to a virtual machine configuration. When the administrator tries to power on the virtual machine, an error is displayed and the virtual machine remains powered off.
Which of the following virtual machine configuration settings needs to be applied to enable the virtual machine to power on?

Enable Video Card 3D Graphics.

Reserve all guest memory.

Set Memory Shares to High.

Disable CPU Hot Plug.

Q27. Drag and drop each Horizon console predefined role on the left to its matching function on the right.

Q28. Which pre-requisite should be met before installing the Horizon Connection Server?

The host system must be a vSphere VM with a static IP address.

Use a domain user account with administrator privileges on the Horizon Connection Server.

An SSL server certificate must be installed on the Horizon Connection Server.

Install AD DS and AD LDS Tools on the Horizon Connection Server.

Q29. Refer to the exhibit.
An administrator wants to set the initial login into a VDI desktop to be full screen.
In the Group Policy Management Editor Window, mark the setting that needs to be configured by clicking on it.

Q30. A junior-level Horizon administrator is not able to see all RDS farms.
Where would a high-level administrator need to make changes to correct the issue?

Category Folder

Access Groups

Global Entitlements

Global Policies

Q31. An administrator wants to deploy a RDS farm which can be patched in a rolling process with zero downtime.
Which of the following statements is true in this scenario?

This cannot be done as updating a Farm always incurs downtime.

Create an instant-clone RDS desktop farm.

Create a manual RDS desktop farm.

Nothing needs to be done. All RDS farms can be patched in a rolling process with zero downtime.

Q32. Drag and drop each Desktop Persistence type on the left to its matching description on the right.

Q33. An end-user is experiencing a black screen when connecting to their virtual desktop. After a few seconds, the connection closes. Which could be the cause of the issue? (Choose three.)

There is a vRAM shortage on the Horizon virtual machine.

The Client machine video memory is too high.

The incorrect video driver version is installed on the Horizon virtual machine.

The Horizon Virtual Machine video memory is too high.

There is an incorrect firewall configuration.

A black screen when connecting to a Horizon virtual desktop can be caused by various reasons, such as network issues, hardware issues, Horizon tunnel issues, or underlying guest operating system issues. Based on the options given, the following could be the cause of the issue:
A vRAM shortage on the Horizon virtual machine. This can affect the display performance and cause a black screen or a disconnect. To resolve this issue, you should configure the pool to provide enough video memory for the resolutions you plan to present to the clients1.
The incorrect video driver version installed on the Horizon virtual machine. This can cause compatibility issues and prevent the display protocol from working properly. To resolve this issue, you should verify that the View desktop is using the correct video driver and that it is compatible with the VMware Tools and Horizon Agent versions installed23.
An incorrect firewall configuration. This can block or misroute the display protocol traffic and cause a connection failure. To resolve this issue, you should verify that the required ports are open between the client, UAG/Security server/Connection server, and VDI machine4 .
The other options are not likely to cause a black screen when connecting to a Horizon virtual desktop:
The client machine video memory is too high. This should not affect the display protocol performance or cause a black screen. The client machine video memory is only used to render the display on the local device, not on the remote desktop.
The Horizon virtual machine video memory is too high. This should not cause a black screen or a disconnect either. The Horizon virtual machine video memory is used to allocate resources for the display protocol on the server side, not on the client side.
References:
Dual monitors configured using PCoIP does not span both the monitors for VMware View and Connecting to a VDI desktop with PCoIP displays a black screen and disconnects after 10 seconds Error attaching to SVGADevTap, error 4000: EscapeFailed reported by PCoIP server Interoperability Matrices Configuring PCoIP Secure Gateway in VMware View
[Network Ports in VMware Horizon]

Q34. A VMware Horizon on-premises environment’s Senior Administrator’s team is attempting to update the golden image for an Instant Clone desktop pool which an administrator created a month before. The Senior Administrator’s team is a member of the AD group “Horizon View Operators”.
The team states that they cannot login to the vCenter Server where the golden image resides to update the golden image.
What must the Senior Administrator do to enable the team to connect to vCenter and update the VM that is the source of desktop pools for their on-premises VMware Horizon solution?

Go to vSphere Client, add permissions for “Horizon View Operators”.

Connect to each desktop pool in Horizon, and add entitlements for “Horizon View Operators”.

Go to DEM (Dynamic Environment Manager) and add permissions for “Horizon View Operators” to update the golden image.

Go to Horizon Console, add permissions for “Horizon View Operators”.

Q35. An administrator is configuring load-balancing settings in Horizon Console for a RDSH Farm. Which two check boxes can be selected to influence the load balancing behavior? (Choose two.)

The floating dynamic host profile setting, created in the vSphere profile section.

The use custom script setting for customized RDSH load balancing.

The Include Session Count setting to include the session count on the RDSH for load balancing.

The Horizon DRS setting for fully automated vSphere load balancing.

Load balancing is a feature that allows administrators to distribute the load of published desktop and application sessions across multiple RDS hosts in a farm. Load balancing can improve the performance and availability of the sessions and the hosts. Horizon offers two ways of configuring load balancing for RDS hosts: using load balancing settings in Horizon Console or using custom load balancing scripts.
The load balancing settings in Horizon Console allow administrators to define how Horizon calculates the server load index, which indicates the load on each RDS host. The server load index can range from 0 to 100, where 0 represents no load and 100 represents full load. A server load index of -1 indicates that load balancing is disabled. Horizon uses the server load index to determine which RDS host is the best candidate for placing a new session request.
The load balancing settings in Horizon Console include the following check boxes that can be selected to influence the load balancing behavior:
The use custom script setting for customized RDSH load balancing: This setting allows administrators to override the default behavior of the load balancing settings and control the placement of new sessions by writing and configuring custom load balancing scripts. The custom scripts must write the server load index to a specific registry key on each RDS host. Horizon will use the value from the registry key instead of calculating it from the other settings.
The Include Session Count setting to include the session count on the RDSH for load balancing: This setting allows administrators to include the number of sessions (connected, pending, and disconnected) on each RDS host as a factor in calculating the server load index. By default, Horizon uses the following formula to calculate the server load index based on the session count: (connected sessions + pending sessions + disconnected sessions)/ (maximum session count). If the maximum session count is configured as unlimited, Horizon falls back to using the absolute number of total sessions.
The other options are not check boxes that can be selected in the load balancing settings in Horizon Console:
The floating dynamic host profile setting, created in the vSphere profile section: This option is not related to load balancing for RDS hosts, but rather to dynamic environment manager for instant-clone desktops. A dynamic host profile is a vSphere profile that contains configuration settings for instant-clone desktops, such as network settings, domain join settings, and customization scripts. A floating dynamic host profile is a type of dynamic host profile that applies to floating desktop pools, where users are assigned a random desktop from a pool at each login.
The Horizon DRS setting for fully automated vSphere load balancing: This option is not related to load balancing for RDS hosts, but rather to distributed resource scheduler (DRS) for vSphere clusters. DRS is a feature that monitors and balances the CPU and memory resources across multiple ESXi hosts in a cluster. DRS can also migrate virtual machines between hosts using vMotion to optimize resource utilization and performance. Horizon DRS is an extension of DRS that integrates with Horizon and provides additional capabilities, such as affinity rules, maintenance mode, and power management.
Horizon DRS can be configured with different automation levels, such as fully automated, partially automated, or manual.
References: Configuring Load Balancing for RDS Hosts in Horizon Console, Load Balancing Settings, Load Balancing Scripts, [Dynamic Host Profiles], and [VMware Horizon 8.x Professional Course]

Q36. End-users are complaining that they are frequently being asked for credentials when opening additional apps.
Which step should the administrator take to resolve the issue?

Configure SSO Timeout by modifying the Global Settings in Horizon Administrator.

Configure a time limit by modifying the Horizon GPO.

Configure Desktop Timeout by modifying the Pool Settings in Horizon Administrator.

Configure Session Timeout by modifying the Client Settings in Horizon Client.

Q37. Having configured two standalone Horizon pods, what steps should be taken to join them in a Cloud Pod Architecture (CPA) deployment?

On one pod, initialize the CPA. On the second pod, join the CPA. On one pod, create Global Entitlements, and add local pools from each pod.

Initialize the CPA on both Pods. On the second pod, sync the CPA. On one pod, create Global Entitlements, and add local pools from each pod.

On one pod, initialize the CPA. On the second pod, join the CPA. On one pod, create Cloud Entitlements, and sync pools from each pod. Initialize the CPA on both Pods.

On the second pod, sync the CPA. On one pod, create Cloud Entitlements, and add local pools from each pod.

Q38. In a load balanced Horizon POD with three Connection Servers, there are 450 active Blast sessions connected.
What happens if one of these Connection Servers runs into an unplanned outage?

All 450 active sessions are disconnected, and have to re-connect again by the end-user.

All active sessions will stay connected, because HTTPS Secure Tunnel and Blast Secure Gateway are disabled.

All 450 active session are logged off immediately.

Only the active sessions from the failed Connection Server are disconnected, because HTTPS Secure Tunnel is disabled.

In a load balanced Horizon POD with three Connection Servers, there are 450 active Blast sessions connected.
If one of these Connection Servers runs into an unplanned outage, only the active sessions from the failed Connection Server are disconnected, because HTTPS Secure Tunnel is disabled. This means that the other two Connection Servers can still handle the remaining sessions without interruption.
The HTTPS Secure Tunnel is a feature that allows Horizon Client devices to establish secure connections to virtual desktops and applications through the Connection Server. When this feature is enabled, all the display protocol traffic is tunneled through the Connection Server, which acts as a proxy between the client and the desktop. This increases the security and simplifies the network configuration, but also adds some overhead and dependency on the Connection Server availability1.
When this feature is disabled, the Horizon Client devices connect directly to the desktops using their IP addresses or hostnames, bypassing the Connection Server. This reduces the load and dependency on the Connection Server, but also requires more network configuration and firewall rules to allow direct access to the desktops2.
The Blast Secure Gateway is a similar feature that allows Horizon Client devices to establish secure connections to virtual desktops and applications using the Blast Extreme protocol through the Connection Server. When this feature is enabled, the Blast Extreme traffic is tunneled through the Connection Server, which acts as a gateway between the client and the desktop. When this feature is disabled, the Horizon Client devices connect directly to the desktops using Blast Extreme3.
In this scenario, both HTTPS Secure Tunnel and Blast Secure Gateway are disabled, which means that the Horizon Client devices connect directly to the desktops using Blast Extreme. Therefore, if one of the Connection Servers fails, only the sessions that were authenticated by that Connection Server are affected. The other sessions can continue without interruption, as long as they can reach their desktops directly4.
The other options are not correct for this scenario:
All 450 active sessions are disconnected, and have to re-connect again by the end-user. This would be true if HTTPS Secure Tunnel or Blast Secure Gateway were enabled, and all the display protocol traffic was tunneled through the Connection Server. In that case, any failure of a Connection Server would disconnect all the sessions that were using it as a proxy5.
All active sessions will stay connected, because HTTPS Secure Tunnel and Blast Secure Gateway are disabled. This would be true if there was no dependency on the Connection Server after authentication.
However, even with HTTPS Secure Tunnel and Blast Secure Gateway disabled, there is still some communication between the Horizon Client and the Connection Server for session management and heartbeat monitoring. If a Connection Server fails, these communications are lost and the sessions are terminated.
All 450 active session are logged off immediately. This would be true if there was a global setting in Horizon Console to log off users when a Connection Server fails. However, there is no such setting in Horizon Console. The default behavior is to disconnect users when a Connection Server fails, not log them off.
References:
Configuring HTTPS Secure Tunnel
Configuring Network Ports for Direct Connections
Configuring Blast Secure Gateway
Load Balancing Across Multiple Pods
Horizon 7: Monitoring health of Horizon Connection Server using Load Balancer
[Horizon 7 Pods]
[Global Settings for Client Sessions in Horizon Console]
[VMware Horizon Architecture Planning]

Q39. Which are the required permissions an administrator must assign to the user account for instant-clone operations in Active Directory before creating instant-clone desktop pools? (Choose three.)

Create and Delete Child objects

Read and Write All Properties

Modify Owner

Write to service principal names

List contents

Create and Delete Computer Objects

Q40. Refer to the exhibit.
Drag and drop the ports on the left to allow an external PCoIP connection through Unified Access Gateway (UAG) into the diagram on the right.

Q41. Adobe Acrobat 11 has been assigned to a user. VM25 already has Adobe Acrobat 11 and is natively installed.
What happens when the user logs on to VM25?

The App Volume package does not get attached because the natively installed application has priority.

The user-assigned application is attached to VM25. When the user clicks on the application shortcut, the App Volume package for Adobe Acrobat 11 is opened.

Although a shortcut to the App Volume package is created on the user desktop, the application does not get attached to VM25.

A shortcut to the user-assigned application is created on the user desktop, and when they click on the shortcut, the application gets attached to VM25.

Q42. What is the default URL used to access the Horizon Console?

https://<connection_server_FQDN>/admin

https://<connection_server_FQDN>/default

https://<connection_server_IP>/administrator

https://<connection_server_IP>/login

Q43. An administrator is configuring load-balancing settings in Horizon Console for a RDSH Farm. Which two check boxes can be selected to influence the load balancing behavior? (Choose two.)

The floating dynamic host profile setting, created in the vSphere profile section.

The use custom script setting for customized RDSH load balancing.

The Include Session Count setting to include the session count on the RDSH for load balancing.

The Horizon DRS setting for fully automated vSphere load balancing.

Explanation
Load balancing is a feature that allows administrators to distribute the load of published desktop and application sessions across multiple RDS hosts in a farm. Load balancing can improve the performance and availability of the sessions and the hosts. Horizon offers two ways of configuring load balancing for RDS hosts: using load balancing settings in Horizon Console or using custom load balancing scripts.
The load balancing settings in Horizon Console allow administrators to define how Horizon calculates the server load index, which indicates the load on each RDS host. The server load index can range from 0 to 100, where 0 represents no load and 100 represents full load. A server load index of -1 indicates that load balancing is disabled. Horizon uses the server load index to determine which RDS host is the best candidate for placing a new session request.
The load balancing settings in Horizon Console include the following check boxes that can be selected to influence the load balancing behavior:
The use custom script setting for customized RDSH load balancing: This setting allows administrators to override the default behavior of the load balancing settings and control the placement of new sessions by writing and configuring custom load balancing scripts. The custom scripts must write the server load index to a specific registry key on each RDS host. Horizon will use the value from the registry key instead of calculating it from the other settings.
The Include Session Count setting to include the session count on the RDSH for load balancing: This setting allows administrators to include the number of sessions (connected, pending, and disconnected) on each RDS host as a factor in calculating the server load index. By default, Horizon uses the following formula to calculate the server load index based on the session count: (connected sessions + pending sessions + disconnected sessions)/ (maximum session count). If the maximum session count is configured as unlimited, Horizon falls back to using the absolute number of total sessions.
The other options are not check boxes that can be selected in the load balancing settings in Horizon Console:
The floating dynamic host profile setting, created in the vSphere profile section: This option is not related to load balancing for RDS hosts, but rather to dynamic environment manager for instant-clone desktops. A dynamic host profile is a vSphere profile that contains configuration settings for instant-clone desktops, such as network settings, domain join settings, and customization scripts. A floating dynamic host profile is a type of dynamic host profile that applies to floating desktop pools, where users are assigned a random desktop from a pool at each login.
The Horizon DRS setting for fully automated vSphere load balancing: This option is not related to load balancing for RDS hosts, but rather to distributed resource scheduler (DRS) for vSphere clusters. DRS is a feature that monitors and balances the CPU and memory resources across multiple ESXi hosts in a cluster. DRS can also migrate virtual machines between hosts using vMotion to optimize resource utilization and performance. Horizon DRS is an extension of DRS that integrates with Horizon and provides additional capabilities, such as affinity rules, maintenance mode, and power management.
Horizon DRS can be configured with different automation levels, such as fully automated, partially automated, or manual.
References: Configuring Load Balancing for RDS Hosts in Horizon Console, Load Balancing Settings, Load Balancing Scripts, [Dynamic Host Profiles], and [VMware Horizon 8.x Professional Course]

Q44. Refer to the exhibit.
Drag and drop the components on the left that are part of the logical architecture for a single-site deployment of VMware Horizon into their correct position in the diagram on the right.

Q45. Refer to the exhibit.
An administrator wants to be able to see the desktop VM’s active session in vSphere Console.
In the Group Policy Management Editor window, mark the correct VMware Blast setting to be configured by clicking on it.