Users report long sign-in times when FSLogix Profile Containers are mounted on your Azure Virtual Desktop session hosts. You suspect Microsoft Defender Antivirus scanning is adding latency. To optimize FSLogix without broadly reducing protection, which two exclusions should you configure on the session hosts? Each correct answer presents part of the solution.

The two correct exclusions directly address potential conflicts between Microsoft Defender Antivirus and FSLogix Profile Containers, optimizing performance without significantly compromising security. Adding process exclusions for frxsvc.exe and frxccd.exe prevents Defender from interfering with the core FSLogix services that manage profile containers. These executables are fundamental to FSLogix operation, and scanning them can introduce significant latency during user sign-in and profile access. Excluding .vhd and .vhdx file extensions from real-time scanning prevents Defender from scanning the actual profile container files while they are actively being accessed by users. Since these files are constantly being read from and written to, real-time scanning can cause I/O bottlenecks and slow down profile loading. Excluding the entire C:\Users folder is too broad and reduces overall security. Opening TCP 3389 is for RDP connectivity, not antivirus optimization. Excluding all network drives is also too broad and could leave other critical data unprotected.