Question #1
To reduce the risk of users downloading malware to the corporate network, an administrator wants to
allow end-users to open only intranet websites inside their virtual desktop. Additionally, the administrator wants to configure all other URLs to automatically open in a browser on the end-user’s client machine.
Which steps should the administrator take to meet the requirements? (Choose two.)
- A . Enable the URL Content Redirection feature in Horizon Agent.
- B . Disable the Allow External Website feature in Horizon Agent.
- C . Enable secure website settings in the Global Settings Security menu.
- D . Configure group policy settings to indicate how Horizon Agent redirects the URL
- E . Enable the URL Content Redirection feature on the desktop pool settings.
Correct Answer: AD
AD
Explanation:
The URL Content Redirection feature allows administrators to configure specific URLs to open on the client machine or in a remote desktop or published application. This can help reduce the risk of users downloading malware to the corporate network, as well as improve the user experience and performance of certain web applications.
To meet the requirements of the scenario, the administrator needs to enable the URL Content Redirection feature in Horizon Agent when installing or upgrading it on the instant-clone desktops. This will allow Horizon Agent to send or receive URLs from Horizon Client, depending on the redirection direction. The administrator also needs to configure group policy settings to indicate how Horizon Agent redirects the URL. Specifically, the administrator needs to enable agent-to-client redirection, which means that Horizon Agent sends the URL to Horizon Client, which opens the default application for the protocol in the URL on the client machine. The administrator also needs to specify which URLs are redirected from a remote desktop to a client, and which URLs are not redirected. In this case, the administrator needs to configure a whitelist of intranet websites that are allowed to open inside the virtual desktop, and a blacklist of all other websites that are automatically redirected to a browser on the client machine.
The other options are not relevant or sufficient for meeting the requirements. Disabling the Allow External Website feature in Horizon Agent will prevent users from accessing any external websites from their virtual desktops, which might not be desirable or practical. Enabling secure website settings in the Global Settings
Security menu will not affect how URLs are redirected, but only how secure connections are established between Horizon components. Enabling the URL Content Redirection feature on the desktop pool settings will not work unless it is also enabled in Horizon Agent and configured with group policy settings.
References: Configuring URL Content Redirection and [VMware Horizon 8.x Professional Course]
AD
Explanation:
The URL Content Redirection feature allows administrators to configure specific URLs to open on the client machine or in a remote desktop or published application. This can help reduce the risk of users downloading malware to the corporate network, as well as improve the user experience and performance of certain web applications.
To meet the requirements of the scenario, the administrator needs to enable the URL Content Redirection feature in Horizon Agent when installing or upgrading it on the instant-clone desktops. This will allow Horizon Agent to send or receive URLs from Horizon Client, depending on the redirection direction. The administrator also needs to configure group policy settings to indicate how Horizon Agent redirects the URL. Specifically, the administrator needs to enable agent-to-client redirection, which means that Horizon Agent sends the URL to Horizon Client, which opens the default application for the protocol in the URL on the client machine. The administrator also needs to specify which URLs are redirected from a remote desktop to a client, and which URLs are not redirected. In this case, the administrator needs to configure a whitelist of intranet websites that are allowed to open inside the virtual desktop, and a blacklist of all other websites that are automatically redirected to a browser on the client machine.
The other options are not relevant or sufficient for meeting the requirements. Disabling the Allow External Website feature in Horizon Agent will prevent users from accessing any external websites from their virtual desktops, which might not be desirable or practical. Enabling secure website settings in the Global Settings
Security menu will not affect how URLs are redirected, but only how secure connections are established between Horizon components. Enabling the URL Content Redirection feature on the desktop pool settings will not work unless it is also enabled in Horizon Agent and configured with group policy settings.
References: Configuring URL Content Redirection and [VMware Horizon 8.x Professional Course]
Question #2
Drag and drop each Desktop Persistence type on the left to its matching description on the right.
Correct Answer:
Question #3
What are two best practices for Windows Golden Image Optimization? (Choose two.)
- A . Activate Windows OS paging.
- B . Turn on automatic Windows maintenance (scheduled tasks).
- C . Turn on automatic Windows Updates.
- D . Disable unnecessary services.
- E . Disable power options.
Correct Answer: D E
D E
Explanation:
Windows golden image optimization is the process of reducing the size and improving the performance of the Windows OS image that is used as the base for the desktop pools.
Some of the best practices for Windows golden image optimization are:
– Disable unnecessary services: Services that are not required for the desktop functionality or user experience should be disabled to reduce the resource consumption and potential security risks.
For example, services such as Windows Search, Windows Defender, Windows Update, and Superfetch can be disabled for better performance and stability.
– Disable power options: Power options such as hibernation and sleep mode should be disabled to free up disk space and avoid potential issues with the desktop state. Hibernation can consume a large amount of disk space by creating a hiberfil.sys file that stores the system memory contents when the desktop is powered off. Sleep mode can cause problems with network connectivity and user sessions when the desktop is resumed from a low-power state.
Other best practices for Windows golden image optimization include:
– Activate Windows OS paging: Paging is a mechanism that allows the OS to use a portion of the disk as virtual memory when the physical memory is insufficient. Paging can improve the performance and stability of the desktops by preventing out-of-memory errors and reducing memory contention. However, paging can also increase disk I/O and wear, so it should be configured with caution and monitored regularly.
– Turn off automatic Windows maintenance (scheduled tasks): Automatic Windows maintenance is a feature that runs various tasks such as disk defragmentation, disk cleanup, security scanning, and system diagnostics in the background. These tasks can consume a lot of CPU, memory, and disk resources and interfere with the user experience and desktop performance. Therefore, it is recommended to turn off automatic Windows maintenance and run these tasks manually or on a scheduled basis when the desktops are not in use.
– Turn off automatic Windows Updates: Automatic Windows Updates is a feature that downloads and installs updates for the OS and other Microsoft products in the background. These updates can consume bandwidth, disk space, and CPUresources and cause compatibility issues with some applications or drivers. Therefore, it is recommended to turn off automatic Windows Updates and manage the updates manually or through a centralized tool such as VMware Update Manager or Microsoft WSUS. References: [Optimizing Your VMware Horizon View 7.x Golden Image] and [VMware Horizon 8.x Professional Course]
D E
Explanation:
Windows golden image optimization is the process of reducing the size and improving the performance of the Windows OS image that is used as the base for the desktop pools.
Some of the best practices for Windows golden image optimization are:
– Disable unnecessary services: Services that are not required for the desktop functionality or user experience should be disabled to reduce the resource consumption and potential security risks.
For example, services such as Windows Search, Windows Defender, Windows Update, and Superfetch can be disabled for better performance and stability.
– Disable power options: Power options such as hibernation and sleep mode should be disabled to free up disk space and avoid potential issues with the desktop state. Hibernation can consume a large amount of disk space by creating a hiberfil.sys file that stores the system memory contents when the desktop is powered off. Sleep mode can cause problems with network connectivity and user sessions when the desktop is resumed from a low-power state.
Other best practices for Windows golden image optimization include:
– Activate Windows OS paging: Paging is a mechanism that allows the OS to use a portion of the disk as virtual memory when the physical memory is insufficient. Paging can improve the performance and stability of the desktops by preventing out-of-memory errors and reducing memory contention. However, paging can also increase disk I/O and wear, so it should be configured with caution and monitored regularly.
– Turn off automatic Windows maintenance (scheduled tasks): Automatic Windows maintenance is a feature that runs various tasks such as disk defragmentation, disk cleanup, security scanning, and system diagnostics in the background. These tasks can consume a lot of CPU, memory, and disk resources and interfere with the user experience and desktop performance. Therefore, it is recommended to turn off automatic Windows maintenance and run these tasks manually or on a scheduled basis when the desktops are not in use.
– Turn off automatic Windows Updates: Automatic Windows Updates is a feature that downloads and installs updates for the OS and other Microsoft products in the background. These updates can consume bandwidth, disk space, and CPUresources and cause compatibility issues with some applications or drivers. Therefore, it is recommended to turn off automatic Windows Updates and manage the updates manually or through a centralized tool such as VMware Update Manager or Microsoft WSUS. References: [Optimizing Your VMware Horizon View 7.x Golden Image] and [VMware Horizon 8.x Professional Course]
Question #4
What is the effect of changing any VMware Blast policy that cannot be changed in real time?
- A . Horizon Client detects the change and prompts the user to reboot once every 480 seconds.
- B . VMware Tools services is restarted by Microsoft GPO Update service.
- C . VMware Tools detects the change and immediately applies the new setting within 480 seconds.
- D . Microsoft GPO update rules apply and GPOs are updated manually or by restarting the Horizon Agent.
Correct Answer: D
D
Explanation:
VMware Blast policy settings are stored in the registry key HKLMSoftwarePoliciesVMware, Inc.VMware BlastConfig on the remote desktops or RDS hosts that use the VMware Blast display protocol. These settings can be configured by using the VMware Blast ADMX template file (vdm_blast.admx) and applying it through Microsoft Group Policy Object (GPO). Some of these settings can be changed in real time, which means that they take effect immediately after the policy is applied, without requiring a reboot or a reconnection of the Horizon Client. However, some of these settings cannot be changed in real time, which means that they require a reboot or a reconnection of the Horizon Client to take effect.
The effect of changing any VMware Blast policy that cannot be changed in real time is that the Microsoft GPO update rules apply and GPOs are updated manually or by restarting the Horizon Agent.
This means that the new policy settings will not be applied until one of the following events occurs:
– The Horizon Agent service is restarted on the remote desktop or RDS host. This can be done manually by using the Services console or the command-line tool sc.exe, or automatically by using a scheduled task or a script.
– The remote desktop or RDS host is rebooted. This can be done manually by using the Restart option in Windows, or automatically by using a scheduled task or a script.
– The Group Policy refresh interval is reached. This is a configurable time interval that determines how often the system checks for and applies new or changed GPOs. By default, this interval is 90 minutes for domain members and 5 minutes for domain controllers, with a random offset of 0 to 30 minutes. This interval can be modified by using the Group Policy refresh interval for computers setting in the ComputerConfigurationAdministrative TemplatesSystemGroup Policy folder of the Group Policy Management Console.
Therefore, to ensure that the VMware Blast policy settings that cannot be changed in real time are applied as soon as possible, it is recommended to restart the Horizon Agent service or reboot the remote desktop or RDS host after applying the policy.
References: VMware Blast Policy Settings, Group Policy refresh intervals, and [VMware Horizon 8.x Professional Course]
D
Explanation:
VMware Blast policy settings are stored in the registry key HKLMSoftwarePoliciesVMware, Inc.VMware BlastConfig on the remote desktops or RDS hosts that use the VMware Blast display protocol. These settings can be configured by using the VMware Blast ADMX template file (vdm_blast.admx) and applying it through Microsoft Group Policy Object (GPO). Some of these settings can be changed in real time, which means that they take effect immediately after the policy is applied, without requiring a reboot or a reconnection of the Horizon Client. However, some of these settings cannot be changed in real time, which means that they require a reboot or a reconnection of the Horizon Client to take effect.
The effect of changing any VMware Blast policy that cannot be changed in real time is that the Microsoft GPO update rules apply and GPOs are updated manually or by restarting the Horizon Agent.
This means that the new policy settings will not be applied until one of the following events occurs:
– The Horizon Agent service is restarted on the remote desktop or RDS host. This can be done manually by using the Services console or the command-line tool sc.exe, or automatically by using a scheduled task or a script.
– The remote desktop or RDS host is rebooted. This can be done manually by using the Restart option in Windows, or automatically by using a scheduled task or a script.
– The Group Policy refresh interval is reached. This is a configurable time interval that determines how often the system checks for and applies new or changed GPOs. By default, this interval is 90 minutes for domain members and 5 minutes for domain controllers, with a random offset of 0 to 30 minutes. This interval can be modified by using the Group Policy refresh interval for computers setting in the ComputerConfigurationAdministrative TemplatesSystemGroup Policy folder of the Group Policy Management Console.
Therefore, to ensure that the VMware Blast policy settings that cannot be changed in real time are applied as soon as possible, it is recommended to restart the Horizon Agent service or reboot the remote desktop or RDS host after applying the policy.
References: VMware Blast Policy Settings, Group Policy refresh intervals, and [VMware Horizon 8.x Professional Course]
Question #5
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.
Correct Answer:
Question #6
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.
Correct Answer:
Question #7
The administrator of Windows 10 desktops in a VMware Horizon environment needs to build a new Windows 10 desktop pool. This new pool will be dedicated to training and onboarding new employees. The administrator has created a shortcut on a test machine, which has successfully opened the web browser to the on-boarding applications. After deploying the new desktop pool across the company, the administrator notices that the shortcut placed on desktops is not available to any other user connecting to the desktop pool.
Which two options are available for the administrator to make this shortcut available to all desktop pool users, while minimizing ongoing administrative effort, before updating the desktop pool golden image? (Choose two.)
- A . Copy the shortcut during user provisioning to a non-writeable App Volume.
- B . Copy the shortcut to the Windows Default Domain Controller Policy.
- C . Copy the shortcut to c:usersPublicDesktop.
- D . Configure a Shortcut with Horizon View Client.
- E . Configure a Shortcut with DEM (Dynamic Environment Manager).
Correct Answer: C E
C E
Explanation:
The two options that are available for the administrator to make the shortcut available to all desktop pool users, while minimizing ongoing administrative effort, before updating the desktop pool golden image are:
– Copy the shortcut to c:usersPublicDesktop. This option will place the shortcut in the public desktop folder, which is shared by all users who log on to the same computer. The public desktop folder is normally a hidden folder, so the administrator needs to enable the option to show hidden files and folders in File Explorer1. This option does not require any additional software or configuration, but it will only work for the existing desktops in the pool. If new desktops are added or refreshed, the shortcut will not be copied automatically.
– Configure a Shortcut with DEM (Dynamic Environment Manager). This option will use the DEM console to create a shortcut configuration that will apply the shortcut to the user’s desktop during logon2. The administrator needs to install and configure DEM on the Horizon environment, and create a configuration share and a profile archive share for storing the DEM settings3. This option requires more initial setup, but it will work for any desktop in the pool, regardless of whether it is new or refreshed. It also allows more flexibility and control over the shortcut properties and conditions.
The other options are not valid or feasible because:
– Copying the shortcut during user provisioning to a non-writeable App Volume will not work because App Volumes are used to deliver applications, not shortcuts. App Volumes are virtual disks that are attached to the virtual machines at runtime, and they contain application files, registry entries, and settings4. Copying a shortcut to an App Volume will not make it appear on the user’s desktop.
– Copying the shortcut to the Windows Default Domain Controller Policy will not work because this policy is used to configure settings for domain controllers, not desktops. The Default Domain Controller Policy is a Group Policy Object (GPO) that is linked to the Domain Controllers organizational unit (OU) in Active Directory, and it contains security settings that are applied to all domain controllers in the domain5. Copying a shortcut to this policy will not affect any desktops in the Horizon environment.
– Configuring a Shortcut with Horizon View Client will not work because Horizon View Client is used to connect to remote desktops and applications, not to create shortcuts. Horizon View Client is a software application that runs on various devices and platforms, and it allows users to access their virtual desktops and applications through a secure connection6. Configuring a shortcut with Horizon View Client will not make it appear on the user’s desktop.
References:
– How to make a desktop shortcut available for all users in Windows 101
– VMware Dynamic Environment Manager (DEM) 2306 C Carl Stalhood2
– VMware Tech Zone Antivirus Considerations in a VMware Horizon Environment: exclusions for Horizon View, App Volumes, User Environment Manager, ThinApp3
– App Volumes Overview
– Default Domain Controller Policy5
– VMware Horizon Clients Documentation6
C E
Explanation:
The two options that are available for the administrator to make the shortcut available to all desktop pool users, while minimizing ongoing administrative effort, before updating the desktop pool golden image are:
– Copy the shortcut to c:usersPublicDesktop. This option will place the shortcut in the public desktop folder, which is shared by all users who log on to the same computer. The public desktop folder is normally a hidden folder, so the administrator needs to enable the option to show hidden files and folders in File Explorer1. This option does not require any additional software or configuration, but it will only work for the existing desktops in the pool. If new desktops are added or refreshed, the shortcut will not be copied automatically.
– Configure a Shortcut with DEM (Dynamic Environment Manager). This option will use the DEM console to create a shortcut configuration that will apply the shortcut to the user’s desktop during logon2. The administrator needs to install and configure DEM on the Horizon environment, and create a configuration share and a profile archive share for storing the DEM settings3. This option requires more initial setup, but it will work for any desktop in the pool, regardless of whether it is new or refreshed. It also allows more flexibility and control over the shortcut properties and conditions.
The other options are not valid or feasible because:
– Copying the shortcut during user provisioning to a non-writeable App Volume will not work because App Volumes are used to deliver applications, not shortcuts. App Volumes are virtual disks that are attached to the virtual machines at runtime, and they contain application files, registry entries, and settings4. Copying a shortcut to an App Volume will not make it appear on the user’s desktop.
– Copying the shortcut to the Windows Default Domain Controller Policy will not work because this policy is used to configure settings for domain controllers, not desktops. The Default Domain Controller Policy is a Group Policy Object (GPO) that is linked to the Domain Controllers organizational unit (OU) in Active Directory, and it contains security settings that are applied to all domain controllers in the domain5. Copying a shortcut to this policy will not affect any desktops in the Horizon environment.
– Configuring a Shortcut with Horizon View Client will not work because Horizon View Client is used to connect to remote desktops and applications, not to create shortcuts. Horizon View Client is a software application that runs on various devices and platforms, and it allows users to access their virtual desktops and applications through a secure connection6. Configuring a shortcut with Horizon View Client will not make it appear on the user’s desktop.
References:
– How to make a desktop shortcut available for all users in Windows 101
– VMware Dynamic Environment Manager (DEM) 2306 C Carl Stalhood2
– VMware Tech Zone Antivirus Considerations in a VMware Horizon Environment: exclusions for Horizon View, App Volumes, User Environment Manager, ThinApp3
– App Volumes Overview
– Default Domain Controller Policy5
– VMware Horizon Clients Documentation6
Question #8
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.
Correct Answer: A C
A C
Explanation:
Cloud Pod Architecture is a feature that allows administrators to link multiple Horizon pods across sites and data centers to form a single logical entity called a pod federation. Cloud Pod Architecture enables global entitlements, which allow users to access desktops and applications from any pod in the pod federation. Cloud Pod Architecture also provides load balancing, high availability, and disaster recovery capabilities for Horizon deployments.
However, Cloud Pod Architecture has some feature limitations that administrators should be aware of. Two of these limitations are:
– Cloud Pod Architecture does not support Active Directory two-way trusts between domains: This means that the domains that contain the Horizon pods in the pod federation must have a one-way trust relationship, where the domain that contains the Cloud Pod Architecture home site trusts all the other domains, but not vice versa. A two-way trust relationship, where each domain trusts and is trusted by all the other domains, is not supported by Cloud Pod Architecture and can cause authentication and entitlement issues.
– Kiosk mode clients are not supported unless a workaround has been implemented: This means that users who log in to Horizon Client in kiosk mode, which is a mode that allows users to access a single desktop or application without entering credentials, cannot access desktops or applications from a Cloud Pod Architecture implementation. Kiosk mode clients are not compatible with global entitlements and load balancing features of Cloud Pod Architecture. However, there is a workaround that involves creating a dedicated user account and a dedicated desktop pool for each kiosk mode client and using a script to launch Horizon Client with the appropriate parameters. For instructions, see VMware Knowledge Base (KB) article 21488881.
The other options are not limitations of Cloud Pod Architecture:
– Cloud Pod Architecture is supported with Unified Access Gateway appliances: Unified Access Gateway is a platform that provides secure edge services for Horizon deployments, such as secure remote access, load balancing, and authentication. Unified Access Gateway is compatible with Cloud Pod Architecture and can be configured to route user requests to the appropriate pod in the pod federation based on global entitlements and load balancing policies.
– Cloud Pod Architecture can span multiple sites and data centers simultaneously: This is one of the main benefits of Cloud Pod Architecture, as it allows administrators to scale up and out their Horizon deployments across different geographic locations and network boundaries. Cloud Pod Architecture can support up to 15 pods per pod federation andup to 5 sites per pod federation, with a maximum of 200,000 sessions per pod federation.
– The Cloud Pod Architecture feature is supported in an IPv6 environment: IPv6 is the latest version of the Internet Protocol that provides a larger address space and enhanced security features for network communication. Cloud Pod Architecture supports IPv6 environments and can operate in mixed IPv4 and IPv6 environments as well.
References: Cloud Pod Architecture Limitations in Horizon 8 and [VMware Horizon 8.x Professional Course]
A C
Explanation:
Cloud Pod Architecture is a feature that allows administrators to link multiple Horizon pods across sites and data centers to form a single logical entity called a pod federation. Cloud Pod Architecture enables global entitlements, which allow users to access desktops and applications from any pod in the pod federation. Cloud Pod Architecture also provides load balancing, high availability, and disaster recovery capabilities for Horizon deployments.
However, Cloud Pod Architecture has some feature limitations that administrators should be aware of. Two of these limitations are:
– Cloud Pod Architecture does not support Active Directory two-way trusts between domains: This means that the domains that contain the Horizon pods in the pod federation must have a one-way trust relationship, where the domain that contains the Cloud Pod Architecture home site trusts all the other domains, but not vice versa. A two-way trust relationship, where each domain trusts and is trusted by all the other domains, is not supported by Cloud Pod Architecture and can cause authentication and entitlement issues.
– Kiosk mode clients are not supported unless a workaround has been implemented: This means that users who log in to Horizon Client in kiosk mode, which is a mode that allows users to access a single desktop or application without entering credentials, cannot access desktops or applications from a Cloud Pod Architecture implementation. Kiosk mode clients are not compatible with global entitlements and load balancing features of Cloud Pod Architecture. However, there is a workaround that involves creating a dedicated user account and a dedicated desktop pool for each kiosk mode client and using a script to launch Horizon Client with the appropriate parameters. For instructions, see VMware Knowledge Base (KB) article 21488881.
The other options are not limitations of Cloud Pod Architecture:
– Cloud Pod Architecture is supported with Unified Access Gateway appliances: Unified Access Gateway is a platform that provides secure edge services for Horizon deployments, such as secure remote access, load balancing, and authentication. Unified Access Gateway is compatible with Cloud Pod Architecture and can be configured to route user requests to the appropriate pod in the pod federation based on global entitlements and load balancing policies.
– Cloud Pod Architecture can span multiple sites and data centers simultaneously: This is one of the main benefits of Cloud Pod Architecture, as it allows administrators to scale up and out their Horizon deployments across different geographic locations and network boundaries. Cloud Pod Architecture can support up to 15 pods per pod federation andup to 5 sites per pod federation, with a maximum of 200,000 sessions per pod federation.
– The Cloud Pod Architecture feature is supported in an IPv6 environment: IPv6 is the latest version of the Internet Protocol that provides a larger address space and enhanced security features for network communication. Cloud Pod Architecture supports IPv6 environments and can operate in mixed IPv4 and IPv6 environments as well.
References: Cloud Pod Architecture Limitations in Horizon 8 and [VMware Horizon 8.x Professional Course]
Question #9
Refer to the exhibit.
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.
Correct Answer:
Question #10
Which two scenarios are appropriate for a cloud implementation of a VDI solution over an on-premises solution? (Choose two.)
- A . The organization already has infrastructure to support a VDI.
- B . The organization needs to setup high availability and disaster recovery.
- C . The organization needs to quickly scale-up in disparate geographical locations.
- D . The organization has limited CapEx budget.
- E . The organization controls highly confidential data.
Correct Answer: C D
C D
Explanation:
A cloud implementation of a VDI solution over an on-premises solution is appropriate for the following scenarios:
– The organization needs to quickly scale-up in disparate geographical locations. A cloud VDI solution can provide faster provisioning, deployment, and management of virtual desktops and applications across multiple regions and data centers. A cloud VDI solution can also offer better performance, availability, and user experience for remote and mobile workers who need to access their desktops and applications from anywhere and any device12.
– The organization has limited CapEx budget. A cloud VDI solution can reduce the upfront capital expenditure (CapEx) required to purchase, install, and maintain the hardware and software infrastructure for a VDI solution. A cloud VDI solution can also lower the operational expenditure (OpEx) by shifting the responsibility of managing, updating, and securing the VDI infrastructure to the cloud provider. A cloud VDI solution can offer flexible and predictable pricing models based on usage, subscription, or consumption13.
The other scenarios are not appropriate for a cloud implementation of a VDI solution over an on-premises solution because:
– The organization already has infrastructure to support a VDI. If the organization has already invested in the hardware and software resources to support a VDI solution, it may not be cost-effective or feasible to migrate to a cloud VDI solution. The organization may also have existing policies, processes, and workflows that are tailored to the on-premises VDI solution and may not be compatible with the cloud VDI solution4.
– The organization needs to setup high availability and disaster recovery. While a cloud VDI solution can provide high availability and disaster recovery capabilities, it may not be sufficient or reliable for some organizations that have strict requirements for data protection, compliance, and business continuity. An on-premises VDI solution can offermore control, customization, and security over the backup, replication, and restoration of the VDI data and applications in the event of a disaster5.
– The organization controls highly confidential data. A cloud VDI solution may pose some risks or challenges for organizations that handle sensitive or regulated data, such as financial, healthcare, or government data. A cloud VDI solution may not meet the compliance standards or regulations that apply to the organization’s data. A cloud VDI solution may also expose the organization’s data to potential breaches, leaks, or unauthorized access by third parties. An on-premises VDI solution can provide more visibility, governance, and encryption over the organization’s data6.
References: =
1: VMware: What is Desktop as a Service (DaaS)?
2: Parallels: VDI in the Cloud: Which Cloud VDI Product Is Right for You?
3: Microsoft Azure: What Is Virtual Desktop Infrastructure (VDI)?
4: VMware: On-Premise vs Cloud: Which is Better for Your Business?
5: VMware: Disaster Recovery Solutions for Virtual Desktop Infrastructure (VDI)
6: Microsoft Azure: Virtual desktop infrastructure security best practices
C D
Explanation:
A cloud implementation of a VDI solution over an on-premises solution is appropriate for the following scenarios:
– The organization needs to quickly scale-up in disparate geographical locations. A cloud VDI solution can provide faster provisioning, deployment, and management of virtual desktops and applications across multiple regions and data centers. A cloud VDI solution can also offer better performance, availability, and user experience for remote and mobile workers who need to access their desktops and applications from anywhere and any device12.
– The organization has limited CapEx budget. A cloud VDI solution can reduce the upfront capital expenditure (CapEx) required to purchase, install, and maintain the hardware and software infrastructure for a VDI solution. A cloud VDI solution can also lower the operational expenditure (OpEx) by shifting the responsibility of managing, updating, and securing the VDI infrastructure to the cloud provider. A cloud VDI solution can offer flexible and predictable pricing models based on usage, subscription, or consumption13.
The other scenarios are not appropriate for a cloud implementation of a VDI solution over an on-premises solution because:
– The organization already has infrastructure to support a VDI. If the organization has already invested in the hardware and software resources to support a VDI solution, it may not be cost-effective or feasible to migrate to a cloud VDI solution. The organization may also have existing policies, processes, and workflows that are tailored to the on-premises VDI solution and may not be compatible with the cloud VDI solution4.
– The organization needs to setup high availability and disaster recovery. While a cloud VDI solution can provide high availability and disaster recovery capabilities, it may not be sufficient or reliable for some organizations that have strict requirements for data protection, compliance, and business continuity. An on-premises VDI solution can offermore control, customization, and security over the backup, replication, and restoration of the VDI data and applications in the event of a disaster5.
– The organization controls highly confidential data. A cloud VDI solution may pose some risks or challenges for organizations that handle sensitive or regulated data, such as financial, healthcare, or government data. A cloud VDI solution may not meet the compliance standards or regulations that apply to the organization’s data. A cloud VDI solution may also expose the organization’s data to potential breaches, leaks, or unauthorized access by third parties. An on-premises VDI solution can provide more visibility, governance, and encryption over the organization’s data6.
References: =
1: VMware: What is Desktop as a Service (DaaS)?
2: Parallels: VDI in the Cloud: Which Cloud VDI Product Is Right for You?
3: Microsoft Azure: What Is Virtual Desktop Infrastructure (VDI)?
4: VMware: On-Premise vs Cloud: Which is Better for Your Business?
5: VMware: Disaster Recovery Solutions for Virtual Desktop Infrastructure (VDI)
6: Microsoft Azure: Virtual desktop infrastructure security best practices
Question #11
Which of the following statements are true about Application Profiler?
- A . Application Profiler is installed using VMware Dynamic Environment Manager Enterprise Setup Wizard and explicitly selecting local drive installation.
- B . VMware Dynamic Environment Manager Agent and the Application Profiler cannot be installed on the same machine.
- C . Application Profiler is installed automatically when installing VMware Dynamic Environment Manager FlexEngine.
- D . Application Profiler is installed automatically when installing Dynamic Environment Manager Management Console.
Correct Answer: A
A
Explanation:
Application Profiler is a tool that analyzes the registry and file system locations where the settings for a particular application are stored, and creates a Flex configuration file for use with Dynamic Environment Manager. Application Profiler is installed using VMware Dynamic Environment Manager Enterprise Setup Wizard and explicitly selecting local drive installation1. This option allows you to install Application Profiler on a separate machine from the Dynamic Environment Manager Agent or Management
Console. Alternatively, you can install Application Profiler on the same machine as the Dynamic Environment Manager Agent or Management Console, by selecting network share installation1.
VMware Dynamic Environment Manager Agent and the Application Profiler can be installed on the same machine, but it is not recommended. This is because the Dynamic Environment Manager Agent might interfere with the profiling process by applying settings to the application being profiled1. Therefore, it is best to use a clean system for profiling applications.
Application Profiler is not installed automatically when installing VMware Dynamic Environment Manager FlexEngine or Management Console. FlexEngine is the component that applies the user environment settings during logon, logoff, and session reconnect or disconnect events2. Management Console is the component that allows you to configure and manage the user environment settings2. Neither of these components requires Application Profiler to function. Application Profiler is an optional tool that helps you create Flex configuration files for applications that are not included in the predefined settings library1. References:
– VMware Dynamic Environment Manager Overview2
– Using Application Profiler1
A
Explanation:
Application Profiler is a tool that analyzes the registry and file system locations where the settings for a particular application are stored, and creates a Flex configuration file for use with Dynamic Environment Manager. Application Profiler is installed using VMware Dynamic Environment Manager Enterprise Setup Wizard and explicitly selecting local drive installation1. This option allows you to install Application Profiler on a separate machine from the Dynamic Environment Manager Agent or Management
Console. Alternatively, you can install Application Profiler on the same machine as the Dynamic Environment Manager Agent or Management Console, by selecting network share installation1.
VMware Dynamic Environment Manager Agent and the Application Profiler can be installed on the same machine, but it is not recommended. This is because the Dynamic Environment Manager Agent might interfere with the profiling process by applying settings to the application being profiled1. Therefore, it is best to use a clean system for profiling applications.
Application Profiler is not installed automatically when installing VMware Dynamic Environment Manager FlexEngine or Management Console. FlexEngine is the component that applies the user environment settings during logon, logoff, and session reconnect or disconnect events2. Management Console is the component that allows you to configure and manage the user environment settings2. Neither of these components requires Application Profiler to function. Application Profiler is an optional tool that helps you create Flex configuration files for applications that are not included in the predefined settings library1. References:
– VMware Dynamic Environment Manager Overview2
– Using Application Profiler1
Question #12
An administrator needs to deploy an application to specific users in their instant-clone desktop environment with the following characteristics:
• The application needs to be updated very frequently.
• The application needs to be installed as soon as possible.
• The application is not multi-user aware.
Which solution would meet the requirements?
- A . VMware Horizon Published Application
- B . VMware Dynamic Environment Manager
- C . VMware ThinApp
- D . VMware App Volumes
Correct Answer: D
D
Explanation:
VMware App Volumes is a real-time application delivery system that allows administrators to assign applications to users and groups in Horizon. App Volumes uses virtual disks called packages to store and deliver applications. When a user logs on to a desktop, the App Volumes agent attaches the assigned packages to the desktop and merges them with the OS disk. The user can then access the applications as if they were natively installed.
App Volumes is a suitable solution for deploying an application to specific users in an instant-clone desktop environment with the following characteristics:
– The application needs to be updated very frequently: App Volumes allows administrators to update applications in real time by using the update or push-image operations. These operations replace the existing packages with new ones that have the latest updates applied, without affecting the user data or settings. The updated packages are delivered to the users at the next login or refresh.
– The application needs to be installed as soon as possible: App Volumes allows administrators to install applications quickly and easily by using a clean packaging system and capturing the application installation process. The resulting package can be assigned to users or groups immediately, without requiring any recomposing or rebooting of the desktops.
– The application is not multi-user aware: App Volumes allows administrators to deliver applications that are not multi-user aware by using writable volumes. Writable volumesare user-specific virtual disks that store user-installed applications, data, and settings. Writable volumes can be attached to desktops along with application packages, and they can isolate the user-installed applications from the system-installed applications.
The other options are not suitable for meeting the requirements:
– VMware Horizon Published Application: This option allows administrators to publish applications from RDS hosts to users in Horizon. However, this option requires a separate RDS infrastructure and licensing, and it does not support instant updates or writable volumes for user-installed applications.
– VMware Dynamic Environment Manager: This option allows administrators to manage user profiles and policies in Horizon. However, this option does not deliver or update applications, and it does not support writable volumes for user-installed applications.
– VMware ThinApp: This option allows administrators to package applications into portable executables
that can run on any Windows system without installation. However, this option requires a separate packaging process and licensing, and it does not support instant updates or writable volumes for user-installed applications.
References: App Volumes Architecture, Updating Applications in Real Time, Writable Volumes Overview, and [VMware Horizon 8.x Professional Course]
D
Explanation:
VMware App Volumes is a real-time application delivery system that allows administrators to assign applications to users and groups in Horizon. App Volumes uses virtual disks called packages to store and deliver applications. When a user logs on to a desktop, the App Volumes agent attaches the assigned packages to the desktop and merges them with the OS disk. The user can then access the applications as if they were natively installed.
App Volumes is a suitable solution for deploying an application to specific users in an instant-clone desktop environment with the following characteristics:
– The application needs to be updated very frequently: App Volumes allows administrators to update applications in real time by using the update or push-image operations. These operations replace the existing packages with new ones that have the latest updates applied, without affecting the user data or settings. The updated packages are delivered to the users at the next login or refresh.
– The application needs to be installed as soon as possible: App Volumes allows administrators to install applications quickly and easily by using a clean packaging system and capturing the application installation process. The resulting package can be assigned to users or groups immediately, without requiring any recomposing or rebooting of the desktops.
– The application is not multi-user aware: App Volumes allows administrators to deliver applications that are not multi-user aware by using writable volumes. Writable volumesare user-specific virtual disks that store user-installed applications, data, and settings. Writable volumes can be attached to desktops along with application packages, and they can isolate the user-installed applications from the system-installed applications.
The other options are not suitable for meeting the requirements:
– VMware Horizon Published Application: This option allows administrators to publish applications from RDS hosts to users in Horizon. However, this option requires a separate RDS infrastructure and licensing, and it does not support instant updates or writable volumes for user-installed applications.
– VMware Dynamic Environment Manager: This option allows administrators to manage user profiles and policies in Horizon. However, this option does not deliver or update applications, and it does not support writable volumes for user-installed applications.
– VMware ThinApp: This option allows administrators to package applications into portable executables
that can run on any Windows system without installation. However, this option requires a separate packaging process and licensing, and it does not support instant updates or writable volumes for user-installed applications.
References: App Volumes Architecture, Updating Applications in Real Time, Writable Volumes Overview, and [VMware Horizon 8.x Professional Course]
Question #13
An administrator has been tasked with determining the type of VMware Horizon deployment for their organization.
These requirements have been provided to the administrator:
• It must support Windows 10 Enterprise multi-session desktops.
• It must support App Volumes.
• It must support centralized brokering.
• It must automatically route end-users to the most appropriate virtual workspace.
Which deployment solution meets the requirements?
- A . VMware vSphere Desktop Edition
- B . VMware Workspace ONE Unified Endpoint Management
- C . VMware Horizon On-Premises
- D . VMware Horizon Cloud on Microsoft Azure
Correct Answer: D
D
Explanation:
VMware Horizon Cloud on Microsoft Azure is the only deployment solution that meets all the requirements. VMware Horizon Cloud on Microsoft Azure supports Windows 10 Enterprise multi-session desktops, which are a new Remote Desktop Session Host exclusive to Azure Virtual Desktop on Azure1. It also supports App Volumes, which is a real-time application delivery system that enables IT to instantly provision applications to users or desktops. VMware Horizon Cloud on Microsoft Azure supports centralized brokering, which means that the Horizon Cloud Service acts as a single point of entry for end users to access their virtual desktops and applications. VMware Horizon Cloud on Microsoft Azure also supports automatic routing of end-users to the most appropriate virtual workspace, using the Universal Broker feature. Universal Broker is a cloud-based brokering service that provides a unified user experience across multiple Horizon pods and clouds.
VMware vSphere Desktop Edition does not support Windows 10 Enterprise multi-session desktops, as they are only available on Azure Virtual Desktop1. VMware Workspace ONE Unified Endpoint Management does not support App Volumes, as it is a different solution for managing devices and applications. VMware
Horizon On-Premises does not support automatic routing of end-users to the most appropriate virtual workspace, as it requires manual configuration of load balancing and global entitlements. References:
– Profile production applications in Azure with Application Insights Profiler1
– Using Application Profiler – VMware Docs2
– First look at profiling tools – Visual Studio (Windows)3
– App Volumes Overview
– Horizon Cloud Service on Microsoft Azure Architecture
– Universal Broker Overview
– Workspace ONE UEM Overview
– Load Balancing Across Pods and Sites in a Cloud Pod Architecture Environment
D
Explanation:
VMware Horizon Cloud on Microsoft Azure is the only deployment solution that meets all the requirements. VMware Horizon Cloud on Microsoft Azure supports Windows 10 Enterprise multi-session desktops, which are a new Remote Desktop Session Host exclusive to Azure Virtual Desktop on Azure1. It also supports App Volumes, which is a real-time application delivery system that enables IT to instantly provision applications to users or desktops. VMware Horizon Cloud on Microsoft Azure supports centralized brokering, which means that the Horizon Cloud Service acts as a single point of entry for end users to access their virtual desktops and applications. VMware Horizon Cloud on Microsoft Azure also supports automatic routing of end-users to the most appropriate virtual workspace, using the Universal Broker feature. Universal Broker is a cloud-based brokering service that provides a unified user experience across multiple Horizon pods and clouds.
VMware vSphere Desktop Edition does not support Windows 10 Enterprise multi-session desktops, as they are only available on Azure Virtual Desktop1. VMware Workspace ONE Unified Endpoint Management does not support App Volumes, as it is a different solution for managing devices and applications. VMware
Horizon On-Premises does not support automatic routing of end-users to the most appropriate virtual workspace, as it requires manual configuration of load balancing and global entitlements. References:
– Profile production applications in Azure with Application Insights Profiler1
– Using Application Profiler – VMware Docs2
– First look at profiling tools – Visual Studio (Windows)3
– App Volumes Overview
– Horizon Cloud Service on Microsoft Azure Architecture
– Universal Broker Overview
– Workspace ONE UEM Overview
– Load Balancing Across Pods and Sites in a Cloud Pod Architecture Environment
Question #14
On a VMware vCenter managed virtual machine, how does the VMware Horizon Agent know which Connection Server it should register with during the Instant Clone pool creation process?
- A . Administrator provides this information in the "Add Pool" creation wizard.
- B . Horizon Agent retrieves this information from an DNS SRV record.
- C . Administrator provides this information in the Horizon Agent Installation Wizard on the master image.
- D . Horizon Agent queries VMware Tools for a Guestlnfo Variable during the cloning process.
Correct Answer: D
D
Explanation:
On a VMware vCenter managed virtual machine, the VMware Horizon Agent knows which Connection Server it should register with during the Instant Clone pool creation process by querying VMware Tools for a Guestlnfo Variable during the cloning process. The Guestlnfo Variable is a custom property that is set on the parent virtual machine and contains the FQDN of the Connection Server. When the parent virtual machine is cloned, the Guestlnfo Variable is copied to the clone and read by the Horizon Agent. The Horizon Agent then registers with the Connection Server specified in the Guestlnfo Variable12.
The other options are not correct for this scenario:
– Administrator provides this information in the “Add Pool” creation wizard. This option is not correct because the administrator does not need to provide the Connection Server information in the “Add Pool” creation wizard. The administrator only needs to select the vCenter Server, data center, cluster, resource pool, datastore, network, and snapshot of the parent virtual machine. The Connection Server information is already embedded in the parent virtual machine as a Guestlnfo Variable3.
– Horizon Agent retrieves this information from an DNS SRV record. This option is not correct because the Horizon Agent does not use DNS SRV records to find the Connection Server during the Instant Clone pool creation process. DNS SRV records are used by Horizon Client devices to discover Connection Servers when they connect to a Horizon environment. DNS SRV records are optional and can be configured by the administrator to simplify client connections4.
– Administrator provides this information in the Horizon Agent Installation Wizard on the master image. This option is not correct because the administrator does not need to provide the Connection Server information in the Horizon Agent Installation Wizard on the master image. The administrator only needs to select the features and options that are required for the desktop pool, such as VMware Horizon Instant Clone Agent, VMware Dynamic Environment Manager, VMware App Volumes, and so on. The Connection Server information is set on the master image after it is converted to a parent virtual machine by using a PowerShell script5.
References:
– Instant Clones: How Does It Work?
– Instant Clone Domain Administrator Account
– Create an Automated Instant-Clone Desktop Pool
– Configuring DNS Service Records for Horizon Connection Server
– Install Horizon Agent on a Virtual Machine
– [VMware Horizon 8.x Professional]
– [VMware Horizon Architecture Planning]
D
Explanation:
On a VMware vCenter managed virtual machine, the VMware Horizon Agent knows which Connection Server it should register with during the Instant Clone pool creation process by querying VMware Tools for a Guestlnfo Variable during the cloning process. The Guestlnfo Variable is a custom property that is set on the parent virtual machine and contains the FQDN of the Connection Server. When the parent virtual machine is cloned, the Guestlnfo Variable is copied to the clone and read by the Horizon Agent. The Horizon Agent then registers with the Connection Server specified in the Guestlnfo Variable12.
The other options are not correct for this scenario:
– Administrator provides this information in the “Add Pool” creation wizard. This option is not correct because the administrator does not need to provide the Connection Server information in the “Add Pool” creation wizard. The administrator only needs to select the vCenter Server, data center, cluster, resource pool, datastore, network, and snapshot of the parent virtual machine. The Connection Server information is already embedded in the parent virtual machine as a Guestlnfo Variable3.
– Horizon Agent retrieves this information from an DNS SRV record. This option is not correct because the Horizon Agent does not use DNS SRV records to find the Connection Server during the Instant Clone pool creation process. DNS SRV records are used by Horizon Client devices to discover Connection Servers when they connect to a Horizon environment. DNS SRV records are optional and can be configured by the administrator to simplify client connections4.
– Administrator provides this information in the Horizon Agent Installation Wizard on the master image. This option is not correct because the administrator does not need to provide the Connection Server information in the Horizon Agent Installation Wizard on the master image. The administrator only needs to select the features and options that are required for the desktop pool, such as VMware Horizon Instant Clone Agent, VMware Dynamic Environment Manager, VMware App Volumes, and so on. The Connection Server information is set on the master image after it is converted to a parent virtual machine by using a PowerShell script5.
References:
– Instant Clones: How Does It Work?
– Instant Clone Domain Administrator Account
– Create an Automated Instant-Clone Desktop Pool
– Configuring DNS Service Records for Horizon Connection Server
– Install Horizon Agent on a Virtual Machine
– [VMware Horizon 8.x Professional]
– [VMware Horizon Architecture Planning]
Question #15
Refer to the exhibit.
An administrator wants to configure a central SYSLOG server.
Mark the correct menu option by clicking on it.
Correct Answer:
Question #16
Having configured two standalone Horizon pods, what steps should be taken to join them in a Cloud Pod Architecture (CPA) deployment?
- A . 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.
- B . 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.
- C . 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.
- D . On the second pod, sync the CPA. On one pod, create Cloud Entitlements, and add local pools from each pod.
Correct Answer: A
A
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
A
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
Question #17
What are the steps to create a custom role?
- A . 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.
- B . 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.
- C . 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.
- D . 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.
Correct Answer: A
A
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]
A
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]
Question #18
Which storage product allows the pooling of resources to create datastores in a software defined datacenter?
- A . VMware VMFS
- B . VMware Storage I/O Control
- C . VMware HCI Mesh
- D . VMware vSAN
Correct Answer: D
D
Explanation:
VMware vSAN is a storage product that allows the pooling of resources to create datastores in a software defined datacenter. VMware vSAN is a hyper-converged infrastructure solution that integrates compute, storage, and networking resources on industry-standard x86 servers. VMware vSAN aggregates local or direct-attached data storage devices to create a single storage pool shared across all hosts in the vSAN cluster. VMware vSAN enables you to provision and manage storage from the VMware vSphere Web Client or the VMware vCenter Server Appliance Shell. VMware vSAN provides several benefits, such as lower total cost of ownership, simplified management, high performance, scalability, and availability12. References: = 1: VMware Horizon 8 Documentation: VMware vSAN Overview 2: VMware Horizon 8 Documentation: Benefits of Using VMware vSAN with Horizon 8
D
Explanation:
VMware vSAN is a storage product that allows the pooling of resources to create datastores in a software defined datacenter. VMware vSAN is a hyper-converged infrastructure solution that integrates compute, storage, and networking resources on industry-standard x86 servers. VMware vSAN aggregates local or direct-attached data storage devices to create a single storage pool shared across all hosts in the vSAN cluster. VMware vSAN enables you to provision and manage storage from the VMware vSphere Web Client or the VMware vCenter Server Appliance Shell. VMware vSAN provides several benefits, such as lower total cost of ownership, simplified management, high performance, scalability, and availability12. References: = 1: VMware Horizon 8 Documentation: VMware vSAN Overview 2: VMware Horizon 8 Documentation: Benefits of Using VMware vSAN with Horizon 8
Question #19
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 . 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.
- C . The administrator has selected Shared when editing the Host Graphics Settings for the ESXi host in the vCenter Server.
- D . Instant-clone pools do not support NVIDIA GRID vGPU.
- E . The administrator has selected Shared Direct when editing the Host Graphics Settings for the ESXi host in the vCenter Server.
Correct Answer: A B
A B
Explanation:
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
A B
Explanation:
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
Question #20
Which two of the following are features of VMware Horizon Agent for Linux? (Choose two.)
- A . USB redirection
- B . location based printing
- C . display protocol PCoIP
- D . installation registration requirement
- E . session collaboration
Correct Answer: A C
A C
Explanation:
VMware Horizon Agent for Linux is a software component that enables Linux machines to be used as remote desktops or published applications in a Horizon environment. Horizon Agent for Linux supports several features that enhance the user experience and manageability of Linux desktops and applications, such as USB redirection, display protocol PCoIP, multiple-session mode, single sign-on, smart card authentication, and 3D graphics34. However, Horizon Agent for Linux does not support location based printing or session collaboration features that are available for Windows machines5. Also, Horizon Agent for Linux does not require installation registration as it automatically registers with the Connection Server when the viewagent service is started6.
References: = 3: VMware Horizon 8 Documentation: Horizon Agent for Linux 4: VMware Horizon 8 Documentation: Features Supported by Horizon Agent for Linux 5: VMware Horizon 8 Documentation: Features Not Supported by Horizon Agent for Linux 6: VMware Horizon 8 Documentation: Install Horizon Agent on a Linux Machine
A C
Explanation:
VMware Horizon Agent for Linux is a software component that enables Linux machines to be used as remote desktops or published applications in a Horizon environment. Horizon Agent for Linux supports several features that enhance the user experience and manageability of Linux desktops and applications, such as USB redirection, display protocol PCoIP, multiple-session mode, single sign-on, smart card authentication, and 3D graphics34. However, Horizon Agent for Linux does not support location based printing or session collaboration features that are available for Windows machines5. Also, Horizon Agent for Linux does not require installation registration as it automatically registers with the Connection Server when the viewagent service is started6.
References: = 3: VMware Horizon 8 Documentation: Horizon Agent for Linux 4: VMware Horizon 8 Documentation: Features Supported by Horizon Agent for Linux 5: VMware Horizon 8 Documentation: Features Not Supported by Horizon Agent for Linux 6: VMware Horizon 8 Documentation: Install Horizon Agent on a Linux Machine