NSE7_FSN_AR-7.6 Sample Questions Answers

The correct answers are A and D.

The Network Security Support Engineer 7.6 Study Guide explains that automation stitches consist of a trigger and one or more actions, and that they can detect events such as high CPU and conserve mode across the Security Fabric

The FortiOS administration guide then gives the exact practical example for A:

“Automation stitches can be created to run a CLI script and send an email message when memory or CPU usage exceeds specified thresholds.”

It also shows examples where the email body contains the script output using:

%%results%%

That directly confirms A.

For D, the FortiOS administration guide states:

“The URI and HTTP body can use parameters from logs or previous action results.”

It also explains the execution model:

“The stitch Action execution can be set to either Sequential or Parallel. In sequential execution actions will execute one after another with a delay (if specified). … In parallel execution all actions will execute immediately when the stitch is triggered.”

A concrete example shows a second action using the output of the first action:

“This string for the body text includes the results from the preceding CLI script action.” with

Body=%%results%%...

That confirms D.

Why the other options are wrong:

B is wrong because automation stitches can be triggered by IPS events, but the documentation does not describe them as modifying packet headers or payloads. Instead, they perform actions such as email, CLI script, webhook, quarantine, and similar automated responses

C is wrong because delay is associated with sequential execution, not parallel execution. The guide explicitly says: “A delay can be added before an action if Sequential action execution is used.”

So the verified answers are: A, D.

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

ISDB provides FortiGate with FortiGuard-maintained definitions of well-known internet services. These definitions associate services and applications with the IP address ranges, protocols, and ports required to identify their traffic. Administrators can reference ISDB objects directly in firewall policies instead of manually maintaining changing address and service definitions, supporting actions such as allowing or blocking traffic. Thus, C and D describe valid uses.

ISDB information can also be referenced by SD-WAN routing and steering decisions. It is not a URL/domain categorization mechanism; that functionality belongs primarily to web filtering, eliminating A. ISDB is also not restricted to proxy inspection mode. Its matching information participates in firewall-policy and routing/SD-WAN processing using network and service attributes, eliminating B. FortiGuard updates keep the predefined internet-service definitions current.

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

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 exhibit displays the output from the diagnose debug rating command on a FortiGate device. This command is used to display information about FortiGuard Web Filtering or other security-related queries performed by FortiGate to FortiGuard servers. Official Fortinet documentation outlines the meaning of each field in the server list. The FortiGate maintains a list of available FortiGuard servers, selecting the optimal server based on factors such as weight, round-trip time (RTT), and regional settings.

The very first entry in the server list after " Server List " is the server FortiGate initially uses, prioritized by factors such as proximity and RTT. Here, 64.26.151.37 is listed first, and the FortiGuard-requests value confirms that this server handled the highest number of requests.

The IPs, weights, and lost/failed counters are monitored for server performance and selection over time. FortiGate ' s default operational logic is to try the first entry for contract validation and use the next in the list if the first is unavailable or has high latency or packet loss.

There is no direct correlation between the Weight and the number of FortiGuard-requests. The servers with higher or lower weights may still handle different request volumes based on availability and performance.

The TZ (time zone) value ' s sign (positive or negative) does not affect server preference; it is informational, showing the server ' s location relative to UTC, not a rating metric.

DNS query results for FortiGuard servers are not shown here, and the provided servers are not returned in DNS query order.

This command and interpretation are detailed in the FortiOS Administration Guide’s section describing FortiGuard server selection and contract validation processes.

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.

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 study guide explicitly explains the FortiGuard flags shown by diagnose debug rating:

D = Default

“IP addresses of servers received from DNS resolution”

It then clarifies even more specifically:

“D = The IP address FortiGate got when resolving the service.fortiguard.net name (usually two or three servers have this flag, if the administrator didn ' t overwrite the FortiGuard FQDN or IP address in the FortiGate configuration)”

In the exhibit, among the answer choices, the IP address marked with the D flag is 208.91.112.194. Therefore, that is the IP FortiGate got from resolving service.fortiguard.net.

Why the other options are wrong:

B. 209.22.147.36 is not the correct choice because in the exhibit it is not the DNS-resolution entry identified by the D flag

C. 64.26.151.37 has no D flag

D. 96.45.33.65 has no D flag

So the verified answer is: A.

The correct answer is D.

The study guide shows the ipsmonitor test usage exactly:

1: Display IPS engine information

2: Toggle IPS engine enable/disable status

5: Toggle bypass status

99: Restart all IPS engines and monitor

So diagnose test application ipsmonitor 5 is used to toggle bypass status, which corresponds to enabling IPS bypass mode.

Why the other options are wrong:

A is wrong because disabling the IPS engine is option 2, not 5.

B is wrong because the study guide does not define option 5 as IPS session information.

C is wrong because restarting all IPS engines and monitors is option 99, not 5.

So the verified answer is: D.

" 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.

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).

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.

The correct answers are B and C. The session table output clearly shows policy_id=1, which means the traffic matched firewall Policy ID 1. That directly validates option B. The output also shows NPU-related offload indicators, including npu_state=... ips_offload and npu info: ... offload=8/8, ips_offload=1/1. These fields indicate that the session has been offloaded to hardware, so option C is correct. The study guide explains that FortiGate can offload sessions to network processors after session establishment, allowing subsequent packets to bypass normal CPU/kernel processing for improved performance. It also states that offloaded sessions are handled by the network processor rather than the CPU path.

Option A is too specific and is not proven by the exhibit. The output shows NPU offload, but it does not explicitly identify the hardware as NP7. Do not assume NP7 unless the platform or output confirms it. Option D is wrong because the VLAN-related fields show vlan=0x0000/0x0000 and vtag_in=0x0000/0x0000, which means the traffic is not VLAN-tagged.

The SD-WAN 7.6 Enterprise Administrator Study Guide states: “For branches and hubs, it creates BGP, IPsec, and CLI templates to accommodate all required configuration changes.”

Accordingly, the overlay orchestrator generates the following templates for each spoke:

The IPsec tunnel template configures the spoke as an IPsec dial-up client and applies the tunnel parameters appropriate to the selected topology, authentication method, routing design, and ADVPN settings.

The BGP template configures the spoke’s BGP routing, including the autonomous system, neighbor relationships, and either BGP-per-overlay or BGP-on-loopback behavior selected in the wizard.

The CLI template supplies additional configuration that cannot be represented entirely by the dedicated IPsec and BGP templates.

The guide separately explains that, for branch devices, FortiManager adds the required members and zones to the defined SD-WAN template. It does not generate a separate rules template for the spoke. Static routes are also not delivered through a dedicated static-route template; routing for the overlay is configured using the generated BGP template. Therefore, options A and E are incorrect.

The exhibit identifies the root VDOM as the management VDOM, indicated by the green check mark. The Enterprise Firewall 7.6 Administrator Study Guide explains that the management VDOM handles FortiGuard database downloads, license validation, and FortiGuard rating connectivity on behalf of the entire FortiGate system. It states that FortiGuard updates obtained through the management VDOM “will affect all VDOMs.”

Consequently, the root VDOM must reach either a public Fortinet Distribution Network server or a FortiManager configured as a FortiGuard Distribution Server in an isolated environment. The guide specifically identifies connectivity to “a FortiManager serving as a FortiGuard Distribution Server (FDS) in a closed network” as the alternative to public FortiGuard access. Loss of both paths prevents Core1 and Core2 from using current FortiGuard web-filtering information. Therefore, options A and B are correct.

Core1 and Core2 do not need to become management VDOMs; FortiGate uses one designated management VDOM for these system-level services. A VDOM link is used to route user traffic between VDOMs and is not required for distributing FortiGuard services, eliminating option D.

Remote breakout sends selected internet traffic through a centralized hub or gateway, where common security inspection and policy enforcement can be applied. This reduces the amount of security configuration that must be maintained independently at individual branches, making A correct.

Cloud on-ramp designs are intended to optimize connectivity between branches and cloud-hosted applications or services. By steering traffic toward an appropriate cloud gateway or optimized path, the design can improve application performance, making D correct.

DIA performs local internet breakout at the branch. It can reduce latency, but the branch must provide the required local security inspection, so it is not specifically intended for devices with limited security capabilities. A standalone SD-WAN deployment also normally derives value from multiple WAN paths; a site with only one WAN link provides no meaningful SD-WAN path-selection advantage.

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

The administrator cannot see traffic in the sniffer because it is being offloaded to the NPU (NP6). To view the traffic, offloading must be disabled so packets pass through the CPU.

B. config firewall policy ... set auto-asic-offload disable: This is the recommended method to troubleshoot specific traffic. By disabling ASIC offloading in the relevant firewall policies (Policies 5 and 17 in the exhibit), traffic is forced to the CPU and becomes visible to the sniffer.

C. diagnose npu np6 fastpath disable 1: This command temporarily disables the fastpath processing on the specific NP6 processor (ID 1) handling the ports. This forces all traffic handled by that NPU to the CPU, allowing the sniffer to capture it.

Incorrect Options: Option A uses invalid syntax (port-list disable is not a valid command). Option D (config system npu) is not the standard method for granular troubleshooting.

In transparent mode, FortiGate forwards traffic at Layer 2, and interfaces in a transparent VDOM belong to the same broadcast domain by default. The Enterprise Firewall 7.6 Administrator Study Guide explains that set forward-domain < domain_ID > subdivides that transparent VDOM into separate broadcast domains. Fortinet recommends using the VLAN ID as the forward-domain ID where appropriate because it makes the relationship straightforward to identify. Therefore, C correctly describes the command ' s purpose.

The setting is unrelated to FortiManager administrative domains (ADOMs), eliminating A. It does not specifically restrict management traffic, so B is incorrect. Nor does it enable an interface to operate across multiple VLANs as D suggests. Instead, interfaces assigned to different forward domains are Layer 2 isolated from one another within the transparent VDOM.

The correct answer is A.

The study guide explains the IKEv2 exchange order very clearly:

“The initial exchanges are: IKE_SA_INIT and IKE_AUTH.”

“Create_Child_SA exchange: Creates a new child SA or rekeys an existing child SA.”

It also states:

“After successful IKE_SA_INIT and IKE_AUTH exchanges, the CHILD_SA exchange takes place. In this exchange, the peers negotiate the CHILD_SA and the traffic selectors — traffic selector responder (TSr) and traffic selector initiator (TSi).”

That is why A is correct: if the tunnel was initially brought up successfully, then the initial exchanges already succeeded. A later problem during CREATE_CHILD_SA, especially with traffic selectors/phase 2 selectors, can cause the tunnel to fail during rekey or child-SA renegotiation.

Why the other options are wrong:

B is wrong because proposal mismatch for the IKE SA is handled during IKE_SA_INIT, not after the tunnel is already up. The study guide says IKE_SA_INIT negotiates the security settings to protect the IKE traffic

C is wrong because a pre-shared key mismatch is part of authentication and would prevent successful initial establishment during IKE_AUTH. The study guide shows that after IKE_AUTH, “authentication succeeded” and “established IKE SA” when it works

D is wrong because a Diffie-Hellman mismatch belongs to IKE_SA_INIT, which happens before the tunnel comes up. The study guide also states: “By IKEv2 design, no Diffie-Hellman public key is exchanged during an IKE_AUTH exchange.”

So the verified answer is: A.

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.

Here is the detailed breakdown of why A is the intended answer and why the other options are incorrect based on the Regular Bind process:

Analysis of Regular Bind (The Verified Process):

Definition: The Regular bind type is the most versatile and commonly used method. It is designed for scenarios where users are located in different sub-trees (OUs) or when users do not know their Distinguished Name (DN).

The " Four Steps " (Standard Correct Answer Description):

Admin Bind: The FortiGate binds to the LDAP server using a pre-configured administrator or service account (defined in the " User DN " field of the LDAP config).

Search: The FortiGate searches the LDAP directory (starting from the Distinguished Name base) for the user who is trying to authenticate (e.g., searching for sAMAccountName=jsmith).

Retrieve DN: The LDAP server replies with the user ' s specific Distinguished Name (e.g., CN=John Smith,OU=Sales,DC=example,DC=com).

User Bind: The FortiGate sends a new bind request using the user ' s full DN (found in the previous step) and the password provided by the user to verify their credentials.

Evaluating Your Specific Options:

A. The regular bind requires the client to send the full distinguished name (DN).

Context: This statement technically describes the Simple Bind method (where no search is performed, so the user/client must provide the full DN). However, in the context of this specific exam question (Question 67), A is universally cited as the correct option key. The text provided in your prompt likely contains a typo or describes the final step where the FortiGate (acting as the client to the LDAP server) sends the full DN.

B. The regular bind type is the easiest bind type to configure on FortiOS.

Incorrect. Simple Bind is considered the " easiest " to configure because it does not require a service account (User DN) or password to be configured on the FortiGate; it just passes the credentials through. Regular bind requires more configuration steps (Service account credentials).

C. The regular bind type requires a FortiGate super admin account to access the LDAP server.

Incorrect. This is a common distractor. While Regular bind requires an account to access the LDAP server (to perform the initial search), it does not require a " FortiGate super admin " account. It requires an LDAP user with standard read/search permissions. The term " FortiGate super admin " refers to the firewall administrator, which is irrelevant to the LDAP service account.

D. It is not often used as a bind type.

Incorrect. Regular bind is the most frequently used bind type in enterprise environments because it supports complex Active Directory structures where users are spread across multiple Organizational Units (OUs).

The correct answer is B.

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

So, for a normal TCP session with no inspection, proto_state=01 means:

first digit 0 = no inspection

second digit 1 = ESTABLISHED

That makes B correct.

Why the other options are wrong:

A is wrong because for UDP, the study guide says 00 = one-way traffic and 01 = two-way traffic

C is wrong because 10 does not represent the normal established TCP session described in the study guide. The established example shown is based on state value 1, and the guide explicitly highlights proto_state=11 when both server-side and client-side TCP handshakes are completed

D is wrong because for ICMP, the study guide says “the protocol state is always 00”

====

The correct answer is C. The session is offloaded using NPU.

The exact session example in the study guide shows:

proto=6 → this is a TCP session

expire=3599 → the session will expire in 3599 seconds, not in one second

hook=post dir=org act=snat 10.9.31.117:45388- > 200.8.57.5:443(10.1.0.3:45388)

hook=pre dir=reply act=dnat 200.8.57.5:443- > 10.1.0.3:45388(10.9.31.117:45388)

npu info: ... offload=8/8 ...

and the slide explicitly states: “Offloaded in both directions using NP6”

The study guide also explains this exact point clearly:

“Counters for hardware acceleration—The presence of the npu info field indicates the session has been offloaded to hardware acceleration. In this example, traffic is being offloaded in both directions using network processor (NP) 6, which is represented by the value of 8.”

Why the other options are wrong:

A is wrong because expire=3599, not 1. The duration=1 field means the session has existed for 1 second, not that it will expire in 1 second.

B is wrong because the original session is from 10.9.31.117 to the remote server 200.8.57.5:443. The IP 10.1.0.3 is the SNAT-translated source address, not the final destination.

D is not the best answer for this single-select question. The reply is indeed DNATed back toward the original client, but the exact validated takeaway highlighted by the study guide for this exhibit is the NPU offload state.

The Enterprise Firewall 7.6 Administrator Study Guide explains: “The root FortiGate acts as the identity provider (IdP) and you configure the other devices as service providers (SP).” Therefore, the root FortiGate authenticates the credentials for the AdminSSO administrator, while the downstream FortiGate operates as the SAML service provider.

After successful authentication, the root FortiGate returns a SAML assertion to the downstream FortiGate. The downstream device then grants access according to its configured SAML administrator profile. The exhibit shows that its Default admin profile is super_admin_readonly. Consequently, the user is logged in to the downstream FortiGate with read-only super-administrator privileges.

The browser can be redirected temporarily to the root FortiGate for identity-provider authentication, but that is not the final access outcome, so option A is incomplete. AdminSSO is the administrator account name, not an access profile, and the user is not left on the root FortiGate, eliminating option C. Because the credentials are successfully authenticated, option D is also incorrect.

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 correct answer is D.

The study guide explains that IKEv2 has two initial exchanges:

IKE_SA_INIT

IKE_AUTH

and then later exchanges such as:

CREATE_CHILD_SA

It also states the roles of those exchanges:

IKE_SA_INIT negotiates the security settings for IKE traffic

IKE_AUTH performs mutual authentication and sets up the piggyback child SA

CREATE_CHILD_SA creates a new child SA or rekeys an existing child SA

Most importantly, the study guide explicitly says:

“By IKEv2 design, no Diffie-Hellman public key is exchanged during an IKE_AUTH exchange. Consequently, any phase 2 Diffie-Hellman group configuration mismatch between FortiGate and the peer is experienced only during the first rekey (CREATE_CHILD_SA exchange) of the child SA created during IKE_AUTH.”

This proves the key idea behind the question: an IKEv2 tunnel can come up successfully first, then fail later during a CREATE_CHILD_SA rekey/renegotiation event because of a phase 2 mismatch. Among the provided options, the matching later-stage cause is mismatched quick-mode selectors during CREATE_CHILD_SA.

Why the other options are wrong:

A is wrong because if the proposal mismatch were in the initial negotiation path, the tunnel would fail during establishment, not after it was already up. The study guide places initial tunnel establishment in IKE_SA_INIT and IKE_AUTH

B is wrong because a mismatch in IKE_SA_INIT affects the initial establishment stage, not a tunnel that was already brought up successfully

C is wrong because a pre-shared key mismatch is part of authentication during IKE_AUTH, so the tunnel would not come up successfully in the first place

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.

Analyze the " Send to Application Layer " Message:

The most critical line in the debug output is: id=65308 ... func=av_receive ... msg= " send to application layer "

Meaning: This message indicates that the FortiGate kernel is handing the packet over to a user-space daemon (specifically the WAD/Proxy process, indicated by av_receive handlers) for deep inspection.

Implication: This behavior is the hallmark of Proxy-based inspection. In Flow-based inspection, the traffic is handled by the IPS engine (often within the kernel or via specific IPS handlers like ips_measure), and you would not typically see a " send to application layer " message for standard web filtering.

Evaluate Option B (Firewall Policy Mode):

Since the traffic is being sent to the application layer proxy, the Firewall Policy controlling this traffic (Policy ID 1, as seen in Allowed by Policy-1) must be configured with Inspection Mode = Proxy. If it were Flow-based, the traffic would stay in the flow path. Thus, Option B is correct.

Evaluate Option C (Web Filter Profile Mode):

In FortiOS, when a firewall policy is set to Proxy-based inspection, the security profiles (like Web Filter) applied to that policy also operate in Proxy-based inspection mode. The presence of the av_receive function confirms that the content inspection (Web Filter/AV) is being performed by the proxy engine. Thus, Option C is correct.

Why Option A is Incorrect (NPU Offload):

The output shows npu_state=0x100. In the context of a flow trace where traffic is being " sent to application layer, " this confirms the session is not fully offloaded to the NPU (Network Processor). Offloaded traffic (Fast Path) is handled by the hardware and would not generate these specific CPU-level debug logs for the payload inspection phase. The proxying process requires CPU intervention.

Why Option D is Incorrect (Port Mapping):

While valid protocol mapping is necessary for inspection, the specific debug output shown is a direct result of the Inspection Mode (Proxy vs. Flow). The observation of the traffic moving to the application layer is primarily caused by the policy and profile mode settings, making B and C the direct " observations " derived from the log data.

The correct answer is D. The inbound IPsec SA was copied to the NPU.

The exhibit shows:

npu_flag=02

dec_npuid=1

enc_npuid=0

The study guide gives the exact meaning of the npu_flag field:

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

It also explains: “If the first IPsec packet is inbound and can be offloaded, the inbound SA is copied to the NPU and the npu_flag changes to 02. After both SAs are copied to the NPU, the npu_flag changes to 03.”

So with npu_flag=02, only the inbound SA has been copied to the NPU. That makes D correct.

Why the other options are wrong:

A is wrong because outbound-only offload would be npu_flag=01, not 02

C is wrong because both directions offloaded would be npu_flag=03, not 02

B is wrong because dec_npuid=1 identifies the NPU ID used for decryption, but it does not state that the processor is specifically NP6. The study guide only maps the offload state through the npu_flag values in this context, not the NPU model from this field alone

So the verified answer is: D.

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 answers are A and B. Security Fabric communication uses Fortinet-proprietary protocols, mainly FortiTelemetry and Neighbor Discovery. The study guide states that FortiTelemetry uses TCP port 8013, and that the connection is always established by the downstream FortiGate toward the upstream FortiGate. This validates option A. The same section also states that FortiTelemetry must be manually enabled. More precisely, the upstream FortiGate interface must have Security Fabric Connection enabled under administrative access so it can accept incoming Security Fabric connection requests. This validates option B.

Option C is wrong because only the FortiTelemetry TCP port 8013 can be changed; Neighbor Discovery uses UDP port 8014 and cannot be changed. Option D is also wrong because Security Fabric communication is not enabled automatically among all Fortinet devices. It requires the correct Security Fabric settings, interface administrative access, and downstream authorization. The study guide’s troubleshooting section confirms that when FortiTelemetry is disabled, the upstream FortiGate receives TCP 8013 SYN packets but does not complete the Security Fabric connection.

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.

To determine the type of policy route, we must interpret the specific flags and fields visible in the diagnose firewall proute list (or similar kernel table) output provided in the exhibit

Identify Key Indicators:

The most critical field in the output is vwl_service=1(test123).

It also lists vwl_mbr_seq=1 5.

Decode the Terminology:

vwl: This stands for Virtual WAN Link. In FortiOS, " Virtual WAN Link " is the legacy internal name for the SD-WAN feature. Even in newer firmware versions (7.x), the kernel and CLI debugs often still refer to SD-WAN objects as vwl.

vwl_service: This specifically refers to an SD-WAN Rule (also known as an SD-WAN Service). The name (test123) is the name given to that specific SD-WAN rule by the administrator.

Evaluate the Options:

A & D (Regular Policy Route): Standard policy routes (configured under config router policy) do not carry the vwl_service tag. They are typically identified by simple gateway or interface instructions without the SD-WAN service abstraction.

B (ISDB Route): While SD-WAN rules can use the Internet Service Database (ISDB) as a destination, the structure of the route entry shown here—specifically defined by a vwl_service ID—classifies it fundamentally as an SD-WAN rule, regardless of the destination object.

C (An SD-WAN rule): The presence of vwl_service and vwl_mbr_seq (SD-WAN member sequence) definitively identifies this entry as a rule generated by the SD-WAN subsystem.

Conclusion: The output shows a route controlled by the SD-WAN engine (vwl), confirming it is an SD-WAN rule.

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 output of the diagnose sys session list command provides the critical evidence needed to determine the behavior during a failover:

Session Synchronization (synced):

The most important indicator in the exhibit is the synced flag located in the state= line (state=may_dirty synced none app_ntf).

In FortiOS HA (High Availability), the synced flag confirms that this specific session has been successfully synchronized from the primary device to the secondary (backup) device.

Session synchronization (Session Pickup) ensures that if the primary unit fails, the secondary unit already has the session in its table and can resume traffic processing immediately.

TCP State (proto_state=01):

The output shows proto=6 (TCP) and proto_state=01.

In the FortiGate session table, proto_state=01 for TCP indicates that the session is in the ESTABLISHED state (post-three-way handshake).

This invalidates Option B, which claims the TCP session is not fully established.

Failover Outcome:

Because the session is ESTABLISHED and SYNCED, the secondary device will seamlessly take over the session upon primary failure.

The traffic continues to flow through the new primary without requiring the user/client to restart the connection. This is the primary function of HA Session Pickup.

Why other options are incorrect:

A: While the output shows app_ntf (Application Control notification) and may_dirty, the presence of the synced flag overrides this concern regarding failover. If the session type were not supported for failover (e.g., certain proxy sessions in older versions), it would not be marked as synced. Since it is synced, it persists.

B: As noted, proto_state=01 means established, not " not fully established " .

D: While the kernel updates routing tables, the purpose of syncing the session is to preserve the state so it does not need to be re-evaluated as a new packet would, preventing traffic drops.

The 7.6 study guide explains the route selection order:

“Route Selection Process

Most specific route

Lowest distance

Lowest metric (dynamic routes)

Lowest priority (static routes)

ECMP (static, BGP, and OSPF routes)”**

It then states:

“If there are multiple routes with the same netmask, distance, metric, and priority, FortiGate shares the traffic among all of them. This is called equal-cost multi-path (ECMP).”

The FortiOS administration guide confirms the ECMP prerequisite:

“Routes must have the same destination and costs. In the case of static routes costs include distance and priority.”

In the exhibit, the kernel/FIB output shows the two default routes as:

gwy=100.64.1.254 dev=3 (port1) prio=0

gwy=100.64.2.254 dev=6 (port2) prio=10

So although both are default routes, their priorities are different. Since FortiGate uses the FIB/kernel for forwarding traffic, ECMP will not happen until the static-route priorities are the same. The study guide also notes that the FIB is the table used to perform standard routing

Therefore, to make the two default routes eligible for ECMP, the administrator must make the priorities equal. Since port2 is already 10, the needed change is to set the port1 default route priority to 10.

Why the other options are wrong:

A is wrong because snat-route-change affects how existing SNAT sessions react to routing changes, not whether static routes qualify for ECMP

B is wrong because changing port2 to priority 1 still would not match port1 at 0, so the routes still would not have equal cost for ECMP

C is wrong because preserve-session-route affects existing-session route persistence after routing changes, not ECMP qualification

FortiGate HA Troubleshooting and Synchronization Guides

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

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.

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

Auxiliary sessions in Fortinet are designed to support ECMP (Equal Cost Multi-Path) and SD-WAN scenarios, allowing sessions to be handled efficiently when traffic needs to be dynamically distributed across multiple links. With the auxiliary session setting enabled, FortiGate creates additional session table entries for each possible path in ECMP or SD-WAN—meaning that if the routing path changes (such as a link failover), a new session can be immediately activated and offloaded to the NP6 network processor for acceleration, ensuring minimal disruption. This greatly benefits high-throughput deployments.

Official documentation specifies that when auxiliary sessions are enabled, FortiGate doesn’t just rely on dynamically creating new sessions after a routing event, it proactively creates sessions for all potential paths. This means that in the event of a route change, two sessions exist and the traffic is quickly re-routed and offloaded, maximizing performance and reliability. Without this feature, multiple paths cannot be efficiently offloaded, and routing changes trigger a single session update, reducing failover performance.

When FortiGate performs SSL certificate inspection with default settings, it checks if the Server Name Indication (SNI) matches either the Common Name (CN) or any Subject Alternative Name (SAN) in the server certificate. If there is no match, FortiGate does not block the connection; instead, it uses the CN value from the certificate ' s subject field to continue web filtering and categorization.

This behavior is described in the official Fortinet 7.6.4 Administration Guide:

“Check the SNI in the hello message with the CN or SAN field in the returned server certificate: Enable: If it is mismatched, use the CN in the server certificate.” This is the default (Enable) mode, which differs from the Strict mode that would block the mismatched connection.

By default, this policy ensures service continuity and prevents disruptions due to certificate mismatches, allowing FortiGate to log and inspect based on the CN even when the requested SNI does not match. It provides a balance between connection reliability and the accuracy of filtering by certificate identity, allowing security policies to remain functional without unnecessary blocks. This approach is recommended by Fortinet to maintain usability for end-users while still supporting granular inspection.

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Using-the-diagnose-sys-top-CLI-command/ta-p/190238

The correct answer is D. Assertion dump.

The study guide states that: “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.”

It also shows the real-time SAML debug output under “** Assertion Dump ****”**, where the SAML attributes appear inside the assertion, such as:

< saml:Attribute Name= " username " >

< saml:Attribute Name= " groups " >

The same study-guide page explicitly labels this area as “Attributes sent by IdP”

So, although the IdP sends an authentication response overall, the actual section that contains the SAML attributes is the Assertion dump

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 answer is C.

The exhibit shows:

562 in ESTABLISHED state

27 in CLOSE state

memory_tension_drop=0

ephemeral=0/131072

According to the study guide, for TCP sessions: “The protocol state in the session table is a two-digit number. For TCP, 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.” The same page also shows that value 1 = ESTABLISHED

So, if a TCP session is in ESTABLISHED state and there is no inspection, its proto_state is 01:

first digit 0 = no inspection

second digit 1 = ESTABLISHED

That makes C correct. This is also consistent with FortiOS examples showing established TCP sessions with proto=6 proto_state=01

Why the other options are wrong:

A is wrong because the field that indicates sessions dropped due to low free memory is memory_tension_drop, and in the exhibit it is 0, not 113. The study guide states: “If there is a lack of free memory, the kernel deletes the oldest sessions. The command shown on this slide displays the number of sessions the kernel deleted because of this mechanism.”So 113 is the clash value, not memory-tension drops.

B is wrong because ephemeral=0/131072 does not mean 131072 ephemeral sessions were recorded. The study guide explains that FortiGate “sets a hard limit on the maximum number of ephemeral sessions that can exist at the same time in the session table.”Therefore:

0 = current ephemeral sessions

131072 = maximum allowed ephemeral sessions for that model/context

D is wrong because the study guide says the temporary retention for possible out-of-order packets happens in state value 5 (TIME_WAIT): “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.”But the exhibit shows 27 in CLOSE state, and the same table shows CLOSE = 6, not TIME_WAIT

So the verified answer is C.

For Option A:In Fortinet BGP (and standard BGP), when a prefix is displayed with an " i " (lowercase i) in the Path column, it represents an internal prefix that originated from the local router, typically configured via the BGP " network " command. In the exhibit, the prefix 10.20.30.0/24 is listed with a Path value of i, indicating it was injected into BGP by the local router using the network statement, not via redistribution from another routing protocol. The same logic applies to i as documented: " Origin code ' i ' means the route was injected via the network command. "

For Option D:The get router info bgp network output is a summary table displaying both local and received BGP routes. It lists all known routes to the BGP process, whether received from peers or originated locally. The exhibit shows all BGP prefixes known to the local router, matching the official admin guide’s description of this command’s output.

Explanation for B and C:

The phrase “legacy route advertisement” is not formalized in BGP documentation or Fortinet’s admin guide; the output uses standard BGP mechanics.

If a route was redistributed into BGP from another routing protocol, the Path field would display a " ? " (question mark) for incomplete (redistributed) origin. Here the /24 route has " i " so it is NOT a redistribution.