Question 430
In the Bayview Compliance pilot environment, a controlled verification is required for: Ransomware preparedness requires Controlled Folder Access for shared profile folders, but the first policy blocks legitimate profile writes. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A simulated unauthorized write is blocked while legitimate FSLogix and business application updates to protected folders succeed. This is an independently observable result of the targeted change: Pilot Controlled Folder Access rules and appropriate authorized-app allowlisting before broad deployment to AVD session hosts. It closes the specific Bayview Compliance failure: Ransomware preparedness requires Controlled Folder Access for shared profile folders, but the first policy blocks legitimate profile writes.
Incorrect Answers
Sampled hosts report the same tamper protection and real-time protection settings after policy refresh. This is evidence for a DIFFERENT remediation: Deploy the intended Defender AV configuration using Microsoft Intune or Group Policy and monitor enforcement drift. That remediation addresses: Multiple hosts in the same pool have inconsistent Defender Antivirus policies because administrators changed settings locally during troubleshooting. It does not establish resolution of the Bayview Compliance problem: Ransomware preparedness requires Controlled Folder Access for shared profile folders, but the first policy blocks legitimate profile writes. The required outcome here is: A simulated unauthorized write is blocked while legitimate FSLogix and business application updates to protected folders succeed.
A newly provisioned host appears in the defender portal with a current sensor health report and expected device identity. This is evidence for a DIFFERENT remediation: Use the supported onboarding package and image or device lifecycle to enroll AVD multi-session hosts into Defender for Endpoint. That remediation addresses: AVD session hosts are missing Defender for Endpoint devices because the image was captured before onboarding the security sensor correctly. It does not establish resolution of the Bayview Compliance problem: Ransomware preparedness requires Controlled Folder Access for shared profile folders, but the first policy blocks legitimate profile writes. The required outcome here is: A simulated unauthorized write is blocked while legitimate FSLogix and business application updates to protected folders succeed.
An unsigned test binary is blocked in enforcement mode while all approved line-of-business applications launch normally. This is evidence for a DIFFERENT remediation: Deploy a tested App Control for Business policy with staged audit and enforcement suitable for multi-session application workloads. That remediation addresses: An AVD image permits arbitrary unsigned executables in user-writable directories despite corporate application allowlisting requirements. It does not establish resolution of the Bayview Compliance problem: Ransomware preparedness requires Controlled Folder Access for shared profile folders, but the first policy blocks legitimate profile writes. The required outcome here is: A simulated unauthorized write is blocked while legitimate FSLogix and business application updates to protected folders succeed.