ZDTA
Free ZDTA practice questions
10 questions from our ZDTA practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, User & Device Management
Corporate security requires that ZIdentity administrators sign in only from the corporate network and with phishing-resistant MFA, while emergency break-glass access remains possible. Which configuration meets these requirements?
- AA Client Connector app profile with a logout password so that administrators cannot sign out while working off-network
- BA ZPA access policy that publishes the admin portal as a private app reachable only through App Connectors in the HQ
- CA ZIA URL filtering rule that blocks the admin portal domain for every user who is outside the corporate office network
- DAn admin sign-on policy that limits admin access by source network and requires FIDO2 MFA, excluding one break-glass account Correct answer
Answer and explanation: ZIdentity admin sign-on policies can restrict administrator access by conditions such as location or network, and authentication can require strong methods such as FIDO2/WebAuthn, while a controlled break-glass account preserves emergency access. URL filtering only applies to traffic forwarded through ZIA and does not enforce MFA strength. The Zscaler admin portal is a Zscaler-hosted service, not a private app behind App Connectors. Logout passwords control the client, not admin authentication.
Question 2 of 10, User & Device Management
An organization federates ZIdentity with Microsoft Entra ID over SAML. A new hire's assertion contains department=Finance and memberOf=Payroll-Approvers, but the user receives the default internet policy instead of the Finance URL filtering rule. The Finance rule references the Payroll-Approvers group. What is the MOST likely cause?
- AThe Finance rule sits below the default rule, so the default rule matches first
- BThe user has not yet rebooted, so Zscaler Client Connector is still caching the previous anonymous session token
- CThe IdP attribute carrying group membership is not mapped to the Zscaler group attribute Correct answer
- DEntra ID sends department values in lowercase, and Zscaler group names are matched case-sensitively in policy
Answer and explanation: Group-based policy only works when the IdP attribute that carries group membership is mapped to the group attribute in Zscaler; otherwise the user is authenticated but lands in no matching group and falls through to the default policy. A reboot is not required for attribute evaluation after authentication. The default rule is always evaluated last in rule order, so a Finance rule cannot sit below it. Case-sensitivity of department values does not explain a group-based rule failing.
Question 3 of 10, Platform Management
A manufacturing plant has unreliable internet links but many users who access local private apps. The company wants ZPA brokering to keep working for local users even during an internet outage. Which component should be deployed?
- AA second App Connector group in the head office to back up the plant connectors
- BA ZPA Private Service Edge at the plant alongside the local App Connectors Correct answer
- CA ZIA Virtual Service Edge at the plant to inspect internet-bound traffic
- DAdditional GRE tunnels from the plant to two ZIA data centers for failover
Answer and explanation: A ZPA Private Service Edge runs on the customer premises and brokers ZPA connections locally, so on-site users can keep reaching local private apps when the internet link fails, subject to configured cached policy and credential lifetimes. A ZIA Virtual Service Edge handles internet traffic inspection, not ZPA brokering. More GRE tunnels relate to ZIA and still depend on internet links. A head office connector group would also require internet connectivity to reach.
Question 4 of 10, Platform Management
After a merger, Company A (Zscaler customer, Okta IdP) must give Company B employees (Entra ID IdP, not yet on Zscaler) access to Company A's internet security and two internal apps within weeks, without merging directories first. Which approach meets this requirement with the LEAST disruption?
- AGive Company B users local accounts in the ZIA hosted database and ZPA Browser Access with shared credentials
- BMigrate all Company B accounts into Okta first, then let Client Connector enroll those users under the existing Okta SAML configuration
- CBuild a site-to-site IPsec tunnel between the two companies and route Company B users through Company A's data center
- DAdd Entra ID as a second IdP in ZIdentity, map its users to groups, and use those groups in ZIA and ZPA rules Correct answer
Answer and explanation: ZIdentity supports multiple IdPs, so Company B can authenticate with its own Entra ID while its users are mapped into groups that ZIA and ZPA policy reference, giving access quickly without a directory merge. Migrating accounts to Okta first is slower and more disruptive. A site-to-site tunnel extends network trust, which conflicts with zero trust and gives broad lateral access. Shared or locally managed accounts weaken identity assurance and auditability.
Question 5 of 10, Policy & Security Configuration
The security team wants a list of internal partner domains to be treated differently from their Zscaler-assigned category, without changing how the rest of the category is handled. What is the BEST way to achieve this?
- AAdd the domains to the SSL inspection bypass list
- BEdit the predefined category to remove those domains so they fall into the Miscellaneous category
- CCreate a custom URL category with those domains and use it in a rule above the category rule Correct answer
- DSubmit a recategorization request to Zscaler for each domain and wait for the change to apply globally
Answer and explanation: Custom URL categories hold tenant-specific domains and can be referenced by their own rule placed above the broader rule, giving targeted handling. A recategorization request changes global classification and is not a policy tool for partner domains. SSL bypass changes decryption, not filtering decisions. Predefined categories are maintained by Zscaler and their membership cannot be edited by the tenant.
Question 6 of 10, Policy & Security Configuration
A company wants ZPA users to reauthenticate with the IdP every eight hours for sensitive finance applications, while other apps keep the default session length. Which ZPA policy type should be configured?
- AAn access policy with a time-of-day schedule that blocks finance applications outside business hours
- BAn inspection policy that resets finance sessions every eight hours when a signature is detected
- CA client forwarding policy that bypasses the finance segments after eight hours of continuous use
- DA timeout policy for the finance application segments with an eight-hour reauthentication timeout Correct answer
Answer and explanation: ZPA timeout policies define reauthentication timeouts and idle timeouts per application segment, enabling stricter session lengths for sensitive apps. Client forwarding policies decide whether traffic is sent to ZPA, not how often users reauthenticate. A time-based access rule restricts when access is allowed but does not force reauthentication. Inspection policy applies AppProtection signatures and does not manage session lifetime.
Question 7 of 10, Policy & Security Configuration
A Cloud Sandbox policy is set to Allow and Scan for unknown executables from Miscellaneous or Unknown sites. Security leadership now wants to ensure patient-zero users never run a first-seen malicious file. What should the administrator change?
- ACreate a file type control rule that cautions users before downloading any Windows executable
- BSet the sandbox action to Quarantine so the first download is held until a verdict returns Correct answer
- CLower the Advanced Threat Protection suspicious content threshold so more pages are blocked outright
- DAdd an SSL inspection rule for Miscellaneous or Unknown sites
Answer and explanation: Quarantine holds the first instance of an unknown file until the sandbox returns a verdict, preventing patient-zero infection, while Allow and Scan lets the first user receive the file. Tuning ATP page risk affects web page blocking, not file detonation timing. SSL inspection is a prerequisite for scanning HTTPS content but does not change the allow-first behavior. A caution page still lets the user download and run the file.
Question 8 of 10, Monitoring, Reporting & Analytics
Risk360 shows the organization's highest contributing factor is External Attack Surface, driven by exposed VPN gateways and remote desktop services. What is the MOST effective way to reduce this risk using the Zero Trust Exchange?
- AEnable SSL inspection for the VPN and RDP services so attackers cannot hide in encrypted traffic
- BRaise the Advanced Threat Protection threshold so attacks against those internet-facing endpoints are blocked inline
- CPublish those services through ZPA and decommission the internet-facing VPN and RDP Correct answer
- DAdd the VPN gateway IPs to a ZIA firewall Allow rule so their traffic is logged and inspected
Answer and explanation: Replacing exposed VPN and RDP services with ZPA removes the internet-facing listeners, which is what drives external attack surface risk. ZIA firewall rules apply to outbound user traffic, not to inbound attacks on exposed gateways. ATP thresholds tune web threat blocking for users, not inbound exposure. SSL inspection of outbound traffic does not hide exposed services from internet scans.
Question 9 of 10, Troubleshooting & Incident Response
A user can browse a gambling site even though URL filtering blocks the Gambling category. Web Insights shows the transaction was allowed with the SSL inspection field marked as not inspected. What is the MOST likely explanation?
- AURL filtering only applies to traffic forwarded through Client Connector, not GRE
- BGambling is a super category, so blocking it requires a matching firewall rule
- CThe user accessed the site over HTTP, so URL filtering could not classify the page
- DA higher rule, such as an Allow for a custom category, matched before the Gambling block Correct answer
Answer and explanation: Even without inspection, ZIA can categorize by domain; an allowed transaction for a blocked category means an earlier matching rule allowed it, for example an Allow rule for a custom category or group placed above the Gambling block. HTTP traffic is fully visible and easier to classify. URL categories are enforced in URL filtering, not by firewall rules. URL filtering applies to all forwarding methods, including GRE.
Question 10 of 10, Integration & Optimization
PAC files for a large tenant have grown to hundreds of lines with nested conditions, and page loads slow down on older laptops. Which optimization is MOST appropriate?
- AHost the PAC file on each laptop's desktop so browsers always read the local copy
- BSimplify PAC logic, consolidating bypasses and avoiding DNS-resolving calls Correct answer
- CAdd more DNS lookups to the PAC file so each destination is classified precisely
- DReplace the PAC file with a list of URLs in the URL filtering policy for each user
Answer and explanation: PAC performance suffers from long, complex logic and functions such as isInNet and dnsResolve that trigger DNS lookups, so simplifying and consolidating improves speed. Adding DNS lookups makes it slower. Local copies are hard to maintain and do not fix the logic. URL filtering policy does not replace the forwarding role of a PAC file.