NSE4 · Question #87
Examine the following CLI configuration: config system session-ttl set default 1800 end What statement is true about the effect of the above configuration line?
The correct answer is A. Sessions can be idle for no more than 1800 seconds. The config system session-ttl set default 1800 command sets the default idle timeout for sessions on the FortiGate to 1800 seconds.
Question
Examine the following CLI configuration:
config system session-ttl set default 1800 end What statement is true about the effect of the above configuration line?
Options
- ASessions can be idle for no more than 1800 seconds.
- BThe maximum length of time a session can be open is 1800 seconds.
- CAfter 1800 seconds, the end user must re-authenticate.
- DAfter a session has been open for 1800 seconds, the FortiGate sends a keepalive packet to both
How the community answered
(57 responses)- A91% (52)
- B2% (1)
- C5% (3)
- D2% (1)
Why each option
The `config system session-ttl set default 1800` command sets the default idle timeout for sessions on the FortiGate to 1800 seconds.
The `config system session-ttl set default 1800` command configures the global default idle timeout for all new sessions passing through the FortiGate, meaning that if a session remains inactive for 1800 seconds (30 minutes), it will be automatically terminated.
This command sets the *idle* timeout, not the absolute maximum length of time a session can be open; active sessions will reset their idle timer.
The `session-ttl` command manages session state termination based on inactivity, not user re-authentication; re-authentication is typically governed by authentication policies or timeouts.
FortiGate session-ttl refers to the session's idle timeout, and the device does not automatically send keepalive packets to prolong sessions based on this setting.
Concept tested: FortiGate session idle timeout (session-ttl)
Source: https://docs.fortinet.com/document/fortigate/7.4.0/cli-reference/62078/config-system-session-ttl
Topics
Community Discussion
No community discussion yet for this question.