The correct answer is B . The core security risk of a split tunnel VPN is loss of visibility and consistent inspection for the traffic that bypasses the tunnel and goes directly to the internet. Zscaler’s Secure Mobile Access reference architecture explains that traditional VPNs backhaul traffic to a central data center for security through a legacy appliance stack, while modern remote work leads to a lack of visibility into what users are accessing and how the network is performing when the organization no longer controls the path.

ZIA guidance similarly states that user traffic must be forwarded to the nearest ZIA Service Edge so it can be inspected and either forwarded or blocked according to policy, and that the same authentication and policy should follow the user wherever they are. If some traffic exits directly to the internet outside that enforcement path, the organization loses the visibility and control needed to make reliable policy decisions on those flows. That is the real Zero Trust concern with split tunneling. It creates blind spots rather than a uniformly enforced security model. Therefore, the best answer is loss of visibility into traffic going directly to the internet .

The correct answer is B . Traditional networks have historically relied on implicit trust because the foundational model of TCP/IP networking is built to enable connectivity , not to establish trust or least-privileged access. Once a user or device is on the network, routing and addressing make it possible to reach other resources unless additional controls are layered on top. This is exactly the legacy pattern that Zero Trust seeks to replace.

Zscaler’s Universal ZTNA guidance explains that legacy approaches connected users to applications by placing them in the same network context or routing domain , whereas Zero Trust decouples the user from the network and allows access only to approved applications. The architecture specifically states that users should access applications without sharing network context with them and that granular, context-based policy should control access instead of implicit network trust.

So the underlying reason is architectural: traditional networking protocols were optimized for reachability and communication, not identity-based trust decisions. That is why implicit trust became common, and why Zero Trust is such a significant shift away from the old model.

The correct answer is B. False. In Zero Trust architecture, validating the user’s identity is essential, but it is not the sole attribute used to control access. Zscaler’s architecture guidance explicitly states that policy assignment evaluates factors such as the user, machine, location, group, and more to determine which policy should apply. This means Zero Trust decisions are based on a combination of identity and context, not identity alone.

This distinction is critical. If access were based only on username and authentication, then a compromised account, an unmanaged device, a risky location, or suspicious behavior could still be treated too permissively. Zero Trust avoids that weakness by continuously assessing the broader conditions of the request. Device posture, application sensitivity, session characteristics, network conditions, and dynamic risk signals can all influence whether access is allowed, restricted, isolated, deceived, or blocked. Zscaler also emphasizes that users access applications without sharing network context, which shows that access is not controlled by identity alone or by network location alone, but by a policy engine evaluating multiple attributes together. Therefore, the statement is false.

The correct answer is C . Zscaler documentation describes Zscaler Client Connector as a lightweight software agent that runs on the endpoint and connects user devices to Zscaler cloud-hosted services. It enables protection for internet destinations through ZIA , access to private applications through ZPA , and visibility through ZDX . The secure mobile access reference architecture states that Zscaler Client Connector connects users and devices to the Zscaler Zero Trust Exchange and enables secure access to the internet and private applications from any location.

This directly matches the description in option C. The agent tunnels or redirects the user’s authorized traffic to the Zero Trust Exchange, where security policy and access controls are enforced. It is not a WAF device, not an endpoint itself, and not a marketplace platform. The ZPA troubleshooting guide also notes that the initial request to a private application is initiated from Zscaler Client Connector, which intercepts the application request and forwards it appropriately for policy evaluation and brokering.

Therefore, the correct definition is that Zscaler Client Connector is an endpoint agent that securely tunnels authorized user traffic to the Zero Trust Exchange .

The correct answers are C and D . In legacy architectures, when an application or database is moved from a private data center to a cloud environment, access is often preserved by extending the existing network-centric trust model . One common method is to give the workload a public IP address so it can be reached directly over the internet. Another is to extend MPLS or other routable WAN connectivity into the cloud so that the application remains part of an IP-reachable enterprise network. These are classic legacy approaches because they preserve network reachability instead of shifting to identity-based, application-specific access.

By contrast, Zscaler’s Zero Trust guidance states that users should access applications without sharing network context or routing domain with them. The user can be anywhere, the application can be hosted anywhere, and policy should be granular and context-based , not dependent on exposing services on a routable network. That is why direct internet exposure and MPLS-style extension are considered legacy methods, while Zero Trust replaces them with brokered, application-aware access that minimizes discoverability and lateral movement.

The correct answer is A. Who is connecting. In the Zero Trust model used throughout these questions, the first major section is Verify Identity and Context, which is concerned with understanding the who, what, and where of the access request. The first logical element in that sequence is identifying who is connecting. Zscaler’s authentication architecture makes this explicit by describing authentication credentials as the first step in determining which policies are applied, based on responses from the Identity Provider (IdP). Those responses include the user’s identity, department, and group membership.

Device posture is also important, but it is part of the broader context that follows identity verification. Threat intelligence integrations and ML-based discovery are useful supporting capabilities, yet they are not the first element of the Verify stage. Zero Trust begins by establishing who the requester is, then layering in posture, location, and other contextual conditions to reach an access decision. Therefore, the best answer is Who is connecting.

The correct answers are A and B . In Zero Trust architecture, Data Loss controls exist to prevent sensitive information from leaving the organization in unauthorized ways. Zscaler’s TLS/SSL inspection reference architecture specifically lists Data Loss Prevention (DLP) as a capability that helps prevent sensitive data from leaving the organization . This clearly supports option B , which covers accidental or non-malicious leakage such as unintended sharing, upload mistakes, or improper transfers.

Option A is also correct because data loss controls help detect and stop data theft , including theft carried out by malware or compromised sessions. In Zero Trust, inspection is not limited to who is connecting; it also evaluates what content is moving across the session. That is why encrypted traffic inspection is so important: without it, malicious exfiltration can remain hidden. By contrast, option C describes data integrity and validation functions, which are not the purpose of DLP. Option D refers more to content manipulation or poisoning, which is not the primary function being described by data loss controls in Zscaler’s architecture. Therefore, the correct purposes are detecting data theft and preventing accidental leakage .