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.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit