How does CCU (Concurrent User) utilization vary for different types of access policy deployments in BIG-IP APM?

Question

Options

• ACCU utilization is higher for Clientless VPN than for Remote Desktop access.
• BCCU utilization is the same for all access policy deployments.
• CCCU utilization is higher for Remote Desktop access than for Clientless VPN.
• DCCU utilization depends on the number of licensed users.

• A
  91% (30)
• B
  3% (1)
• C
  6% (2)

Explanation

Option A is correct because Clientless VPN (web portal/browser-based access) maintains persistent browser sessions that tend to accumulate and remain active as long as the user's browser is open - users often leave tabs open, inflating concurrent session counts. Remote Desktop connections, by contrast, are more discrete and controlled; sessions are typically terminated when the user closes the RDP window, releasing the CCU slot more promptly.

Option B is wrong because BIG-IP APM session types differ meaningfully in lifecycle and persistence - treating all access types as CCU-equivalent ignores how session duration and termination behavior drive actual utilization.

Option C is wrong because it reverses the relationship - Remote Desktop sessions are more tightly scoped to active use, whereas Clientless VPN sessions can linger passively in a browser tab without the user actively doing anything.

Option D is wrong because it confuses CCU capacity (the licensed ceiling) with CCU utilization (how efficiently that capacity is consumed by session type) - the number of licensed users sets the maximum, not the utilization pattern.

Memory tip: Think "Clientless = Clingy" - browser-based sessions cling to their CCU slot because browsers stay open, while Remote Desktop sessions drop the slot as soon as the window closes.

No community discussion yet for this question.