Firewall administrators cannot authenticate to a firewall GUI. Which two logs on that firewall will contain authentication-related information useful in troubleshooting this issue? (Choose two.)

Question

Options

• Ams log
• Bauthd log
• CSystem log
• DTraffic log
• Edp-monitor log

• A
  2% (1)
• B
  91% (48)
• D
  6% (3)
• E
  2% (1)

Explanation

authd log is the authentication daemon log - it records all authentication attempts, failures, and errors processed by the authd service, making it the most direct source for diagnosing GUI login failures. System log captures administrative events including login attempts, lockouts, and authentication-related system events, complementing the authd log for troubleshooting access issues.

The distractors are wrong for these reasons: the ms log (management server log) tracks management plane process activity, not authentication events specifically; the Traffic log records data-plane sessions traversing the firewall - completely unrelated to admin GUI logins; and the dp-monitor log monitors data plane health and performance metrics, not management-plane authentication.

Memory tip: Think "Who lets you in?" - authd (the authentication daemon) is the bouncer, and the System log is the building's security register that notes every door-access attempt. Traffic and dp-monitor logs live on the data plane, which has nothing to do with who's logging into the management GUI.

No community discussion yet for this question.