NSE6_FSW-7.2 · Question #10
What are two reasons why time synchronization between FortiGate and its managed FortiSwitch is critical in switch management? (Choose two.)
The correct answer is A. FortiSwitch does not retain its time after a reboot, which gets reset after each reboot. C. FortiSwitch cannot complete the DTLS handshake used in the CAPWAP tunnel. Time synchronization is critical in switch management. If the time on FortiGate and FortiSwitch is not synchronized, FortiSwitch can't complete the DTLS handshake used in CAPWAP, which prevents the switch from connecting to FortiGate. Another reason to have a working setup for…
Question
What are two reasons why time synchronization between FortiGate and its managed FortiSwitch is critical in switch management? (Choose two.)
Options
- AFortiSwitch does not retain its time after a reboot, which gets reset after each reboot.
- BFortiSwitch will not be able to become an NTP server for downstream devices.
- CFortiSwitch cannot complete the DTLS handshake used in the CAPWAP tunnel.
- DFortiSwitch will not allow other FortiSwitch devices in the chain be discovered by FortiGate.
How the community answered
(51 responses)- A75% (38)
- B18% (9)
- D8% (4)
Explanation
Time synchronization is critical in switch management. If the time on FortiGate and FortiSwitch is not synchronized, FortiSwitch can't complete the DTLS handshake used in CAPWAP, which prevents the switch from connecting to FortiGate. Another reason to have a working setup for time synchronization is because FortiSwitch doesn't retain its time after a reboot. When FortiSwitch is rebooted, the time on the switch is reset to the Unix epoch time (midnight of January 1, 1970, UTC).
Topics
Community Discussion
No community discussion yet for this question.