After an internal review of a potentially compromised BYOD device, it is determined that the user side-loaded a malicious app on the personal profile that harvested their contacts. Why was none of the data in the work profile accessible?

The correct answer is that work profile sandboxing and app isolation prevented any access to the work data. Android Enterprise work profiles create a separate, encrypted container on the device. This container isolates work apps and data from personal apps and data. Malicious apps installed in the personal profile cannot access data or apps within the work profile due to this strong sandboxing and isolation. The other options are incorrect because they don't explain the technical reason for the data protection. While an IT admin might review a device or a user might notice unusual activity, these actions are reactive and don't explain why the work data was inherently protected from the malicious app. A weak passcode policy might compromise the personal profile, but it does not bypass the fundamental isolation provided by the work profile for enterprise data.