Free Zscaler ZDTE Practice Exam with Questions & Answers | Set: 2

Zscaler Private Access (ZPA) uses the Log Streaming Service (LSS) to deliver ZPA logs (such as user activity and connector/authentication logs) to external SIEM and analytics platforms. LSS relies on a ZPA App Connector as the local relay between the ZPA service and the downstream log receiver. If network connectivity between ZPA and the local App Connector is interrupted, log delivery may be temporarily disrupted.

According to Zscaler integration guidance, when connectivity between ZPA and the local App Connectors is restored, LSS can retransmit up to 15 minutes of previously undelivered log data, although this retransmission is not guaranteed in all circumstances. This limited replay window is designed to provide reasonable resilience for short outages without requiring large local storage on the connector.

The 15-minute buffer applies specifically to ZPA log streaming scenarios and is distinct from longer-term log retention in Zscaler’s logging cluster or external SIEM. Options A, C, and D overstate the supported replay duration and do not match Zscaler’s documented behavior. To minimize log gaps beyond this 15-minute window, Zscaler recommends resilient network paths for App Connectors and careful monitoring of connector health so that LSS can operate continuously.

===========

In Zscaler, the Endpoint DLP report is specifically designed to give security teams visibility into how end users interact with sensitive data on their endpoints (laptops, desktops, etc.). This report aggregates activity such as copying, saving, printing, uploading, or otherwise handling sensitive content that is detected and classified by Zscaler Endpoint DLP. It focuses on data risk rather than just malware or traffic volumes, so it shows which files, users, and devices are involved in policy matches, along with the context of each event.

Unlike a generic malware or data usage report, the Endpoint DLP report is tightly aligned with DLP policies and data classifications you configure (such as PII, financial data, source code, or custom patterns). This allows you to quickly see which policies are triggering on endpoints, which channels or applications are most frequently involved, and where to fine-tune rules or add additional controls. Because it is endpoint-focused, it covers scenarios even when users are off the corporate network, giving a unified view across inline and endpoint DLP enforcement. For exam purposes, this is why Endpoint DLP report is the correct answer.

===========

Zscaler External Attack Surface Management (EASM) includes a dedicated capability called Lookalike Domains. Zscaler defines lookalike domains as fraudulent or fake domains intentionally created by threat actors to mimic your legitimate domains and brand presence, often for phishing, credential theft, or brand abuse.

Within the EASM portal, the Lookalike Domains pages and widgets present a curated list of suspicious domains that closely resemble your seed or official domains. Analysts can review exposure scores, registrar details, hosting information, and other attributes to determine which of these domains pose the highest risk and warrant takedown or additional monitoring.

This feature is specifically designed for external risk and brand-protection use cases: it highlights where attackers are impersonating your organization on the public internet, which is a core component of digital-risk and external-attack-surface management. While words such as “fake,” “mimic,” or “spoofing” may be used generically in security discussions, “Lookalike Domains” is the exact term and feature name Zscaler uses in the EASM product and documentation. Options A, B, and C do not correspond to a named EASM capability and therefore are not correct in the ZDTE context.

===========

Zscaler Digital Experience (ZDX) organizes its telemetry and alerting around key domains: Application, Network, and Device. Wi-Fi signal strength is a client-side characteristic of the endpoint itself, measured from the user’s device, not from the network path or the application service. In the ZDX training content, Wi-Fi signal, Wi-Fi link speed, CPU, memory, and similar metrics are clearly categorized under Device health.

When creating an alert rule to monitor newly deployed laptops, the administrator should therefore choose a Device-type alert and then select Wi-Fi signal–related metrics and thresholds. This allows ZDX to trigger alerts whenever the Wi-Fi signal on those endpoints falls below an acceptable level, helping operations teams quickly identify poor local wireless conditions that degrade user experience.

Network alerts are intended for end-to-end path health (latency, packet loss, DNS resolution, gateway reachability, etc.), and Application alerts focus on performance and availability of specific apps or services. “Interface” as a standalone alert type is not how ZDX structures its top-level alert categories; interface-related metrics are surfaced as device-side attributes. Consequently, the correct classification for Wi-Fi signal monitoring in ZDX is a Device alert rule.

===========

Zscaler Client Connector supports multiple tunnel modes to send user traffic to the Zscaler security cloud. In the Digital Transformation Engineer material, Z-Tunnel 2.0 is described as the recommended and most capable mode because it supports both web and non-web applications across all ports and protocols. This enables comprehensive inspection and Zero Trust policy enforcement for SaaS, web, and private applications from a single, unified tunnel.

Z-Tunnel 1.0 was primarily designed for web traffic, with limitations around non-web protocols and certain advanced use cases. As enterprises adopt more modern and diverse application stacks (VoIP, collaboration tools, custom TCP/UDP apps), Z-Tunnel 1.0 often cannot provide full coverage. GRE and IPSec tunnels (options A and C) are typically used for site-to-cloud connectivity from branch or data center routers, not as endpoint-based tunnels from user devices.

Z-Tunnel 2.0 uses an advanced encapsulation mechanism that can simultaneously support ZIA and ZPA, apply granular user- and device-based policies, and provide rich telemetry for analytics. It is explicitly positioned in Zscaler’s training as the tunnel mode that delivers end-to-end protection for both web and non-web traffic, making it the correct answer for enterprises needing broad, modern coverage.

===========

Zscaler’s application segmentation is the feature that delivers granular, per-application control over which users can access which private apps. In the ZDTE study material and cyberthreat protection quick reference guides, Zscaler explains that application segmentation makes apps and servers completely invisible to unauthorized users, thereby minimizing the attack surface while allowing authorized users to reach only the specific applications they are entitled to.

Zscaler Private AppProtection builds on this segmentation foundation: policies are defined at the application layer using identity (user, group), context, and app attributes, instead of broad network constructs like IP ranges or subnets. This enables security teams to create fine-grained rules that tightly bind users to individual applications, rather than to entire networks. While Private AppProtection adds inline inspection, virtual patching, and exploit prevention, segmentation is the part that dictates who can talk to what.

Threat intelligence integration (option A) enriches detection but does not itself define access. Role-based access control (option C) applies mainly to admin and management roles in consoles, not to runtime user-to-application paths. User behavior analysis (option D) informs risk but is not the primary enforcement mechanism. The specific feature that provides granular control over user access to particular private applications is application segmentation.

===========

Zscaler Identity (ZIdentity) supports modern, phishing-resistant passwordless authentication using the FIDO2 standard. FIDO2 combines Web Authentication (WebAuthn) and the Client to Authenticator Protocol (CTAP2) to enable users to authenticate with security keys or built-in platform authenticators (such as biometric sensors) without transmitting or storing a reusable password. The Digital Transformation Engineer documentation explains that when a user registers a FIDO2 authenticator with ZIdentity, the service stores a public key tied to that device and account. Future logins are validated using a cryptographic challenge–response, providing strong protection against credential theft and replay attacks.

By contrast, SAML (option B) and OIDC (option C) are federation protocols used for single sign-on (SSO) and identity delegation between an identity provider and service providers; they do not themselves define how passwordless authentication is performed. They can carry assertions from an IdP that might use FIDO2 behind the scenes, but SAML and OIDC are not the passwordless method. SCIM (option D) is a provisioning standard for creating, updating, and deprovisioning identities and groups, not an authentication protocol.

Therefore, the only option that directly represents the protocol enabling passwordless login to a ZIdentity account is FIDO2.

===========

The ZIdentity documentation on external identity providers explains that Zscaler supports various third-party IdPs over SAML and OIDC, and then provides specific configuration guides for each provider. For PingOne, Auth0, and OneLogin, the ZIdentity help explicitly describes configuring each as an OpenID Provider (OP) for ZIdentity, clearly stating that they are used to provide SSO via OpenID Connect (OIDC).

By contrast, the ZIdentity guides for Microsoft AD FS consistently describe configuring AD FS “as the SAML Identity Provider (IdP) for ZIdentity,” and the examples focus on SAML assertions, claim rules, and certificate bindings—not OIDC flows. In other words, AD FS is supported in a SAML mode with ZIdentity, but it is not listed among the IdPs configured as OpenID Providers for OIDC-based integrations.

The Digital Transformation Engineer identity modules reinforce this differentiation by mapping external IdPs to either OIDC or SAML in the ZIdentity configuration, and the hands-on labs use Azure/Microsoft Entra ID or PingOne for OIDC examples, while AD FS is shown only in SAML scenarios.

Therefore, among the options listed, Microsoft AD FS is the external IdP that is unsupported by OIDC with Zscaler ZIdentity, making option C the correct answer.

===========