Free Practice Questions for Zscaler ZDTA Exam

Microsoft Information Protection labels imported into ZIA are used as criteria in DLP policy enforcement. A custom DLP policy can inspect data in motion and take actions based on the sensitivity labels attached to documents. Option D (Creating a custom DLP Policy) is correct because MIP labels are consumed in DLP policy logic, not in PAC, file type, or posture policies.

Why the other options are incorrect:

A. Creating a custom DLP Dictionary: A custom DLP Dictionary defines match patterns. Imported MIP labels are used in DLP policy conditions/actions, not turned into a dictionary.

B. Creating a SaaS Security Posture Control Policy: SSPM checks SaaS tenant configuration, risky settings, and compliance posture.

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

ZDX monitoring uses two major probe types: Web Probes and Cloud Path Probes. Web Probes measure application availability and page-fetch behavior, while Cloud Path Probes show hop-by-hop path quality, latency, packet loss, and network path conditions. Option D (Web Probe and Cloud Path Probe) is correct because those are the supported ZDX probe types.

Why the other options are incorrect:

A. Page Fetch Time Probe and Cloud Path Probe: Page Fetch Time is a metric from web probing; the pair listed is not the clean Web Probe and CloudPath Probe grouping used by ZDX.

B. Web Probe and Page Fetch Time Probe: A Web Probe is valid, but Page Fetch Time is a metric rather than the second probe type. The network path probe is CloudPath.

C. Page Fetch Time Probe and Server Response time Probe: Server Response Time measures how long the destination application takes to respond to a probe or request.

Option A applies least privilege to the east-west workload flow that must remain available. Zscaler explains that microsegmentation uses identity-based, granular policy so each workload communicates only with resources required for its function, while unauthorized communication is blocked. The payroll server should therefore be permitted to reach the database only on TCP 1433, and unrelated servers should have no path to that database. The wiki should also be separated according to its distinct application identity and access requirements. Placing both applications in a broad segment preserves unnecessary reachability and increases the blast radius; IPS signatures do not replace segmentation. A trusted-network condition addresses user context, not server-to-server authorization. Raising a global user-risk threshold likewise does not constrain the compromised payroll workload’s lateral movement. Identity-based service policy directly contains the threat while preserving the required database flow.

Experience Center is the unified management console for Zscaler for Users administration. It provides a single administrative entry point for internet and SaaS access, private applications, digital experience monitoring, and endpoint agent configuration. Option C (Experience Center) is correct because Experience Center is the unified console, whereas OneAPI is automation-focused.

Why the other options are incorrect:

A. identity Admin Portal: Identity Admin Portal focuses on identity administration, while the Experience Center is the broader unified console.

B. Mobile Admin Portal: Mobile Admin Portal/Client Connector administration is for endpoint-agent configuration, not the identity-policy component in the stem.

D. One API: OneAPI is the automation API layer. Administrators use Experience Center as the unified graphical console.

Malware hidden inside HTTPS can only be evaluated after the encrypted session is inspected. ZIA ' s proxy architecture uses TLS Inspection to decrypt the flow, then malware protection engines compare content, signatures, and reputation indicators against known risks before the session is re-encrypted or blocked. Option C (TLS Inspection decrypting traffic to compare signatures for known risks) is correct because TLS inspection is the enabling layer for malware scanning inside encrypted web traffic.

Why the other options are incorrect:

A. Deception creating decoy files for malware to discover: Deception uses decoys, fake credentials, lures, and traps to expose intruders who are exploring the environment.

B. Application Segmentation of users to specific private applications: An Application Segment defines private app reachability by FQDN/IP, ports, and related settings.

D. Data Loss Protection comparing saved filenames for known risks: Comparing saved filenames is weak and easy to evade. Malware scanning inside HTTPS requires TLS inspection so the file content can actually be evaluated.

Answer D is correct. The high-value rule protects only the applications within its scope. Broad contractor or employee allow rules can still match other internal applications without verifying device posture. Each role-specific allow must therefore require the intended SAML or SCIM identity criteria and compliant posture together, so an unmanaged device cannot qualify merely because its user belongs to an allowed group. The posture-gated sensitive-application rule should remain above broader role rules, followed by the explicit high-value block. Moving the block above the valid posture-based allow would deny compliant users as well. Adding only a Trusted Network condition substitutes location for device trust, and changing unrelated fields does not ensure identity and posture are jointly required. ZPA supports AND and OR operators and first-match rule processing. See Zscaler’s Access Policy overview and Access Policy configuration.

Option D blocks both indicator types at the appropriate enforcement layers. Hard-coded IP callbacks can be matched through a destination IP group referenced by a Cloud Firewall Drop rule, while domain-based callbacks can be denied through a custom URL category and URL Filtering policy. Positioning the specific Firewall denial before generic outbound allows ensures that it is evaluated. Zscaler’s Destination IP Group documentation explains how IP addresses, FQDNs, and URL categories are grouped for Firewall policy. The URL Filtering overview documents rules based on URL categories, users, groups, and other criteria. Browser Isolation permits controlled rendering and is not the correct response for confirmed command-and-control infrastructure. TLS inspection alone does not constitute a deny decision. Risk-based page scoring is less deterministic than explicitly blocking known indicators and does not adequately address hard-coded IP callbacks.

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

A watering-hole attack compromises a legitimate website or service that the intended victims already trust and commonly visit. The attacker plants malicious active content, such as injected JavaScript or exploit code, so users are infected during normal browsing instead of being lured to an obviously suspicious site. The answer is Option D (Watering hole attack) because it specifically describes malware hosted on a commonly accessed service, which is the defining trait of this attack type.

Why the other options are incorrect:

A. Remote access trojans: A remote access trojan gives an attacker interactive control over a compromised host after infection.

B. Phishing: Phishing starts with social engineering: fake messages, links, or login pages. The question describes a legitimate common website being seeded with malicious JavaScript.

C. Exploit kits: Exploit kits automate exploitation after a victim reaches malicious content. They can be used inside an attack chain, but the scenario is naming the watering-hole delivery pattern.

Option C expresses both business intent and security boundaries with explicit, ordered File Type Control rules. The narrow allow rule permits contractor uploads of archives only to the approved code repository. The broader rule then blocks archives and executables when the same group uses generic file-sharing applications. Placing the specific allow above the block prevents the general rule from denying the authorized workflow. Zscaler’s File Type Control overview supports policy criteria such as users, groups, applications, and file types. The File Type Control troubleshooting runbook explains that ZIA identifies actual file types using file signatures, rather than trusting extensions, which addresses renamed executables. A single enterprise block is unnecessarily broad. Out-of-band scanning is not a substitute for upload enforcement, and URL Filtering alone cannot reliably distinguish allowed archives from disguised executable content.

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

Zscaler DLP separates detection logic from enforcement policy. Dictionaries contain the sensitive-data patterns, keywords, identifiers, regexes, or fingerprinted data that identify protected information. DLP engines use those dictionaries to evaluate content, and DLP rules or policies decide the enforcement action. Option C (DLP dictionaries) is correct because the detection foundation of a DLP engine is the dictionary content it evaluates against traffic or files.

Why the other options are incorrect:

A. DLP Policies: DLP policies are the enforcement layer that selects actions such as block, notify, quarantine, or allow.

B. DLP Rules: DLP rules combine detection conditions and policy logic; they are not the content-pattern library itself.

D. DLP identifiers: DLP identifiers are individual match elements, while the broader engine/dictionary structure does the content detection work.