AZ-140 · Question #296
You have an Azure Virtual Desktop deployment. You need to implement FSLogix to host user profiles in an Azure Storage account by using Azure file shares. The solution must meet the following requireme
The correct answer is D. DeleteLocalProfileWhenVHDShouldApply. Setting 'DeleteLocalProfileWhenVHDShouldApply' to 1 satisfies both requirements simultaneously. First, it deletes any existing local profile on the session host when a VHD-based profile should apply, ensuring no local profiles persist. Second, because the local profile is removed
Question
You have an Azure Virtual Desktop deployment. You need to implement FSLogix to host user profiles in an Azure Storage account by using Azure file shares. The solution must meet the following requirements:
- Access to a session host must be allowed only if the user profile is
available from the storage account.
- Local profiles must NOT be created on the session hosts.
Which FSLogix registry setting should you use?
Options
- ANoProfileContainingFolder
- BPreventLoginWithFailure
- CProfileType
- DDeleteLocalProfileWhenVHDShouldApply
How the community answered
(21 responses)- A5% (1)
- C10% (2)
- D86% (18)
Explanation
Setting 'DeleteLocalProfileWhenVHDShouldApply' to 1 satisfies both requirements simultaneously. First, it deletes any existing local profile on the session host when a VHD-based profile should apply, ensuring no local profiles persist. Second, because the local profile is removed and there is no fallback, if the Azure Storage account is unreachable and the VHD cannot be mounted, the user cannot log in - enforcing that access is only permitted when the profile is available. 'PreventLoginWithFailure' blocks login on FSLogix failure but does not remove existing local profiles. 'ProfileType' controls read/write modes, and 'NoProfileContainingFolder' blocks login only when the profile folder is absent.
Community Discussion
No community discussion yet for this question.