The two static routes required in the FortiGate configuration to route traffic between both subnets through an inter-VDOM link are:
B. A static route in VDOM2 for the destination subnet 10.0.1.0/24
C. A static route in VDOM1 for the destination subnet 10.0.2.0/24
In VDOM1, a static route for the destination subnet 10.0.2.0/24 is needed to route traffic destined for VDOM2's subnet through the inter-VDOM link.
In VDOM2, a static route for the destination subnet 10.0.1.0/24 is needed to route traffic destined for VDOM1's subnet through the inter-VDOM link.

In the security profile, there are application overrides for specific Facebook-related features, such as
"Facebook" and "Facebook_Video.Play." However, the absence of specific signatures for actions like
"Facebook_Like.Button" might be preventing reactions. You need to ensure that the necessary application signatures for all desired Facebook features, including reactions (like buttons), are included in the security policy. Therefore, retrieving or adding those signatures would resolve the issue.

The configuration shown in the exhibit indicates that the FortiGate is using a Fortinet-specific RADIUS attribute (Fortinet-Group-Name) with the value "Training." This setup allows the FortiGate to authenticate users against the RADIUS server and match them to the "Training" Organizational Unit (OU). By doing so, only users within this specific group or OU can be authenticated and allowed access through the FortiGate.
References:
* FortiOS 7.4.1 Administration Guide: RADIUS Server Configuration

The SSL VPN http-request-header-timeout timer is used to mitigate denial of service (DoS) attacks by limiting the amount of time the FortiGate waits for the client to send an HTTP request header after a connection is established. This helps reduce the attack surface by preventing potential attacks that exploit prolonged connection times without fully completing requests.