The correct answer is A. Networks get extended using VPNs. In legacy architectures, security controls such as firewalls and appliance stacks are typically anchored to the enterprise network perimeter. When users need to work from outside that protected network, the common historical solution is to extend the network to them through a virtual private network (VPN) . This gives the remote user a path back into the corporate environment so the existing perimeter controls can still be used. Zscaler's Universal ZTNA architecture explicitly contrasts Zero Trust with this legacy model by stating that Zero Trust allows users to access applications without sharing network context or routing domain with them.
That contrast is important because VPNs preserve a network-centric trust model. Instead of granting access only to a specific application, VPNs often place users onto a routable enterprise network. Zero Trust replaces this with application-specific, identity- and context-based access. A reliable Wi-Fi connection alone is not a security architecture, single sign-on does not create the network path, and saying remote work is impossible is incorrect because VPNs were the legacy answer. Therefore, the best answer is that legacy networks are extended using VPNs .

The correct answer is A . Zscaler's Zero Trust architecture explicitly states that applications should be inaccessible unless the user is authorized and that the attack surface should remain invisible even to authorized users until policy allows access. The ZPA segmentation guidance says that decoupling the user from network-based access makes applications invisible unless the user is authorized, and the Universal ZTNA guide similarly states that applications should be inaccessible unless the user is authorized.
This means internal applications should not be exposed by default through open inbound listeners or broad network reachability. The Zero Trust model is to keep applications effectively dark to unauthorized initiators and make them available only through the policy-brokered access path. That is more secure than allowing direct access for on-site users, managed devices, or VPN-connected users, because those approaches reintroduce implicit network trust.
Therefore, the correct implementation is to avoid direct exposure of internal applications and allow access only for authorized users through the Zero Trust access model . That aligns directly with ZPA's goal of no broad network access and no lateral movement.

The correct answer is B. False . In Zero Trust architecture, full inline security depends on the ability to inspect what is actually inside the traffic flow, not just the fact that a connection exists. When traffic is encrypted, security services cannot fully evaluate malware, command-and-control traffic, sensitive data movement, risky application behavior, or policy violations unless the traffic is decrypted and inspected .
Zscaler's TLS/SSL inspection guidance makes this clear by positioning decryption as essential for complete visibility and enforcement across encrypted internet traffic.
Without decryption, an organization may still apply limited controls such as destination reputation, IP-based filtering, category decisions, or metadata-based enforcement. However, that is not the same as full security controls inline . Full Zero Trust protection requires deeper visibility into content and transactions so that threat prevention, Data Loss Prevention (DLP), cloud application controls, sandboxing, and other advanced protections can be applied accurately. Because modern traffic is heavily encrypted, failing to decrypt creates blind spots and weakens policy enforcement. Therefore, the statement is false: enterprises cannot deliver full inline security controls across encrypted traffic without decryption.

The correct answer is C . In Zero Trust architecture, access is determined not only by who the user is, but also by the context of the device and access method . Zscaler documentation explains that policy assignment evaluates the user, machine, location, group, and more to determine which policies apply. It also states that Zero Trust access decisions can consider device posture and whether access is being requested under trusted or untrusted conditions.
A browser session from an untrusted device and a session from a device running Zscaler Client Connector represent two different identity-and-context states. The user identity may be the same, but the device trust and posture are different, so the available services and the enforcement outcome can differ. This is exactly how Zero Trust should work: access is tailored to the verified context of the request rather than granted broadly through network location. The other options do not represent a meaningful Zero Trust identity differentiator.
An open-access VPN policy is contrary to Zero Trust, wired versus wireless is primarily a network transport distinction, and MSP management is unrelated to the access decision itself. Therefore, the best answer is C .

The correct answer is B . In Zscaler's Zero Trust architecture, the Verify Identity and Context stage relies on identity systems that can authenticate users and provide policy-relevant attributes. The ZIA authentication architecture explicitly states that Zscaler partners with leading Identity Providers (IdPs) such as Azure Active Directory, Okta, and PingFederate , and that responses from the IdP can include the user's identity, department, and group membership. Those attributes are then used to decide which policies apply.
The ZPA architecture reinforces the same model by stating that SAML and SCIM attributes such as group membership and role are used in access policy rules, and that additional access context can be provided by the SAML Identity Provider . This makes IdP integration a direct part of verification and context evaluation in the Zero Trust process.
The other options are not the best fit for this stage. SIEM tools support logging and analytics, while cloud and data center providers host workloads rather than acting as identity-verification systems. Therefore, the correct answer is IdPs like Okta and PingFederate .