An administrator must apply file-type controls to a subset of users while ensuring evasion-resistant detection.
Which configuration most directly maps a file-type policy to a user group and role-based security requirements?
Option C combines reliable file identification with precise identity and device scope. The official ZDTA Study Guide describes magic-byte analysis, MIME-type validation, and extension checking. Using all three reduces evasion through renamed extensions or misleading content types. Zscaler's File Type Control documentation supports rules scoped by groups, departments, and locations, so the target SCIM group can receive a stricter policy without imposing it globally. Adding device posture further distinguishes trusted and untrusted endpoints. The specific rule should appear above broader rules so it is evaluated first. A global block ignores role differences. MIME-only inspection leaves gaps when content is mislabeled. URL categories identify destinations, not the true format of transferred files. The combined rule provides the requested role-based and evasion-resistant enforcement.