Q: 1
How will configuring set tcp-mss-sender and set tcp-mss-receiver in a firewall policy affect the size
and handling of TCP packets in the network?
Options
Discussion
Option B
C tbh, seems like a reasonable answer since the MSS config should consider headers and payload to avoid fragmentation. Trap is that C makes it sound more manual than how FortiGate handles MSS adjustment, but I still think thinking about header size matters here. Not super confident though.
Its B, but gotta say Fortinet loves to complicate these MSS settings. Setting tcp-mss-sender and receiver just tells the firewall the max TCP data it can handle per segment, that's it really. Sometimes feels like they're just trying to trip us up!
B is right. Configuring tcp-mss-sender/receiver sets the max TCP payload per segment, not about headers in this context.
Maybe B. Setting tcp-mss-sender and receiver basically controls the largest payload the device handles per segment, letting FortiGate manage packet sizing. I could see C if you were doing weird manual header stuff, but that's not typical. Thoughts?
B or C? B explains how MSS limits the max payload per segment, which matches what I've seen on other exams. But in rare custom tunnel setups you do have to think about header size like C says. FortiGate usually handles headers automatically though. Leaning B but not 100% sure.
Yeah it's B here
Its B for this. Most official Fortinet docs and some practice questions describe set tcp-mss-sender/receiver as controlling the max TCP payload per segment. I think that's what they're getting at, not manual header math like C. But if anyone has found something different in the exam or labs, let us know.
B vs C, but pretty sure it's B. The tcp-mss-sender and receiver just set the max TCP payload per segment that devices can handle. C gets tempting because sometimes you have to factor in headers when tunneling, but here it's about a firewall policy with no tunnel context. Anyone else see B tripping people up for this kind of question?
Hard to say, it's B here. The tcp-mss-sender/receiver settings just cap the max TCP payload the device will allow in a segment, headers are automatically taken care of under normal configs. C is tempting since header size matters in rare custom tunnel cases, but not for standard policies. Open if anyone disagrees!
Be respectful. No spam.
