ZDTA Zscaler Digital Transformation Administrator Questions and Answers

Exact Data Match protects structured sensitive data by converting source values into secure hashes before they are used by Zscaler cloud enforcement. The on-premises EDM VM performs indexing locally so raw customer data is not uploaded into the Zscaler cloud. Only hashed values are used for matching. Option C (To automate the indexing process by creating hashes for structured data elements) is correct because the VM automates indexing and sends hashed data, not clear sensitive records, to the cloud.

Why the other options are incorrect:

A. To local analyze cloud transactions for potential PII exfiltration: Local analysis of cloud transactions describes inline inspection behavior. EDM’s on-premises VM is used before enforcement to hash/index structured data safely.

B. To replicate sensitive data across all organizational servers: Replicating sensitive data everywhere would increase exposure. EDM avoids sending raw sensitive structured data to Zscaler by hashing/indexing it locally.

D. To store sensitive data securely and prevent unauthorized data access: Secure storage is a general data-security objective. The EDM VM’s job is not to become a vault; it prepares hashed indexes for matching.

ZIA Malware Protection is an inline security control that blocks malicious files or objects detected through signatures, reputation, and threat-intelligence checks. The policy action must stop the malicious transfer rather than simply route, isolate, or change TLS behavior. Option A (Malware protection) is correct because Block is the malware policy action that prevents the identified malicious content from reaching the user.

Why the other options are incorrect:

B. File reputation: File reputation checks whether an object is known good or bad. The question’s answer is about the behavior-analysis control for unknown files.

C. SHA-256 hashing: SHA-256 hashing is a cryptographic integrity/hash function. It does not execute a suspicious file or observe behavior the way Cloud Sandbox does.

D. Site reputation: Site reputation scores web destinations. It does not detonate or analyze the file itself.

Zscaler Data Protection is primarily adopted to prevent sensitive data from leaving through internet and cloud application channels. The service combines inline DLP, SaaS Security API, endpoint controls, and data discovery to protect data in motion, at rest, and in use. Option C (Prevent loss to Internet and Cloud Apps) is correct because preventing loss to internet and cloud apps is a core data-protection use case.

Why the other options are incorrect:

A. Reduce your Internet Attack Surface: Attack surface is the set of exposed services, addresses, applications, and entry points an attacker can discover.

B. Prevent download of Malicious Files: Blocking malicious downloads is threat protection through malware, ATP, sandbox, or file controls rather than DLP for sensitive data loss.

D. Securely connect users to Private Applications: Secure private-app connectivity is the ZPA use case, not Zscaler Data Protection.

When trusted corporate locations already forward traffic through GRE or IPSec tunnels, Client Connector should not create a second tunnel on top of the location tunnel while the device is on the trusted network. Off trusted network, however, the client must create its own Tunnel 2.0 path to the Zero Trust Exchange. Option C (None for on-trusted and tunnel v2.0 for off-trusted) is correct because the recommended combination is None on trusted and Tunnel 2.0 off trusted.

Why the other options are incorrect:

A. Tunnel v2.0 for on-trusted and tunnel v2.0 for off-trusted: Tunnel v2.0 on a trusted network would duplicate forwarding when GRE/IPSec tunnels already steer location traffic to Zscaler. On trusted networks, the client should not build another tunnel.

B. None for on-trusted and none for off-trusted: None/None leaves Client Connector without tunnel forwarding on both trusted and untrusted networks. That defeats the intended traffic steering design.

D. Tunnel v2.0 for on-trusted and none for off-trusted: Tunnel v2.0 on trusted and none off trusted reverses the desired behavior. Remote/off-trusted users need Client Connector tunneling; trusted locations already use GRE/IPSec.

Inline Data Protection means Zscaler is inspecting data while it is actively moving through an inline traffic path, not after the file is already stored or copied locally. In ZIA, inline DLP evaluates web, SaaS, and webmail uploads in real time by using DLP engines, dictionaries, EDM/IDM, OCR, and other content-inspection logic. That is why Option D (Blocking the attachment of a sensitive document in webmail) is the verified answer: the sensitive document is attached to webmail and Zscaler can stop that outbound transaction before the content leaves the organization.

Why the other options are incorrect:

A. Preventing the copying of a sensitive document to a USB drive: USB-drive blocking is endpoint/data-in-use protection. It stops a local copy action, while inline DLP stops sensitive content as it moves through ZIA traffic.

B. Preventing the sharing of a sensitive document in OneDrive: OneDrive sharing control is normally SaaS API/CASB enforcement against a file already stored in OneDrive. The webmail attachment case is live data-in-motion inspection.

C. Analyzing a customer’s M365 tenant for security best practices: M365 tenant analysis checks configuration posture, permissions, and risky settings. It gives visibility and recommendations; it does not block a user upload in real time.

Blocked Countries is the Advanced Threat Protection feature used to restrict website access based on geographic location. It gives administrators a geographic control to reduce exposure to destinations associated with embargoed, high-risk, or disallowed regions. Option C (Blocked Countries) is correct because the control is based on country/geography, not malware type.

Why the other options are incorrect:

A. Spyware Callback: Spyware Callback blocks outbound C2-style communications. It does not describe the browser exploit category in ATP policy.

B. Botnet Protection: C2/botnet controls detect hosts communicating with known or suspected command-and-control infrastructure.

D. Browser Exploits: Browser Exploits are attacks against browser vulnerabilities. The question’s correct category is the one named by the tested ATP setting, not generic browser exploit handling.

Advanced Threat Protection defends users from malicious active content, phishing, exploit behavior, C2 callbacks, and risky web destinations. It works as part of ZIA's inline security stack, often alongside TLS inspection, Cloud Sandbox, DNS security, IPS, and URL categorization. Option A (Cloud App Control) is correct because malicious active content is the security object ATP is designed to detect and block.

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. Advanced Threat Protection: Advanced Threat Protection blocks malicious active content and related threats. The question is asking for the policy feature named by the configured category, which is not ATP here.

D. Mobile Malware Protection: Mobile Malware Protection focuses on mobile-device malware. The tested ZIA feature is broader web/cloud enforcement rather than mobile-only protection.

Zscaler's unified data-protection model reduces the policy and visibility gaps created by separate point products. A unified stack lets DLP, SaaS Security, endpoint controls, cloud-data protection, and posture insight share consistent classification and enforcement logic. Option D (Eliminating of gaps associated with multiple point solutions) is correct because eliminating gaps between disconnected tools is a major advantage of unified data protection.

Why the other options are incorrect:

A. Reducing visibility into data movement across the cloud: Reducing visibility is a bad outcome. Unified data protection is valuable because it increases visibility across channels and closes blind spots.

B. Working together with traditional hardware appliances: Traditional hardware appliances may still exist, but the advantage being tested is not appliance coexistence. It is eliminating gaps between separate point products.

C. Increasing complexity and manageability in DLP security policies: Increasing complexity is the problem unified data protection is meant to reduce. A single policy/control model should simplify DLP operations.

Intermediate CA rotation reduces exposure if a certificate were mishandled and keeps the inspection trust chain short-lived. Zscaler's rotation model for intermediate CA certificates uses a short validity window rather than long-lived static certificates. Option C (Certificates are rotated every seven days and have a 14-day expiration) is correct because the tested rotation policy is seven-day rotation with a fourteen-day expiration.

Why the other options are incorrect:

A. Certificates are rotated every 90 days and have a 180-day expiration: Ninety-day rotation and 180-day expiration would leave intermediate certificates active much longer than the Zscaler inspection model described here.

B. Lifetime certificates have no expiration date: Lifetime certificates would never expire, which is the opposite of good inspection-certificate hygiene. Zscaler uses short-lived intermediate certificates.

D. Certificates are issued dynamically and expire in 24 hours: A 24-hour expiration would be unnecessarily short and is not the documented intermediate CA timing in this exam item.

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 engines) 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. Hosted PAC Files: A PAC file tells the client or browser which proxy path to use for matching destinations.

B. Index Tool: Index Tool suggests the hashing/indexing utility itself. In Zscaler DLP terminology, the protected content matching object is the IDM/EDM template or dictionary construct named by the answer.

D. VPN Credentials: VPN credentials authenticate remote network access. They are not a DLP matching method for identifying sensitive documents.

The relationship between App Connector Groups and Server Groups is configured when the Server Group is created or edited. The Server Group points to the App Connector Groups that have visibility to the applications, so ZPA knows which connectors can serve the private traffic. Option B (When a new Server Group is created it points to the App Connector Groups that provide visibility to this Server Group) is correct because Server Group configuration establishes the mapping.

Why the other options are incorrect:

A. The relationship between App Connector Groups and Server Groups is established dynamically in the Zero Trust Exchange as users try to access Applications: A Server Group groups application servers and maps them to App Connector Groups that can reach those servers.

C. Both App Connector Groups and Server Groups are linked together via the Data Center element: A Server Group groups application servers and maps them to App Connector Groups that can reach those servers.

D. When you create a new App Connector Group you must select the list of Server Groups to which it provides visibility: A Server Group groups application servers and maps them to App Connector Groups that can reach those servers.

Zscaler SaaS Security Posture Management evaluates supported SaaS platforms for risky configurations, posture gaps, and compliance issues. Google Workspace is one of the supported SaaS environments for posture assessment, whereas storage or collaboration tools in the other choices do not match this SSPM support item. Option D (Google Workspace) is correct because Google Workspace is the supported SaaS platform in this question.

Why the other options are incorrect:

A. Amazon S3: Amazon S3 is cloud object storage, not the SaaS collaboration suite named by the tested SSPM support item.

B. Webex Teams: Webex Teams is a collaboration app. The question’s intended application/control is not Webex Teams.

C. Dropbox: Dropbox is cloud storage. It is a common SaaS destination, but it is not the application identified by the scenario’s correct answer.

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 A (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:

B. Pre-existing Compromise: Pre-existing compromise means the target is already affected before the current event. A watering-hole attack is different: the attacker poisons a site the victims already visit.

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

D. 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.

Custom DLP dictionaries let administrators define the exact business-specific content that should be treated as sensitive. They can include keywords, phrases, patterns, and regex expressions that match regulated data, internal identifiers, or proprietary terms. Option A (Define specific keywords, phrases, or patterns relevant to their organization's sensitive data policy) is correct because those dictionary entries are what Zscaler uses to detect data in motion.

Why the other options are incorrect:

B. Define specific governance and regulations relevant to their organization's sensitive data policy: Governance and regulatory labels help describe policy intent. A custom dictionary needs the actual sensitive-data tokens: keywords, phrases, or patterns.

C. Define specific SaaS tenant relevant to their organization's sensitive data policy: A SaaS tenant value controls which tenant or instance users may access. Custom dictionaries define content patterns, not tenant boundaries.

D. Define specific file types relevant to their organization's sensitive data policy: File type definitions classify files such as executables or archives. Custom DLP dictionaries define sensitive words, phrases, regexes, or identifiers.

ZDX Score is a normalized digital-experience score used to represent how well a user or application is performing. It is expressed on a 1-to-100 scale, making degraded application, network, and endpoint experience easy to compare across users, locations, and time windows. Option A (1-100) is correct because 1-100 is the ZDX scoring range.

Why the other options are incorrect:

B. 1-10: A 1-10 scale is too coarse for ZDX. ZDX uses a 1-100 score so administrators can see more granular experience changes.

C. 1 - 1000: A 1-1000 scale would imply excessive precision that ZDX does not present. The product score is the simpler 1-100 user-experience scale.

D. 0 - 50: A 0-50 range is not the ZDX scale. ZDX scores are represented on a 1-100 scale.

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.

Zscaler Bandwidth Control shapes traffic from the user's perspective by managing outbound flows. Inbound traffic and localhost traffic are not shaped in the same manner because the control point is the egress direction where user traffic leaves toward Zscaler and destinations. Option A (Outbound traffic is shaped. Inbound or localhost traffic is unshaped) is correct because Bandwidth Control shapes outbound traffic only.

Why the other options are incorrect:

B. Outbound or inbound traffic is shaped. Localhost traffic is unshaped: Inbound shaping would control return traffic, which is not how Zscaler Bandwidth Control is applied from the user perspective.

C. Inbound traffic is shaped. Outbound or localhost traffic is unshaped: Inbound shaping would control return traffic, which is not how Zscaler Bandwidth Control is applied from the user perspective.

D. Localhost traffic is shaped. Outbound or Inbound traffic is unshaped: Inbound shaping would control return traffic, which is not how Zscaler Bandwidth Control is applied from the user perspective.

Trusted Network Detection uses network-observable criteria such as DNS server, DNS search domain, gateway, and network ranges to determine whether the endpoint is on a corporate network. An Org ID is tenant identity, not a network characteristic visible on the endpoint. Option C (Org ID) is correct because Org ID is unrelated to trusted-network properties.

Why the other options are incorrect:

A. DNS Server: DNS Server criteria identify a trusted network by checking whether the endpoint sees expected internal resolver addresses.

B. Default Gateway: Default Gateway can identify a local network path, but it is not always one of the exact trusted-network criteria set in this item.

D. Network Range: Network range can describe local addressing, but the tested Trusted Network property set is based on the exact ZCC detection fields in the question.

Botnet Protection targets command-and-control behavior, including known C2 destinations, suspicious command traffic, and unknown C2 patterns detected through analytics or AI/ML. IPS and YARA-style content analysis are used to identify C2-like traffic and malicious patterns, not general malware categories alone. Option A (Command and Control Traffic) is correct because Command and Control traffic is the botnet behavior being protected against.

Why the other options are incorrect:

B. Ransomware: Ransomware encrypts or extorts data after compromise. It is not the callback/C2 category for outbound spyware communication.

C. Trojans: Trojans disguise malicious code as legitimate software. Spyware callback protection targets outbound communication from spyware to its controller.

D. Adware/Spyware Protection: Adware/spyware protection is a broad category. The tested feature is the specific spyware callback protection control.

An App Connector is the ZPA component that sits near private applications and establishes outbound-only connections to the Zscaler cloud. It brokers application reachability without exposing inbound ports or public IP addresses, allowing users to connect to applications rather than networks. Option D (App Connectors mediate seamless communication for applications, services and data sources) is correct because App Connectors mediate communication to private applications, services, and data sources.

Why the other options are incorrect:

A. App Connectors enforce security policies for traffic destined for SaaS applications: SaaS applications are handled by ZIA controls such as URL Filtering, Cloud App Control, and DLP, not by ZPA App Connectors.

B. App Connectors enable user experience monitoring for all applications: User-experience monitoring is ZDX’s job. App Connectors provide the outbound broker path that lets users reach private applications.

C. App Connectors expose a public IP for users to connect to for private application access: Publishing a public IP exposes an attack surface; ZPA avoids that by using inside-out connector connectivity.

A ZDX custom application of type Network measures network-path and application reachability metrics, not local storage performance. Metrics such as server response time, ZDX Score, and gateway information are aligned to network/application experience. Disk I/O is an endpoint hardware metric and is not produced by a network-type custom application probe. Option D (Disk I/O) is correct because Disk I/O is outside the network probe metric set.

Why the other options are incorrect:

A. Server Response Time: Server Response Time measures how long the destination application takes to respond to a probe or request.

B. ZDX Score: ZDX Score summarizes user experience for an application, location, or user from measured telemetry.

C. Client Gateway IP Address: Client Gateway IP identifies the gateway or egress point seen from the client path.

A Zscaler Client Connector Forwarding Profile determines how traffic is steered to the Zscaler cloud and what fallback behavior applies. For Tunnel 2.0, the profile defines how the client behaves when the preferred DTLS tunnel cannot be established, including fallback to TLS where configured. Option A (Fallback methods and behavior when a DTLS tunnel cannot be established) is correct because DTLS fallback behavior is a Forwarding Profile function.

Why the other options are incorrect:

B. Application PAC file location: A PAC file tells the client or browser which proxy path to use for matching destinations.

C. System PAC file when off trusted network: Trusted Network detection decides whether the device is on a known corporate network using signals such as DNS servers, search domains, gateways, or hostname resolution.

D. Fallback methods and behavior when a TLS tunnel cannot be established: TLS tunneling is the fallback encrypted transport when DTLS is unavailable.

In the Zero Trust Exchange functional services view, Antivirus belongs to the Security Services layer. That layer contains protective inspection capabilities such as antivirus, sandbox, firewall/security inspection, and related threat controls. Option C (Security Services) is correct because Antivirus is a security service, not a platform, access-control, or pure ATP-only category.

Why the other options are incorrect:

A. Platform Services: Platform Services provide shared foundations such as policy, identity, and logging. Antivirus belongs under the security-services protection layer.

B. Access Control Services: Access Control Services handle access, segmentation, and conditional controls. Antivirus is a threat inspection capability under Security Services.

D. Advanced Threat Prevention Services: Advanced Threat Prevention is a specific threat capability family. In the functional diagram, Antivirus is grouped more broadly under Security Services.

SAML authenticates the user at login time, but efficient user provisioning needs automated lifecycle mechanisms. SCIM synchronizes users, groups, and attributes from the IdP, while SAML auto-provisioning/JIT can create users dynamically during successful authentication. Option D (SCIM and SAML Autoprovisioning) is correct because SCIM and SAML auto-provisioning are the efficient provisioning methods.

Why the other options are incorrect:

A. Hosted User Database and Directory Server Synchronization: A hosted user database is manual or local account storage; it does not automate lifecycle changes as cleanly as SCIM/JIT.

B. SAML and Hosted User Database: SAML can create users at sign-in with JIT, but by itself it is an authentication assertion, not continuous lifecycle synchronization like SCIM.

C. SCIM and Directory Server Synchronization: SCIM provisions and synchronizes users, groups, and attributes between an identity provider and Zscaler.

The ZDTA study guide frames common breaches around a four-step lifecycle: discover the attack surface, compromise an entry point, move laterally, and exfiltrate data. Finding the attack surface is the reconnaissance phase in which attackers search for exposed VPNs, firewalls, applications, ports, or public services. Option D (Find Attack Surface) is correct because attack-surface discovery is one of the documented stages.

Why the other options are incorrect:

A. Find Cash Safe: That phrase describes a physical-world target, not a step in the cyberattack lifecycle.

B. Find Email Addresses: Email and webhooks forward alerts to people or third-party systems for response workflows.

C. Find Least Secure Office Building: That phrase describes a physical-world target, not a step in the cyberattack lifecycle.

Z-Tunnel 2.0 extends forwarding beyond web proxy traffic by securing all IP unicast traffic through DTLS/TLS tunnels to the Zero Trust Exchange. This enables Cloud Firewall and other controls to inspect all TCP and UDP ports, and ICMP where supported, rather than only browser HTTP/HTTPS flows. Option D (Z-Tunnel 2.0) is correct because Tunnel 2.0 is the all-ports-and-protocols forwarding model for Client Connector.

Why the other options are incorrect:

A. Secure Shell (SSH): RDP, SSH, and VNC are privileged remote access protocols for desktop, shell, and graphical administration.

B. Tunnel with local proxy: Tunnel with Local Proxy creates a loopback proxy path on the endpoint for forwarding selected traffic.

C. Enforce PAC: Enforced PAC controls browser or system proxy behavior. Z-Tunnel 2.0 is the mechanism that secures all IP unicast traffic from the endpoint.

A URL Filtering Caution action is designed for web-style requests where the user can be warned before proceeding. The supported request methods tested here are Connect, GET, and HEAD, which align with browser-driven web access and HTTPS tunnel establishment. Option A (Connect, Get, Head) is correct because those methods are valid for the Caution action.

Why the other options are incorrect:

B. Options, Delete, Put: OPTIONS, DELETE, and PUT are HTTP methods, but the canonical REST basics in the guide include GET, POST, PUT, and DELETE.

C. Get, Delete, Trace: TRACE is an HTTP diagnostic method and is not part of the standard REST method set emphasized for Zscaler automation.

D. Connect, Post, Put: CONNECT is proxy tunneling behavior. REST API basics focus on resource methods such as GET, POST, PUT, and DELETE.

Strict Enforcement requires the installer to know both which Zscaler cloud to enroll against and which policy token authorizes the enforcement configuration. The cloudName parameter directs the client to the correct cloud, while policyToken applies the required strict-enforcement policy during enrollment. Option A (cloudName and policyToken) is correct because those two options are the required installer inputs.

Why the other options are incorrect:

B. userDomain and deviceToken: userDomain tells Client Connector the user login domain so it can route enrollment toward the right IdP.

C. cloudName and deviceToken: cloudName tells the installer which Zscaler cloud or tenant environment the client should use.

D. userDomain and policyToken: userDomain tells Client Connector the user login domain so it can route enrollment toward the right IdP.

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.

A ZPA microtunnel is the per-application communication channel created after the user is authenticated and authorized. It carries traffic from the user side through the Zscaler service edge to the App Connector path for the internal application. Option D (To create an end-to-end communication channel to internal applications) is correct because the M-Tunnel is built for private application communication, not endpoint-to-endpoint or IdP connectivity.

Why the other options are incorrect:

A. To provide an end-to-end communication channel between ZCC clients: ZCC-to-ZCC communication would be peer endpoint connectivity. A ZPA microtunnel is created from the user side toward a specific internal application.

B. To provide an end-to-end communication channel to Microsoft Applications such as M365: Microsoft 365 optimization uses local breakout, DNS locality, and inspection bypass where Microsoft recommends it for performance.

C. To create an end-to-end communication channel to Azure AD for authentication: Azure AD communication is part of authentication. The microtunnel carries private-application traffic after access is authorized.

TLS/SSL inspection can expose customer content to the inspection service, so the contractual and privacy basis matters. The Zscaler Data Processing Agreement governs how Zscaler processes customer data when services such as ZIA inspect encrypted traffic. It is not merely an acceptable-use or marketing privacy statement. Option D (Zscaler Data Processing Agreement) is correct because the DPA is the agreement that addresses customer-data processing responsibilities.

Why the other options are incorrect:

A. Zscaler Compliance Policy: A compliance policy is an internal rule or control statement. The formal privacy/legal agreement for ZIA data processing is the Data Processing Agreement.

B. Zscaler Privacy Policy: A privacy policy explains how data is handled generally. The customer agreement governing processed data is the Data Processing Agreement.

C. Acceptable Use Policy: An Acceptable Use Policy tells users what behavior is allowed. It is not the contractual data-processing agreement for TLS inspection.

Malware scanning has practical file-size limits because the service must inspect objects inline without creating unacceptable latency. The tested Zscaler limit for Malware Protection scans is 400 MB. Larger files require different risk handling, policy design, or sandbox workflows depending on deployment requirements. Option D (Zscaler scans files up to 400 MB) is correct because it states the 400 MB scan limit.

Why the other options are incorrect:

A. Zscaler scans all files regardless of size: Scanning every file regardless of size would create unrealistic latency and resource requirements. Zscaler documents a maximum scan size instead.

B. Zscaler scans files only if they are below 100 MB: A 100 MB limit understates the documented malware-scan size limit. The tested maximum is 400 MB.

C. Zscaler scans files up to 500 MB: A 500 MB limit overstates the documented malware-scan size limit. The tested maximum is 400 MB.

In Zscaler DLP, dictionaries define what sensitive content looks like, while engines combine and apply those dictionaries for detection. A DLP policy then uses an engine to decide whether matching content should be blocked, allowed, notified, or audited. Option C (A Data Loss Prevention policy applies a DLP Engine and a DLP engine uses DLP dictionaries) is correct because it states the proper hierarchy: policy applies a DLP Engine, and the DLP Engine uses DLP dictionaries.

Why the other options are incorrect:

A. A DLP Engine runs over the traffic being sent out and dynamically selects DLP dictionaries to apply: DLP dictionaries hold the sensitive-data patterns, keywords, identifiers, or fingerprinted values used for detection.

B. A Data Loss Prevention policy applies a DLP dictionaries: DLP dictionaries hold the sensitive-data patterns, keywords, identifiers, or fingerprinted values used for detection.

D. A Data Loss Prevention policy applies a DLP Engine: A policy applying only a DLP Engine is incomplete as an explanation. The engine itself uses dictionaries to identify the sensitive content.

Device posture must be re-evaluated regularly because endpoint state can change after access is granted. The maximum default frequency tested here is fifteen minutes, which gives Zscaler a relatively current view of compliance conditions. Option A (15 minutes) is correct because posture profile evaluation can occur every fifteen minutes by default.

Why the other options are incorrect:

B. 2 minutes: Two minutes would create much more frequent posture evaluation than the default maximum cadence. The tested default maximum frequency is fifteen minutes.

C. 5 minutes: Five minutes is more frequent than the default maximum posture-profile evaluation cadence. The tested value is fifteen minutes.

D. 10 minutes: Ten minutes is still shorter than the default maximum posture-profile evaluation cadence. The correct default maximum is fifteen minutes.

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.

Z-Tunnel 2.0 extends forwarding beyond web proxy traffic by securing all IP unicast traffic through DTLS/TLS tunnels to the Zero Trust Exchange. This enables Cloud Firewall and other controls to inspect all TCP and UDP ports, and ICMP where supported, rather than only browser HTTP/HTTPS flows. Option C (Zscaler Client Connector will encapsulate the user's traffic in DTLS/TLS tunnels to the ZTE) is correct because Tunnel 2.0 is the all-ports-and-protocols forwarding model for Client Connector.

Why the other options are incorrect:

A. Zscaler Client Connector will encapsulate the user's traffic in GRE tunnels to the ZTE: Zscaler Client Connector is the endpoint agent that steers traffic, authenticates users, reports posture, and supplies ZDX telemetry.

B. Zscaler Client Connector will encapsulate the user's traffic in IPSec tunnels to the ZTE: IPS inspects traffic inline for exploit signatures and attack patterns, then blocks or resets offending sessions.

D. Zscaler Client Connector will encapsulate the user's traffic in HTTP Connect tunnels to the ZTE: Zscaler Client Connector is the endpoint agent that steers traffic, authenticates users, reports posture, and supplies ZDX telemetry.

Advanced Threat Protection defends users from malicious active content, phishing, exploit behavior, C2 callbacks, and risky web destinations. It works as part of ZIA's inline security stack, often alongside TLS inspection, Cloud Sandbox, DNS security, IPS, and URL categorization. Option C (Malicious active content) is correct because malicious active content is the security object ATP is designed to detect and block.

Why the other options are incorrect:

A. Vulnerable JavaScripts: Vulnerable JavaScript describes risky script behavior or client-side code, but it is narrower than the full ATP active-content category.

B. Large iFrames: An iFrame is an embedded page frame; suspicious iFrames can be a signal, but size alone is not the ATP protection category.

D. Command injection attacks: Command injection targets an application or server by passing operating-system commands through vulnerable input fields.

A ZIA Location represents a network egress point such as a branch, campus, or data center. A Sublocation divides that location into logical traffic groups, commonly to separate employee traffic, guest traffic, IoT networks, or departments so different policies and reporting can apply. Option A (The section of a corporate Location used to separate traffic, like traffic from employees from guest traffic) is correct because a sublocation is a subdivision of a corporate location for traffic separation.

Why the other options are incorrect:

B. The section of a corporate Location that sends traffic to a Subcloud: A subcloud is not how ZIA sublocations are defined for policy and reporting.

C. Every one of the sections in a Corporate Location that use overlapping IP addresses: Overlapping IP space is an addressing challenge; a sublocation is used to separate traffic inside a larger location.

D. A way to separate generic traffic from that coming from Client Connector: Separating generic traffic from Client Connector traffic is not the purpose of ZIA sublocation design.

Cloud Browser Isolation protects users by rendering risky web content in a remote browser environment instead of on the endpoint. URL Filtering can use Isolate as an action, so users may still access selected untrusted sites while scripts, active content, and browser-exploit risk remain separated from the device. Option D (Yes. Isolate is a possible Action for URL Filtering) is correct because isolation is an enforceable URL Filtering action, not a separate manual workaround.

Why the other options are incorrect:

A. No. Cloud Browser Isolation is a separate platform: Browser Isolation renders web content remotely so active content never executes directly on the endpoint.

B. No. Cloud Browser Isolation is only a feature of Advanced Threat Defense: Browser Isolation renders web content remotely so active content never executes directly on the endpoint.

C. Yes. After blocking access to a site, the user can manually switch on isolation: Browser Isolation renders web content remotely so active content never executes directly on the endpoint.

XSS protection addresses malicious browser-side script behavior, including attempts to steal cookies or send potentially malicious requests through a trusted site context. These attacks exploit the browser's trust in a legitimate application and can expose sessions or user data. Option C (Cookie Stealing and Potentially Malicious Requests) is correct because cookie stealing and potentially malicious requests are XSS exploit outcomes.

Why the other options are incorrect:

A. Security Exceptions and Malicious Active Content Protection: Malicious active content means scripts, applets, or browser-executed objects that can exploit or manipulate a user session.

B. File Format Vulnerabilities and Browser Exploits: File-format vulnerabilities and browser exploits are broader exploit categories. XSS specifically abuses script execution in a trusted web context.

D. Cookie Stealing and Advanced Threats Policy: Cookie stealing is an XSS outcome, but “Advanced Threats Policy” is a policy family, not the second XSS exploit type in the answer.

Client Connector profile changes do not always take effect at the moment an administrator saves them. App Profile policy settings such as logout password follow the client's scheduled policy-refresh behavior. The tested interval for these policy updates is sixty minutes. Option D (Policy updates occur every 60 minutes, so the logout password will be in effect after the next scheduled update) is correct because the new logout password is applied after the next scheduled policy update.

Why the other options are incorrect:

A. Policy updates happen in real time, so the new logout password is in effect as soon as the change is saved: The logout password is an App Profile control that prevents users from casually signing out or disabling the client.

B. The new logout password will be in effect after the Activate button is clicked in the Admin portal: The logout password is an App Profile control that prevents users from casually signing out or disabling the client.

C. The new logout password will be in effect after the user clicks Update Policy on the client: The logout password is an App Profile control that prevents users from casually signing out or disabling the client.

Zscaler PageRisk, specifically the Page Risk Index, is the proprietary scoring capability used in ZIA to evaluate the risk of web pages dynamically. Instead of relying only on static URL blocklists, PageRisk uses a multi-data algorithm that considers page content and domain characteristics. Page-content signals include risky scripts, suspicious iFrames, XSS indicators, vulnerable controls, and other active content. Domain signals include reputation, hosting location, age, and relationships to risky top-level domains. The verified answer is Option D (Zscaler applies a multi data algorithm to the web page) because PageRisk is the Zscaler technology used for real-time website risk scoring.

Why the other options are incorrect:

A. Zscaler licenses a PageRisk Feed from a 3rd party: A third-party PageRisk feed would be externally sourced reputation; the Zscaler answer is its own multi-data web-page algorithm.

B. It applies deobfuscation to all data: Deobfuscation can reveal hidden script behavior, but PageRisk uses a broader multi-signal algorithm.

C. It is the RSA Security algorithm: RSA is a cryptographic/public-key algorithm family, not Zscaler web-page risk scoring.