Free Fortinet NSE8_812 Practice Exam with Questions & Answers | Set: 3

To enable application detection on plain-text traffic that has been decrypted by FortiADC, the administrator must perform two configuration tasks on CL-1:

Enable SSL offloading in the firewall policy and select the SSL-Offload protocol options profile.

Enable application control in the firewall policy and select the SSL-Offload-App-Detect application list. References: https://docs.fortinet.com/document/fortigate/6.4.0/cookbook/103438/application-detection-on-ssl-offloaded-traffic

D is correct because Spoke1 will establish an ADVPN shortcut to Spoke2 when it detects that there is a demand for traffic between them. This is explained in the Fortinet Community article on Technical Tip: Fortinet Auto Discovery VPN (ADVPN) under Summary - ADVPN sequence of events. References:https://community.fortinet.com/t5/FortiGate/Technical-Tip-Fortinet-Auto-Discovery-VPN-ADVPN/ta-p/195698

The output in Exhibit A shows that the VPN tunnel is not established because the peer IP address is incorrect. The output in Exhibit B shows that the peer IP address is 192.168.1.100, but the baseline VPN configuration in Exhibit C shows that the peer IP address should be 192.168.1.101.

To restore VPN connectivity, you need to change the peer IP address in the VPN tunnel configuration to 192.168.1.101. The correct configuration is shown below:

config vpn ipsec phase1-interface

edit "wan"

set peer-ip 192.168.1.101

set peer-id 192.168.1.101

set dhgrp 1

set auth-mode psk

set psk SECRET_PSK

next

end

Option A is incorrect because it does not change the peer IP address. Option B is incorrect because it changes the peer IP address to 192.168.1.100, which is the incorrect IP address. Option D is incorrect because it does not include the necessary configuration for the VPN tunnel.

The default load balancing mode for the SD-WAN implicit rule is source IP based. This means that traffic will be load balanced evenly between the overlay members, regardless of the member's priority.

To prevent traffic from being load balanced, you can configure the priority of each overlay member to 10. This will make the member ineligible for load balancing.

The other options are not correct. Changing the load balancing mode to source-IP based will still result in traffic being load balanced. Creating a new static route with the internet sdwan-zone only will not affect the load balancing of the overlay interface. Configuring the cost in each overlay member to 10 will also not affect the load balancing, as the cost is only used when the implicit rule cannot find a match for the destination IP address.

https://docs.fortinet.com/document/fortigate/6.4.0/sd-wan-deployment-for-mssps/775385/defining-interface-members

A is correct because using network-overlay id allows you to configure multiple ADVPN tunnels on a single interface with a single IP address on the DC FortiGate. This is explained in the FortiGate Administration Guide under ADVPN > Configuring ADVPN > Configuring ADVPN on the hub. References: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/978793/advpn https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/978793/advpn/978794/configuring-advpn

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Use-case-of-Network-Ids-with-ADVPN-shortcut/ta-p/241025

C. The IP address of the FortiSwitch is 10.12.240.2:This statement is correct based on the exhibit and your clarification. The exhibit lists the "IP Address" as 10.12.240.2 across multiple entries, including ports and VLANs associated with the device "sup-fgt-hw" (FortiSwitch). Your reasoning indicates that this IP is the management address of the FortiSwitch, as it is consistently shown as the IP for the device containing the ports. In Fortinet’s architecture, as described in the NSE 8 study guide, the management IP of a FortiSwitch is typically configured and visible in such configurations, especially when integrated with FortiGate and FortiNAC. The "Device" column labeling "sup-fgt-hw" further supports that this is the FortiSwitch, and the IP 10.12.240.2 is its management address. This aligns with FortiSwitch management and integration details in the NSE 8 study guide.

D. An unknown host is connected to port3:This statement is correct as the exhibit highlights port3 under the "Name" column for the device "sup-fgt-hw" with a "Rogue Host" status in the "Connection" column, an IP address of 10.12.240.2, a Default VLAN of 100, and an Operational Status of "Link Up." In FortiNAC, a "Rogue Host" indicates an unknown or unauthorized device connected to the network, which FortiNAC identifies for further action or isolation. This is consistent with FortiNAC’s capabilities for detecting and classifying unknown devices, as detailed in the NSE 8 study guide under network access control and rogue device detection.

Why A and B are incorrect:

A. A device that is modeled in FortiNAC is connected on VLAN_4093: This is incorrect based on your clarification that there is no device connected on that port—it is simply the default VLAN (4093) for that entry. The exhibit shows VLAN_4093 with a "Not Connected" status and "Link Up" operational status, but no active device connection is indicated. The NSE 8 study guide emphasizes that FortiNAC requires an active connection and device profiling for a device to be considered "connected," which is not evident here for VLAN_4093.

B. Port8 is connected to a FortiGate in FortiLink mode: This is incorrect because the exhibit shows port8 with a "Learned Uplink" status, which, as you noted, refers to any kind of uplink and does not specifically indicate FortiLink mode. FortiLink mode is a specific configuration between FortiGate and FortiSwitch requiring explicit settings, which are not mentioned or implied in the exhibit. The NSE 8 study guide clarifies that FortiLink mode involves distinct configuration details (e.g., FortiLink interfaces), which are absent here.

Fortinet Network Security Expert 8 Study Guide References:

FortiNAC 7.2 Admin Guide (NSE 8): Sections on Device Visibility, VLAN Management, and Rogue Device Detection.

FortiSwitch 7.2 Admin Guide (NSE 8): Sections on FortiLink Configuration, Network Segmentation, and Management IP Configuration.

FortiGate 7.2 Admin Guide (NSE 8): Sections on Integration with FortiNAC and FortiSwitch for Network Security.