After logging in to a web application, additional authentication is checked at various application points. Which of the following is the PRIMARY reason for such an approach?

Question

Options

• ATo ensure access rights meet classification requirements
• BTo facilitate the analysis of application logs
• CTo ensure web application availability
• DTo support strong two-factor authentication protocols

• A
  81% (44)
• B
  4% (2)
• C
  11% (6)
• D
  4% (2)

Explanation

Checking authentication at multiple points within an application enforces least privilege and access control - ensuring that a user who logged in successfully still has the appropriate rights to access specific resources, features, or data classifications at each step. This is a defense-in-depth strategy: a single login doesn't guarantee that every subsequent action is authorized, especially when different parts of the app handle sensitive or classified data.

Why the distractors are wrong:

• B - Log analysis is a monitoring/audit concern, not a reason to re-authenticate users mid-session.
• C - Availability (uptime, load balancing) is unrelated to authentication checks; adding auth steps would actually reduce availability marginally.
• D - Two-factor authentication (2FA) is a login mechanism, not something applied repeatedly throughout a session at application checkpoints.

Memory tip: Think "access rights at each gate." A government building analogy works well - you badge in at the front door (login), but certain rooms require you to badge again (re-authentication at checkpoints) because not everyone cleared for the building is cleared for every room. That's access control matching classification requirements.

No community discussion yet for this question.