Microsoft - AZ-140: Configuring and Operating Microsoft Azure Virtual Desktop

Sample Questions

• User1 will connect to Host1.
• User2 will connect to Host2.

Explanation:

You must provide an eligible license for each user that accesses Azure Virtual Desktop. The license you need also depends on whether you're using a Windows client operating system or a Windows Server operating system for your session hosts, and whether it's for internal or external commercial purposes. The following table shows the eligible licensing methods for each scenario:

Reference: Eligible licenses to use Azure Virtual Desktop

Explanation:

The session hosts are joined to a Microsoft Entra Domain Services domain which will provide authentication when users accessing the file share.

To use Active Directory accounts for the share permissions of your file share, you need to enable AD DS or Microsoft Entra Domain Services as a source. This process joins your storage account to a domain, representing it as a computer account.

Users needing to store profiles in your file share need permission to access it. To do this, you need to assign each user the Storage File Data SMB Share Contributor role and the required NTFS permissions.

Reference: Store FSLogix profile containers on Azure Files and Active Directory Domain Services or Microsoft Entra Domain Services

Explanation:

There are some requirements to access Microsoft Entra joined session hosts from different Azure Virtual Desktop clients.

The default configuration supports connections from Windows 11 or Windows 10 using the Windows Desktop client. You can use your credentials, smart card, Windows Hello for Business certificate trust or Windows Hello for Business key trust with certificates to sign in to the session host. However, to access the session host, your local PC must meet one of the following conditions:

• The local PC is Microsoft Entra joined to the same Microsoft Entra tenant as the session host
• The local PC is Microsoft Entra hybrid joined to the same Microsoft Entra tenant as the session host
• The local PC is running Windows 11 or Windows 10, version 2004 or later, and is Microsoft Entra registered to the same Microsoft Entra tenant as the session host

If your local PC doesn't meet one of these conditions, add targetisaadjoined:i:1 as a custom RDP property to the host pool. These connections are restricted to entering user name and password credentials when signing in to the session host.

Reference: Microsoft Entra joined session hosts in Azure Virtual Desktop

Explanation:

Azure Virtual Desktop supports two load balancing algorithms for pooled host pools. Each algorithm determines which session host is used when a user starts a remote session. Load balancing doesn't apply to personal host pools because users always have a 1:1 mapping to a session host within the host pool.

The following load balancing algorithms are available for pooled host pools:

• Breadth-first, which aims to evenly distribute new user sessions across the session hosts in a host pool. You don't have to specify a maximum session limit for the number of sessions.

• Depth-first, which keeps starting new user sessions on one session host until the maximum session limit is reached. Once the session limit is reached, any new user connections are directed to the next session host in the host pool until it reaches its session limit, and so on.

Reference: Configure host pool load balancing in Azure Virtual Desktop

Explanation:

If you created virtual machines by using an alternative method outside Azure Virtual Desktop, such as an automated pipeline, you need to install the Remote Desktop Session Host role and register them separately as session hosts to a host pool.

To register session hosts to a host pool, you need to install the Azure Virtual Desktop Agent and the Azure Virtual Desktop Agent Boot Loader on each virtual machine and use the registration key that you generated. You can register session hosts to a host pool by using the agent installers' graphical user interface (GUI) or by using msiexec from a command line.

Reference: Add session hosts to a host pool