When diagnosing an issue, which loggers would provide insight into authentication problems? (Choose Two)

Question

Options

• ASecurity logger
• BSystemOut logger
• CDatabase logger
• DApplication logger

• A
  84% (36)
• C
  9% (4)
• D
  7% (3)

Explanation

Security logger (A) captures authentication and authorization events directly - failed logins, token validation errors, permission denials - making it the primary source for auth diagnostics. SystemOut logger (B) captures general application output including runtime exceptions and stack traces that often surface when authentication failures cascade into errors, providing critical context alongside the security log.

Why the distractors are wrong:

• Database logger (C) tracks SQL queries and DB connections - useful for data issues, but authentication logic typically fails before or independent of database calls.
• Application logger (D) is too vague; in most frameworks, authentication events are deliberately separated into the security logger to isolate access control from business logic logging.

Memory tip: Think "Who's at the door?" - the Security logger is the bouncer checking credentials, while SystemOut is the general intercom that announces when something goes wrong anywhere in the building, including at the door.

No community discussion yet for this question.