In a typical enterprise authentication setup, Zscaler functions as the Service Provider (SP) within the SAML authentication framework. This aligns with Zscaler's architectural principle that identity verification is delegated to an external authoritative Identity Provider (IdP) such as Azure AD, Okta, Ping, or ADFS. Zscaler does not authenticate user credentials directly. Instead, it relies on the IdP to validate the user and then deliver a signed SAML assertion back to Zscaler.
When a user attempts to access the Zscaler service, the authentication request is redirected to the enterprise IdP. The IdP performs credential verification and returns a SAML assertion containing the authenticated user identity and associated attributes. Zscaler, acting as the SP, consumes and validates this assertion, then maps the identity to its internal user records or SCIM-synchronized directory objects. This identity becomes the basis for all ZIA/ZPA policy evaluation, including URL filtering, CASB controls, DLP policies, firewall rules, and access-control enforcement.
Since Zscaler depends on the IdP for primary identity verification and only consumes assertions, Zscaler's role is clearly defined as the Service Provider in a standard authentication configuration.

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.

In the Zscaler Digital Experience (ZDX) section of the Digital Transformation Engineer material, Y-Engine is explicitly defined as ZDX's Automated Root Cause Analysis component. The EDU-200 and study-guide content describe Y-Engine as using machine learning to automatically isolate root causes of performance issues, correlating metrics across applications, networks, and devices so that IT teams spend less time troubleshooting and can get users back to work faster.
Several ZDX overviews and integration documents reiterate that Y-Engine is ZDX's AI/ML-based approach to detect what is causing the ZDX score for a given application or user segment to drop, effectively automating the "why is it slow?" analysis that would otherwise require multiple domain-specific tools.
"Copilot" in the Zscaler context refers to generative-AI assistance that can surface insights and answer questions, but it is built on top of underlying telemetry and correlation engines like Y-Engine; it is not the core Auto-RCA engine itself. "Application Performance" is a metric category within ZDX, and "OAuth request" is simply an authentication mechanism, not a diagnostic engine. Accordingly, the training content makes it clear that Y-Engine is responsible for automated root cause analysis, so option C is correct.

Zscaler Zero Trust SD-WAN is specifically designed to give branches, on-premises data centers, and workloads running in public clouds fast, reliable, and secure access to the internet and private applications using a direct-to-cloud architecture. In the Zscaler Digital Transformation Engineer curriculum, this service is positioned as the connectivity foundation that replaces legacy hub-and-spoke MPLS and VPN designs with cloud-delivered Zero Trust connectivity.
Instead of backhauling traffic to central data centers, branches and sites establish lightweight, policy-driven tunnels directly to the Zscaler cloud, where security inspection and Zero Trust access decisions are applied.
This architecture reduces latency, simplifies routing, and optimizes SaaS and internet performance while simultaneously enabling secure access to private applications without exposing them to the public internet.
App Connectors (option C) are used for application-side connectivity in ZPA, not for full branch or data center connectivity. Browser Access (option B) provides clientless application access for users, not network- level site connectivity. "Zscaler Privileged Remote Access" (option A) is not the term used for this broad connectivity service. Therefore, the only option that matches the described direct-to-cloud, multi-site connectivity role is Zscaler Zero Trust SD-WAN.

Zscaler's Shadow IT and Data Discovery capabilities are delivered primarily through its multimode CASB and data protection services. Shadow IT Discovery automatically identifies unsanctioned cloud applications in use and evaluates them across a large set of risk attributes (for example, security controls, compliance posture, data handling, and business continuity).
Updated Zscaler training and exam content for the Digital Transformation Engineer track describes a significantly expanded cloud app catalog, allowing visibility into up to 100,000 applications and evaluation across approximately 200 risk attributes. This scale is necessary to cover the rapidly growing SaaS ecosystem and to give security teams the granularity needed to distinguish between low-risk and high-risk services.
Earlier public materials referenced smaller catalogs (for example, 8,500 apps with 25 attributes), but the current exam-aligned figures reflect the evolution of Zscaler's data protection and Shadow IT intelligence.
Options A, B, and C therefore underrepresent the scope of Zscaler's catalog and risk model. In the context of the ZDTE curriculum, the correct pairing is 100K apps and 200 risk attributes, which best matches how Zscaler positions its Shadow IT and Data Discovery capabilities for broad visibility and fine-grained risk analysis.