VMware 2V0-51.23 Online Practice Questions and Exam Preparation

VMware 2V0-51.23 Online Questions & Answers

• Question 61:

  An IT support center has been tasked with helping with Horizon desktop user issues.

  What is the minimal level of Horizon Console access they would need to perform this action?

  A. Help Desk Administrators
  B. Local Administrators
  C. Global Help Desk Administrators
  D. Inventory Administrators
  E. Administrators
  A. Help Desk Administrators

  ---

  Explanation/Reference:

  The minimal level of Horizon Console access that the IT support center would need to help with Horizon desktop user issues is the Help Desk Administrators role. This role allows the IT support center to view and troubleshoot user sessions,

  reset user passwords, send messages to users, and perform other help desk tasks. The Help Desk Administrators role can be assigned to users or groups on any access group that contains the desktop pools or farms that the IT support

  center needs to support. The other options are not the minimal level of Horizon Console access for this scenario:

  Local Administrators: This role allows full administration rights on a specific access group and its sub-access groups. This role can perform all the tasks of the Help Desk Administrators role, as well as create, edit, and delete desktop pools,

  farms, applications, entitlements, and other objects. This role is more than what the IT support center needs to help with user issues.

  Global Help Desk Administrators: This role allows full administration rights on all access groups in the Horizon environment. This role can perform all the tasks of the Local Administrators role, as well as create, edit, and delete access groups

  and global entitlements. This role is more than what the IT support center needs to help with user issues.

  Inventory Administrators: This role allows limited administration rights on a specific access group and its sub-access groups. This role can view and manage desktop pools, farms, applications, entitlements, and other objects, but cannot

  create or delete them. This role can also perform some help desk tasks, such as viewing user sessions and sending messages to users, but cannot reset user passwords or troubleshoot sessions. This role is not sufficient for what the IT

  support center needs to help with user issues.

  Administrators: This role allows full administration rights on all access groups in the Horizon environment, as well as global settings, licensing, roles and permissions, events configuration, and other system-wide settings. This role can perform

  all the tasks of theother roles, as well as configure and manage the Horizon infrastructure. This role is more than what the IT support center needs to help with user issues.

  References: Understanding Permissions and Access Groups and [VMware Horizon 8.x Professional Course]

• Question 62:

  An administrator configured a virtual machine to use an NVIDIA card but the virtual machine is not starting up. What could be the cause of the issue? (Choose two.)

  A. 3D graphics cannot be used with local storage.
  B. The Desktop Pool doesn't support 3D cards.
  C. No suitable host could be found.
  D. Not all memory has been reserved on the VM.
  E. Not all CPU has been reserved on the VM.
  C. No suitable host could be found.
  D. Not all memory has been reserved on the VM.

  ---

  Explanation/Reference:

  When configuring a virtual machine to use an NVIDIA graphics card, issues such as the VM not starting can occur if there is no suitable host available that meets the requirements for 3D graphics, or if not all memory required by the 3D graphics card has been reserved for the VM. Ensuring that the host has the necessary 3D graphics capabilities and that the VM is configured with reserved memory can resolve these issues.

• Question 63:

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

  A. Cloud Pod Architecture does not support Active Directory two-way trusts between domains.
  B. Cloud Pod Architecture is not supported with Unified Access Gateway appliances.
  C. Kiosk mode clients are not supported unless a workaround has been implemented.
  D. Cloud Pod Architecture cannot span multiple sites and data centers simultaneously.
  E. The Cloud Pod Architecture feature is not supported in an IPv6 environment.
  A. Cloud Pod Architecture does not support Active Directory two-way trusts between domains.
  C. Kiosk mode clients are not supported unless a workaround has been implemented.

  ---

  Explanation/Reference:

  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]

• Question 64:

  A Horizon administrator has been utilizing Application Profiler from Dynamic Environment Manager to create application-specific user defined settings. These files have grown to 2.3GB in size for a particular user and have negatively impacted the user experience.

  What can be done to the configuration to improve the user experience?

  A. Configure exclusions to filter out unnecessary folders.
  B. Change the default save path.
  C. Configure exclusions to filter out unnecessary registry entries.
  D. Use Deepest Registry Path.
  A. Configure exclusions to filter out unnecessary folders.

  ---

  Explanation/Reference:

  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

• Question 65:

  A Horizon Administrator is publishing an application which will be used by users across multiple Horizon pods and sites. Which feature of Global Entitlements are beneficial to this scenario?

  A. Applications can be hosted from multiple pods but a user sees only a single icon.
  B. Users must be explicitly assigned access to each application in each pod.
  C. Users can pick which pod delivers the application at launch.
  D. Applications do not have to be explicitly published from each pod.
  A. Applications can be hosted from multiple pods but a user sees only a single icon.

  ---

  Explanation/Reference:

  Global Entitlements in VMware Horizon allow for the aggregation of resources across multiple pods and sites into a single entitlement. This feature is particularly beneficial when publishing applications that are hosted across different pods, as it ensures that users see only one icon for the application, regardless of which pod it is hosted on, simplifying the user experience and administration of applications in a multi-pod Horizon environment.

• Question 66:

  HOTSPOT

  An administrator needs to monitor the advanced metrics of desktop sessions in Horizon Console.

  Mark where the administrator would navigate in the Horizon Console by clicking on it.

  Hot Area:

  

  

  ---

  Explanation/Reference:

  

  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.

• Question 67:

  DRAG DROP

  Drag and drop the appropriate firewall ports in support of the Blast Extreme protocol into the correct locations in the diagram on the right.

  Two options will not be used.

  Select and Place:

  

  

  ---

  Explanation/Reference:

• Question 68:

  Which three steps are required to entitle user and groups to pools? (Choose three.)

  A. Run the Active Directory entitlement script in the golden master, when preparing if for the pool.
  B. 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.
  C. 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.
  D. Navigate to Inventory > Desktops > check mark a pool > click on Add Entitlement.
  E. 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.
  B. 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.
  D. Navigate to Inventory > Desktops > check mark a pool > click on Add Entitlement.
  E. 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.

  ---

  Explanation/Reference:

  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

• Question 69:

  An administrator recently deployed a Horizon pod with external access using Unified Access Gateway (UAG).While trying to launch VDI from an External network, VDI launches with a black screen and then disconnects. The administrator has validated the port requirement and all other required ports are open. Users are able to connect internally using the connection server URL. While reviewing the UAG logs, the administrator found that the Blast connection is hitting the Connection Server instead of VDI IP.

  What should the administrator do to resolve the issue?

  A. Update the Blast External URL in UAG with port number.
  B. Upload the Blast Proxy Certificate in Horizon Edge Settings.
  C. Enable Tunnel in UAG.
  D. Disable the Tunnel and Gateways in Horizon Connection Server.
  D. Disable the Tunnel and Gateways in Horizon Connection Server.

  ---

  Explanation/Reference:

  The issue described indicates that the Horizon Connection Server is incorrectly handling traffic that should be directed to the Unified Access Gateway (UAG) and then to the VDI desktops. Disabling the Tunnel and Gateways settings on the Horizon Connection Server forces the UAG to handle the Blast traffic directly, ensuring that the connections are made to the VDI desktops' IP addresses, thus resolving the black screen and disconnection issue.

• Question 70:

  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?

  A. Edit the pool and select the Pre-Launch checkbox to start applications immediately after a user has authenticated to the Horizon Connection Server.
  B. Instead of the application pool being of the RDS Farm type, change the Application Pool type to Desktop Pool.
  C. This cannot be done. Published applications cannot start automatically after a user has authenticated to the Horizon Connection Server.
  D. Nothing needs to be done. Published applications start automatically after a user has authenticated to the Horizon Connection Server.
  A. Edit the pool and select the Pre-Launch checkbox to start applications immediately after a user has authenticated to the Horizon Connection Server.

  ---

  Explanation/Reference:

  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.