Zscaler Updated ZDTA Exam Questions and Answers by elif

The observed entitlement grant and MFA relaxation create active privilege-escalation exposure, so containment cannot wait for further monitoring. Option A removes the newly granted privilege and restores the stronger authentication condition while limiting changes to the affected account and policy. Zscaler’s Authentication Service role guidance confirms that administrators with the relevant permissions can manage users and entitlements. Forensic continuity is preserved by retaining and streaming the existing evidence; Zscaler’s Authentication Service log-streaming documentation supports streaming authentication and administrator-audit data through NSS or Cloud NSS. A global rollback could disrupt unrelated roles and destroy useful configuration context. Monitoring without containment leaves the elevated service account usable. Pausing SIEM ingestion reduces evidence continuity precisely when correlation is required. After containment, the responder should preserve timestamps, request IDs, source geography, and affected-object details.

Option B contains the impact while preserving useful rollout progress. Reverting only the affected macOS regional cohort restores its prior stable state, and continuing controlled pilots elsewhere avoids treating an isolated failure as a universal defect. Dashboard and log monitoring provides evidence about recurrence, affected versions, platforms, and locations before the next expansion decision. Zscaler’s Client Connector deployment best practices recommend testing a new version with a defined user group before broad deployment. Its application-update configuration guidance supports managed version rollout. Pausing or reverting every region unnecessarily delays security fixes for stable cohorts. Collecting packet captures from all users is disproportionate and may introduce new performance or privacy concerns; diagnostics should remain targeted to affected endpoints while normal telemetry tracks the wider pilot.

================

Security exception allow lists in Advanced Threat Protection are used with sandbox handling to exempt or control specific traffic from sandbox analysis behavior. They are not URL-filter, file-type, or IPS policy definitions themselves. Option A (Sandbox) is correct because the exception list applies to Sandbox policy behavior.

Why the other options are incorrect:

B. URL Filtering: URL Filtering controls web destinations by category, URL, risk, and action such as allow, block, caution, or isolate.

C. File Type Control: File Type Control classifies and restricts uploads or downloads by file type, regardless of filename tricks.

D. IPS Control: IPS inspects traffic inline for exploit signatures and attack patterns, then blocks or resets offending sessions.

Identity Threat Detection and Response focuses on identity risk, particularly in directory environments such as Active Directory. To evaluate AD objects, relationships, permissions, and risky identity configura tions, ITDR needs directory-level data rather than raw packet captures or firewall summaries. Option B (Running LDAP queries) is correct because LDAP queries are the standard mechanism for collecting structured AD domain information for identity-risk analysis.

Why the other options are incorrect:

A. Scanning network ports: Port scanning discovers open TCP/UDP services on hosts. ITDR needs AD identity data, so it queries the directory instead of scanning network sockets.

C. Analyzing firewall logs: Firewall logs show network sessions and policy outcomes. They do not expose AD object relationships, permissions, or identity hygiene the way LDAP directory queries do.

D. Packet sniffing: Packet sniffing captures traffic on the wire. ITDR is not passively sniffing packets here; it gathers structured domain information from Active Directory.