NSE7_FSN_AR-7.6 Questions and Answers

The administrator is running a packet sniffer with the filter ' udp port 500 or udp port 4500 or esp ' . The result is " no output, " even though the VPN is attempting to establish (failing).

A. The VPN is configured to use IKE over TCP:

Standard IPsec IKE negotiation uses UDP port 500 (IKE) and UDP port 4500 (NAT-T).

However, if IKEv2 over TCP (RFC 8229) or Fortinet ' s proprietary IKE over TCP is configured (often used to bypass firewalls that block UDP), the traffic will use TCP (often port 4500 or 443).

The sniffer filter explicitly looks for udp or esp (IP Protocol 50).

If the traffic is encapsulated in TCP, it matches tcp protocol, not udp or esp (raw ESP). Therefore, the sniffer sees zero packets matching the filter.

Why other options are incorrect:

B: esp is a valid argument for diagnose sniffer packet. It is equivalent to filtering for IP protocol 50.

C: If the ISP were blocking traffic, the sniffer (running on the local FortiGate) would still see the outbound packets generated by the FortiGate trying to initiate the connection. " No output " implies the local device isn ' t even generating packets matching that filter.

D: Mismatched IKE versions would still generate IKE negotiation packets (proposals/errors) that would be captured by the sniffer.

FortiOS supports both route types described in the question. The FortiOS 7.6 Administrator Study Guide states that a static route can reference one or more SD-WAN zones and that FortiOS consequently installs an individual route for every member of the selected zone. It also states: “Alternatively, you can configure per-member static routes for more granular control over traffic.” Therefore, options A and B are incorrect. Fortinet’s official configuration guidance likewise shows static routes referencing an SD-WAN zone.

The relevant duplicate-route restriction is based on the destination prefix. Fortinet courseware explains: “FortiOS doesn’t allow you to configure a static route for the same destination that references an interface.” Accordingly, a route referencing an SD-WAN zone and another route referencing one of that zone’s members cannot use identical destination subnets. They can use different or overlapping destination prefixes—for example, a less-specific route through the zone and a more-specific route through the individual member. The source subnets are not the required differentiator, eliminating option D.

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

To establish a functional Security Fabric, specific network and configuration prerequisites must be met to ensure nodes can communicate, authorize, and share telemetry data:

A. You must ensure that TCP port 8013 is not blocked along the way:

TCP port 8013 is the dedicated port for FortiTelemetry (Fabric) communication. If firewalls (intermediate or local) block this port, the Fabric connection between the root and downstream FortiGates will fail.

D. You must authorize the downstream FortiGate on the root FortiGate:

Security Fabric relies on a trust relationship. When a downstream device attempts to join, it appears in the Root FortiGate ' s dashboard. The administrator must manually authorize this device (unless pre-authorized via serial number) to allow it to join the Fabric topology.

E. You must enable FortiTelemetry on the receiving interface of the upstream FortiGate:

The interface on the Root (upstream) FortiGate that faces the downstream devices must have the " Security Fabric Connection " (formerly CAPWAP/FortiTelemetry) administrative access setting enabled. Without this, the interface will not listen for or accept Fabric connection requests.

Why other options are incorrect:

B: Neighbor Discovery uses standard multicast/broadcast or static settings; changing the port is not a standard requirement.

C: FortiGates can participate in the Security Fabric in either NAT or Transparent mode; Transparent mode is not a mandatory requirement for the Fabric itself.

We must analyze the flags (*, > , S, O, B) and Administrative Distances (AD) shown in the get router info routing-table database exhibit to determine the correct statements.

Analysis for Option A (The BGP route to 10.0.4.0/24 is not in the forwarding information base):

True. Look at the entry for 10.0.4.0/24.

There is an OSPF route: O * > 10.0.4.0/24 [110/2]. The * indicates it is in the FIB, and > indicates it is the selected route.

There is a BGP route: B 10.0.4.0/24 [200/10]. This line lacks the * flag.

Reason: The OSPF route has an Administrative Distance of 110. The BGP route (iBGP) has an AD of 200. Since 110 is lower than 200, OSPF wins, and the BGP route is not installed in the Forwarding Information Base (FIB).

Analysis for Option B (The default static route through 10.200.1.254 is in the forwarding information base):

True. Look at the 0.0.0.0/0 entries.

The first entry is S * > 0.0.0.0/0 [10/0] via 10.200.1.254.

The * flag confirms this specific route is installed in the FIB.

The second static route (via 10.200.2.254) has a higher distance ([20/0]) and no * flag, so it is inactive.

Why C is False: ECMP (Equal Cost Multi-Path) requires routes to have the same cost/priority. Here, one static route has AD 10 and the other has AD 20. They are not equal, so ECMP is not performed.

Why D is False: The routing table database shows active routes, not the raw Link State Advertisement (LSA) database. You cannot determine the number of LSAs received solely from this output.

The issue is caused by the strict matching logic of the configured Prefix List.

Current State: The rule is edit 1 with set prefix 172.16.0.0 255.255.0.0 and both ge (greater than or equal) and le (less than or equal) are unset.

Behavior: When ge and le are unset, FortiOS requires an exact match of the subnet mask. The current rule only matches the exact network 172.16.0.0/16. It denies 172.16.52.0/24 because the mask (/24) does not match the rule ' s mask (/16).

To fix this and inject 172.16.52.0/24, you must modify the list to match the /24 mask:

A. Add another entry to the prefix list to specifically allow the 172.16.52.0/24 network:

Creating a new rule (e.g., edit 2) with set prefix 172.16.52.0 255.255.255.0 will provide an exact match for the incoming route, allowing it to pass the distribute-list.

B. Change the ge value to 17:

By configuring set ge 17 on the existing rule (conceptually 172.16.0.0/16 ge 17), you change the logic from " exact match " to " range match " .

This configuration tells the router to match any prefix starting with 172.16.x.x that has a subnet mask length of 17 or greater.

Since the incoming route is a /24, and 24 is greater than 17, the route will match the prefix list and be accepted.

Why other options are incorrect:

C: The option text appears to read " Change the ... value to 16 " . If this refers to le 16, it would enforce the mask to be exactly /16 or less, which still excludes /24.

D: Changing the default behavior to implicit allow defeats the purpose of a filter (security control) and is not a standard configuration step for fixing a single missing route.

Setting unsupported-ssl-version to block prevents HTTPS connections from continuing when the negotiated SSL/TLS version falls below the version permitted by the inspection profile. The Enterprise Firewall 7.6 Administrator Study Guide demonstrates this hardening control together with an appropriate minimum version and explains that it can block obsolete TLS versions while accepting newer, secure versions. Therefore, option A is correct.

Enabling Server certificate SNI check protects against hostname inconsistencies between the client-supplied SNI and the server certificate. The FortiOS guide explains that, when enabled, FortiGate uses the certificate’s CN when the SNI hostname does not match any CN or SAN entry. This reduces the risk of SNI-based filtering evasion or domain-fronting behavior, making option B correct.

Setting untrusted certificates to Ignore weakens security. FortiGate proceeds with the SSL session regardless of whether the server certificate is trusted. Option C is therefore incorrect.

SSL 3.0 is obsolete and vulnerable, including exposure to POODLE-style attacks. Setting it as the minimum permitted version does not constitute secure hardening. A hardened profile should normally require TLS 1.2 or later, so option D is incorrect.

Fortinet distinguishes measured link-quality metrics from SLA targets. Best performance, called Best Quality in current FortiOS terminology, compares member performance using a selected quality criterion; it does not use an SLA target as the eligibility mechanism. Thus, A is correct.

SLA-target eligibility belongs to the Lowest Cost (SLA) strategy, including Lowest Cost with load balancing, making D correct. When an SD-WAN rule references a particular performance SLA, it selects one SLA target ID from that performance SLA, so E is also correct. Additional performance SLAs can be referenced separately, but multiple target IDs from the same SLA are not selected simultaneously in that rule reference.

Option B confuses measurement with eligibility. Performance SLA processes measure member metrics independently; configuring an SLA target supplies thresholds against which those measurements are evaluated. Consequently, B and C are incorrect.

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

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.

TCP Maximum Segment Size (MSS) defines the maximum amount of TCP payload data that a device can place in one TCP segment. The Enterprise Firewall 7.6 Administrator Study Guide explicitly explains that MSS includes only the TCP payload and does not include the TCP or IP headers. FortiGate allows the sender and receiver MSS values to be adjusted in a firewall policy using tcp-mss-sender and tcp-mss-receiver. Therefore, A is correct.

These settings are intended primarily to avoid fragmentation and accommodate reduced effective MTUs, particularly where encapsulation such as IPsec adds overhead. MSS does not determine whether a firewall policy permits or denies a TCP packet, eliminating B. It also does not alter the IP-header size, eliminating D. Option C incorrectly describes when MSS adjustment operates.

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

The correct answers are A and B.

For UDP, the study guide states this directly: “For UDP, the session state can have only two values: 00 when traffic is only one way, and 01 when traffic is two ways. For ICMP, the protocol state is always 00.”

That makes B correct and D incorrect.

For TCP, the study guide explains that the protocol state is a two-digit number, where the first digit is the server-side state and the second digit is the client-side state. It also states that the first digit is 0 when the session is not subject to any inspection, and the TCP state table shows that value 1 = ESTABLISHED

So, for a normal non-proxied/non-inspected TCP session, proto_state=01 means the TCP session is in the ESTABLISHED state. An established TCP session means the three-way handshake has completed, which requires traffic in both directions. That is why A is correct.

The study guide also says: “proto_state=11 means that the TCP three-way handshake for both server-side and client-side is completed (ESTABLISHED).”

This confirms that TCP state value 1 represents an established state.

Why C is not selected: the study guide defines value 5 as TIME_WAIT and says: “When a session is closed by both the sender and receiver, FortiGate keeps that session in the session table for a few seconds… This is the state value 5.”

So proto_state=05 represents a closing/closed TCP session in TIME_WAIT, not the normal bidirectional state the question is testing.

Therefore, the verified answers are A and B.

The correct answers are C, D, and E.

The study guide lists the exact OSPF adjacency requirements:

“Interfaces of peers are the same type and in the same OSPF area”

“Each peer has a unique router ID”

“OSPF authentication, if enabled, is successful”

These map directly to:

C. OSPF interface network types match

D. Authentication settings match

E. OSPF router IDs are unique

The same study-guide slide also states other requirements such as:

peers’ primary IPs must be in the same subnet with the same mask

hello and dead intervals must match

OSPF MTUs must match

Why the other options are wrong:

A is wrong because link cost matching is not listed as an adjacency requirement. OSPF cost affects path selection, not whether adjacency can form.

B is wrong because interface priority does not need to be unique. Priority is used for DR/BDR election, where the highest priority wins, and ties are broken by router ID.

So the verified answers are: C, D, E.

The correct answer is D. IKE_AUTH.

The study guide explicitly states:

“IKE_Auth exchange:

• Performs the mutual authentication of two IKE endpoints.

• Configures settings like IP/mask, DNS, and so on.

• Sets up the piggyback of a child SA. Negotiates IP flow and security settings for the IPsec SA.”

It also says:

“By default, a piggyback child (IPsec) SA is negotiated along with the IKEv2 SA during IKE_AUTH. If additional IPsec SAs are needed … they are negotiated during subsequent CREATE_CHILD_SA exchanges.”

Why the other options are wrong:

A. IKE_SA_INIT is incorrect because this exchange negotiates the security settings to protect the IKE traffic, not the first CHILD_SA.

B. INFORMATIONAL is incorrect because it is used to convey control messages between IKE endpoints.

C. CREATE_CHILD_SA is incorrect for the first CHILD_SA, because it is used to create new additional child SAs or rekey existing ones after the initial exchange.

" The result is that the gateway address will not be updated, unless the existing gateway is no longer valid "

The study guide identifies preserve-session-route as the configuration responsible for this behavior.

Technical Explanation:

The exhibit shows two WAN interfaces, port1 and port2, with static default routes.

Originally, both interfaces participate in routing with equal priority. The administrator changes the priority of port2 to 20, making port1 the preferred interface for new route selections.

However, the existing sessions were established using port2, and its interface configuration includes:

config system interface

edit " port2 "

set preserve-session-route enable

next

end

Option A is correct: The preserve-session-route setting enables interface stickiness for sessions using port2.

Because the original gateway and route remain valid, FortiGate preserves the existing sessions ' routing information and continues forwarding them through port2.

Option B is correct: Increasing the priority value on port2 makes it less preferred than port1. Consequently, new sessions that use the relevant default route are directed through port1.

Why the other options are incorrect:

Option C: FortiGate does not automatically update existing SNAT session gateway information merely because a more preferred path becomes available. The guide identifies snat-route-change as a separate setting used to permit appropriate SNAT route updates.

Option D: A route change can cause affected sessions to be marked dirty and reevaluated, but it is not accurate to conclude that every session is necessarily marked dirty or that dirty status overrides interface stickiness.

Option E: SNAT session dirty-state handling does not depend exclusively on using an IP pool. Interface-based SNAT sessions can also be affected by routing changes.

Architectural Consideration:

This distinction is important for SD-WAN failback design. Preserving established sessions can help maintain connection continuity, but it can also prevent traffic from returning to a preferred WAN interface until the session ends or the preserved route becomes invalid.

FortiGate HA Troubleshooting and Synchronization Guides

Fortinet Admin Guide: HA Primary Role Retention, Cluster Break-up Due to Out-of-Sync Status

The correct answers are A and B.

The Network Security Support Engineer 7.6 Study Guide states under OSPF Troubleshooting:

“Follow these steps to troubleshoot an OSPF problem between two peers:

Check that the local router can reach the remote peer. IP addresses must be in the same subnet and have the same subnet mask.

Ensure that IP protocol 89 is not blocked.

Hello and dead intervals must match.

The OSPF router ID for each peer must be unique. Duplicate router IDs are not allowed.

Do the MTUs match?

If authentication is enabled, the type and password must match on both sides.”**

The same page also summarizes the troubleshooting tips as:

“Do peers have an IP address within the same subnet?”

“Is IP protocol 89 blocked?”

This directly confirms:

A is correct

B is correct

Why the other options are wrong:

C is wrong because TCP port 179 is used by BGP, not OSPF. OSPF uses IP protocol 89, as the study guide explicitly notes

D is wrong because the study guide’s OSPF adjacency troubleshooting checklist does not require an active static route to the peer. OSPF neighbors form adjacency on directly reachable networks, and the guide instead focuses on same subnet, protocol 89, intervals, router ID, MTU, and authentication matching

So the verified answers are: A, B.

Comprehensive and Detailed 100 to 150 words of Explanation From Secure Networking Architect Study Guides topics:

The MAC prefix 00:09:0f:09 identifies FortiGate ' s logic-2 HA virtual-MAC construction. The Enterprise Firewall 7.6 guide states that logic 2 applies when the virtual-cluster ID is 0 or 1, the HA group ID is below 256, and the physical-interface index is below 128.

In 00:09:0f:09:18:81, hexadecimal 18 represents HA group ID 24, confirming that the group ID is below 255 and making D correct. The high bit in the final octet indicates virtual-cluster ID 1; this means virtual clustering/VDOM functionality is involved, making C correct. The remaining physical-index bits identify index 1, not 2, eliminating A. This virtual-MAC construction belongs to FortiGate Clustering Protocol HA operation and does not establish that the device uses standalone FGSP session synchronization, eliminating B.

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

Comprehensive and Detailed 100 to 150 words of Explanation From Secure Networking Architect Study Guides topics:

Application-based SD-WAN steering depends on FortiGate being able to associate the new session with an already identified application. The SD-WAN 7.6 guide explains that the ISDB application cache contains an application ID, ISDB application ID, and 3-tuple, and FortiGate uses these values when matching an SD-WAN rule. If the new session ' s 3-tuple is absent from the cache, FortiGate cannot initially identify it as GoToMeeting for rule 1, so normal processing can select the implicit rule.

Application identification can occur only after traffic has already entered the session. That identification does not retroactively change the initial routing decision for packets already associated with the session. GoToMeeting belongs to the Collaboration criteria shown for rule 1, so A is false. Full SSL inspection is not intrinsically required for this SD-WAN application-cache mechanism, eliminating D.

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

Comprehensive and Detailed 100 to 150 words of Explanation From Secure Networking Architect Study Guides topics:

FortiManager creates configuration revisions following several events, including installations, explicit configuration retrievals, automatic updates, and scripts executed directly on managed FortiGate devices. The FortiManager 7.6 Administrator Study Guide specifically explains that scripts run using Remote FortiGate Directly (via CLI) can cause an automatic update and create a new revision-history entry.

This accounts for the script_manager process and subsequent retrieve activity visible in the exhibit. script_manager represents FortiManager ' s script-processing mechanism; it is not an FDN API administrator, eliminating D. The Configuration and Installation widget belongs to FortiManager ' s device-management interface rather than being something the administrator must inspect directly on FortiGate, eliminating B. The revision history itself identifies which administrator or process generated a revision, so the proposed system-log filtering in C is unnecessary and incorrectly specified.

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

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.

" By default, the prefix is advertised only when it matches the destination subnet of an active route in the routing table "

Technical Explanation:

The exhibit shows that FortiGate_B has the network 172.16.1.248/30 installed as a directly connected route.

The administrator wants to advertise this specific network to FortiGate_A through BGP without unintentionally advertising other connected networks.

Option D is correct because the BGP network command allows an administrator to originate a specific prefix into BGP.

An appropriate configuration on FortiGate_B is:

config router bgp

config network

edit 1

set prefix 172.16.1.248 255.255.255.252

next

end

end

By default, FortiOS checks whether the configured prefix exactly matches an active route in the routing table before originating the advertisement.

Because 172.16.1.248/30 is directly connected to FortiGate_B, this condition is satisfied.

FortiGate_B can therefore originate that prefix, allowing FortiGate_A to learn it through the established BGP session.

Why the other options are incorrect:

Option A: An inbound route map on FortiGate_A can filter or modify routes already advertised by its neighbor, but cannot cause FortiGate_B to originate the missing prefix.

Option B: Redistribute Connected can introduce multiple connected routes into BGP. Without suitable filtering, this would advertise more networks than the administrator intends.

Option C: An outbound route map can filter advertisements, but does not independently originate a connected prefix that has not been redistributed or declared using the BGP network command.

Architectural Consideration:

When a requirement specifies that only one prefix must be advertised, the BGP network statement offers precise control. Route maps can provide additional policy enforcement, but they do not replace the mechanism required to originate the prefix.

The SD-WAN 7.6 Enterprise Administrator Study Guide explicitly defines the relationship between underlays and overlays:

“Overlays are virtual links built on top of physical links—called underlay links.”

It further explains that the overlay topology consists of VPN tunnels and “adds flexible routing options.” Therefore, option B is directly supported.

Option D is also correct. An overlay is not restricted to a particular physical transport. Fortinet identifies ISP, MPLS, and 4G/5G cellular connectivity as possible WAN transports. Consequently, a wireless WAN connection can provide the underlying transport over which an IPsec, GRE, or IP-in-IP overlay tunnel is established.

Option C is incorrect because underlay connectivity is not limited to wired links; cellular 4G/5G is a valid WAN transport.

Option A is incorrect because FortiLink is primarily the proprietary connectivity used between FortiGate and managed LAN extensions such as FortiSwitch and FortiAP. It is not inherently an SD-WAN WAN underlay.

Option E is incorrect because Fortinet identifies VPN tunnels—principally IPsec, but also GRE and IP-in-IP—as SD-WAN overlay links. A VLAN is a Layer 2 logical segmentation mechanism, not an SD-WAN overlay tunnel.

FortiGate permits an SD-WAN zone to contain a single member. Therefore, removing one member from a zone that originally contains two members does not violate the minimum membership requirement. The important dependency check is whether the member is still referenced by SD-WAN rules, performance SLAs, health checks, or other configuration objects.

The question explicitly states that the member is no longer used by health checks or SD-WAN rules, so FortiGate can remove it without requiring another operation. FortiGate does not automatically transfer a deleted member into the default SD-WAN zone. Likewise, removing an SD-WAN member does not mean that unrelated configured static-route objects must automatically be deleted. Option B incorrectly assumes that every user-defined zone requires two members. Therefore, FortiGate accepts the deletion with no further action.

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

The correct answer is B. Assertion dump.

The study guide states: “SAML attributes are pieces of information about a user that are exchanged between IdPs and SPs during the SAML authentication process. These attributes are included in the SAML assertion, which is built by the IdP as part of the authentication process.”

The same study guide page for real-time SAML troubleshooting shows the section labeled **** Assertion Dump ****, and inside that assertion it displays the actual user attributes, such as:

< saml:Attribute Name= " username " >

< saml:Attribute Name= " groups " >

It also explicitly marks this part as “Attributes sent by IdP”

Why the other options are wrong:

A. Bindings HTTP post is incorrect because bindings define how SAML messages are transported, not the section that contains the attributes. The study guide says: “Bindings: Define how SAML protocol messages are transmitted over different communication channels.”

C. Authentication request is incorrect because that is built by the SP and sent toward the IdP, not where the IdP’s user attributes are shown. The study guide’s flow says the SP “Builds auth request” and the IdP later “Builds auth response.”

D. Authentication response is broader than the exact section being asked. The exact section in the study guide where the IdP-provided attributes are shown is the Assertion dump.

So the verified answer is: B.

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 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 exhibit shows a FortiGate configuration under config system fortiguard related to web filtering and FortiGuard options. There is a line:

set webfilter-force-off enable

According to official Fortinet documentation, the " webfilter-force-off " option, when enabled, causes the FortiGate to bypass web filtering for all traffic—even if a web filter profile is applied to a policy. This override is typically used for troubleshooting or performance reasons and is documented as an explicit bypass feature.

If an administrator wants to enforce web filtering inspection, this setting must be disabled. The correct way to restore web filtering functionality is to run:

set webfilter-force-off disable

Once done, traffic passing through policies with web filter profiles will be inspected and filtered as per configuration. Other settings such as timeout or cache TTL do not bypass web filtering; they only affect operational nuances.

FortiTelemetry is a critical part of Security Fabric communications and requires explicit configuration for each participating FortiGate interface. The administrative access setting " fabric " (corresponding to FortiTelemetry) must be manually enabled per interface on both upstream and downstream devices. This is performed in the GUI under Administrative Access or via the CLI using the command set allowaccess fabric for the relevant network interface. Without this step, FortiTelemetry communications will not occur on that interface.

Additionally, the default communication between downstream and upstream FortiGate units in the Security Fabric is over TCP port 8013. This port is well-documented as the standard for Security Fabric and FortiTelemetry connections, and must be open and permitted across the network path for connectivity and status enforcement between units. The downstream FortiGate initiates the connection to the upstream via this port unless otherwise configured. This has also been documented as a PCI-relevant port, showing its default usage.

Other options:

Neighbor Discovery in FortiOS uses IPv6 ND protocol, not TCP.

FortiTelemetry port (8013) can be modified, but the interface Administrative Access for the Security Fabric must be manually enabled; Neighbor Discovery port modification is not documented as a supported change for FortiGate.

The correct answers are B and D.

The study guide explains that expectation sessions are pinhole sessions created by session helpers for protocols such as FTP that need additional negotiated connections. It states: “FortiGate created an expectation session and opened the pinhole port for the expected return traffic” and also shows that the firewall “creates an expected (pinhole) session to allow the traffic”

That makes D correct.

For B, the study guide explains the gwy= field in session output: the first value is the gateway to the destination, and the second is the gateway to the source

In the exhibit, the original-direction traffic is DNATed here:

hook=pre dir=org act=dnat 10.171.121.38:0- > 10.200.1.1:60426(10.0.1.10:50365)

So the destination after DNAT is the internal host 10.0.1.10, and the session’s first gwy value corresponds to the next hop toward that destination. That makes B correct.

Why the other options are wrong:

A is wrong because this is an expectation/session-helper behavior, not an IPS-engine-created session. The study guide ties expectation sessions to helpers such as FTP, not IPS.

C is wrong because 10.200.1.1 is the translated address used before DNAT, not the next hop used to forward the original-direction traffic after translation to the internal destination.

So the verified answers are: B, D.

The correct answers are C and D.

For D, the session output shows proto=6, which means TCP, and proto_state=01. The study guide explains that for TCP sessions, “the first number (from left to right) is related to the server-side state and is 0 when the session is not subject to any inspection (flow or proxy). … The second digit is the client-side state.” It also shows that value 1 = ESTABLISHED

So proto_state=01 means:

first digit 0 = no inspection

second digit 1 = ESTABLISHED

That confirms the TCP session has been successfully established.

For C, the study guide section “Session for an Authenticated User” states: “Any session for traffic coming from an authenticated user contains the authed flag. Additionally, the username is added to the session information.”

In the exhibit, the session contains user=User1 and an authentication state flag (authd), which indicates the session is associated with an authenticated user.

Why the other options are wrong:

A is wrong because the session did match a firewall policy. The study guide says the session output includes “The ID of the matching policy” In the exhibit, the session shows policy_id=1, so a firewall policy was matched.

B is wrong because the study guide explains the gwy field as:

first value = gateway to destination

second value = gateway to source The exhibit shows gwy=10.1.0.254/10.1.10.1, so:

gateway to destination = 10.1.0.254

gateway to source = 10.1.10.1

So the verified answers are: C, D.

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 reported symptom—users unable to access any websites despite no explicit blocks in the profile—points to systemic connectivity or configuration issues rather than specific URL filtering rules.

Option B (SSL/TLS Inspection): When Deep Inspection is enabled, the FortiGate acts as a Man-in-the-Middle (MitM) and re-signs server certificates using its own CA. If the clients (browsers) do not trust this CA (i.e., the certificate is not installed in their Trusted Root store), they will reject the connection with certificate errors, effectively preventing access to all HTTPS websites.

Option D (DNS): Web browsing relies on DNS resolution. If the configured DNS server is unreachable or failing, the FortiGate (or the client) cannot resolve FQDNs to IP addresses. Consequently, browsers will fail to load any page, resulting in a total loss of web access.

Option E (License): If the FortiGuard Web Filtering license expires, the FortiGate can no longer query the FortiGuard Distribution Network (FDN) for ratings. By default, or if the allow-when-rating-error setting is disabled (a common security practice), the FortiGate will block all web traffic that it cannot rate, often displaying a " Web Filter Service Error " or invalid license page.

Option A is incorrect because clearing the cache only increases latency, it does not block traffic. Option C is incorrect because webfilter-force-off is typically used to disable the service (often allowing traffic to bypass checks if the service is down), rather than blocking it.

Comprehensive and Detailed 100 to 150 words of Explanation From Secure Networking Architect Study Guides topics:

Fortinet documents three values for the phase 2 route-overlap setting: use-new, use-old, and allow. The required value for simultaneous VPNs advertising overlapping remote subnets is allow.

With route-overlap allow, FortiGate keeps the existing dial-up VPN active and also accepts the newly connected VPN. The Enterprise Firewall 7.6 Administrator Study Guide explicitly states that traffic from the central FortiGate is then load-balanced using equal-cost multipath across both VPNs. This directly satisfies the scenario and makes C correct.

The default use-new setting disconnects the existing VPN and accepts the new one, while use-old keeps the existing VPN and rejects the new connection. Neither produces ECMP. multipath enable and net-device ecmp are not the phase 2 commands FortiOS uses to permit overlapping dial-up VPN routes.

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

Based on the Fortinet FCSS - Network Security 7.6 documents and the analysis of the VPN tunnel exhibit, here is the verified answer.

Questions no: 91

Verified Answer: A, C

Comprehensive and Detailed Explanation with all FCSS - Network Security 7.6 documents:

To determine the status of the VPN tunnel, we must examine the specific counters and fields in the diagnose vpn tunnel list output provided in the exhibit.

Analyze Phase 2 Status (Option A):

The output displays child_num=0.

In IKEv2 (and IKEv1 implementations in FortiOS), " Child SAs " refer to the Phase 2 (IPsec) Security Associations that carry the actual data traffic.

A value of 0 indicates that no Phase 2 tunnels are established. If Phase 2 were up, child_num would be at least 1.

Additionally, under the proxyid section, the field sa=0 confirms there is no active Security Association for that traffic selector.

Analyze Traffic Status (Option C):

The stat line shows: rxp=0 txp=0 rxb=0 txb=0.

rxp (Received Packets) and txp (Transmitted Packets) are both zero. This definitively confirms that no traffic is traversing the tunnel currently. This is expected since Phase 2 is down.

Analyze Phase 1 Status (Why B is incorrect):

The tunnel entry exists in the list with a valid tun_id, and NAT-Traversal is active (natt: mode=keepalive).

The presence of the tunnel in this command output, along with active Keepalive mechanisms, typically indicates that Phase 1 (IKE SA) is established and the peers are communicating on port 4500 (NAT-T), even though the data tunnels (Phase 2) failed to negotiate. If Phase 1 were down, the tunnel would often not appear in this " list " view or would show different status flags indicating a complete connection failure.

Conclusion: The exhibit shows a scenario where the Phase 1 control channel is likely up (evidenced by the entry existence and NATT keepalives), but the Phase 2 data channel is down (child_num=0), resulting in zero traffic flow (rxp=0/txp=0).

To identify the reason for the lack of prefixes, we must interpret the State/PfxRcd and Up/Down columns in the get router info bgp summary exhibit.

Analyze Neighbor Status:

Neighbor 10.125.0.60: State is OpenSent. This session is not established. It is stuck in the negotiation phase.

Neighbor 100.64.3.1: State is Active. This session is not established. The router is actively trying to initiate a TCP connection.

Neighbor 10.127.0.75:

Up/Down: 02:45:55. This indicates the BGP session has been Up (Established) for almost 3 hours.

State/PfxRcd: 0. This number represents the count of prefixes received. The session is fully established, but the neighbor has sent zero routes.

Determine the Cause:

Since the session with 10.127.0.75 is established, connectivity and handshakes (Options A, B, C) are not the issue for this neighbor.

The fact that it is Up but sending 0 prefixes strongly implies that the neighbor is configured to filter out its routes before sending them to the local FortiGate.

Option D correctly identifies this as a RIB-OUT (Routing Information Base - Outbound) configuration issue on the neighbor (Router 10.127.0.75), which prevents it from advertising its routes.

The correct answer is A.

The debug output is for an HTTPS request and shows a hostname value. The study guide explains that with SSL certificate inspection, FortiGate extracts the FQDN from either:

“TLS extension server name indication (SNI)”

“SSL certificate common name (CN)”

So the hostname shown in the real-time web-filter debug can be derived from the SNI in the client request or, if needed, from the CN in the server certificate. That makes A correct.

Why the other options are wrong:

B is wrong because the study-guide example for web-filter real-time debug explicitly says: “This slide shows an example of real-time debug output when the URL to categorize isn ' t in the FortiGuard cache.”In these debugs, cat=255 appears before the final lookup result, so this does not indicate a local-cache hit.

C is wrong because ftgd-allow is the action, not the profile name. The debug line shows the action as action=9 (ftgd-allow) while the profile shown is profile= ' default ' . FortiOS web-filter logs also use the profile field separately from the action field

D is wrong because the final category shown is url_cat=52, not 255. The study guide’s example shows the same pattern: an initial cat=255 in the request line, followed by the resolved result cat=52 url_cat=52

So the verified answer is: A.

FortiManager template groups allow administrators to combine provisioning templates and assign the resulting group to managed devices. A template group can contain different applicable template categories, including system and SD-WAN templates, making E correct.

FortiManager also supports standard CLI and Jinja CLI templates. CLI template groups can contain a mixture of these template types, so C is correct. When multiple CLI templates are grouped, FortiManager processes them in their configured top-to-bottom sequence, making D correct.

Option B is incorrect because FortiManager uses standard CLI scripts and Jinja scripts; Perl is not the supported alternative scripting type described by the FortiManager 7.6 study material. Option A is also incorrect because FortiManager does not impose the stated three-IPsec-template-per-group rule. Template groups are intended to simplify consistent, reusable device provisioning.

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

The correct answer is D.

The exhibit shows:

session_count=591

clash=162

memory_tension_drop=0

TCP sessions:

166 in NONE state

1 in ESTABLISHED state

3 in SYN_SENT state

2 in TIME_WAIT state

The study guide explains the TCP protocol states and states explicitly:

“When a session is closed by both the sender and receiver, FortiGate keeps that session in the session table for a few seconds, to allow for any out-of-order packets that might arrive after the FIN/ACK packet. This is the state value 5.”

In diagnose sys session stat, the exhibit shows 2 in TIME_WAIT state. Since TIME_WAIT = state value 5, those are the sessions being kept briefly for possible out-of-order packets. That makes D correct.

Why the other options are wrong:

A is wrong because session_count=591 is the total number of sessions, while the TCP sessions shown add up to only 172 (166 + 1 + 3 + 2). So not all sessions in the table are TCP sessions.

B is wrong because the study guide says the number of sessions deleted because of low free memory is shown by memory_tension_drop, and in the exhibit it is 0, not 162.

C is wrong because the study guide defines ephemeral/open TCP sessions as those not fully established, but the exhibit does not say all 166 in NONE state are specifically “waiting to complete the three-way handshake.” The clearest directly supported statement from the displayed states is the 2 TIME_WAIT sessions retained for out-of-order packets.

So the verified answer is: D.

The correct answers are C and D.

The study guide’s get vpn ipsec tunnel details example shows:

replay: enabled

inbound and outbound sections with separate SPIs

NPU acceleration: encryption(outbound) decryption(inbound)and it labels these as “Phase 2 SAs for each direction” and “Hardware acceleration”

This directly proves D. Anti-replay is enabled, because the output explicitly says replay: enabled

For the NPU status, the study guide explains the exact npu_flag meanings:

npu_flag=00 = both IPsec SAs loaded to the kernel

npu_flag=01 = outbound IPsec SA copied to NPU

npu_flag=02 = inbound IPsec SA copied to NPU

npu_flag=03 = both outbound and inbound IPsec SAs copied to NPU

Because the exhibit shows hardware acceleration in both directions — encryption(outbound) and decryption(inbound) — the matching npu_flag is 03, not 02. That makes C correct and A incorrect.

Why B is wrong:

The same study guide output labels the tunnel as having Phase 2 SAs for each direction, so different inbound and outbound SPIs are normal for the two SAs. Also, the FortiOS administration guide explains that auto-negotiate controls whether phase 2 SA negotiation is initiated automatically, not whether inbound and outbound SPIs are different: “By default the phase 2 security association (SA) is not negotiated until a peer attempts to send data… Auto-negotiate initiates the phase 2 SA negotiation automatically…”

So the verified answers are: C, D.

The correct answers are B and C.

The study guide has a section titled “Not Verified Status on the Collector Agent” and states:

“The collector agent cannot verify if the user is still logged in” and lists these common causes:

“A firewall is blocking traffic to port 139 and 445”

“The workstation remote registry service is not running”

The guide also explains the verification method:

“For WMI polling mode, the collector agent checks the WMI service. For all the other modes, the collector agent checks the HKEY_USERS hive through remote registry services.” If the workstation does not respond to these checks, the status can become not verified

An additional requirements slide in the same study guide confirms:

“TCP ports 139 and 445 must be open between the collector agent and all workstations”

“Remote registry service must be up and running on each workstation”

Why the other options are wrong:

A is wrong because the study guide mentions a workstation coming out of hibernate mode under a different problem: “No Internet After IP Address Change”, not as a common cause of Not Verified status

D is wrong because DNS resolution issues are also discussed under the IP address change scenario, where the collector agent uses DNS to resolve the workstation name after an IP change. That is separate from the Not Verified causes listed for this log message

So the verified answers are: B, C.

To determine the correct reasons for the adjacency failure, we must analyze the standard OSPF real-time debug output (diagnose ip router ospf all enable or diagnose sniffer packet) typically provided in this exam exhibit.

Analyze the Debug Output:

The debug output in this specific question scenario typically displays an incoming Hello packet line: OSPF: RECV[Hello]: ... auth-type 0 ...

" RECV " : Indicates the packet is coming from the Remote peer.

" auth-type 0 " : Indicates the Remote peer is sending " Null " (No) authentication.

Analyze the Failure:

The adjacency fails because the Local FortiGate is rejecting this packet.

If the Local FortiGate accepts " No Authentication " , it would match auth-type 0 and form the adjacency.

Since it is failing (and producing a debug log), the Local FortiGate must be expecting a different authentication type (Type 1 Cleartext or Type 2 MD5).

Evaluate the Options:

A. The remote peer has either OSPF cleartext or MD5 authentication configured.

Incorrect. The debug shows auth-type 0 (No Auth) coming from the remote peer.

B. There is an OSPF authentication configuration mismatch.

Correct. One side is sending " No Auth " (Remote), and the other expects " Auth " (Local). This is a definition of a mismatch.

C. The local FortiGate does not have OSPF authentication configured.

Incorrect. If the Local unit had " No Auth " configured, it would match the Remote ' s auth-type 0, and the adjacency would come up. The failure implies the Local unit does have auth configured.

D. The local FortiGate has either OSPF cleartext or MD5 authentication configured.

Correct. Because the Local unit is rejecting the " No Auth " packet from the remote peer, it confirms that the Local unit has authentication enabled (expecting Type 1 or 2).

Conclusion: The breakdown of the OSPF negotiation shows that the Remote peer is sending no authentication (Type 0), while the Local FortiGate expects authentication, resulting in a mismatch.

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.