Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. VMware
  5. 2V0-51.23

VMware 2V0-51.23 Exam
VMware Horizon 8.x Professional (Page 9 )

Updated On: 1-Feb-2026
Page 3 of 19
PDF with 89 Questions

Refer to the exhibit.



An administrator is tasked with creating an instant clone pool for their sales department. During the creation of the pool the administrator saw that there is no golden image available, as seen in the exhibit.
Which two actions can an administrator take so that the golden image is showing up in the Golden Image selection window? (Choose two.)

  1. Login to the vSphere Client, select the Golden Image virtual machine and delete all snapshots.
  2. Login to the vSphere Client, select the Golden Image virtual machine and create a snapshot
  3. Refresh the Select Golden Image view and select the Golden Image.
  4. Login to the vSphere Client, select the Golden Image virtual machine and clone it to a new virtual machine.
  5. Login to the vSphere Client, select the Golden Image virtual machine and convert it to a template.

Answer(s): B,E

Explanation:

The administrator can take two actions to make the golden image show up in the Golden Image selection window. First, they can login to the vSphere Client, select the Golden Image virtual machine and create a snapshot. This will make the golden image available in the selection window. Second, they can login to the vSphere Client, select the Golden Image virtual machine and convert it to a template. This will also make the golden image available in the selection window. A golden image is a virtual machine that contains the operating system, applications, and settings that are required for an instant clone desktop pool. To create an instant clone desktop pool, the administrator must select a golden image and a snapshot from the vSphere inventory. The snapshot must be taken after installing and configuring the Horizon Agent on the golden image1. If there is no snapshot or no template available, the golden image will not show up in the selection window.
The other options are not correct for this scenario:
Login to the vSphere Client, select the Golden Image virtual machine and delete all snapshots. This option is not correct because deleting all snapshots will not make the golden image show up in the selection window. In fact, it will prevent the administrator from creating an instant clone desktop pool, as a snapshot is required for instant cloning2.
Refresh the Select Golden Image view and select the Golden Image. This option is not correct because refreshing the view will not change the availability of the golden image in the selection window. The administrator must create a snapshot or a template of the golden image before it can be selected.
Login to the vSphere Client, select the Golden Image virtual machine and clone it to a new virtual machine. This option is not correct because cloning the golden image to a new virtual machine will not make it show up in the selection window. The administrator must still create a snapshot or a template of the cloned virtual machine before it can be selected.


Reference:

Preparing a Golden Image Virtual Machine for Instant-Clones Snapshot vmdk files of the golden image used to publish Instant clone ...
Create an Automated Instant-Clone Desktop Pool
Instant Clone Desktop Pools
[VMware Horizon 8.x Professional]



On a VMware vCenter managed virtual machine, how does the VMware Horizon Agent know which Connection Server it should register with during the Instant Clone pool creation process?

  1. Administrator provides this information in the "Add Pool" creation wizard.
  2. Horizon Agent retrieves this information from an DNS SRV record.
  3. Administrator provides this information in the Horizon Agent Installation Wizard on the master image.
  4. Horizon Agent queries VMware Tools for a Guestlnfo Variable during the cloning process.

Answer(s): D

Explanation:

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.


Reference:

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]



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?

  1. All 450 active sessions are disconnected, and have to re-connect again by the end-user.
  2. All active sessions will stay connected, because HTTPS Secure Tunnel and Blast Secure Gateway are disabled.
  3. All 450 active session are logged off immediately.
  4. Only the active sessions from the failed Connection Server are disconnected, because HTTPS Secure Tunnel is disabled.

Answer(s): D

Explanation:

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.


Reference:

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]



DRAG DROP (Drag and Drop is not supported)
An organization with an existing Windows 2012 R2 Server RDSH farm decided to move to Windows Server 2019 as their new standard. Order the steps that need to be taken by the administrator to deploy a RDS desktop pool with this new standard.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



To deploy a RDS desktop pool with the new standard of Windows Server 2019, the steps should be ordered as follows:
Prepare the Windows Server 2019 golden image. This is the first step because you'll need a prepared OS image to base your RDS desktop pool on.
Add an Automated Farm. Once your golden image is ready, you can set up an automated farm for the RDS desktop pool.
Add a RDS desktop pool. Using the automated farm and the prepared golden image, you can now add the RDS desktop pool.
Entitle AD users and/or groups. With the RDS desktop pool in place, the next step is to give Active Directory (AD) users and groups the necessary entitlements to access the desktops. Launch Horizon Client and verify access to RDS desktop. As the final verification step, launch the Horizon Client to ensure that you can access the newly created RDS desktop pool and that everything is functioning as expected.
So, the sequential order is: Prepare the Windows Server 2019 golden image -> Add an Automated Farm -> Add a RDS desktop pool -> Entitle AD users and/or groups -> Launch Horizon Client and verify access to RDS desktop.



Which two client types have the lowest cost of ownership and are easier to manage deployments, perform firmware updates, and monitor. (Choose two.)

  1. Thin Clients
  2. MacOS Clients
  3. Headless Clients
  4. Zero Clients
  5. Windows Clients

Answer(s): A,D

Explanation:

Thin Clients and Zero Clients have the lowest cost of ownership and are easier to manage due to their minimalistic design, which lacks a full operating system, resulting in fewer components that require updates. These clients are designed for remote desktop services like VMware Horizon, where the computing work is done on the server side, making firmware updates and monitoring simpler and more centralized.



Viewing page 9 of 19
Viewing questions 41 - 45 out of 89 questions



Post your Comments and Discuss VMware 2V0-51.23 exam prep with other Community members:

Join the 2V0-51.23 Discussion