First, create one phase 1 for each path-one phase 1 for the primary VPN and one for the backup VPN. You should also enable DPD on both ends.
Second, create at least one phase 2 definition for each phase 1.
Third, you must add at least one static route for each VPN. Routes for the primary VPN must have a lower distance (or lower priority) than the backup. This causes FortiGate to use the primary VPN while it's available.
If the primary VPN fails, then FortiGate automatically uses the backup route. Alternatively, you could use a dynamic routing protocol, such as OSPF or BGP.

Before FortiGate can send logs to FortiAnalyzer, the FortiGate device must be authorized on the FortiAnalyzer. This establishes trust and allows log forwarding from FortiGate to FortiAnalyzer.

It does not accept config changes, because it might increase memory usage even further. It explicitly does NOT run any quarantine actions. You can configure IPS fail-open to control how IPS behaves when the IPS socket buffer is full.

Note that the ImplicitSD-WAN rule name does not appear in the SD-WAN Rule Name column.
When the traffic is steered according to this rule, the field remains empty.

The "d-wan" zone in FortiGate SD-WAN configuration is the default SD-WAN zone created when SD- WAN is enabled. This zone contains all the interfaces assigned to SD-WAN and is essential for the functionality of the SD-WAN feature. The "d-wan" zone cannot be deleted because it is required for SD-WAN operations. Option A is incorrect because the underlay zone does not contain port1.