Zscaler Zero Trust Cyber Associate Questions and Answers
What is the ultimate goal of policy enforcement?
Options:
State a conditional allow or a conditional block.
Issue a log that can be interpreted in a modern SOC.
Designate an initiator as always trustworthy or always untrustworthy.
Track network bandwidth utilization across destination application categories.
Answer:
AExplanation:
The correct answer is A. State a conditional allow or a conditional block. In Zero Trust architecture, policy enforcement exists to make a specific access decision for a specific request based on current context. That context includes identity, device posture, location, application sensitivity, risk, and other relevant factors. The outcome is not a permanent trust label, and it is not merely an operational log or reporting artifact. Instead, the core purpose of enforcement is to apply the correct control result to that single request.
This is why Zero Trust policy is often described as conditional . An access request may be allowed, blocked, isolated, restricted, or otherwise controlled depending on the risk and business rules in effect at that moment. The critical point is that the decision is dynamic and context-driven , not static. Logs may be generated as a byproduct, but logging is not the ultimate goal. Likewise, Zero Trust does not treat users as permanently trusted or untrusted. The architecture assumes continuous evaluation. Therefore, the best answer is that policy enforcement ultimately produces a conditional allow or conditional block outcome for each access request.
What options are available to an enterprise whose cybersecurity solution does not provide inline content inspection?
Options:
Leverage the lowest-latency path, which typically involves service chaining to send traffic to a specialized branch where a stack of firewalls is hosted on a rack.
Only view the metadata of a connection, such as who is calling and where they are calling.
Optimize their throughput.
Leverage tremendous cost savings, since TLS/SSL connections have a per-packet premium cost associated with processing them.
Answer:
BExplanation:
The correct answer is B . If a security platform cannot perform inline content inspection , then it cannot fully inspect the payload of encrypted or application traffic. In practical terms, that means the enterprise is limited mainly to observing connection-level metadata such as source, destination, ports, categories, and other session attributes rather than the actual content moving through the session. Zscaler’s TLS/SSL inspection reference architecture explains that when encrypted traffic is not decrypted, advanced analysis tools such as malware protection, sandboxing, and related controls cannot fully inspect that traffic. It also notes that traditional security appliances often handle only a small fraction of their normal traffic capacity when decryption is enabled, which is one reason many legacy environments inspect only a subset of traffic.
From a Zero Trust perspective, this limitation is significant because policy should be based not only on the existence of a connection, but also on what the connection is actually doing. Without inline inspection, hidden malware, risky transactions, and sensitive data loss can evade full control. Therefore, the realistic fallback is metadata visibility only, not full protection.
A Zero Trust network can be:
Options:
Located anywhere.
Built on IPv4 or IPv6.
Built using VPN concentrators.
Located anywhere and built on IPv4 or IPv6.
Answer:
DExplanation:
The correct answer is D. Located anywhere and built on IPv4 or IPv6. In Zero Trust architecture, the network and application access model is not tied to a specific physical location, branch, or data center. Zscaler’s Zero Trust guidance emphasizes that users, devices, and applications can be securely connected in any location , which is a core shift away from legacy perimeter-based designs. The architecture is also described as IP independent , meaning policy and access decisions are not fundamentally anchored to traditional network constructs such as fixed addressing or trusted subnets. This is why Zero Trust can operate across modern environments regardless of where workloads reside.
The option about VPN concentrators is incorrect because VPN-based architecture is associated with legacy remote-access models that extend network trust and expose services differently from Zero Trust. In contrast, Zero Trust reduces implicit trust, avoids broad network-level access, and focuses on secure, application-aware connectivity. Therefore, the most complete and accurate answer is that a Zero Trust network can be located anywhere and built on IPv4 or IPv6 , rather than being limited to a legacy transport or perimeter model.
Assessing risk is:
Options:
A non-recurring process to determine how to treat requests from a specific initiator for the next 30 days.
Universal control across the entire enterprise. Once assessed, risk applies to all traffic from that enterprise.
An ongoing process to verify publicly known bad actor IP addresses.
An assessment of all things related to the current connection, previous context, and considered on an ongoing basis for future requests, thus allowing for unique and dynamic changes in the consideration of risk.
Answer:
DExplanation:
The correct answer is D . In Zero Trust architecture, risk assessment is continuous and adaptive , not static. Zscaler documentation states that policy decisions consider far more than a one-time identity check. User access is evaluated using context such as user identity, device posture, location, group membership, and time of day , and those conditions can change between requests. ZPA guidance also states that organizations should use logs to determine which users are accessing which apps, and automatically adapt based on any changes in context .
This directly supports the idea that risk is based on the current connection , informed by previous context , and continually reconsidered for future access attempts. Option A is incorrect because Zero Trust does not create a long-lived 30-day trust decision. Option B is incorrect because risk is not universally applied to all enterprise traffic once assessed. Option C is too narrow, since risk is not limited to checking public bad-IP lists. Instead, Zero Trust risk is dynamic and contextual, enabling policy to change uniquely for each request as conditions evolve. That is why the best answer is D .
Identifying and proving the who value, that is, who is the initiating entity, is usually a function of a government agency.
Options:
True
False
Answer:
BExplanation:
The correct answer is B. False . In Zero Trust architecture, identifying and validating who is making a request is normally handled through enterprise identity systems , not by a government agency. Zscaler’s authentication architecture explains that authentication credentials and identity responses from an Identity Provider (IdP) are the first step in determining which policies should apply. Those responses can include the user’s identity, groups, and department, which are then used in policy enforcement.
ZPA guidance also shows that SAML and SCIM attributes from the identity provider are used to support application access policy. This means the “who” value is typically proven through the organization’s identity stack, such as an IdP, directory service, or integrated authentication platform, not through an external government authority.
While government-issued identity documents may be part of a hiring or registration process in some organizations, that is not how Zero Trust runtime identity verification is generally performed. In practice, the “who” is established through enterprise-controlled authentication and context systems. Therefore, the statement is false.
What is the trend that is increasing security risk through legacy solutions that drive network sprawl?
Options:
A spread-out group of access control lists (ACLs) and firewall rules, with each firewall and VPN appliance only enforcing a subset of the total rule list.
A desire to replace edge routers with SD-WAN boxes, which can leverage multiple uplinks for active-active VPN failover.
An ongoing dependence on Layer 2 and Layer 3 switching, without consideration for upcoming 5G architectures.
More applications moving to the cloud, users being remote, and VPNs and firewalls extending IP connectivity out to several different locations.
Answer:
DExplanation:
The correct answer is D . Zscaler’s Zero Trust architecture specifically contrasts modern distributed environments with legacy VPN- and firewall-based designs. The reference architecture explains that users are now remote, applications can be hosted in public cloud, private cloud, or data centers, and access must work across any location. In legacy models, organizations respond by extending IP connectivity outward through VPNs, firewalls, and other network-based controls. That expansion increases the attack surface, preserves broad network trust, and drives network sprawl instead of reducing it.
The same guidance states that Zero Trust gives users access to applications without ever placing them on the network or exposing apps to the internet . This is important because legacy architectures extended the organizational perimeter to end users, allowing lateral movement and increasing risk when users and apps became more distributed. Option A describes a symptom of legacy complexity, but option D captures the broader trend that is causing the sprawl in the first place: cloud migration, remote users, and the continued use of VPN and firewall architectures to maintain connectivity. That is the most accurate Zero Trust answer.
How is risky behavior controlled in a Zero Trust architecture?
Options:
Permanent quarantining of devices in a particular VLAN.
Re-categorization of an initiator, and their organization, so that subsequent access requests are limited, deceived, or stopped.
Logging violations in a public database.
Deploying best-in-class security appliances.
Answer:
BExplanation:
The correct answer is B . In Zero Trust architecture, risky behavior is controlled through continuous evaluation and policy-based response , not through static network constructs such as VLAN quarantine or dependence on standalone appliances. Zscaler’s Zero Trust guidance emphasizes granular, context-based policies that evaluate the user, device, application, and surrounding conditions before and during access. In the ZPA architecture material, Zscaler states that applications should remain inaccessible unless the user is authorized, and policy should be independent of IP address or location.
The strongest architecture match is option B , because Zscaler documentation describes security outcomes such as inline prevention, deception, and threat isolation for compromised or risky users. That means when behavior becomes suspicious, later access attempts can be restricted, misdirected, or blocked based on updated policy context. This is fundamentally different from a legacy response such as placing a device permanently in a VLAN, which remains network-centric and coarse-grained. Logging alone also does not control risk, and simply deploying security appliances does not deliver Zero Trust by itself. Zero Trust controls risky behavior by dynamically adjusting enforcement based on observed context and threat posture, which best aligns with option B.
Assessing, calculating, and delivering a risk score is: (Select 2)
Options:
An assessment of inline and out-of-band network traffic.
A review of known configuration, and the absence of other configuration details, of cloud-hosted services in relation to best practices, industry standards, and compliance models to ensure misconfigurations, issues, and vulnerabilities are understood and highlighted.
An assessment of the content, not just the connection, of services, so that malicious functions are not downloaded and protected information is not lost.
Only focused on initiator context.
Answer:
A, BExplanation:
The correct answers are A and B . In Zero Trust architecture, risk scoring is broader than a simple connection decision. It is derived from multiple forms of context and telemetry so that policy can adapt based on changing conditions. Option A is correct because risk can be informed by both inline observations and out-of-band analysis. This reflects the Zero Trust principle of continuous assessment rather than one-time trust establishment.
Option B is also correct because modern risk evaluation includes the security posture of cloud-hosted services , including known configuration weaknesses, missing controls, misconfigurations, compliance gaps, and other exposures. This aligns with Zero Trust thinking because access and trust decisions should account for more than identity alone; they should also reflect the security condition of the service being accessed.
Option C describes content inspection and data protection , which are critical controls, but that is not the best definition of calculating and delivering a risk score. Option D is incorrect because Zero Trust risk is not only about initiator context . It also considers application, service, transaction, and environmental conditions. Therefore, the two correct answers are A and B .
Where is it most effective to assess the content of a connection?
Options:
At the policy enforcement point, as close to an initiator as possible, for example the closest edge.
Within a data center deployed in a one-armed concentrator mode.
On disk, after first being copied several times for a backup.
Within an ISP’s fiber backbone.
Answer:
AExplanation:
The correct answer is A . In Zero Trust architecture, content inspection is most effective when it happens inline at the policy enforcement point and as close to the initiator as possible . This improves both security and user experience. From a security standpoint, inspecting traffic early allows the platform to identify malware, risky content, command-and-control behavior, and sensitive data movement before the traffic continues deeper into the environment or reaches the destination. From a performance standpoint, enforcing policy at the nearest edge reduces unnecessary backhaul and helps maintain a more efficient path.
This aligns with modern cloud-delivered Zero Trust design, where users connect to the nearest enforcement point rather than being forced through a central data center stack. A one-armed concentrator model is a legacy deployment concept and is less effective for distributed users and applications. Inspecting data only after it has been copied to disk is too late for inline protection, and an ISP backbone is not the enterprise’s policy enforcement location. Therefore, the best answer is that content should be assessed at the enforcement point closest to the initiator , such as the nearest service edge.
The second part of a Zero Trust architecture after verifying identity and context is:
Options:
Controlling content and access.
Re-checking the SAML assertion.
Enforcing policy.
Microsegmentation.
Answer:
AExplanation:
The correct answer is A. Controlling content and access. In the Zero Trust architecture sequence used in Zscaler’s architectural model, the flow is first to verify identity and context , then to control content and access , and finally to enforce policy . This order is important because Zero Trust does not begin by trusting the network. Instead, it first determines who the user is and what the conditions of the request are, such as device posture, location, group membership, and other contextual factors. Once that context is established, the architecture then evaluates the application request and the content flowing through the connection so that appropriate controls can be applied.
This second stage is where Zero Trust moves beyond identity alone. It is not enough to know who the user is; the architecture must also assess what they are trying to access and whether the transaction itself should be restricted, inspected, isolated, or blocked. Re-checking a SAML assertion is too narrow, microsegmentation is a design technique rather than the named architecture stage, and enforcing policy is the third stage. Therefore, the second part is controlling content and access .
In a network secured with a stack of security appliances and firewalls, what happens when people want to work from outside the network?
Options:
Networks get extended using VPNs.
Users simply need a reliable Wi-Fi connection.
Work from outside the network is not possible.
A single sign-on solution can be leveraged to accomplish this.
Answer:
AExplanation:
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 .
Connections to destination applications are the same, regardless of location or function.
Options:
True
False, each application, whether internal or external, trusted or untrusted, must be considered for connectivity based on the risk profile and risk acceptance of each enterprise.
Answer:
BExplanation:
The correct answer is B . In Zero Trust architecture, application connectivity is not treated as identical across all destinations . Each application must be evaluated according to its business purpose, sensitivity, exposure, trust level, data handled, user population, and enterprise risk tolerance . This is a core departure from legacy network-centric design, where many applications were reached through the same broad network access model once a user was connected.
Zero Trust instead applies application-specific and context-aware access control . An internal private application, a sanctioned Software as a Service (SaaS) platform, an unmanaged external website, and a high-risk destination should not all receive the same access treatment. Some may require direct allow, some may require isolation, some may require additional inspection, and some may need to be blocked entirely.
This is why Zero Trust policy is granular rather than uniform. The architecture assumes that connectivity decisions must reflect risk . Application location alone does not determine trust, and neither does function alone. The enterprise must decide how each destination is handled based on its overall risk profile and policy requirements. Therefore, the statement is false.
What facilitates constant and uniform application of policy enforcement?
Options:
Open and clear communication channels across Network and Security teams.
The policy remains the same, conditionally, and is applied equally regardless of the location of the enforcement point.
Leveraging policy enforcement capabilities available through traditional security appliances.
Application access happens on-premises, typically either from within the data center or the corporate campus, where large security stacks are deployed.
Answer:
BExplanation:
The correct answer is B . A core Zero Trust principle is that policy should be consistent and context-based , regardless of where the user is, where the application is hosted, or where the enforcement service is located. In other words, the same business and security policy must be applied uniformly across all access requests, with outcomes changing only when the evaluated context changes. This creates predictable and repeatable enforcement across branches, campuses, home offices, mobile users, and cloud-hosted applications.
Legacy environments often struggle with this because different firewalls, VPN gateways, and security stacks may each enforce only part of the intended rule set, leading to drift and inconsistency. Zero Trust addresses that by moving toward a centralized, policy-driven control model that is applied equally across the distributed environment. Communication between teams is important operationally, but it is not what fundamentally enables constant and uniform enforcement. Traditional appliances and on-premises security stacks also do not solve the consistency problem at scale. Therefore, the best answer is that uniform enforcement is facilitated when the same conditional policy is applied equally regardless of the enforcement point’s location .
What are the three main sections that the elements of Zero Trust are grouped into?
Options:
Verify Identity and Context, Control Content and Access, and Enforce Policy.
VPNs, firewalls, and legacy architectures.
Castle-and-moat security architectures, with the data center and inbound DMZ being key.
Routers, switches, and wireless access points.
Answer:
AExplanation:
The correct answer is A . In the Zero Trust architecture model used throughout this question set, the elements of Zero Trust are grouped into three major sections: Verify Identity and Context , Control Content and Access , and Enforce Policy . This structure reflects the way Zero Trust moves away from implicit trust based on network location and instead applies security based on identity, context, content awareness, and policy-driven control.
First, the architecture verifies who is making the request and under what conditions , such as device posture, location, group membership, or risk context. Next, it controls what is being accessed and what content is involved , which is where inspection, application awareness, and content-based protections become essential. Finally, it enforces policy by applying the exact outcome required for that request, such as allow, restrict, isolate, deceive, or block.
The other answer choices describe legacy infrastructure components or traditional perimeter approaches, not the three conceptual sections of Zero Trust. Therefore, the only correct grouping is Verify Identity and Context, Control Content and Access, and Enforce Policy .
Historically, initiators and destinations have shared which of the following?
Options:
A network, because prior to Zero Trust there was no other way to connect the two.
The same IP subnet range.
The same punch card machine, pre-computer.
Physical hard drives and storage.
Answer:
AExplanation:
The correct answer is A . Historically, before modern Zero Trust models were adopted, the normal way to connect a user to an application or service was to place both within a shared network context . This did not always require the exact same subnet, but it did require some level of common routable network connectivity. Legacy architectures assumed that once the user was on the trusted network, or extended into it through technologies such as VPN, they could reach the destination across that network.
Zero Trust architecture changes this assumption. Zscaler’s architectural guidance emphasizes that users should gain access to applications without sharing network context or routing domain with those applications. That is one of the most important distinctions between legacy network-centric security and Zero Trust. The user no longer needs broad network reachability just to get to a specific service. Option B is too narrow because shared access historically did not always mean the same subnet. Options C and D are clearly incorrect. Therefore, the best answer is that initiators and destinations historically shared a network , because legacy connectivity depended on routed network access rather than identity-based, per-application brokerage.
A Zero Trust policy enablement and subsequent application connection should always be permanent.
Options:
True
False
Answer:
BExplanation:
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 .
What is policy enforcement with a Zero Trust solution?
Options:
Access control delivered via authentication, authorization, and accounting through a protocol such as RADIUS.
SCIM, leveraging an IdP.
Placing virtual firewall images in every public cloud you are deployed in.
The unique and definitive implementation of control, solely for that access request.
Answer:
DExplanation:
The correct answer is D . In Zero Trust architecture, policy enforcement is the specific control decision applied to a particular access request , based on the exact context of that request at that moment. Zscaler’s architecture guidance emphasizes granular, context-based policies that control application access independently of IP address or location. It also explains that policy is determined by evaluating the user, device, location, group, and other factors, which means enforcement is transaction-specific rather than a broad network permission.
Option A refers to traditional AAA concepts and protocols, which may participate in identity workflows but do not define Zero Trust policy enforcement by themselves. Option B , SCIM with an Identity Provider (IdP), relates to identity provisioning rather than runtime enforcement. Option C reflects a legacy or infrastructure-centric design pattern, not Zero Trust. In contrast, Zero Trust enforcement is the actual outcome applied to that single request, such as allow, restrict, isolate, deceive, or block, depending on verified context. This is why the best answer is that policy enforcement is the unique and definitive implementation of control solely for that access request , not a generalized network-level permission model.
In a Zero Trust architecture, should applications that you manage have any exposed inbound listeners?
Options:
Inbound listener ports should only be accessible to those initiators who are allowed access. All other access, and visibility, must be denied.
Yes, allow anyone to connect to the listening service, just like having your website on the internet for anyone to connect with.
Yes, allow all inbound to any service; the firewall will protect the application.
Only allow access to those who share the same network.
Answer:
AExplanation:
The correct answer is A . A major principle of Zero Trust architecture is that managed applications should not be broadly discoverable or openly reachable in the way legacy internet-facing services often are. Access should be limited only to explicitly authorized initiators , and all other visibility and reachability should be denied. This reduces attack surface, prevents opportunistic scanning, and limits exposure to exploitation attempts before authentication and policy evaluation occur.
Zero Trust does not assume that a firewall alone is sufficient protection for an exposed application. Instead, it seeks to minimize or eliminate unnecessary public exposure in the first place. Likewise, requiring the user to be on the same network is a legacy network-trust model, not a Zero Trust principle. The correct model is that access is granted only after identity and context are verified and policy allows it .
So while an application may technically listen for approved brokered access, it should not be openly visible to unauthorized users or the general internet. Therefore, the best answer is that inbound access should be available only to permitted initiators , while all other access and visibility are denied.
Content inspection of encrypted content at scale is widely available on most network-based security platforms, such as firewalls, to deploy.
Options:
True
False
Answer:
BExplanation:
The correct answer is B. False . In Zero Trust architecture, inspection of encrypted traffic is a major requirement because most internet traffic is now encrypted, and threats frequently hide inside TLS/SSL sessions. However, Zscaler’s TLS/SSL inspection reference guidance explains that this type of inspection is not widely available at scale on most traditional network-based security platforms . Conventional security appliances typically experience a major reduction in effective traffic-handling capacity when decryption is enabled, which is one of the main reasons many legacy environments only inspect a limited subset of encrypted traffic.
This limitation is important in Zero Trust because selective inspection creates blind spots. If encrypted traffic is not inspected broadly, malware delivery, command-and-control activity, risky application behavior, and data exfiltration can bypass security controls. Zscaler’s architecture is designed to move this function to a cloud-delivered inline security model so inspection can occur more consistently and at scale. Therefore, the statement is false because traditional firewalls and similar appliances have historically struggled to provide encrypted content inspection broadly and efficiently enough for modern Zero Trust needs.
There are three sections that make up a successful Zero Trust architecture: (1) Verify Identity and Context, (2) Control Content and Access, and (3) ______.
Options:
Integration with an SSO provider.
SAML- and SCIM-based authentication for assessing posture.
Enforce Policy.
Data Loss Prevention.
Answer:
CExplanation:
The correct answer is C. Enforce Policy. In the Zscaler Zero Trust model, the architecture is built around three major functions: verify identity and context , control content and access , and enforce policy . Verification establishes who the user is and the conditions of the request, including factors such as device posture, location, group membership, and other contextual signals. Zscaler documentation states that policy assignment evaluates the user, machine, location, and more to determine which policies should apply.
After verification, the platform controls access and content by inspecting and evaluating the connection, the application, and the traffic according to defined business and security requirements. The third step is enforcement, where the system applies the exact result for that specific request, such as allowing, blocking, restricting, isolating, or otherwise controlling the transaction. Zscaler’s architecture also describes using a cloud service to enforce contextual policies and emphasizes that users connect directly to applications, not the network.
The other options are supporting technologies or specific capabilities, but they do not represent the third major architecture section. The correct completion is therefore Enforce Policy .
Verification of user and device identity is to be enabled for:
Options:
Any person who wants to connect to an enterprise-controlled application, including employees, third parties, and partners.
Remote employees only.
Untrusted third parties only.
Employees connecting from unmanaged endpoint devices only.
Answer:
AExplanation:
The correct answer is A. In Zero Trust architecture, verification of both user identity and device context should be applied to any person requesting access to an enterprise-controlled application. That includes employees, contractors, partners, and other third parties. Zscaler’s Universal ZTNA guidance states that Zero Trust gives users access to applications based on granular, context-based policies and that the user can be anywhere while the application can be hosted anywhere. This model is not restricted only to remote employees or only to outside parties.
The central principle is that no category of user receives automatic trust simply because of employment status, device ownership, or location. Instead, every access request must be evaluated using current identity and contextual information. That is why Zero Trust architectures verify not just the individual but also conditions such as device posture, location, group, and other policy-relevant attributes. Restricting this verification only to remote staff, unmanaged devices, or external users would recreate the implicit-trust problem that Zero Trust is meant to eliminate. Therefore, the correct architectural answer is that verification should apply to any person connecting to an enterprise-controlled application.
As a connection goes through, the Zero Trust Exchange:
Options:
Initiates the three sections of a Zero Trust architecture (Verify, Control, Enforce), which once completed, will allow the Zero Trust Exchange and the application to complete the transaction.
Sits as a ruggedized, hardened appliance in the data center of the enterprise, where the enterprise must establish private links to major peering hubs.
Acts as the opposite of a reverse proxy, inspecting every single packet that goes out, but strictly without the ability to provide controls such as firewalling, intrusion prevention system (IPS), or data loss prevention (DLP).
Forwards packets as a passthrough cloud security firewall.
Answer:
AExplanation:
The correct answer is A . In Zscaler’s architecture, the Zero Trust Exchange is not just a packet-forwarding firewall or a single appliance. It is the cloud-delivered policy and security fabric that evaluates access through the core Zero Trust sequence of verify, control, and enforce . The architecture documents describe Zero Trust access as depending on establishing identity, evaluating context, and then applying the appropriate control for that specific request. ZPA guidance explains that users are evaluated for context such as location, device posture, groups, and time of day, and access is granted only if the request matches the required policies.
Option B is incorrect because the Zero Trust Exchange is not limited to a hardened enterprise data center appliance. Option C is incorrect because Zscaler explicitly provides inline controls such as firewalling, DLP, and related inspection services. Option D is also incomplete because the Zero Trust Exchange does more than pass traffic through; it makes access and security decisions. Therefore, the best architecture-aligned answer is that the Zero Trust Exchange carries out the Zero Trust process of Verify, Control, and Enforce as part of completing the transaction.