[Feb 09, 2024] Get Up-To-Date Real Exam Questions for 2V0-51.23 with New Materials
Updated 2V0-51.23 Certification Exam Sample Questions
NEW QUESTION # 11
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.
Answer:
Explanation:
Explanation
VMware Horizon Client Configuration
NEW QUESTION # 12
Which two of the following are features of VMware Horizon Agent for Linux? (Choose two.)
- A. location based printing
- B. installation registration requirement
- C. USB redirection
- D. session collaboration
- E. display protocol PCoIP
Answer: C,E
NEW QUESTION # 13
Refer to the exhibit.
Drag and drop the labels on the left into their correct location in the diagram of VMware Horizon Architecture on the right.
Answer:
Explanation:
Explanation
NEW QUESTION # 14
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?
- A. Category Folder
- B. Access Groups
- C. Global Entitlements
- D. Global Policies
Answer: B
Explanation:
Explanation
Access groups are a way of organizing and delegating the administration of machines, desktop pools, application pools, and farms in Horizon. By default, all these objects reside in the root access group, which appears as / or Root (/) in Horizon Console. A high-level administrator can create sub-access groups under the root access group and assign different permissions to different administrators for each access group. For example, a high-level administrator can create an access group called RDS Farms and assign the Inventory Administrators role to a junior-level administrator for that access group. This way, the junior-level administrator can see and manage all the RDS farms that are in the RDS Farms access group, but not the ones that are in other access groups or the root access group. Therefore, to correct the issue of a junior-level administrator not being able to see all RDS farms, a high-level administrator needs to make changes to the access groups and the permissions associated with them. References: Understanding Permissions and Access Groups and [VMware Horizon 8.x Professional Course]
NEW QUESTION # 15
Which vCenter privileges are required only for instant clones VMs with a Trusted Platform Module (vTPM) device?
- A. Configure Host USB device
- B. Manage custom attributes
- C. Manage KM5
- D. Upgrade virtual machine compatibility
Answer: C
Explanation:
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]
NEW QUESTION # 16
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.)
- A. VMware Dynamic Environment Manager
- B. VMware App Volumes Writeable Volumes
- C. Roaming Profiles
- D. Flexible profiles
- E. Persona Management
Answer: A,B,E
Explanation:
Explanation
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 thisproblem, 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.
References: Writable Volumes Overview, Configuring User Profiles with Horizon Persona Management, VMware Dynamic Environment Manager Overview, and [VMware Horizon 8.x Professional Course]
NEW QUESTION # 17
Which three of the following are benefits of using Virtual Machines? (Choose three.)
- A. Independent of physical hardware.
- B. Bound to a specific set of hardware components.
- C. Easy to move or copy.
- D. Faster to provision.
- E. Difficult to move or copy.
Answer: A,C,D
Explanation:
Explanation
One of the benefits of using virtual machines is that they are independent of physical hardware. This means that they can run on any compatible host machine, regardless of the underlying hardware components. This also enables them to be migrated, moved, or copied easily from one host to another, without requiring any reconfiguration or installation. This enhances the flexibility and portability of virtual machines, as well as their availability and disaster recovery.
Another benefit of using virtual machines is that they are faster to provision than physical machines. This is because they can be created from templates or snapshots, which contain preconfigured operating systems and applications. This reduces the time and effort needed to install and configure software on each machine.
Moreover, virtual machines can be cloned or duplicated quickly, allowing for rapid scaling and deployment of multiple identical instances.
References :=
Virtual Machines Overview
Creating and Provisioning Virtual Machines
Migrating Virtual Machines
NEW QUESTION # 18
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?
- A. Enable Video Card 3D Graphics.
- B. Set Memory Shares to High.
- C. Reserve all guest memory.
- D. Disable CPU Hot Plug.
Answer: C
Explanation:
Explanation
To enable a virtual machine to power on with a PCI graphics accelerator, such as a GPU, attached to it, the administrator needs to reserve all guest memory for that virtual machine. This is because PCI devices require direct memory access (DMA) to function properly, and memory overcommitment can interfere with DMA operations. Reserving all guest memory ensures that no memory swapping or ballooning occurs on the virtual machine, and that the memory address space is contiguous and available for DMA56.
The other options are not required or valid because:
Enabling Video Card 3D Graphics is not necessary for using a PCI graphics accelerator. This option is for using software-accelerated graphics or virtual shared graphics acceleration (vSGA) on a virtual machine7.
Setting Memory Shares to High does not guarantee that all guest memory will be reserved. Memory shares only affect how memory resources are distributed amongcompeting virtual machines when there is memory contention on the host. Memory shares do not prevent memory overcommitment or swapping.
Disabling CPU Hot Plug does not affect the use of a PCI graphics accelerator. CPU Hot Plug allows adding or removing virtual CPUs from a powered-on virtual machine. It has no relation to PCI devices or DMA operations.
References := 5: VMware vSphere 7 Documentation: Add a PCI Device to a Virtual Machine 6: VMware Knowledge Base: Enabling DirectPath I/O causes virtual machines to fail to power on (1010789) 7: VMware Workstation Pro Documentation: Prepare a Virtual Machine to Use Accelerated 3D Graphics : VMware vSphere Resource Management Documentation: Memory Resource Management : VMware vSphere Virtual Machine Administration Documentation: Hot Add Memory and CPU Resources
NEW QUESTION # 19
Which three VMware Horizon based resources does Unified Access Gateway (UAG) provide access to?
(Choose three.)
- A. thin clients
- B. virtual desktops
- C. physical Windows machines
- D. IOT devices
- E. RDSH-based applications
Answer: B,C,E
Explanation:
Explanation
Unified Access Gateway (UAG) is a secure gateway appliance that provides access to VMware Horizon based resources such as virtual desktops, RDSH-based applications, and physical Windows machines. UAG supports multiple authentication methods and protocols, such as SAML, OAuth, and RADIUS, to provide secure access to end users from any device and location. UAG also provides edge services such as load balancing, high availability, and firewall rules to optimize the performance and availability of Horizon based resources12. References := 1: VMware Horizon Architecture Planning: Unified Access Gateway 2: VMware Unified Access Gateway Administration Guide: Introduction to Unified Access Gateway
NEW QUESTION # 20
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?
- A. All active sessions will stay connected, because HTTPS Secure Tunnel and Blast Secure Gateway are disabled.
- B. All 450 active sessions are disconnected, and have to re-connect again by the end-user.
- C. All 450 active session are logged off immediately.
- D. Only the active sessions from the failed Connection Server are disconnected, because HTTPS Secure Tunnel is disabled.
Answer: D
Explanation:
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.
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]
NEW QUESTION # 21
Refer to the exhibit.
Drag and drop the ports on the left to allow an external Blast Extreme connection through Unified Access Gateway (UAG) into the diagram on the right.
Answer:
Explanation:
Explanation
NEW QUESTION # 22
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?
- A. Port TCP 32111 is disabled.
- B. Printing is disabled in the Horizon Desktop Pool.
- C. The VMware Integrated Printing feature is not installed in the Horizon Client.
- D. Port TCP 9427 is disabled.
Answer: B
Explanation:
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]
NEW QUESTION # 23
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.)
- A. The Horizon DRS setting for fully automated vSphere load balancing.
- B. The use custom script setting for customized RDSH load balancing.
- C. The Include Session Count setting to include the session count on the RDSH for load balancing.
- D. The floating dynamic host profile setting, created in the vSphere profile section.
Answer: B,C
Explanation:
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]
NEW QUESTION # 24
Drag and drop each Horizon console predefined role on the left to its matching function on the right.
Answer:
Explanation:
Explanation
The following is the correct answer for the drag and drop question:
Administrator -> Performs all desktop, session, and pool-related operation.
Inventory Administrator -> Performs all administrative functions and applies to an Access Group.
Local Administrator -> No rights to manage Cloud Pod or the Global Data Layer.
Predefined Administrator Roles (vmware.com)
The predefined administrator roles in Horizon console are designed to provide different levels of access and control over the Horizon environment. Each role has a set of privileges that grant the ability to perform specific actions or view certain information. You can assign these roles to users or groups on the root access group, which gives them access to all inventory objects in the system, or on a specific access group or federation access group, which limits their scope to the objects within that group. You cannot modify the predefined roles, but you can create custom roles by selecting individual privileges.
The Administrator role is the most powerful role in Horizon console. It allows the user to perform all administrative operations, including creating and managing desktop pools, sessions, farms, applications, global settings, and other administrators. In a Cloud Pod Architecture environment, this role also enables the user to configure and manage a pod federation and manage remote pod sessions. The Administrator role on the root access group is equivalent to a super user role, as it gives full access to everything in the system. Therefore, you should assign this role to a limited number of users.
The Inventory Administrator role is similar to the Administrator role, but it applies only to an access group.
This means that the user can perform all administrative functions on the inventory objects that belong to that access group, such as desktop pools, farms, applications, and sessions. However, the user cannot manage global settings or other administrators. This role is useful for delegating administration of specific resources to different users or groups.
The Local Administrator role is a restricted version of the Inventory Administrator role. It applies only to an access group and does not grant any rights to manage Cloud Pod Architecture features or the Global Data Layer. This means that the user can only manage local inventory objects within that access group, such as desktop pools, farms, applications, and sessions. This role is suitable for administrators who do not need to access or modify global settings or cross-pod resources.
The Help Desk Administrator role is a specialized role that allows the user to perform desktop and application actions for troubleshooting and support purposes. These actions include shutting down, resetting, restarting, logging off, disconnecting, and sending messages to users' desktops or applications. The user can also perform remote assistance actions such as ending processes or viewing system information for a user's desktop or application. The user cannot create or modify any inventory objects or settings with this role.
References :=
Some possible references are:
Predefined Administrator Roles
Assigning Administrator Roles
Understanding Roles and Privileges
NEW QUESTION # 25
An administrator needs to enable Session Collaboration in the VMware Horizon environment. What will be used as a requirement to enable Session Collaboration?
- A. PCoIP protocol
- B. dedicated Instant Clone pool
- C. BLAST protocol
- D. floating Instant Clone pool
Answer: C
Explanation:
Explanation
Collaboration is a feature that allows users to invite other users to join an existing Windows or Linux remote desktop session with both screen sharing and audio out features enabled. A remote desktop session that is shared in this way is called a collaborative session. The user that shares a session with another user is called the session owner, and the user that joins a shared session is called a session collaborator. A Horizon administrator must enable the Session Collaboration feature for the desktop pool or farm that contains the remote desktops that support collaboration.
One of the requirements to enable Session Collaboration is to use the VMware Blast display protocol for the remote desktops. VMware Blast is a protocol that provides high-performance, high-quality graphics and multimedia delivery over LAN or WAN networks. VMware Blast supports Session Collaboration by allowing multiple users to view and interact with the same remote desktop session simultaneously. Other display protocols, such as PCoIP or RDP, do not support Session Collaboration and will not allow users to share or join collaborative sessions.
Therefore, to enable Session Collaboration in the VMware Horizon environment, the administrator needs to use the BLAST protocol as arequirement. References: Configuring Session Collaboration, Sharing Remote Desktop Sessions, and [VMware Horizon 8.x Professional Course]
NEW QUESTION # 26
How does an administrator enable debug logging for a single user in VMware Dynamic Environment Manager?
- A. Create an empty FlexDebug.log file in the log folder.
- B. Create an empty FlexDebug.txt file in the log folder.
- C. Configure the FlexEngine GPO to DEBUG.
- D. Update the FlexEngine registry to DEBUG.
Answer: B
Explanation:
Explanation
To enable debug logging for a single user in VMware Dynamic Environment Manager, the administrator needs to create an empty FlexDebug.txt file in the same folder as the standard log file for this user. This will trigger FlexEngine to switch to debug logging for this particular user1. Debug logging is useful for troubleshooting purposes, as it provides more detailed information about the FlexEngine operations and actions1.
The other options are not correct because:
Updating the FlexEngine registry to DEBUG will not enable debug logging for a single user, but for all users who log on to the same computer. This option can only be set through Group Policy settings and applies to all users1. Moreover, this option is not recommended, as it can cause performance issues and disk space consumption due to the large size of the log files1.
Creating an empty FlexDebug.log file in the log folder will not enable debug logging for a single user, as the file name must be exactly FlexDebug.txt. The file extension must be .txt, not .log1.
Configuring the FlexEngine GPO to DEBUG will not enable debug logging for a single user, but for all users who are affected by the GPO. This option can only be set through Group Policy settings and applies to all users1. Moreover, this option is not recommended, as it can cause performance issues and disk space consumption due to the large size of the log files1.
References:
Enabling debug logging for a single user in VMware Dynamic Environment Manager1
NEW QUESTION # 27
Refer to the exhibit.
An administrator wants to configure a central SYSLOG server.
Mark the correct menu option by clicking on it.
Answer:
Explanation:
NEW QUESTION # 28
An administrator is preparing to upgrade Horizon Connection Servers in parallel.
What action must first be performed to ensure that there are no issues with Horizon LDAP replication within the Pod?
- A. Execute ViewDBChk.cmd --scanMachines.
- B. Execute repadmin.exe/showrepl localhost:389.
- C. Execute vdmadmin.exe -S.
- D. Execute vdmexport.exe -f Myexport.lDF.
Answer: B
Explanation:
Explanation
The action that must first be performed to ensure that there are no issues with Horizon LDAP replication within the Pod is to execute repadmin.exe/showrepl localhost:389. This command will display the replication status of the local Connection Server instance and show any errors or warnings that might affect the replication process1. The administrator should run this command on each Connection Server instance in the Pod before upgrading them in parallel, and resolve any issues that are reported.
The other options are not valid or feasible because:
Executing ViewDBChk.cmd --scanMachines will not check the Horizon LDAP replication status, but rather scan the vCenter Server inventory for virtual machines that are managed by Horizon and report any inconsistencies or errors2. This command is useful for troubleshooting virtual machine issues, but not for verifying LDAP replication.
Executing vdmexport.exe -f Myexport.lDF will not check the Horizon LDAP replication status, but rather export the Horizon LDAP configuration data to a file named Myexport.lDF3. This command is useful for backing up or restoring the Horizon LDAP data, but not for verifying LDAP replication.
Executing vdmadmin.exe -S will not check the Horizon LDAP replication status, but rather display the health status of the Connection Server instances in the Pod4. This command is useful for monitoring the Connection Server performance and availability, but not for verifying LDAP replication.
References:
Repadmin Examples1
ViewDBChk Tool2
Back Up Horizon Configuration Data3
Display Health Status Information4
NEW QUESTION # 29
Which three steps are required to entitle user and groups to pools? (Choose three.)
- A. During pool creation in the entitlement pane, click on add, search for users and groups in the Active Directory, continue and finish the pool creation.
- B. Navigate to Inventory > Desktops > check mark a pool > click on Add Entitlement.
- C. Navigate to Users and Groups > Entitlements > click on Entitlements > click on Add Entitlements, search for users and groups in the Users pane and add the desired desktop pool in the next pane Desktop Pools.
- D. During the Pool creation the desired Active Directory OU for the VMs will be specified. This will automatically add the preconfigured associated user group to the Horizon entitlements.
- E. Run the Active Directory entitlement script in the golden master, when preparing if for the pool.
Answer: A,B,C
Explanation:
Explanation
To entitle users and groups to pools, you need to perform the following steps:
During pool creation in the entitlement pane, click on add, search for users and groups in the Active Directory, continue and finish the pool creation. This option allows you to entitle users and groups to a desktop or application pool at the same time as you create the pool3.
Navigate to Inventory > Desktops > check mark a pool > click on Add Entitlement. This option allows you to add entitlements to an existing desktop or application pool after you create the pool4.
Navigate to Users and Groups > Entitlements > click on Entitlements > click on Add Entitlements, search for users and groups in the Users pane and add the desired desktop pool in the next pane Desktop Pools. This option allows you to review and manage the entitlements for users and groups from a single location5.
The other options are not required or valid for entitling users and groups to pools. Running the Active Directory entitlement script in the golden master is not necessary as Horizon 8 automatically synchronizes with Active Directory domains that are configured in Horizon Console6. Specifying the desired Active Directory OU for the VMs during pool creation does not automatically add the preconfigured associated user group to the Horizon entitlements as you still need to select the users or groups from the search results7. References := 3: VMware Horizon 8 Documentation: Add Entitlements During Pool Creation 4:
VMware Horizon 8 Documentation: Add Entitlements After Pool Creation 5: VMware Horizon 8 Documentation: Review and Manage Entitlements 6: VMware Horizon 8 Documentation: Active Directory Requirements forHorizon Connection Server 7: VMware Horizon 8 Documentation: Create an Automated Desktop Pool
NEW QUESTION # 30
How do multiple Horizon Connection Server instances in a pod maintain synchronization?
- A. Horizon Connection Server instances keep their data in an MS SQL database, which works as the central hub.
- B. Horizon Connection Server instances keep their data in an Oracle database, which works as the central hub.
- C. Horizon Connection Server instances keep their data in a local MySQL DB. The data is synchronized once every 24h.
- D. Horizon Connection Server instances keep their data in an AD LDS database, which is automatically synchronized between the Connection Server.
Answer: D
Explanation:
Explanation
Horizon Connection Server instances keep their data in an AD LDS database, which is automatically synchronized between the Connection Server. AD LDS is a Lightweight Directory Access Protocol (LDAP) directory service that provides flexible support for directory-enabled applications, without the dependencies that are required for Active Directory Domain Services (AD DS). AD LDS provides much of the same functionality as AD DS, but it does not require the deployment of domains or domain controllers. In a Horizon environment, each Connection Server instance has a copy of the AD LDS database and replicates changes to other Connection Server instances in the same pod. This ensures that the Connection Server instances have consistent and up-to-date information about the Horizon resources and user sessions12 References:
Configuring Horizon Connection Server1
Understanding VMware Horizon Services2
NEW QUESTION # 31
......
2V0-51.23 Study Guide Cover to Cover as Literally: https://www.prep4king.com/2V0-51.23-exam-prep-material.html
Get Unlimited Access to 2V0-51.23 Certification Exam Cert Guide: https://drive.google.com/open?id=1UFK4950VZjafMjwX7JEh8vtCFhQEF_dw
