When configuring a loopback interface as the BGP source for connecting to an ISP, two important settings must be applied:
1. Enable EBGP Multihop (ebgp-enforce-multihop)
BGP normally expects directly connected neighbors, but since the ISP and FortiGate A are using loopback interfaces, packets will not be sent directly between their physical interfaces. The ebgp- enforce-multihop command allows BGP to form an eBGP peering over multiple hops.
2. Set the Update Source (update-source)
Since FortiGate is using a loopback interface as the source, the update-source command ensures that BGP updates originate from the loopback interface rather than a physical interface.
This is essential because BGP peers must match the source IP with the configured neighbor address.

The Fortinet FGSP (FortiGate Session Life Support Protocol) cluster allows session synchronization between two FortiGate devices to provide seamless failover. However, ICMP (ping) is a connectionless protocol, and by default, FortiGate does not synchronize connectionless sessions unless explicitly enabled.
In the exhibit:
# The command get system session list | grep icmp on FortiGate_B returns no output, meaning that ICMP sessions are not being synchronized from FortiGate_A.
# If session-pickup-connectionless is disabled, FortiGate_B will not receive ICMP sessions, causing packet loss during failover.

Comprehensive and Detailed Explanation From Exact Extract documents and Knowledge:
External Feeds (also known as Fabric Connectors or Threat Feeds) are used to dynamically import and update lists of IP addresses, domain names, or URLs from a remote server.
This feature allows FortiGate to automatically pull a daily updated IP block list from an external source and use it within a firewall policy. Because the FortiGate periodically checks the external server for updates, the firewall policy objects are refreshed automatically without requiring manual intervention, CLI scripts, or configuration reloads, making it the ideal solution for maintaining up-to-date block lists.

Comprehensive and Detailed 150 to 200 words of Explanation From Exact Extract of Enterprise Firewall 7.6 Administrator documents:
According to the FortiOS 7.6 Infrastructure study guide and Hardware Acceleration documentation, the Network Processor 7 (NP7) is the flagship hardware component designed to offload high-performance network traffic from the system CPU. A critical advancement of the NP7 over previous generations (such as the NP6) is its native support for Virtual eXtensible LAN (VXLAN) hardware acceleration.
In enterprise environments where VXLAN is used to extend Layer 2 segments over a Layer 3 network, the encapsulation and decapsulation of VXLAN headers can be computationally expensive. The NP7 provides specialized circuitry to perform these operations at line rate, significantly reducing latency and preventing CPU saturation. This allows the FortiGate to maintain high throughput even when handling complex overlay tunnels.
While the CP9 (Content Processor) (Option C) provides acceleration for SSL/TLS inspection and IPsec encryption, it does not handle network layer encapsulation like VXLAN. NTurbo (Option D) is a software feature that offloads firewall sessions to the network processors but is not a hardware chip itself. The SP5 (Option B) also supports VXLAN offloading in newer mid-range models, but the NP7 is the primary
"specialized acceleration hardware" referenced for high-end enterprise performance in the 7.6 curriculum.

The FortiGate SSL/SSH inspection profile is configured for Full SSL Inspection, which is necessary to analyze encrypted HTTPS traffic. However, the firewall policy is protecting an SSL server (the Linux server hosting the website), and currently, the SSL/SSH profile only applies to client-side SSL inspection.
To detect HTTPS-based attacks targeting the Linux server:
# FortiGate must act as an SSL intermediary to inspect encrypted traffic destined for the web server.
# The administrator must upload the SSL certificate of the Linux web server to FortiGate so that the server- side SSL inspection can decrypt incoming HTTPS traffic before analyzing it.