2V0-51.23 Online Practice Questions and Answers

Correct Answer: B

Explanation: A Trusted Platform Module (vTPM) is a virtualized version of a physical TPM device that provides enhanced security for virtual machines. A vTPM device can be added to a virtual machine to enable features such as encryption,

attestation, and key management. A vTPM device requires a Key Management Server (KMS) to store and manage the encryption keys.

To create instant clones VMs with a vTPM device, the vCenter Server user must have certain privileges in addition to those required for instant clones without a vTPM device. One of these privileges is Manage KMS, which allows the user to

perform cryptographic operations on the vTPM device, such as cloning, decrypting, encrypting, migrating, and registering. The Manage KMS privilege is part of the Cryptographic operations privilege group on vCenter Server.

The other options are not required only for instant clones VMs with a vTPM device:

Upgrade virtual machine compatibility: This privilege allows the user to upgrade the virtual hardware version of a virtual machine to support new features and capabilities. This privilege is required for instant clones VMs regardless of whether

they have a vTPM device or not.

Configure Host USB device: This privilege allows the user to configure USB devices on an ESXi host and attach them to a virtual machine. This privilege is not related to vTPM devices or instant clones VMs.

Manage custom attributes: This privilege allows the user to create, edit, and delete custom attributes for vCenter Server objects. Custom attributes are user-defined fields that can store additional information about objects. This privilege is not

related to vTPM devices or instant clones VMs.

References: Privileges Required for the vCenter Server User With Instant Clones, vSphere Virtual Machine Administration, and [VMware Horizon 8.x Professional Course]

Correct Answer: B

Explanation: 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 ADAMdatabase that stores the Horizon configuration data. References: Installation Prerequisites for Horizon Connection Server and [VMware Horizon

8.x Professional Course]

Correct Answer: D

Explanation: VMware App Volumes is a real-time application delivery system that allows administrators to assign applications to users and groups in Horizon. App Volumes uses virtual disks called packages to store and deliver applications.

When a user logs on to a desktop, the App Volumes agent attaches the assigned packages to the desktop and merges them with the OS disk. The user can then access the applications as if they were natively installed.

App Volumes is a suitable solution for deploying an application to specific users in an instant-clone desktop environment with the following characteristics:

The application needs to be updated very frequently: App Volumes allows administrators to update applications in real time by using the update or push- image operations. These operations replace the existing packages with new ones that

have the latest updates applied, without affecting the user data or settings. The updated packages are delivered to the users at the next login or refresh. The application needs to be installed as soon as possible: App Volumes allows

administrators to install applications quickly and easily by using a clean packaging system and capturing the application installation process. The resulting package can be assigned to users or groups immediately, without requiring any

recomposing or rebooting of the desktops.

The application is not multi-user aware: App Volumes allows administrators to deliver applications that are not multi-user aware by using writable volumes. Writable volumesare user-specific virtual disks that store user-installed applications,

data, and settings. Writable volumes can be attached to desktops along with application packages, and they can isolate the user-installed applications from the system-installed applications. The other options are not suitable for meeting the

requirements:

VMware Horizon Published Application: This option allows administrators to publish applications from RDS hosts to users in Horizon. However, this option requires a separate RDS infrastructure and licensing, and it does not support instant

updates or writable volumes for user-installed applications. VMware Dynamic Environment Manager: This option allows administrators to manage user profiles and policies in Horizon. However, this option does not deliver or update

applications, and it does not support writable volumes for user-installed applications.

VMware ThinApp: This option allows administrators to package applications into portable executables that can run on any Windows system without installation. However, this option requires a separate packaging process and licensing, and it

does not support instant updates or writable volumes for user-installed applications.

References: App Volumes Architecture, Updating Applications in Real Time, Writable Volumes Overview, and [VMware Horizon 8.x Professional Course]

Correct Answer: AC

Explanation: 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 andup 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.

References: Cloud Pod Architecture Limitations in Horizon 8 and [VMware Horizon 8.x Professional Course]

Correct Answer: D

Explanation: 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. References: 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

Correct Answer: D

Explanation: VMware Blast policy settings are stored in the registry key HKLM\Software\Policies\VMware, Inc.\VMware Blast\Config on the remote desktops or RDS hosts that use the VMware Blast display protocol. These settings can be configured by using the VMware Blast ADMX template file (vdm_blast.admx) and applying it through Microsoft Group Policy Object (GPO). Some of these settings can be changed in real time, which means that they take effect immediately after the policy is applied, without requiring a reboot or a reconnection of the Horizon Client. However, some of these settings cannot be changed in real time, which means that they require a reboot or a reconnection of the Horizon Client to take effect. The effect of changing any VMware Blast policy that cannot be changed in real time is that the Microsoft GPO update rules apply and GPOs are updated manually or by restarting the Horizon Agent. This means that the new policy settings will not be applied until one of the following events occurs: The Horizon Agent service is restarted on the remote desktop or RDS host. This can be done manually by using the Services console or the command-line tool sc.exe, or automatically by using a scheduled task or a script. The remote desktop or RDS host is rebooted. This can be done manually by using the Restart option in Windows, or automatically by using a scheduled task or a script. The Group Policy refresh interval is reached. This is a configurable time interval that determines how often the system checks for and applies new or changed GPOs. By default, this interval is 90 minutes for domain members and 5 minutes for domain controllers, with a random offset of 0 to 30 minutes. This interval can be modified by using the Group Policy refresh interval for computers setting in the ComputerConfiguration\Administrative Templates\System\Group Policy folder of the Group Policy Management Console. Therefore, to ensure that the VMware Blast policy settings that cannot be changed in real time are applied as soon as possible, it is recommended to restart the Horizon Agent service or reboot the remote desktop or RDS host after applying the policy. References: VMware Blast Policy Settings, Group Policy refresh intervals, and [VMware Horizon 8.x Professional Course]

Correct Answer: B

Explanation: App Volumes is a real-time application delivery system that allows administrators to assign applications to users and groups in Horizon. App Volumes uses virtual disks called packages to store and deliver applications. When a user logs on to a desktop, the App Volumes agent attaches the assigned packages to the desktop and merges them with the OS disk. The user can then access the applications as if they were natively installed. In this scenario, Adobe Acrobat 11 has been assigned to a user as an App Volumes package. When the user logs on to VM25, which already has Adobe Acrobat 11 natively installed, the App Volumes agent attaches the package to VM25 and creates a shortcut on the user desktop. However, the package does not overwrite or conflict with the natively installed application. Instead, when the user clicks on the shortcut, the App Volumes package for Adobe Acrobat 11 is opened and runs in an isolated environment. This allows the user to use different versions of the same application without affecting each other or the OS. References: App Volumes Architecture and [VMware Horizon 8.x Professional Course]

Correct Answer: A

Explanation: To improve the user experience when using Application Profiler from Dynamic Environment Manager to create application-specific user defined settings, the administrator can configure exclusions to filter out unnecessary folders and registry entries. Exclusions are rules that specify which file system or registry locations are not included in the Flex configuration file. Exclusions can reduce the size of the Flex configuration file and the profile archive, and improve the performance of the application profiling and synchronization processes12. The other options are not valid or effective because: Changing the default save path does not affect the size or content of the Flex configuration file or the profile archive. It only changes where the files are stored on the local machine3. Using Deepest Registry Path does not reduce the size of the Flex configuration file or the profile archive. It only changes how the registry locations are displayed in the Application Profiler interface4. There is no such thing as Cloud Entitlements in Dynamic Environment Manager. The correct term is Global Entitlements, which are used in Cloud Pod Architecture to entitle users to desktops or applications across multiple pods5. References := 1: VMware Dynamic Environment Manager Application Profiler Administration Guide: Filtering and Optimizing the Analysis Details 2: VMware Dynamic Environment Manager Application Profiler Administration Guide: Exclusions 3: VMware Dynamic Environment Manager Application Profiler Administration Guide: Advanced Configuration of Application Profiler 4: VMware Dynamic Environment Manager Application Profiler Administration Guide: Editing the Flex Configuration File

5: VMware Horizon 8 Documentation: Understanding Global Entitlements in Cloud Pod Architecture

Correct Answer: D

Explanation: VMware vSAN is a storage product that allows the pooling of resources to create datastores in a software defined datacenter. VMware vSAN is a hyper-converged infrastructure solution that integrates compute, storage, and networking resources on industry-standard x86 servers. VMware vSAN aggregates local or direct-attached data storage devices to create a single storage pool shared across all hosts in the vSAN cluster. VMware vSAN enables you to provision and manage storage from the VMware vSphere Web Client or the VMware vCenter Server Appliance Shell. VMware vSAN provides several benefits, such as lower total cost of ownership, simplified management, high performance, scalability, and availability12. References := 1: VMware Horizon 8 Documentation: VMware vSAN Overview 2: VMware Horizon 8 Documentation: Benefits of Using VMware vSAN with Horizon 8

Correct Answer: A

Explanation: Writable Volumes are user-specific virtual disks that store user-installed applications, data, and settings. App Volumes is a real-time application delivery system that uses Writable Volumes to deliver applications that are not multiuser aware. However, sometimes it might be necessary to prevent App Volumes from persisting specific databetween sessions, such as temporary files, application updates, or registry keys. To do this, administrators can specify exclusions

for Writable Volumes in a policy file called snapvol.cfg.

The snapvol.cfg file is a text file that contains policy settings for App Volumes. These settings determine which files and registry keys are captured or excluded by App Volumes. The snapvol.cfg file can be customized by administrators to suit

different needs and scenarios. The snapvol.cfg file can be applied to both application packages and Writable Volumes.

To specify exclusions for Writable Volumes, administrators can use the following keywords in the snapvol.cfg file:

exclude_uwv_file: This keyword excludes a file or folder path from being persisted on a Writable Volume. For example, exclude_uwv_file=\Program Files (x86)\Notepad++ excludes the folder location of Notepad++ from being overwritten

during an update.

exclude_uwv_reg: This keyword excludes a registry key or value from being persisted on a Writable Volume. For example,

exclude_uwv_reg=\REGISTRY\MACHINE\SOFTWARE\Notepad++ excludes the registry location of Notepad++ from being overwritten during an update. The snapvol.cfg file must be uploaded to the Writable Volume by using the Update

Writable Volumes feature in App Volumes Manager. The exclusions will take effect after the user logs off and logs back in to the desktop.

The other options are not valid files for specifying exclusions for Writable Volumes:

config.ini: This file is used to configure the App Volumes agent settings, such as the App Volumes Manager address, the logging level, and the SSL certificate validation.

svservice.log: This file is used to record the App Volumes agent log messages, such as the agent status, the package attachment, and the error messages. json.cfg: This file does not exist in App Volumes. References: Writable Volume

Exclusions, Policy Files (snapvol.cfg) in App Volumes, and [VMware Horizon 8.x Professional Course]

Correct Answer: C

Explanation: 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.

References: Configuring VMware Integrated Printing, Enable or Disable Printing for a Desktop Pool, and [VMware Horizon 8.x Professional Course]

Correct Answer:

Correct Answer:

To correctly sequence the TLS Certificate Configuration Steps:

Get a new signed TLS certificate from a CA.Before making any modifications or importing the certificate, you'll first need to obtain a new signed TLS certificate from a Certificate Authority (CA). So, this should beStep 1.

Import the TLS certificate into the Windows local computer certificate store.After obtaining the new signed TLS certificate, the next logical step is to import this certificate into the Windows local computer certificate store. This would beStep 2.

Modify the certificates/ friendly names to vdm and reflect the current active certificate.Once the certificate is imported, the next step is to modify its friendly names to ensure the Horizon Service recognizes and uses this certificate. This

becomesStep 3.

Restart Horizon Service.Finally, after all the modifications and configurations are done, you should restart the Horizon Service to apply the changes. This isStep 4.

Correct Answer:

Correct Answer:

To monitor the advanced metrics of desktop sessions in Horizon Console, you need to use the Horizon Help Desk Tool. This is a web application that you can use to get the status of Horizon 8 user sessions and to perform troubleshooting

and maintenance operations1. You can also view performance details for a virtual or published desktop session that uses the PCoIP or VMware Blast display protocol2.

To access the Horizon Help Desk Tool, you need to click on the Monitoring tab on the left side of the Horizon Console. Then, you need to select Help Desk from the drop-down menu. This will open the Horizon Help Desk Tool in a new

browser tab. You can then search for a user, machine, or pool and view the session details. You can also click on More to see the advanced metrics such as latency, bandwidth, protocol, and frame rate1.