NSE4_FGT-6.4 · Question #65
Why does FortiGate Keep TCP sessions in the session table for several seconds, even after both sides (client and server) have terminated the session?
The correct answer is A. To allow for out-of-order packets that could arrive after the FIN/ACK packets. TCP provides the ability for one end of a connection to terminate its output while still receiving data from the other end. This is called a half-close. FortiGate unit implements a specific timer before removing an entry in the firewall session table. When a session is closed…
Question
Why does FortiGate Keep TCP sessions in the session table for several seconds, even after both sides (client and server) have terminated the session?
Options
- ATo allow for out-of-order packets that could arrive after the FIN/ACK packets
- BTo finish any inspection operations
- CTo remove the NAT operation
- DTo generate logs
How the community answered
(23 responses)- A70% (16)
- B9% (2)
- C4% (1)
- D17% (4)
Explanation
TCP provides the ability for one end of a connection to terminate its output while still receiving data from the other end. This is called a half-close. FortiGate unit implements a specific timer before removing an entry in the firewall session table. When a session is closed by both sides, FortiGate keep in the sessione table for a few seconds more, to allow any out-of-order packets that could arrive after the FIN/ACK packet. This is the
Topics
Community Discussion
No community discussion yet for this question.