Refer to the exhibit.
The administrator can see the traps for the failed login attempts, but can not see the traps of successful login attempts.
What command is needed to resolve the issue?
A . Configure logging history 2
B . Configure logging history 3
C . Configure logging history 4
D . Configure logging history 5
Answer: D
Explanation:
By default, the maximum severity sent as a syslog trap is warning. That is why you see syslog traps for login failures. Since a login success is severity 5 (notifications), those syslog messages will not be converted to traps.
To fix this, configure:
Note: The syntax of login block is: login block-for seconds attempts tries within seconds