Comprehensive and Detailed Explanation From Exact Extract documents and Knowledge:
OSPF external routes (Type 5 LSAs) can be learned from multiple paths. For a FortiGate to install multiple equal-cost paths into the routing table-a feature known as ECMP (Equal-Cost Multi-Path) -the OSPF process must have ECMP enabled and the maximum path count must be set to a value greater than one. If ECMP is disabled or the limit is set to 1, the FortiGate will select only the single best path (based on cost and RFC 1583/2328 selection rules) to install in the routing table, even if multiple valid advertisements exist.

Applying an aggressive IPS profile without prior testing can disrupt legitimate applications by incorrectly identifying normal traffic as malicious. To prevent disruptions while still monitoring for threats:
# Enable IPS in "Monitor Mode" first:
# This allows FortiGate to log and analyze potential threats without actively blocking traffic.
# Administrators can review logs and fine-tune IPS signatures to minimize false positives before switching to blocking mode.
# Verify and adjust signature patterns:
# Some signatures might trigger unnecessary blocks for legitimate application traffic.
# By analyzing logs, administrators can disable or modify specific rules causing false positives.

According to the FortiManager central management documentation, pre-run CLI templates are specifically designed for provisioning tasks on Low-Touch Provisioning (LTP) or Zero-Touch Provisioning (ZTP) model devices. Once the installation is performed for the first time and the real device is successfully linked to FortiManager, the template is automatically unassigned (auto-unassigned) from the firewall. This is distinct from standard CLI templates, which remain assigned to the device until an administrator manually removes them.

The diagram shows a multi-area OSPF network where:
FortiGate A is in OSPF Area 0 (Backbone area).
FortiGate B is in OSPF Area 0.0.0.1 and is connected to an RIP network.
To ensure that OSPF Area 0 (0.0.0.0) learns routes from the external RIP network, FortiGate B must redistribute RIP routes into OSPF.
Steps to achieve this:
1. Enable route redistribution on FortiGate B to inject RIP-learned routes into OSPF.
2. This allows OSPF Area 0.0.0.1 to forward RIP routes to OSPF Area 0 (0.0.0.0), making the external network visible.

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.