Ace Your ZDTA Digital Transformation Administrator Exam

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 cate gories identify destinations, not the true format of transferred files. The combined rule provides the requested role-based and evasion-resistant enforcement.

For a deployment using both ZIA and ZPA, the cleanest authentication model is SAML for both services. A shared SAML IdP gives consistent identity, attributes, and group context for internet/SaaS access and private-application access. Option C (Configure Authentication using SAML on both ZIA and ZPA) is correct because using SAML on both ZIA and ZPA provides unified authentication.

Why the other options are incorrect:

A. Use forms Authentication in ZPA and SAML in ZIA: SAML provides browser-based federation by carrying signed assertions from the identity provider to the service provider.

B. Use forms Authentication in ZIA and SAML in ZPA: SAML provides browser-based federation by carrying signed assertions from the identity provider to the service provider.

D. Use forms Authentication for both ZIA and ZPA: Forms authentication is an application-login method. ZIA and ZPA authentication should be based on the supported identity integration model in the scenario, not generic forms auth.

Zscaler File Type Identification uses more than a file extension because attackers can rename files to bypass simple checks. The inspection process evaluates magic bytes, MIME type, and file extension to classify files more accurately before applying File Type Control policy. Option C (Magic bytes, mime type and file extension) is correct because those are the three inspection levels tested here.

Why the other options are incorrect:

A. Mime type, file extension and file size: MIME type is metadata declaring the content type of a transferred object.

B. File extension, content type and file size: File extension is the visible suffix such as .exe or .docx; it is useful but easy for attackers to rename.

D. Magic bytes, mime type and MS Office version: Magic bytes are header values inside a file that reveal the real file type even if the extension is changed.

ZPA evaluates SAML attributes supplied in the user’s assertion. If group membership changes at the identity provider after that assertion was issued, an existing session can continue presenting the old attribute until reauthentication obtains an updated assertion. Zscaler’s IdP migration guidance explicitly instructs users to reauthenticate to receive an updated SAML assertion and then verify policies that use SAML or SCIM attributes. The administrator should compare the assertion issue time with the directory change, force or await reauthentication, and retest the deny rule with the refreshed group value. URL Filtering is a ZIA web control and does not suppress ZPA access policy. Posture logic does not replace identity attributes, and a matched deny is not downgraded by location-group priority. Stale SAML membership therefore explains why the earlier policy evaluation allowed access despite the recent directory change.