FCSS_EFW_AD-7.6 Practice Questions

When configuring a BGP peering session with an external neighbor (eBGP), such as an ISP, using a loopback interface as the source, two specific configuration requirements must be met in FortiOS:

update-source (B): By default, BGP uses the IP address of the physical egress interface to initiate the TCP connection to a neighbor. If you want the BGP session to be sourced from a loopback interface (which is a common practice for stability, as loopbacks do not go down unless the entire router fails), you must explicitly define this using the set update-source < interface > command under the neighbor configuration.

ebgp-enforce-multihop (A): Standard eBGP sessions have a default Time-to-Live (TTL) of 1, meaning the peer is expected to be directly connected. When peering using loopback addresses, the loopback interface is logically one hop away from the physical link. Therefore, the connection will fail unless you increase the TTL. The set ebgp-enforce-multihop < hop-count > command allows the BGP session to be established even if the peer is not on a directly connected subnet or if loopbacks are used.

In the provided exhibit (image_bd178a.jpg), the CLI shows the neighbor configuration. To successfully peer with the ISP (10.200.3.1) using a local loopback, the administrator would need to add:

set update-source " loopback0 "

set ebgp-enforce-multihop 2 (or a higher value)

Based on the packet capture provided in the exhibit and Fortinet ' s Enterprise Firewall 7.6 inspection standards:

Web Filtering Effectiveness (B): The exhibit shows the Server Name Indication (SNI) extension within the Client Hello, specifically indicating the hostname www.fortinet.com. When a firewall policy is configured for SSL Certificate Inspection , the FortiGate does not decrypt the payload but instead relies on the SNI or the certificate ' s Subject/SAN fields to identify the website. Therefore, a web filtering profile can effectively categorize and block/allow this traffic based on the domain name found in the SNI.

TLS Version Support (D): The supported_versions extension is a feature introduced with TLS 1.3 to negotiate the version of the handshake. In the exhibit, the extension explicitly lists two versions: TLS 1.3 (0x0304) and TLS 1.2 (0x0303) . This tells the FortiGate exactly which protocols the client is capable of using for this session.

Why A is incorrect: Antivirus profiles require Deep SSL Inspection (full decryption) to scan the actual files and payload of the session. Since the policy is using Certificate Inspection , the FortiGate cannot see the cleartext data, rendering the antivirus profile ineffective for this encrypted traffic.

Why C is incorrect: While the Subject Alternative Name (SAN) is a common way to identify a site, it is found in the server ' s certificate. In this specific capture, the SNI (Server Name Indication) is already present in the Client Hello, which allows the FortiGate to apply security profiles even before the server ' s certificate is seen.