How to Configure VTY Lines for Idle Session Termination
A network engineer must configure the VTY lines on a router to achieve these results: • Remote access should be permitted for all feasible protocols. • Only a password should be required for device authentication. • All idle EXEC sessions must be terminated in 60 minutes. Which configuration should be applied?
Community Votes
59% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests precise keyword interpretation: 'idle' mandates exec-timeout, while the login command ensures password-only authentication without requiring usernames.
This question evaluates Cisco IOS VTY line configuration, focusing on the critical distinction between exec-timeout and absolute-timeout for managing idle sessions. Community consensus confirms that exec-timeout is the only command that terminates idle sessions without disrupting active traffic.
Candidates frequently select the option with absolute-timeout because they overlook the word 'idle', mistakenly assuming any 60-minute cutoff applies universally to all sessions regardless of user activity.
Community Discussion (10 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Core Concept: VTY Line Authentication & Timeout Commands
Although the provided options appear truncated in the prompt, this classic Cisco exam scenario tests three distinct VTY configuration requirements: 1. Protocol Flexibility:transport input all permits all supported remote access methods (SSH, Telnet, etc.), satisfying the "all feasible protocols" requirement.
2. Authentication Method: The login command enables password verification for the VTY line. Combined with the password command, it ensures only a password is required. Using login local would incorrectly mandate a username-password pair via AAA, which community comment #7 correctly identifies as a common distractor.
3. Session Management: The critical differentiator lies between exec-timeout and absolute-timeout.
- exec-timeout <minutes> <seconds> terminates an EXEC session only when it becomes idle. Setting this to 60 0 perfectly matches the requirement to drop idle sessions after one hour.
- absolute-timeout <minutes> forcibly terminates a session after a fixed duration, regardless of whether the user is actively typing or transferring data. As highlighted in comments #2 and #5, this violates the specific "idle" constraint.Why Option C is Correct
Option C correctly pairstransport input all, login, and exec-timeout 60 0. As noted by multiple community experts, exec-timeout is the precise tool for idle session management. The presence of login ensures the configured line password is actually prompted during connection attempts, addressing the authentication requirement cleanly.Why Other Options Fail
- Options using
absolute-timeoutviolate the "idle" constraint. While they do disconnect sessions after 60 minutes, they punish active users performing long-running tasks, which is undesirable in production environments. - Options omitting
loginfail the authentication requirement because the line password is ignored unless thelogindirective is explicitly enabled under the VTY configuration, a point emphasized in comments #1 and #3.
Official Reference
- Cisco IOS Configuration Fundamentals Command Reference: exec-timeout
- Cisco IOS Configuration Fundamentals Command Reference: absolute-timeout
- Cisco IOS Configuration Fundamentals Command Reference: transport input
Exam Strategy
When encountering timeout configuration questions, immediately underline keywords like idle, active, or fixed duration. "Idle" always points to exec-timeout, while "fixed/hard cutoff" points to absolute-timeout. Additionally, verify that login is present whenever a line password is configured; without it, the password is effectively disabled.
Related Analysis
Practice All 350-401 Questions
Access 218 questions with complete answers and detailed explanations.
View Full 350-401 Practice Test →
logincommand, this password will not be requested during the connection." "The third condition is literally met by solution C, but solution B also meets it. Because it is never specified 'idle exec' sessions only. Using absolute-timeout closes all sessions, active or inactive (meeting our third condition