Official docs and some practice tests always call out RDP properties for quick fixes like this. So pretty confident it's A here. Just change clipboard/drive redirection on HostPool1, no Intune config needed.
Q: 2
You have an Azure subscription named Subscription that contains an Azure Virtual Desktop host pool
named HostPool1.
HostPool1 is managed by using Microsoft Intune. Subscription1 contains 50 users that connect to
HostPool1 by using computers that run Windows 10.
You need to prevent the users from copying files between an Azure Virtual Desktop session and the
computers. The solution must minimize administrative effort.
What should you do?
Options
Discussion
storage1 in Bucket 1, storage5 in Bucket 2, storage2 in Bucket 3. Saw the same order in the official study guide.
A . Editing the RDP properties at the host pool level is the standard way to stop clipboard and drive redirection for all sessions, so users can't copy files between their devices and AVD. Intune config profiles are for managing endpoints but don't affect AVD session controls like this. Pretty sure this is what Microsoft expects for least admin effort. Disagree?
Yep, storage1 first for GRS, then storage5 (ZRS), finally storage2 (LRS). That's the order by redundancy FSLogix cares about.
Don’t think D works here, A is correct. The config profile in Intune controls device settings, but to block copying in Azure Virtual Desktop, you need to set the RDP properties on the host pool directly.
A
Maybe D works since HostPool1 is managed by Intune. I thought a configuration profile could block clipboard and drive redirection too, just by pushing a policy. Not 100% sure that's enough for AVD sessions though-anyone disagree?
D imo
It’s D for me. Since HostPool1 is managed with Intune, I figured a configuration profile could push device restriction settings across all the clients, including clipboard and drive redirection. Pretty sure about it but could be mixing up with compliance policy here.
A
Be respectful. No spam.
Question 2 of 35