Refer to the exhibit.
Refer to the exhibit.
When 'preserve-session-route enable' is configured on a FortiGate device, it prevents the reevaluation of session routing information for existing sessions, even after a route change. This means that any sessions already established do not have their routing information changed, and thus continue to use the old route. On the other hand, new sessions created after the route change will use the new routing paths. Therefore, FortiGate does not change the routing information on existing sessions after a route change, which aligns with the correct option.
through port2. Hub2 drops any already established TCP sessions. • With preserve-session-route enable, FortiGate does not reevaluate the session, and the session remains established through port1 and hub1. Active TCP sessions do not change. FortiGate routes new sessions through port2. pag 153 sdwan study 7.2. Y posiblemente algo de la D
AC. There should be two answers
A y C son correctas
A & C are correct, 2 answers
Nope, for checking of new routes and tagging them as "dirty" you also have to configure config firewall policy set firewall-session-dirty check-new end as stated here https://community.fortinet.com/t5/FortiGate/Technical-Tip-Information-about-firewall-session-dirty/ta-p/195802 Thus only A is correct.
C is correct too. Page 154. "With preserve-session-route enable, FortiGate does not reevaluate the session, and the session remains established through port1 and hub1. Active TCP sessions do not change. FortiGate routes new sessions through port2." It says "FortiGate performs routing lookups for NEW SESSIONS only, after a route change. " and that's true. After the route change, old sessions stay with the old route. But for new sessions, Fortigate performs a route lookup.
C is not correct, just A.
A is correct
A is correct. But also C. Page 154.