The correct answer is B. False . Zero Trust architecture is built around least-privileged, context-based access
, not permanent entitlement. Zscaler's ZPA guidance explains that ZTNA provides users secure connectivity to private applications without ever placing them on the network and that access is granted based on granular policies . When a user attempts to access a resource, the user's context is matched against policy, and if the requirements are not met, the application is effectively unreachable.
This means access is conditional and specific , not permanently enabled after one successful decision.
Zscaler also emphasizes that users connect directly to apps, not the network , minimizing attack surface and eliminating lateral movement. A permanent connection model would resemble legacy VPN behavior, where a user gains broad, lasting access to a routed network environment. Zero Trust rejects that model. Instead, policy enablement and application connectivity are tied to the active request and the context at the time of access. If posture, location, or policy conditions change, the decision can also change. Therefore, Zero Trust connections should not always be permanent, and the correct answer is False .

The correct answer is A . By definition, Zero Trust connections are independent of the network for control or trust . This is one of the most important distinctions between Zero Trust and legacy security models. In traditional architectures, trust is often inherited from network location. If a user is on the corporate network, or connected into it by VPN, that user may gain broad access based on network reachability. Zero Trust rejects that model. Instead, trust is established through identity, posture, context, and policy for each access request.
Because of this, the underlying transport network becomes less important from a trust perspective. Whether the user is on Wi-Fi, broadband, mobile internet, IPv4, or IPv6 is not the defining factor in the access decision. The connection can operate over many types of networks, but the network itself is not what grants trust . Options B, C, and D all describe legacy or infrastructure-specific dependencies that Zero Trust is designed to avoid. A Zero Trust connection is therefore defined by policy-controlled, context-aware access , not by dependence on a particular network type or appliance path.

The correct answer is B . In Zero Trust architecture, deception as a conditional block policy means suspicious or malicious activity is not sent to the real destination. Instead, the request is redirected to a decoy or controlled service , allowing defenders to observe and understand the behavior without exposing the actual workload. This provides both protection and intelligence. It blocks harmful access while generating insight into attacker methods, compromised accounts, or risky automation.
This aligns with the Zero Trust idea that policy outcomes can be more sophisticated than simple allow or deny. A conditional block with deception is especially valuable when an enterprise wants to stop the request but also gain visibility into why the request is suspicious and how the initiator behaves when interacting with what it believes is the real target.
The other options do not match the concept. Extortion negotiations are unrelated, quarantine VLANs are a legacy network-centric control, and branch local breakout is a traffic-forwarding design choice. Therefore, deception allows the enterprise to selectively redirect questionable access attempts to a decoy service and gather useful security insight while keeping the real destination protected.

The correct answer is A . In Zero Trust architecture, policy enforcement applies to every access request , including requests from users who may ultimately be authorized. Zscaler documentation explains that when a user requests access, the platform evaluates context such as identity, posture, location, group membership, and application conditions , then enforces the matching policy. This means that authorized users are not exempt from policy; rather, policy is what determines whether they are authorized for that specific request.
ZPA guidance also states that access policies use explicit logic based on application segments, SAML attributes, client type, and posture profiles, and that traffic that does not match a policy is automatically blocked . This is fully consistent with the principle that no access should occur outside authorization and policy control.
Option A is the only choice that matches that Zero Trust principle, even though its wording is broader than the question. Options B, C, and D are incorrect because they either exclude authorized users from enforcement or imply unnecessary visibility to destinations. In Zero Trust, all traffic is subject to policy , and nothing should be allowed without authorization.