Fortinet NSE7_FSN_AR-7.6 Fortinet NSE 7 - Secure Networking 7.6 Architect Exam Practice Test

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.

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.

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.

The BGP debug output shows session information for peers, including state details. According to official Fortinet BGP documentation, if the session state with a peer does not show " Idle, " " Active, " or " Connect, " but instead shows " Established, " " Up, " or related counters (e.g., messages sent/received or uptime), it indicates the session is operational. In this scenario, the peer 10.127.0.75 is the only one showing a positive indication of a live, established session. Other options like neighbor-range configuration, AS mismatch, or route-maps blocking prefixes are not supported by evidence provided in a simple BGP session state debug, nor does the output show errors relating to local or remote AS issues.

The correct interpretation comes from Fortinet ' s BGP troubleshooting guide, which outlines how to read session status and neighbor states in debug and summary outputs.

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 SD-WAN 7.6 Enterprise Administrator Study Guide states: “An SD-branch is a site with an SD-WAN spoke FortiGate device and one or multiple extensions.” It explains that FortiSwitch and FortiAP provide wired and wireless LAN connectivity through FortiLink, while FortiExtender supplements WAN connectivity by providing 4G/5G transport.

The guide further explains that the management plane sees extension-device ports as logical interfaces belonging to the controlling FortiGate. Therefore, FortiSwitch, FortiAP, and FortiExtender do not become independent SD-WAN topology nodes and do not require separate topologies. FortiGate devices with FortiLink connections also do not need to be excluded.

FortiExtender is specifically designed as a natural SD-WAN extension that introduces cellular connectivity as another WAN transport. Consequently, a FortiGate using FortiExtender can function as a hub, provided it satisfies the required capacity, routing, and IPsec design requirements. There is no rule requiring hubs to be extension-free. Therefore, option D correctly describes the unified topology shown in the exhibit.

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

To determine the correct conclusions, we analyze the specific lines in the IKE real-time debug output provided in the exhibit:

Analysis for Option A (The remote peer is the initiating peer):

Evidence: The very first line of the debug output reads: ike 0:624000:98: responder: main mode get 1st message...

The keyword responder indicates that this local FortiGate is receiving the connection request. Consequently, the remote peer must be the initiator sending the request. The phrase " get 1st message " confirms the local unit is receiving the initial packet of the negotiation sequence.

Conclusion: This statement is True.

Analysis for Option B (This is a phase 1 negotiation):

Evidence: The same line mentions main mode.

In IPsec VPNs, Main Mode and Aggressive Mode are exclusively used for Phase 1 (IKE SA) negotiations. Phase 2 (Child SA) negotiations use Quick Mode. The presence of " main mode " definitively identifies this as a Phase 1 exchange.

Conclusion: This statement is True.

Analysis for Option C (There is a Diffie-Hellman group mismatch):

Evidence:

Incoming proposal (Remote): Lists type=OAKLEY_GROUP, val=MODP2048 (Group 14) in the first proposal proposal.

My proposal (Local): Lists type=OAKLEY_GROUP, val=MODP2048 (Group 14).

Since both the remote peer and the local gateway support and are proposing MODP2048 (Group 14), there is no Diffie-Hellman group mismatch. The actual mismatch visible in the logs is between the Encryption/Hash algorithms (Remote proposes AES-256/SHA2-256, while Local proposes AES-128/SHA), but the DH groups match.

Conclusion: This statement is False.

Analysis for Option D (This is a phase 2 negotiation):

As established in the analysis for Option B, " Main Mode " is a Phase 1 protocol. If this were Phase 2, the debug would show " Quick Mode " .

Conclusion: This statement is False.

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

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.

To determine the cause of the failure, we must analyze the IKEv2 debug output provided in the exhibit (image_ad3dc6.jpg):

Identify the Negotiation Phase:

The debug log shows: responder received CREATE_CHILD exchange.

In IKEv2, the CREATE_CHILD_SA exchange is used to create new Child SAs (Phase 2) or to rekey existing ones.

The fact that the tunnel was previously " brought up successfully " implies the initial IKE SA (Phase 1) is stable, and this error is occurring specifically during a rekey event, which often involves Perfect Forward Secrecy (PFS).

Analyze the Proposals (The Mismatch):

Incoming Proposal (Remote Peer):

The remote peer sends a proposal containing two Diffie-Hellman groups: type=DH_GROUP, val=MODP2048 (Group 14) and type=DH_GROUP, val=MODP1536 (Group 5).

My Proposal (Local FortiGate):

The local FortiGate configuration expects: type=DH_GROUP, val=MODP3072 (Group 15).

Result of the Negotiation:

The debug output concludes with: no proposal chosen and Negotiate SA Error.

This error occurs because the local FortiGate cannot find a common Diffie-Hellman group between what it requires (Group 15) and what the peer is offering (Groups 14 or 5).

While this is technically a mismatch occurring during the Phase 2 (Child SA) creation, " A Diffie-Hellman mismatch " (Option A) is the precise root cause identified in the logs.

Why other options are incorrect:

B: The log shows received create-child request, confirming that UDP traffic is reaching the device and is not blocked.

C: The failure is in the CREATE_CHILD exchange (Phase 2/Rekey), not the IKE_SA_INIT or IKE_AUTH (Phase 1) exchanges.

D: While the mismatch is occurring within the Phase 2 definitions, Option A is the specific technical reason for the no proposal chosen error shown in the DH_GROUP lines.

FortiGate requires an eligible SD-WAN member to have a valid route to the destination in the forwarding information base (FIB). Therefore, a member without such a route cannot be selected, making B correct. FortiGate also performs a FIB best-match check when evaluating an SD-WAN rule. If the resolved best-route interface is not an SD-WAN member, FortiGate skips that SD-WAN rule, confirming D.

ISDB routes operate as policy routes and are evaluated before SD-WAN rules, so C is also correct. A static route does not automatically bypass SD-WAN; static routes can provide the FIB routes required by SD-WAN members. Likewise, directly connected routes do not categorically take precedence over every SD-WAN rule. The applicable behavior depends on FIB resolution and whether the resolved interface belongs to SD-WAN.

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

FortiOS performs several routing checks before standard forwarding-table processing. The FortiOS 7.6 Administrator Study Guide describes the sequence explicitly. FortiGate first evaluates regular policy routes. If no applicable policy route forwards the packet, FortiGate evaluates Internet Service Database routes, followed by configured SD-WAN rules.

Only after those policy-routing mechanisms have been evaluated does FortiGate perform the standard forwarding information base (FIB) lookup. Static and dynamically learned routes, including BGP routes, are represented in this normal routing stage.

Consequently, among the available choices, the correct ordering is policy routes, ISDB routes, SD-WAN rules, and then static routes through the FIB. Options A and B incorrectly place SD-WAN before ISDB or policy routing, while C incorrectly places SD-WAN ahead of the regular policy-routing stages. Therefore, D is correct.

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

The correct answers are A and D.

The study guide states:

“Application layer test commands do not display information in real time. They display statistics and configuration information about a feature or process. You can also use some of these commands to restart a process or execute a change in its operation.”

This directly proves:

A is correct because they can display statistics and configuration information

D is correct because some of them can restart a process/application

Why the other options are wrong:

B is wrong because the study guide explicitly says application-layer test commands do not display information in real time. Real-time output is done with diagnose debug application ... commands instead.

C is wrong because diagnose debug console enable is related to debug output behavior, not a requirement for application-layer test commands to display output. The study guide does not describe test commands that way.

====

The get router info ospf database brief output on FGT-2 clearly indicates that Area 0.0.0.5 is configured as a [Stub] area.

In OSPF, a Stub Area is specifically designed to reduce the size of the Link State Database (LSDB) on internal routers. The primary behavior of a Stub area is that it does not accept Type 5 (AS External) LSAs.

FGT-3 is the ASBR (Autonomous System Border Router) and is importing static routes, which are generated as Type 5 LSAs in the OSPF domain.

FGT-1 acts as the ABR (Area Border Router). Because Area 0.0.0.5 is a Stub area, FGT-1 blocks these Type 5 LSAs from entering Area 0.0.0.5.

Consequently, FGT-2 will not receive the specific external routes advertised by FGT-3. Instead, the ABR (FGT-1) injects a default route (0.0.0.0/0) into the Stub area to allow connectivity to the external world, which is visible in the database output.

While the question text mentions FGT-3 not receiving routes, the definitive configuration shown in the exhibit is the Stub area setting, which directly corresponds to the blocking of Type 5 LSA propagation (Option A).

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.

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

The SD-WAN 7.6 Enterprise Administrator Study Guide describes two MSSP-hosted hub models that fit these requirements. A multi-tenant MSSP hub can dedicate one VDOM to each customer, while a second model provides a dedicated FortiGate VM hub for each customer. In both designs, spokes remain at customer locations and can use direct internet access locally.

These models also suit significant spoke-to-spoke traffic because most intersite traffic can use ADVPN shortcuts rather than being forced through the hub. The MSSP retains responsibility for the overlay control plane and centralized management. A customer-premises hub is more appropriate when substantial spoke-to-hub traffic exists, such as branches accessing centrally hosted workloads or centralized internet breakout. Therefore, the shared-VOM hub model and dedicated MSSP-hosted hub model are the appropriate choices.

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

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.

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.

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

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.

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

https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Static-URL-filter-actions-explained/ta-p/206632

The correct answer is A. This behavior is dictated by the configuration command set snat-route-change enable shown in Exhibit 1 under config system global.

Routing Change: By changing the priority of route ID 2 from 10 to 0, it becomes lower than route ID 1 (priority 5). In FortiOS, a lower priority value indicates a more preferred route. Consequently, the active route for the destination changes from port1 to port2.

SNAT Implication: The existing session (shown in Exhibit 2) is using Source NAT (SNAT) with the IP address associated with port1 (10.200.1.1). If the traffic were simply switched to port2, the source IP would be incorrect for that interface and the return traffic would likely fail or be dropped.

snat-route-change enable: This specific setting instructs the FortiGate on how to handle established SNAT sessions when a routing change occurs that alters the preferred outgoing interface. When enabled, if a route change forces an SNAT session to a new interface, FortiGate flushes (deletes) the session from the session table. This is necessary because a live TCP session cannot survive a change in its source IP address. The client must initiate a new session, which will then be created using the new correct route (port2) and the corresponding new SNAT IP.

If this setting were disabled, the session would likely remain " sticky " to the original interface (port1) until it closed, provided the route still existed. However, the explicit configuration forces the deletion.

FortiOS Admin Guide: Static Routing, SNAT Route Change Feature

To display debug output on FortiGate devices, you must always run both the application-specific debug command and the global debug enable command. The command diagnose debug application ike -1 sets up the detail level for the IKE daemon debug, but it does not display any debug output on its own. As described in the FortiOS CLI debugging manuals, the command diagnose debug enable activates debug output on the console, making all previously set debugs visible. This is especially important for VPN troubleshooting—without the enable command, no output appears even if there is VPN traffic.

The correct diagnostic sequence is:

diagnose debug application ike -1

diagnose debug enable

This procedure is found in every FortiOS CLI debug tutorial and troubleshooting workflow.

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.

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

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.

The 8.8.8.8/32 route is visible in the OSPF database on FGT-B but not installed into the routing table—the most likely explanation is that FGT-B is filtering it from being installed.

According to the official Fortinet administration guide for FortiOS 7.6.4 under the section " Configuring a RADIUS server, " the supported RADIUS authentication methods you can configure via the CLI with config user radius are:

pap

chap

mschap

mschapv2

auto

The relevant CLI syntax is set auth-type {auto | ms_chap_v2 | ms_chap | chap | pap}​. You can confirm this directly in the configuration table and from real CLI sessions.

EAP (Extensible Authentication Protocol) is NOT an authentication option you can directly set under config user radius. EAP methods (such as EAP-TLS, EAP-PEAP, EAP-TTLS) are negotiated between the RADIUS client and server but are not configurable as an explicit auth-type option in FortiOS. EAP authentication is typically used automatically by features like 802.1X, not through the user radius object authentication-type setting, and always requires proper backend workings between supplicant and RADIUS server

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.

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

Parallel Path Processing (PPP) in FortiOS refers to the system’s ability to evaluate and select among multiple processing paths—often involving dedicated network processors, content processors, or CPU-based workflows—to optimally process packets. The official documentation highlights that the PPP engine dynamically selects which hardware or software path to use for each session based on session characteristics, policy configuration, and traffic type. This dynamic selection results in optimal throughput and resource utilization.

The document specifies that PPP assesses several processing paths in parallel, using decision logic to determine whether a session should be offloaded to specialist hardware (like NP6, CP9, etc.) or stay in the CPU path, ensuring that each packet is handled by the most efficient available method under current load and policy. Hardware and software configurations both influence this outcome, but it is the PPP engine ' s decision-making that defines the optimal path per session.

The session output includes the flags:

state=redir local may_dirty ...

npu_state=00000000

offload=0/0

The 7.6 study guide explains these flags directly:

local = “Session is to/from local stack”

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

may_dirty = “Session is allowed by a firewall policy”

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

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

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

Why the other options are wrong:

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

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

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

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.

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.

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 Enterprise Firewall 7.6 Administrator Study Guide specifically warns that all-zero phase 2 selectors can introduce invalid paths during migrations, particularly when many routes are advertised across VPN tunnels or overlapping networks exist. One recommended mitigation is to use dynamic routing protocols to explicitly control which subnets are permitted and advertised through the tunnel, making A correct.

Fortinet also recommends defining the required encryption domains precisely in the phase 2 selectors. Specifying the exact network segments ensures that only designated traffic is eligible for the IPsec tunnel, making D correct. An IPsec aggregate provides redundancy but does not solve inappropriate route or encryption-domain selection. Assigning IP addresses to tunnel interfaces can support routing designs, but it is not the documented mitigation for invalid paths caused by overly broad all-zero selectors.

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

The diagnose debug authd fsso server command is the primary tool for troubleshooting communication between the FortiGate and the FSSO Collector Agent. This debug output reveals the status of the connection and the reasons for failure. The three most common connectivity issues identified by this debug are:

FortiGate cannot reach the IP address of the collector agent (Option C): The debug will show connection timeouts or " host unreachable " errors if the Layer 3 connectivity is missing.

The connection was refused / Port mismatch (Option B): If the FortiGate can reach the IP but the Collector Agent is not listening on the specified port (default 8000), the debug will display " Connection refused. " This often happens if the port configured on the FortiGate does not match the listening port on the agent.

The pre-shared key does not match (Option D): If the IP and Port are correct, the next step is authentication. If the password configured on the FortiGate does not match the one on the Collector Agent, the debug will explicitly show an " Authentication failed " or " password mismatch " error during the handshake.

Note on other options: Option A (SSL) is less common than basic connectivity/auth mismatches. Option E (Group filters) relates to user processing logic, which occurs after connectivity is established.

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.

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

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

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

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

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 C. 64.26.151.37.

The study guide explains the FortiGuard flags shown by diagnose debug rating:

D = Default

I = Initial

T = Timing

F = Failedand specifically: “F = The server is down”

So even though 121.111.236.179 has the lowest RTT in the exhibit, it has the F flag, meaning FortiGate considers that server failed/down, so it will not be chosen.

To determine which active server is selected, the FortiOS administration guide states:

“The server list is sorted first by weight. The server with the smallest RTT appears at the top of the list regardless of weight. … Therefore the top position in the list is selected based on RTT while the other positions are based on weight.”

Among the valid, non-failed choices in the exhibit:

64.26.151.37 → RTT 45

209.22.147.36 → RTT 103

96.45.33.65 → RTT 144

208.91.112.194 → RTT 107

The active server with the lowest RTT is 64.26.151.37, so that is the server FortiGate will choose.

So the verified answer is: C.