Zscaler ZDTE Practice Test Questions Answers

Zscaler External Attack Surface Management (EASM) is focused on discovering and monitoring an organization’s internet-facing digital assets. In the Engineer curriculum, EASM is described as continuously identifying domains, subdomains, hostnames, IP addresses, TLS certificates, and cloud services that are exposed to the public internet. A key example used in the training is hostnames that “leak” internal context, such as environment names, projects, technologies, or business units. These hostnames are treated as digital entities because they represent externally reachable services and can give valuable clues to an attacker during reconnaissance.

By contrast, SSL inspection certificates installed on endpoints are internal controls and not part of the external attack surface. A Zscaler App Connector is designed to initiate only outbound connections and is intentionally not directly reachable from the internet, so its IP address is not an EASM discovery target. Likewise, lists of compromised usernames and passwords relate to threat intelligence and identity protection, not the mapping of exposed assets. Therefore, the only option that correctly matches the type of digital entity EASM is meant to identify is a service hostname that contains revealing information.

===========

Zscaler Digital Experience (ZDX) uses web probes to measure application performance from the user’s perspective. Official ZDX reference material and EDU/ZDTE study guides describe the four key web-probe metrics as Page Fetch Time (PFT), DNS Time, Server Response Time (Time to First Byte), and Availability. These same metrics are explicitly called out in training and exam prep as the values that can be used when defining application-level alert rules (for example, “DNS Time > X ms” or “Server Response Time > Y ms”).

ZDX documentation also explains that each alert rule type (Application, Device, Network, or Call Quality) has its own metrics and criteria, and that application alerts are driven by web-probe metrics like DNS Time and Server Response Time, while network alerts use CloudPath metrics such as latency and packet loss. Because both DNS Time and Server Response Time are application-probe metrics, they can legitimately be used together as criteria in an application-type alert rule.

By contrast, combinations that mix web-probe metrics with network-only metrics (like Packet Loss Rate) or vaguely defined “Network Response Time” do not reflect how ZDX structures its alert criteria per type. Therefore, among the listed options, the pair that correctly represents valid ZDX alert criteria for application monitoring is DNS Time and Server Response Time.

===========

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.

===========

In Zscaler’s PAC file guidance for directing traffic to specific Subclouds, the fully qualified proxy host name is constructed using the standard gateway label, followed by the subcloud identifier, and then the Zscaler cloud domain. In template form, this is represented as:

{GATEWAY.<</b>Subcloud>.<</b>Zscaler cloud>}

Here, GATEWAY corresponds to the Zscaler gateway label, is the dynamically assigned subcloud (which helps optimize routing and resiliency), and represents the customer’s Zscaler cloud domain (for example, one of the standard ZIA cloud domains). The Digital Transformation Engineer training emphasizes that using the correct order of these variables ensures that browsers resolve to the appropriate subcloud-specific gateway, enabling optimized performance and regional affinity.

Options B and C incorrectly introduce or misplace a REGION label, which does not match the documented variable order when explicitly targeting a Subcloud. Option D reverses the positions of GATEWAY and , which does not align with the hostname structure used by Zscaler for subcloud-aware PAC configurations.

Therefore, the correct PAC variable pattern for forwarding web traffic specifically to a Subcloud is {GATEWAY.<</b>Subcloud>.<</b>Zscaler cloud>}.