[2026年08月] 問題集簡単概要ZTCA試験問題Fast2test
ZTCAトレーニング認証最新版をゲットZero Trust Associate
Zscaler ZTCA 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
質問 # 24
Zero Trust access can work over any type of network.
- A. False
- B. True
正解：B
解説：
The correct answer is A. True. Zero Trust architecture is designed so that access decisions are independent of the underlying network as a trust boundary. Zscaler's ZPA guidance states that Zero Trust Network Access (ZTNA) gives users secure connectivity to private applications without ever placing them on the network, and that users can access applications without sharing network context with them.
Zscaler Client Connector guidance also states that it connects user devices to Zscaler cloud-hosted services independent of the user's location, and the ZIA traffic-forwarding architecture explains that the same authentication and policy follow the user wherever they are. This means the access model can work across corporate networks, home broadband, public Wi-Fi, mobile networks, branch environments, and other transport types, because trust is derived from identity, posture, context, and policy, not from being on a particular network.
The network still carries the traffic, but it does not determine trust. That is one of the defining characteristics of Zero Trust. Therefore, the statement is true: Zero Trust access can work over any type of network.
質問 # 25
As a connection goes through, the Zero Trust Exchange:
- A. 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).
- B. 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.
- C. Forwards packets as a passthrough cloud security firewall.
- D. Sits as a ruggedized, hardened appliance in the data center of the enterprise, where the enterprise must establish private links to major peering hubs.
正解：B
解説：
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.
質問 # 26
Content inspection of encrypted content at scale is widely available on most network-based security platforms, such as firewalls, to deploy.
- A. True
- B. False
正解：B
解説：
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.
質問 # 27
Should policy enforcement apply to all traffic, including from authorized initiators?
- A. A true Zero Trust solution must never allow any access without authorization.
- B. Zero Trust allows all initiators to see the destination, regardless of role and responsibility.
- C. No. It should only apply to unauthorized initiators.
- D. Unauthorized initiators are blackholed by default.
正解：A
解説：
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.
質問 # 28
Enterprises can deliver full security controls inline, without needing to decrypt traffic.
- A. True
- B. False
正解：B
解説：
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.
質問 # 29
The Zscaler Client Connector is:
- A. A marketplace platform that connects different types of business clients to each other.
- B. An agent installed on the endpoint to tunnel authorized user traffic to the Zero Trust Exchange for protection of SaaS, private applications, and internet-bound traffic.
- C. A device used to create a secure communication channel with a Web Application Firewall (WAF).
- D. A cloud-managed endpoint device via an MDM solution.
正解：B
解説：
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 .
質問 # 30
How is policy enforcement in Zero Trust done?
- A. Conditionally, in that an allow or a block will have additional controls assigned, for example Allow and isolate, or Block and Deceive.
- B. At the network level, by source IP.
- C. As a binary decision of allow or block.
- D. Without trust, for example Zero Trust.
正解：A
解説：
In Zero Trust architecture, policy enforcement is conditional and context-based , not limited to a simple binary allow-or-block model. Zscaler's reference architectures explain that policy is evaluated using the full user context, including identity, device posture, location, group membership, and other conditions. Access decisions are therefore based on whether specific policy conditions are true, rather than only on static network attributes such as source IP address. For example, the same authenticated user may be allowed access from a managed device at headquarters but denied from an airport, even with the same credentials.
Zscaler documentation also shows that Zero Trust policy can go beyond simple pass or deny outcomes by applying additional controls . In DNS Security and Control, requests can be allowed, blocked, or modified.
In ZIA policy development, Cloud App controls allow more granular outcomes than standard allow/block, such as restricting specific actions, applying quotas, or controlling what a user can do inside an application.
This reflects the Zero Trust principle that enforcement is adaptive, granular, and tied to business and security context rather than network location alone.
質問 # 31
Why have traditional networks relied on implicit trust to connect initiators to workloads?
- A. It was easier to create direct P2P links between all devices, providing connectivity for rapid- downloading applications like BitTorrent and file sharing.
- B. Layer 3 ACLs are sufficient for blocking untrusted initiators.
- C. Security breaches were historically less frequent.
- D. TCP/IP, the foundation of most networks, inherently favors connectivity over trust.
正解：D
解説：
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.
質問 # 32
The Zscaler Zero Trust Exchange has:
- A. Scalable inspection solutions at 150+ public locations and locally in private locations.
- B. Expanded its scope to try to provide the proof for Fermat's Last Theorem.
- C. Inspection controls only in limited core sites.
- D. Locations in few high-traffic geographic regions.
正解：A
解説：
The correct answer is C . Zscaler's reference architectures consistently describe the Zero Trust Exchange as a globally distributed inline cloud platform operating across more than 150 data centers worldwide . The Traffic Forwarding in ZIA reference architecture states that Zscaler has deployed ZIA Service Edge devices in 150+ data centers around the world , allowing users to connect to the nearest service edge for policy enforcement, TLS/SSL inspection, firewalling, and other security services. This design removes the need for centralized backhauling and supports consistent security regardless of user location.
The option mentioning "limited core sites" is incorrect because the Zscaler model is specifically designed to avoid relying on a small number of centralized inspection points. The option about "few high-traffic regions" is also incorrect for the same reason. In addition, Zscaler architecture supports private service edge deployment models for organizations that require local processing in private environments, extending the Zero Trust Exchange model beyond public cloud service edges. Therefore, the only accurate architecture- aligned answer is that Zscaler provides scalable inspection at 150+ public locations and in private locations where needed .
質問 # 33
What is a security limitation of traditional firewall/VPN products?
- A. Their IP addresses are published on the internet.
- B. They rely on easily tampered-with endpoint software.
- C. They cannot be scaled to handle increased load.
- D. SSL-encrypted VPN traffic bypasses security inspection.
正解：D
解説：
The correct answer is B. A key limitation of many traditional firewall and virtual private network (VPN) architectures is that encrypted VPN traffic can bypass or reduce effective security inspection, especially when the architecture is designed mainly to provide network connectivity rather than full inline content inspection.
Zscaler's TLS/SSL inspection guidance explains that without decryption, organizations are limited in how well they can inspect content for malware, data exfiltration, and risky activity. It also notes that legacy platforms often struggle to inspect encrypted traffic at scale, which creates blind spots in protection.
This matters because Zero Trust is not satisfied by simply creating a secure tunnel. A tunnel can protect confidentiality in transit, but it does not guarantee that the content inside the connection is safe or compliant.
Zscaler's Zero Trust architecture shifts away from broad network access and toward inline, policy-driven inspection and enforcement. The issue is not merely internet publication of IPs or scalability in the abstract; the deeper security weakness is that encrypted traffic can traverse the legacy VPN model without full security visibility and control.
質問 # 34
What purpose do Data Loss controls serve? (Select all that apply)
- A. Error checking and validation to ensure data integrity.
- B. Preventing non-malicious and/or accidental data leakage.
- C. Detecting data theft through malware.
- D. Intercepting data poisoning attempts from authorized users.
正解：B、C
解説：
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 .
質問 # 35
Should a Zero Trust solution inspect traffic for all destinations?
- A. No. It is important to find a balance. The Zero Trust solution should give the enterprise the ability to implement inspection for any application or destination. Although it is strongly recommended, it is up to the enterprise to decide where inspection is needed.
- B. No. Traffic should never be inspected.
- C. No. Only non-TLS/SSL-based traffic should be inspected.
- D. No. Only traffic destined to engineering services and financial applications.
正解：A
解説：
The correct answer is C . In Zscaler's Zero Trust architecture, the recommended goal is to inspect as much traffic as possible , especially encrypted traffic, because inspection enables key protections such as malware detection, sandboxing, intrusion prevention system (IPS), browser isolation, Data Loss Prevention (DLP), cloud app controls, tenancy restrictions, and file type controls. The TLS/SSL inspection reference architecture explicitly states that organizations should strive for 100% of traffic to be inspected and that Zscaler strongly recommends this as the starting point.
At the same time, the same guidance also confirms that exceptions can exist. It says bypasses may be required for regulatory, vendor, or contractual reasons, and that bypasses should be used only in extreme circumstances . Examples include certificate-pinned applications, some Microsoft 365 flows, and certain regulated destinations. That means the platform should be able to inspect any application or destination , but the enterprise decides where inspection is ultimately enforced. Therefore, the best answer is not "always inspect with no exceptions," but rather that full inspection is strongly recommended while allowing enterprise- controlled exceptions when justified.
質問 # 36
There are alternative traffic forwarding methods to the Client Connector that leverage edge forwarding protocols to connect sites to the Zero Trust Exchange. Two of these protocols are:
- A. IPSec and IKEv2.
- B. Single Sign-On and Public Cloud Access.
- C. Security Appliance and Router.
- D. IPSec and GRE.
正解：D
解説：
The correct answer is A. IPSec and GRE. In the Zscaler Internet Access (ZIA) traffic forwarding architecture, branch offices and sites can send traffic to the Zero Trust Exchange through several forwarding methods. The reference architecture explicitly identifies GRE tunnels and IPsec tunnels as supported methods for forwarding traffic from branch routers, SD-WAN devices, and similar site infrastructure to the nearest ZIA Service Edge.
This is different from Client Connector , which is typically used for individual endpoints such as laptops and mobile devices. For fixed locations, edge-based forwarding protocols are preferred because they allow the site' s egress traffic to be securely transported to Zscaler without requiring the endpoint client on every device. The other options are incorrect because Single Sign-On is an identity function, not a traffic forwarding protocol; Security Appliance and Router are device categories, not protocols; and IKEv2 is associated with IPsec negotiation rather than being presented here as the pair of branch forwarding methods in the ZIA architecture.
Therefore, the two protocols specifically called out as alternative forwarding methods to Client Connector are IPSec and GRE .
質問 # 37
If an enterprise is protecting its services at a network level, such as using firewalls, what happens to that protection when a user leaves the network? (Select 2)
- A. A path from initiator to the network must be put in place, for example VPN.
- B. Network access is maintained via TCP keepalive messages.
- C. Users will continue to be able to access services via the internet.
- D. The initiator will not have access to the service.
正解：A、D
解説：
The correct answers are A and D . In a legacy, network-based protection model, security controls such as firewalls are tied to the enterprise network perimeter. When a user leaves that network, the user typically loses direct access to internal services because the protection model assumes the user is on the trusted network or connected into it. To restore access, the organization usually has to establish a path back into the network , most commonly through a virtual private network (VPN) or another routable connection. Zscaler's Zero Trust guidance contrasts directly with this legacy pattern by stating that users should access applications without sharing network context with them.
This is one of the reasons Zero Trust replaces legacy VPN-centric design. ZPA documentation explicitly contrasts Zero Trust with legacy VPNs and firewalls by emphasizing that users connect directly to applications, not the network , thereby minimizing attack surface and removing dependence on being
"inside" the network. Therefore, in a network-level protection model, once the user leaves the network, access is not naturally preserved; instead, access is lost unless a path such as VPN is put in place . The TCP keepalive option is unrelated, and unrestricted internet access to services would contradict the private, firewall-protected network design.
質問 # 38
A Zero Trust policy enablement and subsequent application connection should always be permanent.
- A. True
- B. False
正解：B
解説：
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 .
質問 # 39
Policy enforcement in Zero Trust is assessed:
- A. For every access request.
- B. Only if the risk score is high.
- C. For authorized users only.
- D. For all traffic from the initiating source.
正解：A
解説：
The correct answer is D. For every access request. Zero Trust architecture does not assume that a user, device, or session remains trusted after an initial decision. Instead, access is evaluated request by request , using current identity and contextual information. Zscaler's ZPA guidance explains that when a user authenticates, context such as location, device posture, user group, department, and time of day is evaluated, and when the user attempts to access a resource, that context is matched against policy to determine whether access should be allowed.
ZIA guidance reinforces the same principle by stating that policy assignment evaluates the user, device, location, group, and more to determine which policies apply. That means policy enforcement is not limited to high-risk sessions, nor is it applied only once to all future traffic from a source. It is also not restricted only to already authorized users, because the authorization decision itself is part of the evaluation. In Zero Trust, each access request is independently assessed and enforced according to current policy and context. That is why the best answer is for every access request .
質問 # 40
What is policy enforcement built to enable?
- A. Network access to all available applications.
- B. Blocking access to applications and the network.
- C. Forwarding traffic on to a virtual DMZ.
- D. Granular access from the verified initiator only to the verified application, under the correct risk and content controls.
正解：D
解説：
The correct answer is C. In Zero Trust architecture, policy enforcement exists to provide precise, least- privileged access. It is not designed to place a user broadly onto the network, and it is not limited to simply blocking everything. Instead, it enables granular access from the verified initiator to the specific verified application, while also applying the correct policy conditions related to risk, content inspection, and business requirements.
This is one of the central differences between Zero Trust and legacy security models. Traditional VPN and firewall architectures often grant broad network connectivity first and then attempt to restrict behavior afterward. Zero Trust reverses that logic. The user is not trusted because they reached the network. Instead, the user receives access only to the exact application or service that policy permits, and only under the validated conditions for that request.
That is why granular policy enforcement is so important. It reduces attack surface, limits lateral movement, and aligns access with identity, context, and content-aware controls. Therefore, the best answer is granular access from the verified initiator only to the verified application, under the correct risk and content controls.
質問 # 41
Sometimes authorized and allowed initiators may request malicious access to services. What would be the best policy enforcement for an enterprise?
- A. Conditionally allow access and have a resource from Network Security review based on logs later.
- B. Allow access only during business hours.
- C. Allow untethered access.
- D. Conditionally block (Deceive).
正解：D
解説：
The correct answer is C. Conditionally block (Deceive). In Zero Trust architecture, authorization alone is not enough to guarantee that a request is safe. An otherwise authorized user, device, or workload can still generate malicious, compromised, or suspicious access attempts. For that reason, Zero Trust policy enforcement must remain contextual and adaptive , even after identity and access have already been validated. Zscaler's architecture emphasizes that access policies are based on the entire user context , including device, location, and compliance, and that different policy outcomes can be enforced based on those values.
A deception-based conditional block is the strongest answer because it both prevents harmful access and gives defenders insight into attacker behavior by redirecting suspicious activity away from the real service.
This is more effective than simply allowing access during business hours or allowing the activity and reviewing logs later, because those approaches do not stop the potentially malicious action in real time. Zero Trust is built around preventive, policy-driven enforcement , not delayed review. Therefore, if an authorized initiator behaves maliciously, the best enforcement is to conditionally block with deception .
質問 # 42
Third parties that can be integrated at the point of Verifying Identity and Context in the Zero Trust process include:
- A. Data center providers such as Equinix, where customer hardware is typically hosted.
- B. IdPs (Identity Providers) such as Okta and PingFederate, which are used for SSO (Single Sign-On).
- C. Web scalers such as GCP, Azure, and AWS, where cloud workloads are typically hosted.
- D. Open-source SIEM tools such as OSSM and the ELK Stack.
正解：B
解説：
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 .
質問 # 43
Which crucial step occurs during the "Enforce Policy" stage?
- A. Verification of identity and context of the connection.
- B. A handshake between the initiator and destination application.
- C. Connecting an initiator to internal and external applications from the Zero Trust Exchange.
- D. The setup of an enterprise SSO or AD server for credential validation.
正解：C
解説：
The correct answer is A . In the Zero Trust sequence, Verify Identity and Context happens first, followed by Control Content and Access , and then Enforce Policy . The enforce stage is where the platform applies the policy decision and enables the approved transaction to proceed in the allowed manner. In Zscaler's model, this means the Zero Trust Exchange brokers or permits the connection to the authorized application under the right controls.
Option D is incorrect because verification of identity and context belongs to the earlier Verify stage. Option C is about identity infrastructure setup, not runtime enforcement. Option B may occur at a transport level, but it is not the defining Zero Trust function of the Enforce stage.
The best match is therefore the actual application of the policy outcome: the initiator is connected to the appropriate internal or external application through the Zero Trust Exchange according to policy. This is consistent with Zscaler's architecture, where users, devices, and applications are securely connected through the cloud platform and access is granted only after policy evaluation.
質問 # 44
What are some of the outputs of dynamic risk assessment?
- A. Categories, criteria, and insights pertaining to each access request.
- B. A backup and restore configuration process, run manually during a change window.
- C. A full PCAP of the inline data transfer.
- D. An ML/AI-driven engine analyzing and determining application segments after wildcard domains are established.
正解：A
解説：
The correct answer is A . In Zero Trust architecture, dynamic risk assessment produces decision-support outputs that help determine how each access request should be handled. Zscaler's identity and policy guidance explains that policy decisions are made by evaluating factors such as the user, device, location, group, and more to determine which policies apply. This means the output of risk assessment is not a packet capture or an operational maintenance workflow; it is the contextual information used to classify the request and enforce the appropriate control outcome.
This aligns closely with the idea of categories, criteria, and insights attached to an access request.
Categories help classify the transaction or destination, criteria define which conditions are being evaluated, and insights provide the context needed to allow, restrict, deceive, isolate, or block. By contrast, a full PCAP is a troubleshooting artifact, not a core policy output. Backup and restore processes are administrative operations, and ML-based application segmentation is a separate discovery or segmentation capability rather than the direct output of dynamic risk assessment. Therefore, the best Zero Trust answer is that dynamic risk assessment produces contextual outputs tied to each access request so policy enforcement can be precise and adaptive.
質問 # 45
Connections to destination applications are the same, regardless of location or function.
- A. True
- B. 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.
正解：B
解説：
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.
質問 # 46
How are services protected in a legacy scenario when they are discoverable on the public Internet? (Select all that apply)
- A. Establishing a DMZ that would include multiple products and services.
- B. Dynamic Application Security Testing (DAST).
- C. A large security stack including appliances that handle functions like global load balancing, firewalling, DDoS, and more.
- D. A web application firewall (WAF) for protecting against DDoS and other botnet style attacks.
正解：A、C、D
解説：
The correct answers are A, C, and D . In a legacy architecture, applications that are exposed and discoverable on the public Internet are usually protected by building a DMZ (demilitarized zone) and placing multiple security technologies in front of the service. This commonly includes a large security stack made up of separate appliances or services for functions such as load balancing, firewalling, distributed denial-of-service (DDoS) protection, and related edge security controls. A web application firewall (WAF) is also a standard protective element in these public-facing designs because it adds inspection and protection for web-based attack patterns and internet-originated abuse.
Option B, DAST , is not a correct answer because Dynamic Application Security Testing is a testing and assessment method, not a live architectural protection control that sits inline to defend exposed services in production. Zero Trust architecture contrasts with this legacy model by removing direct public discoverability and reducing dependence on a complex exposed edge stack. Instead of defending openly exposed applications with layered perimeter tools, Zero Trust aims to make applications less discoverable and access more identity- and policy-driven.
質問 # 47
Connections approved by the Zero Trust Exchange must then enable permanent network-level access for at least 30 days.
- A. True
- B. False
正解：B
解説：
The correct answer is B. False . Zero Trust architecture is specifically designed to avoid giving users broad, lasting network-level access after a connection is approved. Zscaler's Universal ZTNA guidance states that users connect directly to applications, not the network , which minimizes attack surface and eliminates lateral movement. This means approval is tied to the specific access request and the relevant context at that moment, not to an ongoing entitlement to the underlying network.
The idea of granting network-level access for 30 days is much closer to a legacy VPN model, where a user is placed onto a routable network and may retain broad reachability beyond the immediate business need. Zero Trust does the opposite. It verifies identity and context, evaluates policy, and then enforces a specific control outcome for that request. If the user's context changes, the policy outcome can also change. That is why Zero Trust is often described as dynamic and per-access , rather than static and persistent. A connection approved by the Zero Trust Exchange does not imply a long-term network privilege; it enables only the necessary application access under current policy conditions.
質問 # 48
......
認証トレーニングZTCA試験問題集テストエンジン：https://jp.fast2test.com/ZTCA-premium-file.html