How can you tune policy settings to limit the number of active sessions per IP address in BIG-IP APM?

Question

Options

• ABy adjusting the virtual server's connection rate limit settings
• BBy configuring the traffic management settings on the BIG-IP device
• CBy enabling the "Session Limit" option in the access profile settings
• DBy implementing custom iRules to track active sessions per IP address

• A
  4% (2)
• C
  94% (45)
• D
  2% (1)

Explanation

Option C is correct because BIG-IP APM's access profile settings include a native Session Limit feature that allows administrators to cap the number of concurrent sessions originating from a single IP address, providing a built-in policy control without custom code.

Option A is wrong because virtual server connection rate limits control the rate of incoming TCP connections, not the count of active authenticated APM sessions per IP. Option B is a vague distractor - "traffic management settings" is not a specific BIG-IP APM construct and has no direct mechanism for per-IP session limits. Option D is wrong because while iRules could implement this logic, it requires custom development and is not the intended or recommended approach - APM already exposes this natively in the access profile.

Memory tip: Think "APM = Access Profile Manager" - anything that limits access (like session counts) lives in the access profile, not the virtual server or iRules layer.

No community discussion yet for this question.