Free ZDTA Questions Attempt

Option C preserves the protection supplied by Zscaler’s category hierarchy while adding a more specific business exception. Zscaler supports custom URL entries that retain parent-category membership, so a site can remain subject to its security classification instead of losing that context when added to a custom category. The administrator can then reference the custom category in a deliberately scoped, higher-priority URL Filtering rule, applying Allow to validated low-risk destinations or Isolate to uncertain content. Broader security-category rules continue to block destinations that require stronger enforcement. Replacing parent membership risks removing security classification, while a global allow is overly permissive. Bandwidth shaping controls capacity, not destination risk. Bypassing URL Filtering through Cloud App Control would also undermine the stated requirement to maintain protection.

Answer C is correct. ZPA Access Policy uses a top-down, first-match evaluation model. If an earlier allow rule matches the requested App Segment and the current Trusted Network condition, ZPA applies that allow action and stops processing the rule list. A later catch-all rule blocking contractors therefore cannot reverse the decision. The administrator should confirm the matched rule in the access logs, then narrow the earlier allow by adding the required identity, group, posture, or application criteria, or place the contractor restriction before the broader allow. Inspection and data-protection policies do not silently weaken an Access Policy deny. Client Forwarding bypass can prevent ZPA evaluation altogether, but it does not create the “secondary pass” described in option D. See Zscaler’s Access Policy configuration and Access Policy overview.

For a new cloud-gen firewall configuration, a default block posture is the safer baseline. Administrators should explicitly permit required business traffic and preserve required Zscaler service rules instead of leaving a broad default allow that weakens least-privilege design. Option A (Block all traffic) is correct because block all traffic is the recommended default-deny stance.

Why the other options are incorrect:

B. Permit all traffic: Permit-all firewall posture lets unexpected services leave the network until later rules stop them.

C. Disable the firewall: Disabling the firewall removes the enforcement layer instead of creating a safe default rule set.

D. Allow only web traffic (ports 80/443): Allowing only ports 80/443 would ignore valid non-web business traffic that may need explicit firewall rules.

Option B addresses a documented App Connector prerequisite. App Connectors establish outbound TLS connections to ZPA infrastructure and validate the ZPA service through certificate pinning. An inline device that intercepts TLS substitutes its own certificate, causing certificate validation and registration to fail. Zscaler’s App Connector deployment prerequisites explicitly state that all inline or man-in-the-middle TLS interception must be disabled because the service enforces certificate pinning. The App Connector deployment guide repeats the same requirement. The Azure egress policy therefore needs a narrowly scoped inspection bypass for required ZPA destinations. A fixed NAT address is not the remedy for a certificate-pinning failure. Disabling health checks would reduce operational visibility and does not repair registration. Delaying scale-set activity or waiting for DNS TTL expiration also leaves TLS interception in the connection path.

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