NSE7_FSN_AR-7.6 Exam Dumps - Fortinet NSE 7 Network Security Architect Questions and Answers

The correct answers are A, D, and E. This is a feasible path RPF check scenario. In FortiGate’s default RPF behavior, FortiGate checks whether the routing table contains a valid return route to the source IP address through the same interface on which the packet arrived. The study guide’s RPF feasible path example states that FortiGate “checks the routing table for a route that matches the source address and incoming interface of the first original packet.” It then gives the exact result: User A passes because “there is a default route through wan1,” so packets received on wan1 pass the RPF check regardless of source address. User B fails because FortiGate does not have a route to 95.56.234.24 through wan2. User C fails because FortiGate does not have a route to 10.0.4.63 through port1. Therefore, option B is wrong because FortiGate is not allowing asymmetric return routing here. Option C is wrong because the default route points out wan1, not port1, so it cannot validate User C’s packet arriving on port1.

The study guide states:

“The kernel memory slabs are collections of objects with a common purpose. The kernel uses them to store information in memory.”

It also gives the exact calculation rule:

“Total slab size = available objects x object size”

From the exhibit:

tcp_session 3 5 1500 ...

So:

available objects = 5

object size = 1500

Therefore:

Total slab size = 5 × 1500 = 7500 kB

That makes D correct, and it is associated with the kernel, not user space.

Why the other options are wrong:

A is wrong because sctp_session 0 0 1600 ... gives 0 × 1600 = 0, but slabs are associated with the kernel, not user space.

B is wrong because ip_session 1 3 1200 ... gives 3 × 1200 = 3600, but again slabs are kernel memory, not user space.

C is wrong because ip6_session 0 0 1300 ... gives 0 × 1300 = 0, not 1300.

The session output reveals a session with proto=1 (ICMP) and the origin and reply directions show address and NAT translations. Specifically, the hook=post dir=org act=snat shows that source NAT is performed for outgoing packets, where the source 10.1.10.10:40602 is translated to 10.200.5.1:8 (likely ICMP id 8, not a TCP/UDP port). The reply direction, hook=pre dir=reply act=dnat, indicates destination NAT for incoming packets: packets incoming for 10.200.5.1:60430 are destination-NATed to 10.1.10.10:40602. The gateway (gwy) is listed as 10.200.1.254/10.1.0.1, which for outgoing traffic means that return traffic is directed to the gateway (10.200.1.254), per the NAT policy. This is confirmed by the FortiOS Session Table Guide, which explains that the returned ICMP reply will be routed out to this NAT gateway. The session statistics and logical flow (SNAT out, matching DNAT in) reinforce that reply traffic to the initiator traverses via 10.200.1.254.

According to the official Fortinet documentation (Technical Tip: Useful FSSO Commands), heartbeat messages play a crucial role in communication between the FSSO Collector Agent and FortiGate. These messages are regularly sent from the Collector Agent to verify its status, maintain session awareness, and confirm connectivity between the authentication infrastructure and FortiGate appliances.

Option B is confirmed by Fortinet, as the collector agent logs on Windows or its management console will specifically note heartbeat events, connection status, and any issues maintaining contact with FortiGate units.

Option C is validated by both official CLI documentation and the technical tip linked. On FortiGate, heartbeat messages from the collector agent are visible using real-time debug tools such as diagnose debug application authd or FSSO-specific commands. These enable administrators to monitor live logon states, session status, and connection health directly from the FortiGate CLI. The debug stream shows heartbeats received and their effect on active logons, associating health monitoring with active sessions.

Heartbeat operation is fully automated once FSSO is set up—there is no requirement for manual enablement or configuration, aligning with Fortinet’s philosophy of seamless integration and centralized management across the Security Fabric. This ensures that both FortiGate and the collector agent can quickly and reliably detect any miscommunication or outage, addressing authentication issues proactively.

The correct answers are C and D.

The key clue is the command itself:

diagnose debug application fssod -1

The study guide explicitly states: “There is a specific FortiGate daemon that handles the polling mode. It is the fssod daemon. To enable agentless polling mode real-time debug use the command: diagnose debug application fssod -1.”

That directly proves D. FSSO is using agentless polling mode to detect logon events.

The study guide also states: “In agentless polling mode, FortiGate frequently polls all workstations (as a standalone collector agent does) to check which users are still logged in. You can sniffer this traffic on port 445.”

That directly proves C. FortiGate is frequently polling the workstation in case the user has logged out.

Why the other options are wrong:

A is wrong because the “cannot verify if the user is still logged in” / Not Verified condition is described for the collector agent workstation status, not as a conclusion from this FortiGate fssod debug line. The study guide says: “A user goes to not verified status when they log out, or when there is a problem in the polling done by the collector agent to the workstation.”

B is wrong because DC Agent mode is part of agent-based FSSO, where DC agents send events to a collector agent. This output is from the fssod daemon, which the study guide ties to agentless polling mode, not DC Agent mode.

E is wrong because TCP port 8000 is used for communication between the collector agent and FortiGate, while in agentless polling mode FortiGate polls workstations and that traffic can be sniffed on TCP port 445.

So the verified answers are: C, D.

FortiOS Admin Guide: Static Routing, SNAT Route Change Feature

To capture encrypted IPsec phase 2 (ESP) traffic between two FortiGate devices, the correct protocol filter to use is ip proto 50. According to the Fortinet official sniffing and debugging documentation, ESP (Encapsulating Security Payload) is used for encrypted phase 2 payload transfer and always uses IP protocol number 50. Running the command diagnose sniffer packet any ' ip proto 50 '  captures only ESP packets, which represent the encrypted traffic—whether originating or transiting the device.

If there is no NAT device between FortiGates, ESP is not encapsulated in UDP (thus not on UDP port 4500; if NAT-T were required, packets would be UDP-encapsulated, but the scenario explicitly says NAT is not in use). UDP port 500 is for IKE control (negotiation) traffic, and AH (Authentication Header, ip proto 51) is not used for encryption in standard IPsec phase 2 with ESP.

This matches the official CLI reference from Fortinet for VPN and traffic analysis.

**

The best verified answer is C.

The study guide says that when FortiGate is in conserve mode, it activates protection measures to recover memory space:

“System configuration cannot be changed”

“FortiGate skips quarantine actions (including FortiSandbox analysis)”

It also explains that inspection behavior can be reduced while in conserve mode:

“pass (default): All new sessions pass without inspection until FortiGate switches back to non-conserve mode.”

“The av-failopen setting also applies to flow-based antivirus inspection.”

The FortiOS administration guide summarizes this behavior as:

“This causes functions such as antivirus scanning to change how they operate to reduce the functionality and conserve memory without compromising security.”

That is why C is the closest correct choice: FortiGate can reduce functionality of some processes, especially antivirus-related inspection, to preserve memory.

Why the other options are wrong:

A is wrong because FortiGate does not automatically reboot as a default conserve-mode action. A reboot can be configured through an automation stitch, but that is an optional administrator-defined response, not the built-in conserve-mode behavior

B is wrong because the documentation does not say FortiGate switches from proxy-based inspection to flow-based inspection. Instead, it may pass traffic without inspection depending on av-failopen settings

D is not generally correct for conserve mode. The study guide says FortiGate starts dropping new sessions only when memory usage exceeds the extreme threshold: “If memory usage exceeds the extreme threshold, all new sessions that require inspection (flow-based or proxy-based) are blocked.”

So the verified answer is: C.

The SD-WAN 7.6 Enterprise Administrator Study Guide explicitly states: “Firewall policies for SD-WAN traffic must reference SD-WAN zones and not individual members.”

In the exhibit, HUB1-VPN1 is an individual member of the HUB1 SD-WAN zone. However, policy 3 incorrectly uses HUB1-VPN1 as its outgoing interface. FortiManager cannot compile and commit that policy because an SD-WAN member cannot be referenced directly by an SD-WAN firewall policy. The administrator must change the policy’s To interface from HUB1-VPN1 to its parent zone, HUB1.

Option C is incorrect because the guide specifically explains that an IPsec interface does not require normalization when it is used as an SD-WAN member: “SD-WAN members don’t use normalized interfaces.” The normalized LAN interface shown in the policy is appropriate because it maps the local interface for each managed FortiGate, but the overlay side must reference the HUB1 zone.

Option D remains invalid because it still references individual SD-WAN members. Option A does not correct the invalid outgoing-interface reference; policy 3 already uses the policy package installation targets.