Posture Profiles give a comprehensive view of a device's security state - checking OS version, patch level, antivirus status, disk encryption, and more - making them the richest criteria for trust decisions in access policies for sensitive private apps.

Z-Tunnel 2.0 extends forwarding beyond web proxy traffic by securing all IP unicast traffic through DTLS
/TLS tunnels to the Zero Trust Exchange. This enables Cloud Firewall and other controls to inspect all TCP and UDP ports, and ICMP where supported, rather than only browser HTTP/HTTPS flows. Option C (Zscaler Client Connector will encapsulate the user's traffic in DTLS/TLS tunnels to the ZTE) is correct because Tunnel 2.0 is the all-ports-and-protocols forwarding model for Client Connector.
Why the other options are incorrect:
A). Zscaler Client Connector will encapsulate the user's traffic in GRE tunnels to the ZTE: Zscaler Client Connector is the endpoint agent that steers traffic, authenticates users, reports posture, and supplies ZDX telemetry.
B). Zscaler Client Connector will encapsulate the user's traffic in IPSec tunnels to the ZTE: IPS inspects traffic inline for exploit signatures and attack patterns, then blocks or resets offending sessions.
D). Zscaler Client Connector will encapsulate the user's traffic in HTTP Connect tunnels to the ZTE:
Zscaler Client Connector is the endpoint agent that steers traffic, authenticates users, reports posture, and supplies ZDX telemetry.

Option C tests both the observed behavior and the controls needed to see it. Zscaler notes that attackers use SSL/TLS to conceal data exfiltration and command-and-control traffic, making decryption and inspec tion necessary for visibility. The Web Insights filters distinguish TLS-inspected from uninspected transactions, so the team can confirm whether suspicious outbound flows were actually decrypted. ZIA threat and DLP evidence should be correlated with ZPA user-activity fields to identify unusual private-application access by the same user or device. The team should then verify that DLP and botnet policies covered those decrypted sessions and review any exceptions. Option B examines only part of the evidence. Raising firewall severity changes labeling rather than validating protection, while broad Sandbox reanalysis focuses on downloaded files and does not confirm encrypted egress coverage. Correlation plus policy validation reveals the actual control gap.

Legacy firewalls introduce performance risk because they were designed around centralized perimeter enforcement and hardware capacity limits. Cloud and remote-work traffic creates encrypted, high-volume flows that can overwhelm appliance-based inspection and force inefficient backhauling. Option C (Gen AI Insights Logs) is correct because performance degradation is a real business risk of legacy firewall architecture.
Why the other options are incorrect:
A). SaaS Security Logs: SaaS Security logs cover API/CASB activity in SaaS tenants. Prompt visibility for generative AI applications belongs in Gen AI Insights logs.
B). Web Insights Logs: Web Insights logs summarize web traffic activity; Gen AI prompt visibility belongs in Gen AI Insights where enabled.
D). Advanced Firewall Logs: Advanced Firewall logs show firewall sessions and network applications, not Gen AI prompt content.

When a ZDX custom application is configured with the type set to'Network', the administratorwill not get Disk I/O metricsfor users. Disk I/O metrics relate to local client device performance and are not part of network-type application probes which focus on network latency, server response, and other network-centric measurements.
The study guide notes that Disk I/O is part of endpoint-level monitoring and is not collected by network-type probes, unlike metrics such as Server Response Time or ZDX Score which are network related.