VMware 2V0-51.23 Exam Practice Test Instant Access

Question 1

A Horizon administrator does not see the health status for the Unified Access Gateways (UAG) they configured in the Horizon Console.

What two options could be causing the issue? (Choose two.)

AThe Connection Server needs to be rebooted.

BThe firewall hasn't been configured properly to allow traffic on port 443.

CAnother license is needed for UAG health overview.

DThe pod needs to be added to the Cloud Pod Federation.

EThe name entered in the Horizon console doesn't match up with the system name in UAG.

Answer : B, E

If the Horizon Console does not display the health status of configured Unified Access Gateways (UAGs), it could be due to improper firewall configuration blocking traffic on port 443, which is essential for secure communication. Additionally, a discrepancy between the system name in UAG and the name entered in the Horizon Console can also prevent the console from correctly retrieving and displaying the UAG's health status.

Question 2

After creating a global entitlement, an administrator clicks on the name and navigates to Local Pools. The administrator clicks on Add but no local pools show up in the selection windows.

What can be one explanation for this?

AGlobal entitlements can only be configured with local Instant clone pools.

BGlobal entitlements can only be configured with local manual pools.

CGlobal entitlements setting must be matching with the local pool setting, otherwise they cannot be selected.

DGlobal entitlements can only be configured with local RDSH pools.

Answer : C

For a global entitlement to include local desktop pools, the settings and configurations of the global entitlement must be compatible with those of the local pools. If there is a mismatch in settings, such as display protocol, user assignment type (dedicated or floating), or other critical configurations, the local pools will not appear as selectable options when adding them to a global entitlement.

Question 3

An administrator wants to ensure that user's desktop experience is consistent regardless of the desktop they connect to.

What solution should be used to meet the requirement?

APersona Management

BTemporary Profiles

CDynamic Environment Manager

DLocal Profiles

Answer : C

VMware Horizon's Dynamic Environment Manager (DEM) is designed to provide a consistent and personalized desktop experience for users across different sessions and desktops. DEM manages user profiles and policies dynamically, ensuring that user settings, preferences, and application configurations are consistent no matter which desktop a user connects to, thus meeting the requirement for a uniform desktop experience.

Question 4

An administrator has created an application pool for frequently used applications using and RDS Farm. The administrator wants to start these applications immediately after a user has authenticated to the Horizon Connection Server.

Which of the following statement is accurate in this scenario?

AEdit the pool and select the Pre-Launch checkbox to start applications immediately after a user has authenticated to the Horizon Connection Server.

BInstead of the application pool being of the RDS Farm type, change the Application Pool type to Desktop Pool.

CThis cannot be done. Published applications cannot start automatically after a user has authenticated to the Horizon Connection Server.

DNothing needs to be done. Published applications start automatically after a user has authenticated to the Horizon Connection Server.

Answer : A

In VMware Horizon, the Pre-Launch feature allows for the initiation of applications immediately after user authentication, reducing the launch time of frequently used applications. By editing the application pool settings and enabling the Pre-Launch option, administrators can improve user experience by having critical applications ready as soon as the authentication process is completed.

Question 5

After a disaster recovery failure which left the data center unavailable, a company's VMware Horizon Administration Team has decided to increase the capacity of their VMware Horizon desktop pools and their resiliency.

Which two deployment options would support the requirement? (Choose two.)

AVMware Horizon deployed in the same local data center.

BVMware Horizon Desktop deployed as a Service on vCloud Air.

CVMware Horizon deployed on VMware Cloud on VMware.

DVMware Horizon deployed on VMware Cloud on AWS.

EVMware Horizon deployed in a remote data center.

Answer : D, E

To increase the capacity and resiliency of VMware Horizon desktop pools, deploying Horizon on VMware Cloud on AWS or in a remote data center are viable options. VMware Cloud on AWS provides a scalable and secure cloud platform, allowing for quick expansion and disaster recovery capabilities. Similarly, deploying Horizon in a remote data center can provide geographical diversity, reducing the impact of localized disasters and improving overall resilience.

Question 6

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 7

A user is complaining that each time they logon they need to change the settings for the e-mail client.

Which three options can an administrator deploy to make sure the user's settings are being saved? (Choose three.)

AVMware App Volumes Writeable Volumes

BRoaming Profiles

CPersona Management

DVMware Dynamic Environment Manager

EFlexible profiles

Answer : A, C, D

The user's problem is that their settings for the e-mail client are not being saved across sessions. This means that their user profile, which contains their personal data, settings, and preferences, is not being preserved or synchronized properly. To solve this problem, the administrator can deploy one or more of the following options to manage user profiles in Horizon:

VMware App Volumes Writable Volumes: This option allows users to store user-installed applications, data, and settings on a disk independent of the VM. Writable volumes can be attached to desktops along with application packages, and they can isolate the user-installed applications from the system-installed applications. Writable volumes can also be configured to capture specific files and registry keys by using the snapvol.cfg policy file. This option can help users retain their e-mail client settings on a writable volume that is attached to their desktop at each login.

Persona Management: This option allows administrators to manage user profiles by using a remote repository that stores user profiles. Persona Management synchronizes the user profile between the remote repository and the local desktop at login, logout, and at regular intervals during the session. Persona Management also supports profile redirection, which allows administrators to redirect certain folders in the user profile to a network share or a writable volume. This option can help users access their e-mail client settings from the remote repository or the redirected folder at each login.

VMware Dynamic Environment Manager: This option allows administrators to manage user profiles and policies by using a central share that stores user configuration files. Dynamic Environment Manager captures and applies user settings and preferences based on conditions and triggers, such as location, device, or application launch. Dynamic Environment Manager also supports profile archives, which allow administrators to back up and restore user profiles on demand or on schedule. This option can help users apply their e-mail client settings from the central share or the profile archive at each login.

The other options are not valid options for managing user profiles in Horizon:

Roaming Profiles: This option is a native Windows feature that allows users to access their user profile from any computer in a domain by storing it on a network share. However, this option is not recommended for Horizon because it can cause long login times, profile corruption, and data loss due to its synchronous and overwrite behavior. Roaming profiles are also incompatible with instant clones and linked clones.

Flexible profiles: This option does not exist in Horizon or Windows. It might be confused with Flex Profiles, which is a third-party product from Liquidware that provides profile management solutions similar to Dynamic Environment Manager.

VMware 2V0-51.23 VMware Horizon 8.x Professional Exam Practice Test