Palo Alto Networks Certified Security Service Edge Engineer (Prisma Access SASE) Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose D0

  - Security policy evaluation in Strata Cloud Manager follows a hierarchical precedence based on configuration scope, and rules placed in a broader or higher-level scope are evaluated before rules placed in a more specific, lower-level folder such as Mobile Users or a particular connection type. If the new Web Security rule restricting the user group was created within a lower-level, more specific scope, it will not be reached at all whenever traffic first matches a broader, higher-level allow rule earlier in the evaluation order - the higher- level rule effectively wins by virtue of being processed first, and policy lookup stops at the first match. That is exactly the behavior described in the scenario: blocked applications continue to be reachable because a rule elsewhere in the hierarchy, evaluated ahead of the newly created restriction, is already permitting the traffic. This makes option D the accurate description of the root cause. Option C describes the reverse relationship and does not match how rule hierarchy actually influences precedence in this platform. Improper threat management settings (option A) would affect logging or blocking behavior for identified threats, not whether the URL/application access rule is evaluated at all, so it does not explain complete rule bypass. Option B is a plausible but unsubstantiated guess about scope targeting; the scenario gives no indication the rule was misapplied to a connection type rather than a hierarchy level, whereas rule-order precedence is the classic, most common cause of " rule appears configured correctly but has no effect. " Reference:Strata Cloud Manager - Security Policy Rule Order and Configuration Scope Precedence.