In Zscaler App Protection, the core design model is built around three fundamental building blocks presented in a specific logical order: Profiles, Controls, and Policies. The Digital Transformation Engineer material explains that App Protection’s goal is to apply fine-grained security actions to applications and user sessions based on risk and context.
First, Profiles define who is being governed. They group users or devices that share common characteristics (such as department, location, or risk level). Next, Controls define what actions are allowed, restricted, or inspected. Examples include limiting copy-and-paste, file uploads and downloads, printing, clipboard usage, or enforcing additional inspection for sensitive content and risky behaviors. Finally, Policies define when and where those controls are applied by mapping profiles to specific applications or traffic categories under defined conditions (such as user risk posture, device posture, or access method).
Options A and B contain the same elements but in the wrong conceptual order compared to how App Protection is taught and implemented. Option C describes generic security concepts, not the explicit App Protection building-block terminology. Therefore, the correct sequence and terminology, matching the App Protection framework, is Profiles, Controls, Policies.
===========
