2024年08月 VMware 2V0-51.23実際にある問題と100%カバー率リアル試験問題
2V0-51.23無料試験問題と解答PDF最新問題2024年08月
VMware Horizon 8.x Professional Examsとしても知られるVMware 2V0-51.23試験は、VMware Horizon 8環境の実装、管理、トラブルシューティングのスキルと知識を検証したいITプロフェッショナル向けに設計されています。この認定試験は、仮想化とVMwareテクノロジーの強力な基盤を持ち、デスクトップとアプリケーションの仮想化の専門知識を拡大しようとしている個人を対象としています。
質問 # 49
How do multiple Horizon Connection Server instances in a pod maintain synchronization?
- A. Horizon Connection Server instances keep their data in an AD LDS database, which is automatically synchronized between the Connection Server.
- B. Horizon Connection Server instances keep their data in a local MySQL DB. The data is synchronized once every 24h.
- C. Horizon Connection Server instances keep their data in an Oracle database, which works as the central hub.
- D. Horizon Connection Server instances keep their data in an MS SQL database, which works as the central hub.
正解：A
解説：
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
質問 # 50
An organization with an existing Windows 2012 R2 Server RDSH farm decided to move to Windows Server
2019 as their new standard. Order the steps that need to be taken by the administrator to deploy a RDS desktop pool with this new standard.
正解：
解説：
Explanation:
To deploy a RDS desktop pool with the new standard of Windows Server 2019, the steps should be ordered as follows:
Prepare the Windows Server 2019 golden image. This is the first step because you'll need a prepared OS image to base your RDS desktop pool on.
Add an Automated Farm. Once your golden image is ready, you can set up an automated farm for the RDS desktop pool.
Add a RDS desktop pool. Using the automated farm and the prepared golden image, you can now add the RDS desktop pool.
Entitle AD users and/or groups. With the RDS desktop pool in place, the next step is to give Active Directory (AD) users and groups the necessary entitlements to access the desktops.
Launch Horizon Client and verify access to RDS desktop. As the final verification step, launch the Horizon Client to ensure that you can access the newly created RDS desktop pool and that everything is functioning as expected.
So, the sequential order is: Prepare the Windows Server 2019 golden image -> Add an Automated Farm -> Add a RDS desktop pool -> Entitle AD users and/or groups -> Launch Horizon Client and verify access to RDS desktop.
質問 # 51
Refer to the exhibit.
An administrator wants to configure a central SYSLOG server.
Mark the correct menu option by clicking on it.
正解：
解説：
質問 # 52
Refer to the exhibit.
An administrator is tasked with creating an instant clone pool for their sales department. During the creation of the pool the administrator saw that there is no golden image available, as seen in the exhibit.
Which two actions can an administrator take so that the golden image is showing up in the Golden Image selection window? (Choose two.)
- A. Login to the vSphere Client, select the Golden Image virtual machine and delete all snapshots.
- B. Login to the vSphere Client, select the Golden Image virtual machine and create a snapshot
- C. Login to the vSphere Client, select the Golden Image virtual machine and convert it to a template.
- D. Refresh the Select Golden Image view and select the Golden Image.
- E. Login to the vSphere Client, select the Golden Image virtual machine and clone it to a new virtual machine.
正解：B、C
解説：
Explanation
The administrator can take two actions to make the golden image show up in the Golden Image selection window. First, they can login to the vSphere Client, select the Golden Image virtual machine and create a snapshot. This will make the golden image available in the selection window. Second, they can login to the vSphere Client, select the Golden Image virtual machine and convert it to a template. This will also make the golden image available in the selection window.
A golden image is a virtual machine that contains the operating system, applications, and settings that are required for an instant clone desktop pool. To create an instant clone desktop pool, the administrator must select a golden image and a snapshot from the vSphere inventory. The snapshot must be taken after installing and configuring the Horizon Agent on the golden image1. If there is no snapshot or no template available, the golden image will not show up in the selection window.
The other options are not correct for this scenario:
Login to the vSphere Client, select the Golden Image virtual machine and delete all snapshots. This option is not correct because deleting all snapshots will not make the golden image show up in the selection window. In fact, it will prevent the administrator from creating an instant clone desktop pool, as a snapshot is required for instant cloning2.
Refresh the Select Golden Image view and select the Golden Image. This option is not correct because refreshing the view will not change the availability of the golden image in the selection window. The administrator must create a snapshot or a template of the golden image before it can be selected.
Login to the vSphere Client, select the Golden Image virtual machine and clone it to a new virtual machine. This option is not correct because cloning the golden image to a new virtual machine will not make it show up in the selection window. The administrator must still create a snapshot or a template of the cloned virtual machine before it can be selected.
References:
Preparing a Golden Image Virtual Machine for Instant-Clones
Snapshot vmdk files of the golden image used to publish Instant clone ...
Create an Automated Instant-Clone Desktop Pool
Instant Clone Desktop Pools
[VMware Horizon 8.x Professional]
質問 # 53
Which are the required permissions an administrator must assign to the user account for instant-clone operations in Active Directory before creating instant-clone desktop pools? (Choose three.)
- A. Create and Delete Child objects
- B. Create and Delete Computer Objects
- C. Read and Write All Properties
- D. List contents
- E. Write to service principal names
- F. Modify Owner
正解：A、B、C
解説：
For instant-clone operations in Active Directory, the user account used by VMware Horizon needs specific permissions to manage computer objects effectively. These include the ability to create and delete child objects and computer objects, as well as read and write all properties of those objects. These permissions ensure that Horizon can create, modify, and clean up computer accounts associated with instant clones, facilitating seamless desktop provisioning and management.
質問 # 54
When integrating a Linux OS based desktop into Active Directory, which three of the following can be used?
(Choose three.)
- A. Windows Domain Join
- B. OpenLDAP Server Pass-through authentication
- C. Winbind Domain Join
- D. System Security Services Daemon (SSSD) LDAP authentication against the AD
- E. OpenLDAP Server Cut-through authentication
正解：A、C、D
解説：
Integrating a Linux OS-based desktop into Active Directory can be achieved using Winbind for domain joining and authentication, Windows Domain Join through tools like Samba, and System Security Services Daemon (SSSD) for LDAP authentication against Active Directory. These methods enable Linux desktops to participate in a Windows-centric environment, allowing for centralized authentication and management.
質問 # 55
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.
正解：
解説：
Explanation:
VMware Horizon Client Configuration
質問 # 56
Which three steps are required to entitle user and groups to pools? (Choose three.)
- A. 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.
- C. Run the Active Directory entitlement script in the golden master, when preparing if for the pool.
- D. Navigate to Inventory > Desktops > check mark a pool > click on Add Entitlement.
- E. 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.
正解：A、B、D
解説：
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
質問 # 57
An administrator is creating an instant clone desktop pool and needs to enable NVIDIA Grid 3D Rendering.
NVIDIA GRID vGPU and drivers are installed on the physical ESXi hosts.
In Horizon Console, when creating an instant-clone pool, the NVIDIA GRID vGPU option is not available in the 3D Render field.
Which two of the following could be the reason for the issue? (Choose two.)
- A. Horizon 8 does not have an explicit 3D renderer option for instant clone. Select Manage Using vSphere Client in the 3D Render field. Instant-clones inherit the settings configured in the vSphere Client for the golden image.
- B. The administrator has selected Shared when editing the Host Graphics Settings for the ESXi host in the vCenter Server.
- C. In Horizon Console, when an instant-clone pool is created, the golden image and snapshot that the administrator selected has not been configured for NVIDIA GRID vGPU.
- D. The administrator has selected Shared Direct when editing the Host Graphics Settings for the ESXi host in the vCenter Server.
- E. Instant-clone pools do not support NVIDIA GRID vGPU.
正解：A、C
解説：
To enable an instant-clone pool to use NVIDIA GRID vGPU, the administrator needs to do the following:
Install NVIDIA GRID vGPU in the physical ESXi hosts and select Shared Direct in the Host Graphics Settings12.
Prepare a golden image with NVIDIA GRID vGPU configured, including selecting the vGPU profile to use12.
Take a snapshot of the golden image12.
In Horizon Console, when creating an instant-clone pool, select Manage Using vSphere Client in the 3D Render field. Instant-clones inherit the settings configured in the vSphere Client for the golden image12.
Therefore, the possible reasons for the issue are:
The administrator has selected Shared instead of Shared Direct when editing the Host Graphics Settings for the ESXi host in the vCenter Server. This option is for vSGA, not vGPU3.
The golden image and snapshot that the administrator selected has not been configured for NVIDIA GRID vGPU. The administrator needs to verify that the correct vGPU profile is selected and that the NVIDIA drivers are installed in the golden image4.
The other options are not valid because:
Horizon 8 does have an explicit 3D renderer option for instant clone, but it is Manage Using vSphere Client, not NVIDIA GRID vGPU12.
Instant-clone pools do support NVIDIA GRID vGPU as long as the ESXi hosts and the golden image are properly configured12.
References := 1: VMware Horizon 8 Documentation: Enable NVIDIA GRID vGPU for Instant-Clone Pools 2:
VMware Horizon 8 Documentation: Configuring 3D Rendering for Automated Instant Clone Farms 3:
VMware Horizon 8 Documentation: Types of Graphics Acceleration 4: VMware Horizon 8 Documentation: Prepare a Virtual Machine to Use Accelerated 3D Graphics
質問 # 58
Having configured two standalone Horizon pods, what steps should be taken to join them in a Cloud Pod Architecture (CPA) deployment?
- A. Initialize the CPA on both Pods. On the second pod, sync the CPA. On one pod, create Global Entitlements, and add local pools from each pod.
- B. On one pod, initialize the CPA. On the second pod, join the CPA. On one pod, create Cloud Entitlements, and sync pools from each pod. Initialize the CPA on both Pods.
- C. On one pod, initialize the CPA. On the second pod, join the CPA. On one pod, create Global Entitlements, and add local pools from each pod.
- D. On the second pod, sync the CPA. On one pod, create Cloud Entitlements, and add local pools from each pod.
正解：C
解説：
Explanation
To join two standalone Horizon pods in a Cloud Pod Architecture (CPA) deployment, the administrator needs to perform the following steps:
On one pod, initialize the CPA. This step creates a pod federation and enables global data replication among all pods in the federation. The pod that initializes the CPA becomes the first pod in the federation67.
On the second pod, join the CPA. This step adds an existing standalone pod to an existing pod federation. The pod that joins the CPA inherits the global data from the federation89.
On one pod, create Global Entitlements, and add local pools from each pod. This step allows users to access desktops or applications from any pod in the federation based on their entitlements and load-balancing policies .
The other options are not correct or complete because:
Initializing the CPA on both pods is not necessary or possible. Only one pod can initialize the CPA and create a pod federation. The other pods must join an existing pod federation68.
Syncing the CPA on the second pod is not a valid step. Syncing is a process that occurs automatically among all pods in a pod federation to ensure data consistency and availability.
Creating Cloud Entitlements is not a valid term. The correct term is Global Entitlements, which are used in CPA to entitle users to desktops or applications across multiple pods.
References := 6: VMware Horizon 8 Documentation: Initialize Cloud Pod Architecture 7: VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8 8: VMware Horizon 8 Documentation:
Join a Pod to an Existing Pod Federation 9: VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8 : VMware Horizon 8 Documentation: Create a Global Entitlement : VMware Horizon 8Documentation: Understanding Global Entitlements in Cloud Pod Architecture : VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8
質問 # 59
An administrator is tasked with creating a new pool of desktops with hardware-accelerated graphics with vMotion support. Which graphic acceleration types can the administrator choose to meet the requirement?
- A. Virtual Shared 3D rendering
- B. Virtual Dedicated Graphics Acceleration
- C. Virtual Shared Pass-through Graphics Acceleration
- D. Virtual Shared Direct access 3D
正解：C
質問 # 60
Which of the following components enables central communication, management, and configuration of multiple ESXi servers?
- A. VMware DEM (Dynamic Environment Manager)
- B. VMware Horizon View
- C. VMware vCenter Server
- D. VMware Remote Console
正解：C
解説：
VMware vCenter Server is the central management component for ESXi servers, allowing administrators to manage multiple ESXi hosts and virtual machines (VMs) from a single console. It provides essential management capabilities, including resource allocation, performance monitoring, and centralized access control, making it the cornerstone for managing a VMware virtualized infrastructure.
質問 # 61
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. Use Deepest Registry Path.
- B. Configure exclusions to filter out unnecessary registry entries.
- C. Change the default save path.
- D. Configure exclusions to filter out unnecessary folders.
正解：D
解説：
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
質問 # 62
Refer to the exhibit.
An administrator wants the current site to be designated as the Home Site for a user.
Mark the menu option on the left that will allow the administrator to assign home sites by clicking on it.
正解：
解説：
Explanation:
In VMware Horizon, to designate a Home Site for a user, you would use the "Cloud Pod Architecture" feature, which allows you to set home sites and manage global entitlements across multiple pods and sites in a Horizon environment.
In the exhibit's menu on the left, you should click on "Cloud Pod Architecture" to proceed with designating a Home Site for a user.
質問 # 63
Which two of the following are features of VMware Horizon Agent for Linux? (Choose two.)
- A. location based printing
- B. USB redirection
- C. session collaboration
- D. display protocol PCoIP
- E. installation registration requirement
正解：B、D
質問 # 64
Refer to the exhibit.
Drag and drop the ports on the left to allow an external PCoIP connection through Unified Access Gateway (UAG) into the diagram on the right.
正解：
解説：
質問 # 65
Which three steps are required to entitle user and groups to pools? (Choose three.)
- A. 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.
- C. Run the Active Directory entitlement script in the golden master, when preparing if for the pool.
- D. Navigate to Inventory > Desktops > check mark a pool > click on Add Entitlement.
- E. 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.
正解：A、B、D
解説：
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 for Horizon Connection Server 7: VMware Horizon 8 Documentation: Create an Automated Desktop Pool
質問 # 66
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. Printing is disabled in the Horizon Desktop Pool.
- B. Port TCP 9427 is disabled.
- C. The VMware Integrated Printing feature is not installed in the Horizon Client.
- D. Port TCP 32111 is disabled.
正解：A
解説：
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]
質問 # 67
What are the steps to create a custom role?
- A. In the navigation pane under the Settings section click on Administrators > Entitlements > Add. Once the add Role pane opens, add a name for the role and select the specific privileges.
- B. In the navigation pane under the Settings section dick on Administrators > Roles and Permission > Add.
Once the Add Role pane opens, add a name for the role and select the specific privileges. - C. In the navigation pane under the Settings section click on Administrators > Users and Groups > Add.Once the Add Role pane opens, add a name for the role and select the specific privileges.
- D. In the navigation pane under the Settings section click on Administrators > Roles and Permission > Users and groups > Add. Once the Add Role pane opens, add a name for the role and select the specific privileges.
正解：B
解説：
Explanation
Roles and permissions are a way of controlling the access and actions of administrators and users in Horizon.
By default, Horizon provides two predefined roles: Administrators and Read Only Administrators. However, a high-level administrator can create custom roles with specific privileges to suit different needs and scenarios.
To create a custom role, the administrator needs to follow these steps:
In the navigation pane under the Settings section, click on Administrators > Roles and Permissions.
In the Roles and Permissions page, click on Add.
In the Add Role pane, enter a name for the role in the Role Name text box.
In the Privileges section, select the checkboxes for the privileges that you want to assign to the role. You can expand or collapse the categories to view or hide the sub-privileges. You can also use the Select All or Deselect All buttons to select or clear all the privileges in a category.
Click on Save to create the custom role.
The custom role will appear in the Roles and Permissions page, where you can edit or delete it as needed. You can also assign the custom role to users or groups in the Users and Groups page. References: [Create Custom Roles] and [VMware Horizon 8.x Professional Course]
質問 # 68
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. Persona Management
- C. Flexible profiles
- D. VMware App Volumes Writeable Volumes
- E. Roaming Profiles
正解：A、B、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.
References: Writable Volumes Overview, Configuring User Profiles with Horizon Persona Management, VMware Dynamic Environment Manager Overview, and [VMware Horizon 8.x Professional Course]
質問 # 69
Adobe Acrobat 11 has been assigned to a user. VM25 already has Adobe Acrobat 11 and is natively installed.
What happens when the user logs on to VM25?
- A. Although a shortcut to the App Volume package is created on the user desktop, the application does not get attached to VM25.
- B. A shortcut to the user-assigned application is created on the user desktop, and when they click on the shortcut, the application gets attached to VM25.
- C. The App Volume package does not get attached because the natively installed application has priority.
- D. The user-assigned application is attached to VM25. When the user clicks on the application shortcut, the App Volume package for Adobe Acrobat 11 is opened.
正解：D
解説：
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]
質問 # 70
End-users are complaining that they are frequently being asked for credentials when opening additional apps.
Which step should the administrator take to resolve the issue?
- A. Configure SSO Timeout by modifying the Global Settings in Horizon Administrator.
- B. Configure Session Timeout by modifying the Client Settings in Horizon Client.
- C. Configure Desktop Timeout by modifying the Pool Settings in Horizon Administrator.
- D. Configure a time limit by modifying the Horizon GPO.
正解：A
解説：
Explanation
Single sign-on (SSO) is a feature that allows users to log in to Horizon Client once and launch remote desktops and applications without being prompted for credentials again. SSO is enabled by default and can be configured in the Global Settings of Horizon Administrator. One of the settings is SSO Timeout, which determines how long the user's credentials are cached before they expire. If the SSO Timeout is too short, users might be frequently asked for credentials when opening additional apps. To resolve this issue, the administrator can increase the SSO Timeout value or set it to -1, which means that no SSO timeout limit is set. References: Global Settings for Client Sessions in Horizon Console and [VMware Horizon 8.x Professional Course]
https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-console-administration/GUID-E2A7CA32-193D-
質問 # 71
Refer to the exhibit.
Drag and drop the components on the left that are part of the logical architecture for a single-site deployment of VMware Horizon into their correct position in the diagram on the right.
正解：
解説：
Explanation
質問 # 72
Adobe Acrobat 11 has been assigned to a user. VM25 already has Adobe Acrobat 11 and is natively installed.
What happens when the user logs on to VM25?
- A. Although a shortcut to the App Volume package is created on the user desktop, the application does not get attached to VM25.
- B. A shortcut to the user-assigned application is created on the user desktop, and when they click on the shortcut, the application gets attached to VM25.
- C. The App Volume package does not get attached because the natively installed application has priority.
- D. The user-assigned application is attached to VM25. When the user clicks on the application shortcut, the App Volume package for Adobe Acrobat 11is opened.
正解：D
解説：
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]
質問 # 73
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 450 active session are logged off immediately.
- B. All active sessions will stay connected, because HTTPS Secure Tunnel and Blast Secure Gateway are disabled.
- C. Only the active sessions from the failed Connection Server are disconnected, because HTTPS Secure Tunnel is disabled.
- D. All 450 active sessions are disconnected, and have to re-connect again by the end-user.
正解：C
解説：
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]
質問 # 74
......
VMware 2V0-51.23リアル2024年最新のブレーン問題集模擬試験問題集：https://jp.fast2test.com/2V0-51.23-premium-file.html