AZ-140 · Question #260
You have an Azure subscription that is linked to a hybrid Microsoft Entra tenant. You have an Azure Virtual Desktop deployment that contains the host pools shown in the following table. All the…
The correct answer is E. Pool1, Pool2, Pool3, and Pool4. All four pools can access share1 because every session host in the deployment is Microsoft Entra joined, and Azure Files supports Microsoft Entra Kerberos authentication for Entra joined machines in a hybrid tenant - meaning there is no pool-type restriction on accessing…
Question
You have an Azure subscription that is linked to a hybrid Microsoft Entra tenant. You have an Azure Virtual Desktop deployment that contains the host pools shown in the following table. All the session hosts are Microsoft Entra joined. You plan to implement FSLogix profile containers and store them on an Azure Files share named share1. Which host pools contain session hosts that can access the FSLogix profile containers on share1?
Exhibit
Options
- APool1 only
- BPool1 and Pool2 only
- CPool1 and Pool3 only
- DPool1, Pool2, and Pool3 only
- EPool1, Pool2, Pool3, and Pool4
How the community answered
(30 responses)- A3% (1)
- B7% (2)
- C13% (4)
- D3% (1)
- E73% (22)
Explanation
All four pools can access share1 because every session host in the deployment is Microsoft Entra joined, and Azure Files supports Microsoft Entra Kerberos authentication for Entra joined machines in a hybrid tenant - meaning there is no pool-type restriction on accessing FSLogix profile containers. The table likely differentiates pools by type (pooled vs. personal) and/or validation environment status, but neither attribute blocks Azure Files access; FSLogix profile containers on Azure Files work for both pooled and personal host pools equally. Distractors A–D incorrectly imply that only certain pool configurations (e.g., pooled-only, or non-validation-only) are compatible, which would be true under older AD DS-only authentication models but not with Microsoft Entra Kerberos.
Memory tip: Think "Entra joined = Kerberos ticket = Azure Files access" - once all hosts share the same Entra join type, pool topology (personal vs. pooled, validation vs. production) is irrelevant to FSLogix storage connectivity.
Topics
Community Discussion
No community discussion yet for this question.