VMware Horizon 8.x Professional 2V0-51.23 Exam Questions

Page: 1 / 14
Total 89 questions

Want more questions? Get Premium Access.
()

Question 1

What are two Cloud Pod Architecture feature limitations? (Choose two.)

ACloud Pod Architecture does not support Active Directory two-way trusts between domains.

BCloud Pod Architecture is not supported with Unified Access Gateway appliances.

CKiosk mode clients are not supported unless a workaround has been implemented.

DCloud Pod Architecture cannot span multiple sites and data centers simultaneously.

EThe Cloud Pod Architecture feature is not supported in an IPv6 environment.

Answer : A, C

Cloud Pod Architecture is a feature that allows administrators to link multiple Horizon pods across sites and data centers to form a single logical entity called a pod federation. Cloud Pod Architecture enables global entitlements, which allow users to access desktops and applications from any pod in the pod federation. Cloud Pod Architecture also provides load balancing, high availability, and disaster recovery capabilities for Horizon deployments.

However, Cloud Pod Architecture has some feature limitations that administrators should be aware of. Two of these limitations are:

Cloud Pod Architecture does not support Active Directory two-way trusts between domains: This means that the domains that contain the Horizon pods in the pod federation must have a one-way trust relationship, where the domain that contains the Cloud Pod Architecture home site trusts all the other domains, but not vice versa. A two-way trust relationship, where each domain trusts and is trusted by all the other domains, is not supported by Cloud Pod Architecture and can cause authentication and entitlement issues.

Kiosk mode clients are not supported unless a workaround has been implemented: This means that users who log in to Horizon Client in kiosk mode, which is a mode that allows users to access a single desktop or application without entering credentials, cannot access desktops or applications from a Cloud Pod Architecture implementation. Kiosk mode clients are not compatible with global entitlements and load balancing features of Cloud Pod Architecture. However, there is a workaround that involves creating a dedicated user account and a dedicated desktop pool for each kiosk mode client and using a script to launch Horizon Client with the appropriate parameters.For instructions, see VMware Knowledge Base (KB) article 21488881.

The other options are not limitations of Cloud Pod Architecture:

Cloud Pod Architecture is supported with Unified Access Gateway appliances: Unified Access Gateway is a platform that provides secure edge services for Horizon deployments, such as secure remote access, load balancing, and authentication. Unified Access Gateway is compatible with Cloud Pod Architecture and can be configured to route user requests to the appropriate pod in the pod federation based on global entitlements and load balancing policies.

Cloud Pod Architecture can span multiple sites and data centers simultaneously: This is one of the main benefits of Cloud Pod Architecture, as it allows administrators to scale up and out their Horizon deployments across different geographic locations and network boundaries. Cloud Pod Architecture can support up to 15 pods per pod federation and up to 5 sites per pod federation, with a maximum of 200,000 sessions per pod federation.

The Cloud Pod Architecture feature is supported in an IPv6 environment: IPv6 is the latest version of the Internet Protocol that provides a larger address space and enhanced security features for network communication. Cloud Pod Architecture supports IPv6 environments and can operate in mixed IPv4 and IPv6 environments as well.

Question 2

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

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

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

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

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

Answer : B

One of the prerequisites for installing the Horizon Connection Server is to use a domain user account with administrator privileges on the system. This is because the installer needs to access and modify certain system files and registry settings, as well as create and configure the VMware Horizon View services. The installer also authorizes an Administrators account that has full administration rights for the Horizon environment, including the right to install replicated Connection Server instances. The other options are not prerequisites for installing the Horizon Connection Server. The host system can be a physical or virtual machine, but it must have an IP address that does not change. An SSL server certificate is not required for the initial installation, but it is recommended to replace the default self-signed certificate with a valid certificate from a trusted CA after the installation. AD DS and AD LDS Tools are not required for installing the Horizon Connection Server, but they can be useful for troubleshooting and managing the ADAM database that stores the Horizon configuration data.Reference:Installation Prerequisites for Horizon Connection Serverand [VMware Horizon 8.x Professional Course]

Question 3

When integrating a Linux OS based desktop into Active Directory, which three of the following can be used? (Choose three.)

AOpenLDAP Server Pass-through authentication

BWinbind Domain Join

COpenLDAP Server Cut-through authentication

DWindows Domain Join

ESystem Security Services Daemon (SSSD) LDAP authentication against the AD

Answer : B, D, E

Integrating a Linux OS-based desktop into Active Directory can be achieved using Winbind for domain joining and authentication, Windows Domain Join through tools like Samba, and System Security Services Daemon (SSSD) for LDAP authentication against Active Directory. These methods enable Linux desktops to participate in a Windows-centric environment, allowing for centralized authentication and management.

Question 4

An administrator is tasked with configuring VMware Integrated Printing. They enabled the VMware Integrated Printing feature during the installation of the Horizon Agent in the golden image, and created a Test Desktop Pool. On a physical end-point where the Horizon Client already is installed, the administrator added multiple network printers which are working perfectly. They test the configuration by connecting to the Horizon Desktop with the Horizon Client, unfortunately they do not see the printers within their Horizon Desktop.

What could be the reason that the administrator is not seeing the printers within his Horizon Desktop session?

APort TCP 9427 is disabled.

BThe VMware Integrated Printing feature is not installed in the Horizon Client.

CPrinting is disabled in the Horizon Desktop Pool.

DPort TCP 32111 is disabled.

Answer : C

One of the possible reasons that the administrator is not seeing the printers within his Horizon Desktop session is that printing is disabled in the Horizon Desktop Pool. Printing is a feature that allows users to print from a remote desktop to any local or network printer available on their client device. Printing can be enabled or disabled for each desktop pool by using the VMware Integrated Printing feature.

VMware Integrated Printing is a feature that supports client printer redirection, location-based printing, and persistent print settings. Client printer redirection enables users to print from a remote desktop to any local or network printer available on their client device. Location-based printing enables users to print to network printers that are physically near their client device. Persistent print settings enable users to retain their print settings across sessions.

To enable or disable printing for a desktop pool, the administrator needs to follow these steps:

In Horizon Console, select Inventory > Desktops.

Select the desktop pool and click Edit.

In the Edit Desktop Pool dialog box, select the VMware Integrated Printing tab.

Select or clear the Enable VMware Integrated Printing check box.

Click OK.

If printing is disabled for a desktop pool, users will not see any printers within their Horizon Desktop session, even if they have installed the VMware Integrated Printing feature in the Horizon Agent and the Horizon Client. Therefore, to resolve this issue, the administrator needs to enable printing for the desktop pool by selecting the Enable VMware Integrated Printing check box.

The other options are not likely to be the reason that the administrator is not seeing the printers within his Horizon Desktop session:

Port TCP 9427 is disabled: This port is used by the VMware Integrated Printing feature for communication between the Horizon Agent and the Horizon Client. If this port is disabled, users might experience printing errors or delays, but they should still see the printers within their Horizon Desktop session.

The VMware Integrated Printing feature is not installed in the Horizon Client: This feature is installed by default in the Horizon Client for Windows, Mac, Linux, Chrome, and HTML Access. If this feature is not installed in the Horizon Client, users might not be able to print from their remote desktops, but they should still see the printers within their Horizon Desktop session.

Port TCP 32111 is disabled: This port is used by ThinPrint for communication between the Horizon Agent and the ThinPrint Client. ThinPrint is a legacy printing feature that has been replaced by VMware Integrated Printing. If this port is disabled, users might experience printing errors or delays with ThinPrint, but they should still see the printers within their Horizon Desktop session if they use VMware Integrated Printing.

Question 5

To reduce the risk of users downloading malware to the corporate network, an administrator wants to allow end-users to open only intranet websites inside their virtual desktop. Additionally, the administrator wants to configure all other URLs to automatically open in a browser on the end-user's client machine.

Which steps should the administrator take to meet the requirements? (Choose two.)

AEnable the URL Content Redirection feature in Horizon Agent.

BDisable the Allow External Website feature in Horizon Agent.

CEnable secure website settings in the Global Settings Security menu.

DConfigure group policy settings to indicate how Horizon Agent redirects the URL

EEnable the URL Content Redirection feature on the desktop pool settings.

Answer : A, D

The URL Content Redirection feature allows administrators to configure specific URLs to open on the client machine or in a remote desktop or published application. This can help reduce the risk of users downloading malware to the corporate network, as well as improve the user experience and performance of certain web applications.

To meet the requirements of the scenario, the administrator needs to enable the URL Content Redirection feature in Horizon Agent when installing or upgrading it on the instant-clone desktops. This will allow Horizon Agent to send or receive URLs from Horizon Client, depending on the redirection direction. The administrator also needs to configure group policy settings to indicate how Horizon Agent redirects the URL. Specifically, the administrator needs to enable agent-to-client redirection, which means that Horizon Agent sends the URL to Horizon Client, which opens the default application for the protocol in the URL on the client machine. The administrator also needs to specify which URLs are redirected from a remote desktop to a client, and which URLs are not redirected. In this case, the administrator needs to configure a whitelist of intranet websites that are allowed to open inside the virtual desktop, and a blacklist of all other websites that are automatically redirected to a browser on the client machine.

The other options are not relevant or sufficient for meeting the requirements. Disabling the Allow External Website feature in Horizon Agent will prevent users from accessing any external websites from their virtual desktops, which might not be desirable or practical. Enabling secure website settings in the Global Settings Security menu will not affect how URLs are redirected, but only how secure connections are established between Horizon components. Enabling the URL Content Redirection feature on the desktop pool settings will not work unless it is also enabled in Horizon Agent and configured with group policy settings.Reference:Configuring URL Content Redirectionand [VMware Horizon 8.x Professional Course]

Question 6

What are the steps to create a custom role?

AIn 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.

BIn 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.

CIn 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.

DIn 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.

Answer : A

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]

Question 7

A new Horizon environment has gone into production. External sessions are being disconnected after a random period of time.

The following information has been documented by the administrator:

. Internal and external users are able to connect to their desktops.

. External sessions connect via Unified Access Gateway.

. Users are immediately able to reconnect but are disconnected again in a few minutes.

. Due to limited amount of public IP addresses, all traffic flows through a load balancer.

. Internal sessions, connected directly to the desktops, are not impacted.

. While the session remains connected, all expected functionality works properly.

What could be a cause of this issue?

AA misconfigured network load balancer is in front of the Unified Access Gateway appliances.

BA misconfigured network load balancer is in front of the Connection Servers.

CRequired firewall ports are not open in front of the Unified Access Gateway appliances.

DRequired firewall ports are not open in front of the Connection Servers.

Answer : A

The disconnections of external sessions while internal sessions remain stable suggest an issue with the network infrastructure external to the Horizon environment, specifically with the load balancer placed in front of the Unified Access Gateway (UAG) appliances. Misconfigurations such as improper session persistence settings can lead to sessions being disconnected or improperly routed, causing the observed random disconnections.