Free Practice Questions for Zscaler ZDTA Exam

Tamper proofing prevents users or malware from disabling or altering Client Connector after installation. The installer must include the explicit anti-tampering flag to activate that protection during deployment. Option D (--enableAntiTampering) is correct because --enableAntiTampering is the command-line parameter for this control.

Why the other options are incorrect:

A. --secureInstall: --secureInstall sounds like a hardening flag, but the ZCC installer parameter for tamper proofing is --enableAntiTampering.

B. --antiTamper: Anti-tampering prevents local users from disabling or removing Client Connector protections.

C. --disableTampering: Anti-tampering prevents local users from disabling or removing Client Connector protections.

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 B (Zscaler PageRisk) because PageRisk is the Zscaler technology used for real-time website risk scoring.

Why the other options are incorrect:

A. Third-Party Sandbox: A sandbox detonates files to observe malicious behavior. PageRisk is a web-page/domain scoring engine, and Zscaler uses native sandboxing rather than a third-party PageRisk service.

C. Browser Isolation Feedback Form: Browser Isolation renders risky pages remotely to protect the endpoint. A feedback form would collect input; it would not calculate real-time web risk.

D. Deception Controller: The Deception controller manages decoys, lures, and honeytokens for intruder detection. It is about lateral-movement detection, not public website scoring.

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.

Encrypted traffic must be decrypted before platform services can inspect headers, payloads, files, and content for policy enforcement. TLS Decryption is the Zscaler platform service that converts encrypted sessions into inspectable traffic inside the proxy architecture, then re-encrypts the traffic after policy decisions are applied. Option D (TLS Inspection) is correct because visibility into encrypted communications depends on TLS Inspection/Decryption, not on the downstream policy module itself.

Why the other options are incorrect:

A. Antivirus: Antivirus scans files and objects for known malware. Visibility into encrypted traffic requires TLS Inspection before AV can inspect HTTPS content.

B. Tenant Restrictions: REST uses resource-oriented URLs and HTTP methods such as GET, POST, PUT, and DELETE.

C. Web Filtering: Web Filtering controls URL/category access. It does not decrypt encrypted payloads for deeper inspection.

OneAPI authentication is based on modern token-based identity, aligned with OIDC/OAuth concepts through ZIdentity. OIDC is preferred for API authentication because it supports structured token validation and controlled access for automation clients. Option A (OIDC) is correct because OIDC is the preferred authentication approach for OneAPI.

Why the other options are incorrect:

B. SCIM: SCIM keeps users, groups, and attributes synchronized. It does not authenticate an API client or issue OneAPI access tokens.

C. SAML: SAML is for browser SSO. OneAPI access tokens come from an OAuth/OIDC-style token endpoint flow, not from a SAML login assertion.

D. EntraID: Entra ID is Microsoft’s identity provider. It can supply identity data, but the Zscaler component in the question is not Entra ID.