Free Fortinet NSE7_FSN_AR-7.6 Practice Exam with Questions & Answers | Set: 4

The correct answers are C and D.

The study guide states: “SSL certificate inspection relies on extracting the FQDN of the URL from either: TLS extension server name indication (SNI), SSL certificate common name (CN).” It also says: “When using SSL certificate inspection, FortiGate is not decrypting the traffic. It is only inspecting the server digital certificates and the SNI field, which are interchanged before the encryption.”

This proves the second part of the answer:

under SSL certificate inspection, FortiGate does not decrypt the traffic

therefore, if the traffic is allowed, it still passes without decryption

That makes D correct.

For the SNI mismatch behavior, the FortiOS administration guide describes the default Server certificate SNI check behavior as:

“Enable: If it is mismatched use the CN in the server certificate for URL”

So if the SNI does not match the CN or any SAN, FortiGate falls back to using the CN from the Subject field for URL handling under the default setting. That makes C correct.

Why the other options are wrong:

A is wrong because with the default SNI-check behavior, when the SNI mismatches the certificate identity, FortiGate does not continue using the mismatched SNI. Instead, it uses the CN in the server certificate for the URL.

B is not the best answer in this single pair selection. While certificate inspection does not decrypt traffic, the key default behavior the documents explicitly highlight for this mismatch case is:

use the CN when SNI mismatches, and

certificate inspection does not decrypt allowed HTTPS traffic.

So the verified answers are: C, D.

The Network Security Support Engineer 7.6 Study Guide explicitly explains this debug message:

“iprope_in_check() check failed, drop” means the packet is destined to a FortiGate IP address and one of these conditions applies:

The service is not enabled

The service is using a different TCP port

The source IP address is not included in the trusted host list

The packet matches a local-in policy with action deny

That directly confirms C. Trusted host list misconfiguration.

Why D is the second valid choice:

The FortiOS administration guide explains that:

“IP pools and VIPs are considered local IP addresses if responding to ARP requests on these external IP addresses is enabled … the FortiGate is considered a destination for those IP addresses … once an IP pool or VIP has been configured … the FortiGate considers it as a local address and will not forward traffic based on the routing table.”

Because iprope_in_check() is a local-in/local-destination type failure, a VIP or IP pool misconfiguration can cause traffic to be treated as destined for the FortiGate itself, which can then trigger this drop condition if the matching local service/local-in handling is not valid. So D is the closest supported second answer from the available choices.

Why the other options are wrong:

A is wrong because policy route problems are not the documented meaning of this specific debug message. The study guide instead ties iprope_in_check() check failed, drop to management/local-in conditions.

B is wrong because the study guide says traffic shaping drops appear as: “Denied by quota check”

The correct answers are A and B.

The exhibit shows:

override: disable

both members are currently in-sync

only port7 appears under HBDEV stats, so it is the active heartbeat interface

the cluster is in HA A-P mode

Why A is correct:

With override disabled, after a failover the new primary keeps that role when the old primary comes back. The FortiOS administration guide states:

“When the primary FortiGate rejoins the cluster the secondary FortiGate continues to operate as the primary FortiGate.”

So if FGVM...649 reboots and FGVM...650 becomes primary, FGVM...650 will remain primary after FGVM...649 rejoins.

Why B is correct:

The study guide states:

“When FortiGate devices configured in an HA cluster lose communication with each other on the heartbeat interface, each FortiGate assumes the role of the primary device.”

The exhibit shows only port7 as the heartbeat device in HBDEV stats

So if port7 is disconnected and heartbeat communication is lost, the cluster can enter a split-brain condition, where both units believe they are primary. The FortiOS administration guide confirms the same behavior: loss of heartbeat communication causes each member to think it is the primary

Why the other options are wrong:

C is wrong because configuration synchronization status is specifically used to detect whether secondary members remain synchronized with the primary. If members are no longer synchronized, the status changes from in-sync to out-of-sync

D is wrong because the study guide explains that during a configuration change, checksums may differ briefly while changes are copied, but it does not describe this as the secondary initiating a “synchronization reset”

So the verified answers are: A, B.

The FortiOS 7.6 Administrator Study Guide states: “The only security features you can apply using SSL certificate inspection mode are web filtering and application control.” Certificate inspection does not decrypt the encrypted payload. However, it can extract the destination hostname from the ClientHello’s server name indication (SNI). The exhibit exposes www.sharepoint.com in the server_name extension, enabling FortiGate to identify, categorize, and enforce web-filtering rules for the requested website. Therefore, option B is correct.

Antivirus inspection requires FortiGate to examine files or other application-layer content inside the encrypted payload. Because certificate inspection does not decrypt that content, an antivirus profile cannot be applied effectively; full SSL inspection is required. This eliminates option A.

The SAN field is not mandatory. FortiGate first attempts to obtain the hostname from SNI and can validate it against either the common name (CN) or SAN in the server certificate. Accordingly, option C is incorrect.

The supported_versions extension explicitly lists TLS 1.3 and TLS 1.2 and no other versions. Although the ClientHello’s legacy Version field displays TLS 1.2 (0x0303), TLS 1.3 clients retain this legacy value for compatibility. The extension identifies the versions the client actually supports, making option D correct.

The output explicitly states This router is an ABR. An OSPF area border router has interfaces participating in multiple OSPF areas and provides connectivity between those areas and the backbone. Therefore, A is correct.

The output also states that the RFC1583Compatibility flag is enabled. The Enterprise Firewall 7.6 Administrator Study Guide explains that FortiGate can use RFC 1583-compatible OSPF path selection for ECMP, where eligible external routes of equal cost can be installed concurrently. This makes D correct.

Nothing in the displayed status identifies the FortiGate as a backup designated router, so B cannot be concluded. Option C describes an autonomous system boundary router (ASBR), which originates external LSAs when redistributing routes into OSPF. Being an ABR does not by itself mean the router is injecting external routing information.

================

The Use Case 2 — BGP Configuration diagram explicitly shows these commands for inter-region BGP neighbors:

set attribute-unchanged next-hop

set ebgp-enforce-multihop enable

Technical Explanation:

The topology contains two independent BGP autonomous systems:

Region A operates within AS 65100.

Region B operates within AS 65200.

Within each region, iBGP exchanges routing information between the hub and its associated spokes. Between the two regions, eBGP propagates routes through the Hub2Hub connection.

Option B is correct: The command set attribute-unchanged next-hop preserves the BGP next-hop attribute when routes are advertised between the regional hubs.

Preserving next-hop information is important in the documented inter-region ADVPN design because it supports the intended routing and shortcut behavior across the overlays. The next-hop addresses must remain reachable through the configured routing infrastructure.

Option C is correct: The command set ebgp-enforce-multihop enable allows eBGP neighbor relationships to operate when the peers are not directly adjacent at the IP routing level.

In this topology, the hubs establish BGP peering using their inter-hub addresses. Enabling eBGP multihop supports the required connectivity when reaching those addresses involves intermediate routed hops.

Why the other options are incorrect:

Option A: set next-hop-self enable causes FortiGate to replace the advertised next hop with its own address. This contradicts the next-hop preservation requirement shown in the study guide ' s configuration for this topology.

Option D: set ebgp-enforce-multihop advpn is not the documented FortiOS configuration syntax. The valid value used here is enable.

Architectural Consideration:

For a multiregion ADVPN design, the architect must ensure that BGP next-hop resolution, inter-hub routing, and IPsec connectivity are consistent. Otherwise, BGP may establish successfully while data-plane forwarding or shortcut creation still fails.

The session output includes the flags:

state=redir local may_dirty ...

npu_state=00000000

offload=0/0

The 7.6 study guide explains these flags directly:

local = “Session is to/from local stack”

redir = “Session is being processed by an application layer proxy”

may_dirty = “Session is allowed by a firewall policy”

This makes C correct, because the local flag means the session either originates from FortiGate or terminates on FortiGate. The FortiOS administration guide states the same meaning: “Session is originated from or destined for local stack.”

This also makes A correct. The redir flag means the session is handled by an application-layer proxy. FortiOS documents explain that proxy-based inspection buffers traffic on the FortiGate and inspects it there, and that proxy-based processing is CPU and memory-intensive

Since the session also shows no NPU offload (npu_state=00000000, offload=0/0), this traffic is being handled in software/CPU, not by the NPU.

Why the other options are wrong:

B is wrong because the redir flag proves the session is not passing without inspection; it is being processed by an application-layer proxy

D is wrong because there is no authentication flag in this session. In Fortinet examples of captive portal/authentication-related sessions, the session state includes auth or authed flags. The study guide shows: “Any session for traffic coming from an authenticated user contains the authed flag.” This exhibit does not show auth or authed, so there is no basis to conclude the client was redirected to a captive portal for authentication.

The correct answer is A.

The debug flow shows:

traffic is going to TCP port 211

FortiGate logs run helper-ftp(dir=original)

The study guide explains exactly what that message means:

“In this example, the run helper-ftp message indicates that the FTP session helper is being used.”

Under normal proxy-based inspection, protocol handling is controlled by Protocol Options. The FortiOS administration guide states:

“Protocol port mapping only works with proxy-based inspection.” and “The ports can be modified to inspect any port with flowing traffic.”

So if the policy is configured for proxy-based inspection but the debug still shows the FTP session helper on port 211, the most likely explanation is that the FTP protocol mapping in Protocol Options is broad enough to match unexpectedly, such as being mapped to Any. That would cause FortiGate to identify the traffic as FTP and invoke the helper.

Why the other options are wrong:

B is wrong because SSL deep inspection is unrelated to this debug. The traffic shown is plain TCP/211, and the key message is about the FTP helper, not SSL decryption.

C is wrong because if FTP had not been mapped to port 211, FortiGate would be less likely to treat this traffic as FTP. The observed run helper-ftp indicates FTP handling is being triggered.

D is wrong because low-memory conserve behavior would typically cause inspection bypass or blocking behavior, not specifically the run helper-ftp message. The study guide’s helper example ties this message to session-helper use, not memory shortage.

So the verified answer is: A.

The correct answer is C.

The exhibit shows the neighbor state as Connect in the State/PfxRcd column. The study guide explains the BGP states exactly as follows:

“Connect: Waiting for a successful three-way TCP connection”

“OpenSent: Waiting for an OPEN message from the peer”

“Established: Peers have successfully exchanged OPEN and keepalive messages”

Because the router is still in Connect state, the TCP three-way handshake has not completed yet. In practical terms, the local router has sent the TCP SYN but has not successfully received the SYN/ACK needed to complete the handshake. That is why C is correct.

Why the other options are wrong:

A is wrong because the message counters alone do not prove that the neighbor is unreachable. The study guide says the State/PfxRcd field shows the BGP state when the session is not established, and here that state is specifically Connect

B is wrong because waiting for an OPEN message happens in OpenSent, not Connect

D is not the best answer for this output. The study guide ties the displayed state directly to the protocol phase: Connect means the device is still waiting for a successful TCP handshake

So the verified answer is: C.