nerdexam
Microsoft

AZ-140 · Question #123

You have an Azure Active Directory Domain Services (Azure AD DS) domain named contoso.com. You have an Azure Storage account named storage1. Storage1 hosts a file share named share1 that has share…

The correct answer is C. Configure the Profiles setting for the session hosts of Pool1. At this stage in the FSLogix setup, the Azure AD DS authentication on the storage account is configured and the share/NTFS permissions are set. The FSLogix agent comes pre-installed on the 'Windows 10 multi-session + Microsoft 365 Apps' gallery image, so installing it again (A)…

Submitted by packet_pusher· Apr 18, 2026Plan and implement user environments and apps

Question

You have an Azure Active Directory Domain Services (Azure AD DS) domain named contoso.com. You have an Azure Storage account named storage1. Storage1 hosts a file share named share1 that has share and file system permissions configured. Share1 is configured to use contoso.com for authentication. You create an Azure Virtual Desktop host pool named Pool1. Pool1 contains two session hosts that use the Windows 10 multi-session + Microsoft 365 Apps image. You need to configure an FSLogix profile container for Pool1. What should you do next?

Options

  • AInstall the FSLogix agent on the session hosts of Pool1.
  • BFrom storage1, set Allow shared key access to Disabled.
  • CConfigure the Profiles setting for the session hosts of Pool1.
  • DGenerate a shared access signature (SAS) key for storage1.

How the community answered

(28 responses)
  • A
    4% (1)
  • B
    4% (1)
  • C
    82% (23)
  • D
    11% (3)

Explanation

At this stage in the FSLogix setup, the Azure AD DS authentication on the storage account is configured and the share/NTFS permissions are set. The FSLogix agent comes pre-installed on the 'Windows 10 multi-session + Microsoft 365 Apps' gallery image, so installing it again (A) is unnecessary. Setting Allow shared key access to Disabled (B) would break the ability to mount the share without Kerberos, which is not needed at this point. Generating a SAS key (D) is used for anonymous/application access, not FSLogix profile containers. The next logical step is to configure the FSLogix Profiles settings on the session hosts - specifically, setting the registry values (VHDLocations pointing to the UNC path of share1 and Enabled set to 1) so FSLogix knows where to store and load user profiles.

Topics

#FSLogix#Azure Virtual Desktop#User Profiles#Session Hosts

Community Discussion

No community discussion yet for this question.

Full AZ-140 Practice