Free Zscaler ZDTA Practice Exam with Questions & Answers | Set: 3

Option B targets the evidence: Client Connector changes state whenever network detection changes. Trusted-network classification determines which Forwarding Profile action applies, so criteria that fluctuate during SSID transitions can alternate traffic between forwarding and bypass. The administrator should use stable, independently verifiable criteria such as DNS server, DNS search domain, default gateway, DHCP server, or egress IP, as appropriate for the branch. Zscaler’s Trusted Networks overview explains that predefined criteria are selected in Forwarding Profiles, while its Forwarding Profile configuration guide describes how Client Connector verifies trusted networks. Expanding the ERP application segment does not correct state transitions. Disabling posture weakens security without stabilizing forwarding. Backhauling all traffic is disproportionate and retains the underlying unreliable trusted-network definition rather than correcting it.

================

Answer A is correct. ZPA brokers a connection between an authorized identity and a specifically defined private application instead of extending network access to the user. App Connectors establish outbound connections to the Zero Trust Exchange, so applications do not require inbound exposure. Zscaler describes this model as a segment of one: users receive least-privileged connectivity to named applications, while unrelated applications and IP ranges remain invisible and unreachable. That directly limits discovery, probing, and lateral movement between the two merging environments while allowing approved business connectivity to continue. VPN concentrators, shared VLANs, and subnet ACLs still place users on routable net works and increase the scope that must be protected. Intrusion detection can report scanning, but it does not remove the underlying reachability. See Zscaler’s Private Access data sheet and ZPA cloud architecture.

One GRE tunnel is sufficient because the required 700 Mbps is below Zscaler’s documented per-tunnel limit and the scenario does not require failover. Zscaler’s GRE deployment best practices state that a GRE tunnel supports up to 1 Gbps when internal addresses are not behind NAT. The GRE self-provisioning guidance also explains that one static IP address can be mapped to a GRE tunnel. Because the underlay is trusted, GRE’s lack of encryption is acceptable for this requirement and avoids IPSec encryption and rekey overhead. A single IPSec tunnel is unsuitable for 700 Mbps because Zscaler documents a lower per-public-source-IP limit for IPSec. Two tunnels add unnecessary configuration and routing complexity when high availability is explicitly excluded. Capacity, MTU, routing, and Service Edge reachability should still be validated before production use.

SCIM is designed to automate identity and group lifecycle changes between the authoritative identity provider and Zscaler. Zscaler’s SCIM documentation identifies roles and entitlements among the attributes that can be associated with users, while entitlement assignment guidance supports assigning administrative or service entitlements to user groups. Option B therefore allows team membership changes made at the IdP to flow into the relevant Zscaler groups, where group-based entitlements consistently govern access. SAML primarily supplies authentication assertions during sign-in and is not a substitute for proactive lifecycle provisioning. Individual assignments create administrative overhead and entitlement drift as teams change. Local accounts further separate Zscaler access from the organization’s authoritative directory and make joiner, mover, and leaver governance harder to maintain.

The failure is caused by an unstable trusted-network signal, so the trusted definition and associated forwarding decisions must be corrected. Zscaler’s Trusted Network search reference lists default gateway and egress IP among the available criteria. Combining stable campus properties prevents the public DNS-resolver change from intermittently classifying on-campus devices as off-trusted. Zscaler’s Forwarding Profile guidance supports applying different forwarding behavior according to trusted-network status. Option B then makes policy intent explicit: HR and SIP bypass only after the campus match, while the following off-trusted rule forwards those applications for inspection when users roam. PAC fallback or proxy enforcement adds another decision path without repairing detection. Relaxing posture checks does not identify the network and would weaken device controls.

When migrating from an on-premises proxy to Tunnel Mode, leaving legacy browser or system proxy settings in place can create loops or conflicting forwarding paths. Best practice is to enforce no proxy configuration so Client Connector owns traffic steering cleanly through the configured tunnel. Option B (Enforce no Proxy Configuration) is correct because Tunnel Mode should not depend on legacy proxy auto-configuration.

Why the other options are incorrect:

A. Execute a GPO update to retrieve the proxy settings from AD: A GPO can push Windows settings, but using it to reapply old proxy configuration works against Tunnel Mode best practice.

C. Use Web Proxy Auto Discovery (WPAD) to auto-configure the proxy: WPAD auto-discovers proxy settings; it can accidentally preserve legacy proxy behavior during a tunnel-mode migration.

D. Use an automatic configuration script (forwarding PAC file): A PAC file tells the client or browser which proxy path to use for matching destinations.

When SSL Inspection policy bypasses a transaction, Zscaler does not decrypt and re-sign the session. Instead, the proxy passes the TLS connection through so the browser receives the real origin-server certificate. This behavior is used for pinned applications, privacy categories, and traffic that should not be decrypted. Option C (When traffic is exempted in SSL Inspection policy rules) is correct because bypassed SSL Inspection rules preserve the server certificate in the user ' s browser session.

Why the other options are incorrect:

A. When traffic contains a known threat signature: Threat signatures trigger security handling such as blocking or inspection. Passing the real server certificate happens when SSL inspection is bypassed.

B. When web traffic is on custom TCP ports: Custom TCP ports affect traffic handling and forwarding. They do not automatically make Zscaler present the real origin certificate to the browser.

D. When user has connected to server in the past: Past connection history does not decide certificate presentation. The SSL Inspection policy action for the current transaction does.

Option B follows the Boolean requirements stated in the policy. The contractor must satisfy group membership, full-disk encryption, and the minimum CrowdStrike ZTA score. Passing the score does not compensate for failing disk encryption because the required conditions are joined by AND; one failed mandatory condition prevents the Allow rule from matching. Zscaler’s Device Posture Profiles overview confirms that ZIA and ZPA policies can use the posture evaluation result. The ZPA Access Policy configuration guide documents posture-profile conditions, and Zscaler supports both CrowdStrike ZTA scoring and full-disk-encryption posture types. Cloud Sandbox protects internet-bound content and is not an alternative ZPA access outcome. App Connector selection does not weaken authorization. A Trusted Network can be a policy criterion, but it does not override additional mandatory conditions unless an explicit earlier bypass rule is configured.

================

Option D makes the group eligible to consume the required Zscaler service. Authentication Service service entitlements assign users or user groups to subscribed services such as Internet & SaaS, Private Access, or Digital Experience. After the Contractor ZPA Users group receives the Private Access entitlement, ZPA Access Policy can determine which specific private applications its members may access. Zscaler’s entitlement-management documentation explicitly states that service entitlements assign Authentication Service users and groups to Zscaler services. The entitlement-assignment guide includes Private Access as an assignable service. Creating duplicate local users undermines identity synchronization. Administrator session lifetime controls administrative authentication, not contractor service eligibility. Device posture can further restrict an entitled user’s access, but it cannot replace the underlying ZPA service entitlement that permits the group to use Private Access.

================

Option A places the threat-intelligence denial where it can match before generic outbound allows without unnecessarily rewriting Zscaler-managed Microsoft 365 logic. The subscribed addresses should be represented by an appropriate destination IP group and referenced in a specific Drop rule. Zscaler’s Destination IP Groups documentation confirms that destination addresses and categories can be grouped for Firewall policy enforcement. Its predefined Firewall Filtering rule documentation explains the special ordering of predefined rules, while Firewall Control best practices emphasize narrowly conditioned rules. Placing the block beneath broad allows makes it ineffective because first-match evaluation has already permitted the traffic. Editing predefined Microsoft 365 behavior introduces avoidable maintenance risk. Broad SaaS allows above the threat block also create the exact exposure the SOC is trying to eliminate.

================