Authentication policies are evaluated in order relative to security rules. If the security rule allowing the traffic appears before the authentication rule, users are not prompted.
Why this answer
When an authentication policy is configured for the 'ssl' application, the firewall must identify the traffic as matching that rule before it reaches the security policy processing. Authentication policies are evaluated prior to security policies, but they exist in a separate rulebase. If the authentication policy rule is not correctly ordered within its own rulebase, or if it is not properly matched, the firewall will proceed to the security policy and possibly allow the traffic without authentication.
One common oversight is not placing the authentication policy rule in a position where it will be evaluated before the traffic is permitted by a broad security rule, such as one allowing web-browsing. In this case, the authentication policy must be placed before the security rule that allows web-browsing traffic, meaning it must be processed first in the firewall's evaluation order.
Exam trap
A common misconception is that authentication policies and security policies share the same rulebase order, but they are separate. Authentication policies are evaluated before security policies, and their ordering among themselves is critical to ensure that authentication is enforced before traffic is allowed by any security rule.
How to eliminate wrong answers
Option A is wrong because the authentication policy is always evaluated in the pre-rulebase, regardless of where the security policy is placed; the issue is the order within the rulebase, not the rulebase location. Option B is wrong because the 'ssl' application is a predefined application in Palo Alto Networks firewalls and does not require a custom signature; it is identified by the firewall's App-ID engine. Option D is wrong because the User-ID agent is not required to capture HTTPS traffic for authentication purposes; the firewall can prompt for credentials using captive portal or other methods without a User-ID agent.