Where are Access Policy session variables stored during a user session?

Question

Options

• Atmsh database
• BSession database
• CiRules context
• DTraffic Management Microkernel

• B
  88% (14)
• C
  6% (1)
• D
  6% (1)

Explanation

During a user session, F5 BIG-IP Access Policy Manager (APM) stores all session variables - such as username, group membership, and client attributes collected during the access policy - in the Session database, a per-session data store keyed by a unique session ID. This allows variables to persist across multiple requests throughout the life of that session and be referenced or modified at any point in the policy flow.

Why the distractors are wrong:

• A (tmsh database): TMSH (Traffic Management Shell) is a configuration management interface, not a runtime data store - it holds system config, not live session state.
• C (iRules context): iRules can read session variables via ACCESS::session commands, but they execute per-connection and don't provide persistent storage; the session database is the actual backing store.
• D (Traffic Management Microkernel): TMM is the packet-forwarding engine responsible for traffic processing, not a named storage layer for application session data.

Memory tip: The answer mirrors the naming - session variables live in the session database. If something belongs to a session, store it where sessions live.

No community discussion yet for this question.