When configuring BIG-IP APM, which setting should be considered to provide a seamless user experience while maintaining security?

Question

Options

• AEnforcing strict password complexity requirements.
• BImplementing multi-factor authentication for all users.
• CAllowing session persistence for certain applications.
• DEnabling automatic logoff after a short period of inactivity.

• A
  10% (3)
• B
  3% (1)
• C
  83% (24)
• D
  3% (1)

Explanation

Allowing session persistence (C) lets authenticated users maintain their sessions across multiple requests or reconnections without re-authenticating, which is the classic balance between usability and security - users aren't interrupted unnecessarily, yet the APM policy still governs access. Option A (strict password complexity) is a general security hardening measure, not specific to session experience on BIG-IP APM. Option B (MFA for all users) increases security but can actively disrupt the user experience by adding friction to every authentication event - it's a trade-off, not a seamless solution. Option D (short inactivity logoff) prioritizes security over experience, forcing users to re-authenticate frequently, which is the opposite of seamless.

Memory tip: Think "persistence = patience" - session persistence lets APM patiently keep the user logged in so they don't have to repeatedly prove who they are, balancing smooth access with controlled security.

No community discussion yet for this question.