In which three ways are Security filters used in Spring Security? (Choose three.)

Question

Options

• ATo provide risk governance.
• BTo drive authentication.
• CTo manage application users.
• DTo provide a logout capability.
• ETo enforce authorization (access control).
• FTo encrypt data.

• A
  10% (5)
• B
  84% (42)
• C
  4% (2)
• F
  2% (1)

Explanation

Spring Security filters sit in a servlet filter chain and handle three core concerns: authentication (B) - verifying who you are via filters like UsernamePasswordAuthenticationFilter; logout (D) - the LogoutFilter intercepts logout requests and clears the security context; and authorization/access control (E) - filters like FilterSecurityInterceptor enforce whether an authenticated user can access a resource. Risk governance (A) and application user management (C) are administrative/business concerns handled outside the filter chain (e.g., in a user service or external governance tool), while encryption (F) is handled by dedicated crypto libraries or transport-layer security, not Spring Security filters. A handy memory anchor: think A-L-A - Authenticate, Logout, Authorize - the three jobs filters actually perform in the request pipeline.

No community discussion yet for this question.