Fortinet Updated FCSS_EFW_AD-7.6 Exam Questions and Answers by jeremy

FortiGate_A and FortiGate_B are in the same autonomous system (AS), and FortiGate_A does not currently have route 172.16.1.248/30 in its routing table. However, FortiGate_B has this route as a connected route.

To dynamically advertise only 172.16.1.248/30 from FortiGate_B to FortiGate_A, the administrator must configure a BGP route map out on FortiGate_B that specifically permits only this prefix.

A BGP route map out on FortiGate_B controls which routes FortiGate_B advertises to FortiGate_A. If no filtering is applied, FortiGate_B might advertise all BGP-learned and connected routes, which is not what the administrator wants. The route map should include a prefix-list that explicitly allows only 172.16.1.248/30 and denies everything else.

Comprehensive and Detailed Explanation From Exact Extract documents and Knowledge:

The TCP Maximum Segment Size (MSS) defines the largest payload (the data portion of the segment, excluding TCP and IP headers) that a device can receive in a single TCP segment.

When you configure tcp-mss-sender and tcp-mss-receiver on a FortiGate interface or tunnel, the FortiGate intercepts the TCP 3-way handshake (SYN and SYN-ACK packets). It modifies the MSS value announced by the hosts to ensure that the resulting segments, once encapsulated (e.g., by IPsec or VXLAN), do not exceed the MTU of the path. By reducing the allowed payload size at the source, FortiGate prevents the need for fragmentation further down the line, which improves overall network efficiency and prevents packet loss in " MTU-tight " environments.

==============

neighbor-group:

● This command is used to group multiple BGP neighbors with the same configuration, reducing redundant configuration.

● Instead of defining individual BGP settings for each spoke, the administrator can create a neighbor-group and apply the same policies, reducing manual work.

neighbor-range:

● This command allows the configuration of a range of neighbor IPs dynamically, reducing the need to manually define each spoke neighbor.

● It automatically adds BGP neighbors that match a given prefix, simplifying deployment.

From the BGP neighbor status output, the key issue is that BGP is stuck in the " Idle " state, meaning the FortiGate is unable to establish a BGP session with its peer 100.65.4.1 (Remote AS 65300).

The output also shows:

● " Not directly connected EBGP " → This means the BGP peer is not on the same subnet, requiring multihop BGP.

● " Update source is Loopback " → Since a loopback interface is used, FortiGate must be configured to allow BGP neighbors over multiple hops.

To resolve this issue, the administrator must enable ebgp-enforce-multihop, which allows BGP sessions to be established even when the neighbors are not directly connected.