In a hub-and-spoke topology using OSPF over IPsec VPNs, the point-to-multipoint network type is necessary to establish neighbor adjacencies between the hub and spokes. This network type ensures that OSPF operates correctly without requiring a designated router (DR) and allows dynamic routing updates across the IPsec tunnels.

These commands adjust the TCP maximum segment size advertised during session setup. That value defines the largest TCP payload a device is willing to receive in a single TCP segment, helping prevent fragmentation issues across the path.

From the Root FortiGate - System Administrator Configuration exhibit:
# The AdminSSO account has the super_admin_readonly role.
From the Downstream FortiGate - Security Fabric Settings exhibit:
# The Security Fabric role is set to Join Existing Fabric, meaning it will authenticate with the root FortiGate.
# SAML Single Sign-On (SSO) is enabled, and the default admin profile is set to super_admin_readonly.
When the AdminSSO user logs into the downstream FortiGate using SSO, the authentication request is sent to the root FortiGate, where AdminSSO has super_admin_readonly permissions. Since the downstream FortiGate inherits this permission through the Security Fabric configuration, the user will be granted super_admin_readonly access.

An external connector using External Feeds lets FortiGate automatically retrieve a regularly updated list of IP addresses from an external source and use that list dynamically in firewall policies. This is the appropriate method when the blocklist changes daily and needs to be enforced without manual updates.

Comprehensive and Detailed 150 to 200 words of Explanation From Exact Extract of Enterprise Firewall 7.6 Administrator documents:
According to the Fortinet Security Fabric 7.6 documentation and FortiAnalyzer study materials, when multiple FortiGate devices are part of a Security Fabric, logs are typically sent to a centralized FortiAnalyzer for a unified view of the network.
In the provided exhibit, the topology shows HQ-NGFW-1 as the Fabric Root and HQ-ISFW as a downstream device. One of the key benefits of the Security Fabric (Option C) is topology-wide visibility, where logs from different devices are correlated.
The traffic log table shows a " Malware " action for traffic originating from 10.0.2.51 (located behind HQ- ISFW) destined for a public IP. If UTM is not enabled on the HQ-ISFW itself, it cannot generate an Antivirus (AV) log. However, because HQ-ISFW is part of the Security Fabric, the traffic eventually passes through the upstream device, HQ-NGFW-1, to reach the internet. If UTM is enabled on HQ-NGFW-1 (Option B), that device will inspect the traffic, detect the malware, and generate the security log. FortiAnalyzer then displays this log as part of the unified threat view, associating it with the original source and the inspection point in the fabric path.