Which type of policy executes after authentication and controls traffic flow?

Question

Options

• AVisual Policy Editor policy
• BLocal Traffic policy
• CiRule policy
• DPer-Request Policy

• A
  5% (2)
• C
  2% (1)
• D
  93% (41)

Explanation

Per-Request Policy is the only policy type in F5 BIG-IP APM designed to execute after authentication - once a session is established by the per-session policy, the Per-Request Policy fires on each individual HTTP request to make dynamic access control and traffic-routing decisions.

• A (Visual Policy Editor) is a graphical tool used to build policies, not a policy type that executes in the data plane.
• B (Local Traffic Policy) operates at the LTM layer for general traffic steering (routing, header manipulation) and has no inherent awareness of authenticated sessions.
• C (iRule) is a TCL scripting mechanism for traffic manipulation at the LTM level - powerful, but not the purpose-built post-authentication control mechanism APM uses.

Memory tip: Think "Per-Request = Post-auth, Per-Hit" - it runs per request after the session is already authenticated, giving you granular, dynamic control over every hit.

No community discussion yet for this question.