You have an Azure subscription. The subscription contains 10 Azure Virtual Desktop session hosts that run Windows 10 Enterprise.You plan to deploy the new Microsoft Teams app to the session hosts.You need to prepare the session hosts for the deployment.Which two components should you install? Each correct answer presents part of the solution.Note: Each correct selection is worth one point.
Answer(s): A,E
Use Microsoft Teams on Azure Virtual DesktopPrerequisitesBefore you can use Microsoft Teams on Azure Virtual Desktop, you need:* Connect to a session host running Windows 10 or 11 multi-session or Windows 10 or 11 Enterprise. Session hosts running an N or KN SKU of Windows aren't supported.*-> For Windows, you also need to install the latest version of the Microsoft Visual C++ Redistributable on your client device and session hosts. The C++ Redistributable is required to use media optimization for Teams on Azure Virtual Desktop.*-> Install the latest version of Windows App or the Remote Desktop client on Windows or macOS that meets the hardware requirements for Microsoft Teams.SlimCore is available on Windows with the following apps and versions:- Windows App for Windows, version 1.3.252 or later- Remote Desktop client for Windows, version 1.2.5405.0 or later* Etc.
https://learn.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd
DRAG DROP (Drag and Drop is not supported)You have an Azure Virtual Desktop deployment that contains the resources shown in the following table.You plan to create private endpoints for the deployment.Which resource supports the connection target sub-resource, feed target sub-resource, and global target sub- resource of each private endpoint? To answer, drag the appropriate resources to the correct target sub- resources. Each resource may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.Note: Each correct selection is worth one point.Select and Place:
Answer(s): A
Box 1: Pool1ConnectionBox 2: AppGroup1FeedBox 3: Workspace1GlobalAzure Virtual Desktop has three workflows with three corresponding resource types to use with private endpoints. These workflows are:1. Initial feed discovery: lets the client discover all workspaces assigned to a user. To enable this process, you must create a single private endpoint to the global sub-resource to any workspace [Box 3]. However, you can only create one private endpoint in your entire Azure Virtual Desktop deployment. This endpoint creates Domain Name System (DNS) entries and private IP routes for the global fully qualified domain name (FQDN) needed for initial feed discovery. This connection becomes a single, shared route for all clients to use.2. Feed download: the client downloads all connection details for a specific user for the workspaces that host their application groups [Box 2]. You create a private endpoint for the feed sub-resource for each workspace you want to use with Private Link.3. Connections to host pools: every connection to a host pool has two sides - clients and session hosts. You need to create a private endpoint for the connection sub-resource for each host pool [Box 1] you want to use with Private Link.The following high-level diagram shows how Private Link securely connects a local client to the Azure Virtual Desktop service.
https://learn.microsoft.com/en-us/azure/virtual-desktop/private-link-overview
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription.You have a Microsoft 365 subscription that contains 1,000 users. Each user is assigned a Microsoft 365 E5 license.You are deploying Azure Virtual Desktop to meet the following requirements:Ensure that user modifications are persistent between the session hosts in the deployment.Support simultaneous connections for 200 external users and 100 internal users.Support apps that require GPU resources.Minimize costs.You perform the following tasks:Deploy three pooled host pools. Each host pool contains 15 session hosts that run Windows 11 Enterprise multi-session. Each session host is deployed to an NV-series virtual machine and supports eight user sessions.Enroll the Azure subscription in per-user access pricing for Azure Virtual Desktop.Implement FSLogix profile containersFor each of the following statements, select Yes if the statement is true. Otherwise, select No.Note: Each correct selection is worth one point.Hot Area:
Box 1: YesYes - The apps have access to GPU resources.The NV-series virtual machines are powered by NVIDIA Tesla M60 GPUs and NVIDIA GRID technology for desktop accelerated applications and virtual desktops where customers are able to visualize their data or simulations. Users are able to visualize their graphics intensive workflows on the NV instances to get superior graphics capability and additionally run single precision workloads such as encoding and rendering. NV-series VMs are also powered by Intel Xeon E5-2690 v3 (Haswell) CPUs.Box 2: YesYes - The deployment minimizes licensing costs.The internal users are covered with the Microsoft 365 E5 license.The external users:Per-user access pricing lets you pay for Azure Virtual Desktop access rights on behalf of external users. External users aren't members of your organization, such as customers of a business.Box 3: YesYes - User modifications are persistent between the session hosts.User profile management for Azure Virtual Desktop with FSLogix profile containersWe recommend using FSLogix profile containers with Azure Virtual Desktop to manage and roam user profiles and personalization. FSLogix profile containers store a complete user profile in a single container. At sign in, this container is dynamically attached to the remote session as a natively supported Virtual Hard Disk (VHDX or VHD) file. The user profile is immediately available and appears in the system exactly like a native user profile. This article describes how FSLogix profile containers work with Azure Virtual Desktop.
https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nv-series https://learn.microsoft.com/en-us/azure/virtual-desktop/enroll-per-user-access-pricing https://learn.microsoft.com/en-us/azure/virtual-desktop/fslogix-profile-containers
DRAG DROP (Drag and Drop is not supported)You have an Azure Virtual Desktop deployment that contains a host pool named Pool1.Pool1 contains session hosts that run Windows 11 Enterprise and have Microsoft Teams installed.Users connect to the session hosts by using client devices that run Windows 10 Enterprise.You need to configure the session hosts and the client devices to meet the following requirements:Teams audio and video must be processed on the client devices.Hardware encoding must be enabled.What should you do? To answer, drag the appropriate actions to the correct devices. Each action may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.Note: Each correct selection is worth one point.Select and Place:
Box 1: Install the Remote Desktop WebRTC Redirector Service Session hostsTeams audio and video must be processed on the client devices.Call redirection optimizes audio calls for WebRTC-based calling apps, reducing latency, and improving call quality. The connection happens between the local device and the telephony app server, where WebRTC calls are offloaded from a remote session to a local device. After the connection is established, call quality becomes dependent on the web page or app providers, just as it would with a non-redirected call.Note: Multimedia redirection redirects video playback and calls in a remote session from Azure Virtual Desktop, a Windows 365 Cloud PC, or Microsoft Dev Box to your local device for faster processing and rendering.Specifically, these two functions work in the following ways:* Video playback redirection*-> Call redirection: optimizes audio calls for WebRTC-based calling apps, reducing latency, and improving call quality. The connection happens between the local device and the telephony app server, where WebRTC calls are offloaded from a remote session to a local device.Box 2: Set the UseHardwareEncoding registry key to a DWORD value of 1.Client devicesHardware encoding must be enabled.Updates to Teams for Azure Virtual Desktop, including the following:The new hardware encoding feature increases the video quality (resolution and framerate) of the outgoing camera during Teams calls. Because this feature uses the underlying hardware on the PC and not just software, we're being extra careful to ensure broad compatibility before turning the feature on by default for all users. Therefore, this feature is currently off by default. To get an early preview of the feature, you can enable it on your local machine by creating a registry key at Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft \Terminal Server Client\Default\AddIns\WebRTC Redirector\UseHardwareEncoding as a DWORD value and setting it to 1. To disable the feature, set the key to 0.
https://learn.microsoft.com/en-us/previous-versions/remote-desktop-client/whats-new-windows
You have an on-premises Windows device named Device1.You have an Azure Virtual Desktop host pool named Pool1 that contains Windows 11 session hosts.You create an application group named AppGrp1. You have an app named App1. App1 is added to AppGrp1 and published as a RemoteApp.You need to ensure that when a user on Device1 connects to App1, Microsoft OneDrive launches.Which two actions should you perform? Each correct answer presents part of the solution.Note: Each correct selection is worth one point.
Answer(s): B,E
Note: Launch Microsoft OneDrive with a RemoteApp in Azure Virtual Desktop You can Launch Microsoft OneDrive alongside a RemoteApp in Azure Virtual Desktop, allowing users to access and synchronize their files while using a RemoteApp. When a user connects to a RemoteApp, OneDrive can automatically launch as a companion to the RemoteApp.In the settings for OneDrive, there's the option Start OneDrive when I sign in to Windows, which ordinarily starts OneDrive when a user signs in. However, this setting doesn't work with RemoteApp in Azure Virtual Desktop. Instead, you configure OneDrive to launch by configuring a registry value. You also enable an enhanced shell experience for RemoteApp sessions, offering support for default file associations, Run/ RunOnce registry keys, and more.Configure OneDrive to launch with a RemoteAppTo configure OneDrive to launch with a RemoteApp in Azure Virtual Desktop, you need to enable an enhanced shell experience for RemoteApp sessions using Group Policy and set a registry value to launch OneDrive when a user connects to a RemoteApp. The Group Policy setting isn't available in Microsoft Intune.1. Download and install the latest version of the OneDrive sync app per-machine on your session hosts.2. If your session hosts are joined to Microsoft Entra ID, silently configure user accounts for OneDrive on your session hosts, so users are automatically signed in to OneDrive.3. The Group Policy settings are only available in Windows 11, version 22H2 or 23H2 with the 2024-07 Cumulative Update for Windows 11 (KB5040442) or later installed.4. Open the Group Policy Management console on a device you use to manage the Active Directory domain.[B, E] 5. Create or edit a policy that targets the computers providing a remote session you want to configure.6. Navigate to Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.7. Double-click the policy setting Enable enhanced shell experience for RemoteApp to open it. Select Enabled, then select OK.8. Set the following registry value:Key: HKLM\Software\Microsoft\Windows\CurrentVersion\RunType: REG_SZName: OneDriveData: "C:\Program Files\Microsoft OneDrive\OneDrive.exe" /background9. Ensure the side-by-side stack on the session host is version 1.0.2404.16770 or higher.10. Restart the session hosts to apply the changes.
https://learn.microsoft.com/en-us/azure/virtual-desktop/onedrive-remoteapp
Post your Comments and Discuss Microsoft AZ-140 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-140 content, but please register or login to continue.