Fortinet NSE7_FSN_AR-7.6 Dumps

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.

" FortiManager offers two approaches to configuring SD-WAN: per-device management and central management. "

The guide also states:

" In per-device management, you configure SD-WAN settings for individual devices. "

Technical Explanation:

FortiManager supports two management approaches for SD-WAN deployments: per-device configuration and centralized SD-WAN management.

Option C is correct because the devices are already managed by FortiManager, and the administrator only needs to configure SD-WAN on a limited number of standalone FortiGate devices.

With per-device management, administrators can configure settings individually through Device Manager without migrating devices to a separate SD-WAN management workflow.

The administrator can access these settings through:

Device Manager → Select Managed FortiGate → Network → SD-WAN

From this interface, administrators can configure SD-WAN zones, members, performance SLAs, and SD-WAN rules according to each device ' s requirements.

The configuration changes are subsequently installed on the managed FortiGate.

Why the other options are incorrect:

Option A: Moving devices into the SD-WAN Manager workflow and using a standalone wizard is not mandatory for basic per-device configuration.

Option B: A dedicated device group is not required simply to configure SD-WAN settings on individual devices.

Option D: FortiManager supports per-device SD-WAN rule configuration without requiring SD-WAN Manager enrollment.

Architectural Consideration:

Centralized SD-WAN management becomes particularly valuable in large deployments requiring consistent templates, automation, and overlay orchestration. However, for a small environment with distinct device configurations, per-device management remains a supported and practical approach.

" The file must contain some mandatory values, such as the device serial numbers, the device names, and the associated blueprints "

Technical Explanation:

FortiManager zero-touch provisioning enables centralized deployment of FortiGate devices through device blueprints, provisioning templates, metadata variables, and model-device registration.

The exhibit shows multiple devices identified by serial numbers, including branch1_fgt, branch2_fgt, shop1_fgt, and shop2_fgt. However, the last row does not contain a device name, and the CSV file does not provide an associated device blueprint.

Option B is correct: Every device being imported must have a defined device name. FortiManager uses the name to identify and manage the corresponding model device in the device database.

Option D is correct: A device blueprint defines the provisioning information associated with a device, including templates, policies, and other configuration requirements. The guide specifically identifies the blueprint as mandatory for the documented bulk-import process.

Why the other options are incorrect:

Option A: User-defined metadata variables provide device-specific configuration values, but FortiManager does not require every optional metadata variable to have a value for every device.

Option C: IP-address metadata variables are required only when the associated configuration needs them. There is no universal requirement that every IP-address metadata field in the CSV must be populated.

Architectural Consideration: The branch_id column also matters for SD-WAN branch deployments, unless FortiManager is configured to assign branch IDs automatically. For FortiGate VM model imports, the guide additionally specifies a VM interface-count field.

To determine the path the traffic will take, we must look at the FortiGate Route Lookup Precedence (Packet Processing Flow) and the specific configurations shown in the exhibit

Analyze the Routing Precedence:

In FortiOS, when a packet arrives (and is not part of an existing session), the FortiGate performs route lookups in a specific order:

Policy Routes: Configured under config router policy (or diagnose firewall proute list). These are checked first. If a packet matches the criteria (Source, Destination, Protocol, Incoming Interface), the Policy Route is used immediately, bypassing the standard routing table.

FIB (Forwarding Information Base): If no Policy Route matches, the device looks at the standard routing table (Static, Connected, Dynamic).

Analyze the Exhibit:

Policy Route Section: The output of diagnose firewall proute list shows an active policy route (id=1).

Destination: 100.65.0.0/255.255.255.0 (Matches the network in the question).

Action: It directs traffic to gateway 10.0.4.253 via oif=6(port4).

Routing Table Section: The output of get router info routing-table database shows multiple routes for 100.65.0.0/24 (Static, OSPF, BGP) all with distance 10. The Static route (S) is currently selected (* > ) in the FIB.

Conclusion:

Because Policy Routes take precedence over the standard routing table (FIB), the FortiGate will forward the traffic using the instructions in Policy Route ID 1. It will not use the Static, BGP, or OSPF routes visible in the routing table for any traffic that matches the policy route ' s criteria (ingress port 3).

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.

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

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

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

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

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.

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.

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

Technical Explanation:

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

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

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

An appropriate configuration on FortiGate_B is:

config router bgp

config network

edit 1

set prefix 172.16.1.248 255.255.255.252

next

end

end

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

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

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

Why the other options are incorrect:

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

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

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

Architectural Consideration:

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

The correct answers are A and B.

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

That makes B correct and D incorrect.

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

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

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

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

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

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

Therefore, the verified answers are A and B.

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

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

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

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.

The correct answer is D. IKE_AUTH.

The study guide explicitly states:

“IKE_Auth exchange:

• Performs the mutual authentication of two IKE endpoints.

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

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

It also says:

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

Why the other options are wrong:

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

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

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

FortiOS Admin Guide: Static Routing, SNAT Route Change Feature

FortiManager allows much of a large branch rollout to be prepared before the physical FortiGate devices are deployed. Model devices can be created in advance and associated with the appropriate policy packages, provisioning templates, device groups, and deployment settings. Therefore, D is correct.

Metadata variables provide the per-device customization required when otherwise identical templates contain values that differ between branches, such as interface names, gateways, addresses, and health-check servers. Their per-device mappings can also be prepared in advance, making C correct.

There is no dedicated provisioning object called a “ZTP template.” ZTP instead combines model devices, provisioning templates, device blueprints, metadata variables, and CSV-based onboarding. Similarly, FortiManager uses a device blueprint rather than an object called a policy blueprint. Consequently, A and B describe nonexistent or incorrectly named provisioning mechanisms.

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

The correct answer is B. Assertion dump.

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

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

< saml:Attribute Name= " username " >

< saml:Attribute Name= " groups " >

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

Why the other options are wrong:

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

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

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

So the verified answer is: B.

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.

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

The Enterprise Firewall 7.6 Administrator Study Guide states: “You can also use the network command to configure FortiGate BGP to advertise prefixes.” Therefore, FortiGate_C must originate the required prefix by adding 100.64.2.0/24 under config router bgp → config network.

By default, the configured prefix must exactly match an active route in FortiGate_C’s routing table. The topology indicates that 100.64.2.0/24 is directly connected to FortiGate_C, so the network-import check succeeds and FortiGate_C advertises that specific prefix to FortiGate_B. FortiGate_B can then advertise the learned BGP route to FortiGate_A through the existing eBGP adjacency.

Connected-route redistribution on FortiGate_C would be too broad because it would redistribute all eligible connected routes, including the other connected subnet 100.65.3.0/24. A route-map-in on FortiGate_A can filter routes that FortiGate_A receives, but it cannot originate a route that FortiGate_C has not advertised. FortiGate_B does not need to redistribute BGP into BGP; normal BGP route propagation handles the advertisement between autonomous systems.

Example configuration on FortiGate_C:

config router bgp

config network

edit 1

set prefix 100.64.2.0 255.255.255.0

next

end

end

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.

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

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 output on FGT-01 confirms that the device is actively encapsulating traffic and sending it as ESP packets (Protocol 50) out of port1 towards the IP address 97.86.16.52. The logs show outgoing packets, which confirms FGT-01 is attempting to initiate or maintain the tunnel and that NAT-Traversal is not being used (as it uses raw ESP).

The output on FGT-02, however, displays (no packets captured). This is significant because the sniffer command diagnose sniffer packet any ' esp ' captures traffic at the network interface level (ingress), regardless of whether a matching VPN configuration exists on the receiving unit. The absence of packets proves that the ESP traffic generated by FGT-01 is physically not arriving at FGT-02 ' s interface.

This behavior is explained by two primary factors:

Option A (Blocking): An intermediate device, such as an ISP router or firewall, is dropping Protocol 50 traffic. Unlike UDP 500/4500, raw ESP is often blocked by default on many networks or legacy devices.

Option C (Routing/Misconfiguration): If the administrator configured the wrong remote peer IP on FGT-01, the packets are being routed to a different destination entirely. Consequently, they never arrive at FGT-02 to be captured.

Option B is incorrect because even without a configured VPN tunnel, the sniffer would still display the incoming ESP packets if they were reaching the interface. Option D is incorrect because FGT-01 is sending ESP, making ' esp ' the correct filter.

The exhibit shows these key lines:

handle_req-Rcvd auth req ... for jsmith in Lab

start_search_dn-base: ' DC=TAC,DC=ottawa,DC=fortinet,DC=com ' filter:sAMAccountName=jsmith

get_all_dn-Found DN 1:CN=John Smith,CN=Users,DC=TAC,DC=ottawa,DC=fortinet,DC=com

The study guide explicitly shows the same LDAP real-time debug pattern and says the request line includes the LDAP server object name:

handle_req-Rcvd auth req ... for jsmith in Lab ...

That supports A: Lab is the configured LDAP server name being used for this authentication request.

For the LDAP flow stage, the study guide states:

“An fnbamd_ldap_build_dn_search_req-base message indicates that FortiGate is performing step two: searching for the user in the LDAP tree.” It also says that if the LDAP server finds the user, the output shows the user’s full DN.

That matches the exhibit’s start_search_dn-base ... filter:sAMAccountName=jsmith and Found DN ... CN=John Smith... lines, so D is correct.

Why the other options are wrong:

B is wrong because the exhibit shows FortiOS has found the user DN CN=John Smith,..., but that does not mean the user is already authenticating with that DN in this step. The study guide says this DN is discovered in step 2, and only in step 3 does FortiGate bind using the user DN.

C is wrong because the exhibit is showing step 2 (Search Request), not step 3 (Bind Request). The study guide separates these steps clearly and shows step 3 with fnbamd_ldap_build_userbind_req-Trying DN ... and __ldap_build_bind_req-Binding to ' CN=John Smith,... '

To solve this high CPU usage scenario involving the ipsengine, we must understand the specific functions of the diagnose test application ipsmonitor commands shown in the troubleshooting steps.

Analyze the Situation:

Exhibit: The diagnose sys top output shows the ipsengine process is in a run state (R) consuming 99% CPU.

Previous Action: The administrator already ran diagnose test application ipsmonitor 5.

Result: The CPU usage did not drop.

Understand the Commands:

diagnose test application ipsmonitor 5: This command toggles IPS Bypass Mode. When enabled, the IPS engine lets traffic pass through without inspection.

Implication: If the CPU was high due to traffic volume, enabling bypass would drop the CPU load immediately.

Failure: Since the CPU remained at 99% after bypass, the ipsengine process is likely frozen, stuck, or in an internal infinite loop unrelated to the current traffic flow. The process itself is the problem, not the traffic volume.

Evaluate the Solution (Option B):

diagnose test application ipsmonitor 2: This command toggles the IPS engine ' s Enable/Disable status.

Because the engine is stuck (bypass failed to relieve pressure), the " Immediate action " required is to stop or restart the process entirely.

Running option 2 effectively disables/kills the stuck IPS engine instance, which will immediately drop the CPU usage to near zero. (It can then be toggled again to restart it).

Why other options are incorrect:

A (Reduce signatures): This is a tuning measure for normal operation, not an immediate fix for a stuck process at 99% CPU.

C (Disable IPS on policies): This is a configuration change that takes time and requires a commit; it is not the most immediate diagnostic tool available.

D (Bypass all IPS engines): This describes the action of command 5 (Bypass), which the prompt explicitly states was already performed and failed.

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 study guide explicitly explains the diagnose debug rating table and says that for each server IP, the output shows “The round trip delay”

That means the RTT value represents the time it takes for FortiGate to send a request and receive the reply from that FortiGuard server.

The FortiOS administration guide also confirms this by stating:

“Each server is probed for Round Trip Time (RTT) every two minutes.”

Why the other options are wrong:

B is wrong because packet loss is shown separately by Curr Lost and Total Lost, while RTT is the round-trip delay

C is wrong because license-validation behavior is indicated by flags such as I = Initial, not by the RTT value itself

D is wrong because the documents do not say RTT starts at a fixed value of 10; it is measured dynamically as round-trip delay

So the verified answer is: A.

To understand why Type 5 LSAs (AS External LSAs) are missing from the Link-State Database (LSDB), we must look at how OSPF generates and propagates them:

A. There is no autonomous system border router (ASBR) in the network:

Reason: Type 5 LSAs are exclusively generated by an ASBR to advertise routes redistributed from other protocols (like Static, BGP, or RIP) into the OSPF domain. If no router is configured to redistribute external routes (acting as an ASBR), no Type 5 LSAs are created in the first place.

C. The local router is located in a stub area:

Reason: By definition, a Stub Area (and a Totally Stubby Area) prevents Type 5 LSAs from entering. The Area Border Router (ABR) connecting the stub area to the backbone filters out all Type 5 LSAs to reduce the size of the LSDB and routing table for routers inside that area. Instead, a default route is usually injected.

Why other options are incorrect:

B: While database filtering exists, standard prefix-list filtering typically affects the routing table (RIB) generation, not the underlying LSDB propagation of Type 5 LSAs, or it is less common than the architectural reasons (Stub/No ASBR).

D: IP Protocol 89 is the transport for OSPF itself. If this were blocked, the OSPF adjacency would not form at all, meaning the router would receive no LSAs (Type 1, 2, etc.), not specifically just Type 5.

The Enterprise Firewall 7.6 Administrator Study Guide ' s multiregion ADVPN example uses iBGP inside each region and eBGP between the two regions. On the hubs ' spoke-facing ADVPN phase 1 interfaces, Fortinet configures auto-discovery-sender enable so the hub can initiate ADVPN shortcut negotiation. It also configures network-id to identify the corresponding overlay. Therefore, B matches the documented configuration.

auto-discovery-receiver is associated with the spoke role and does not pair with remote-ip for this hub configuration. The separate hub-to-hub IPsec tunnel uses auto-discovery-forwarder enable to forward ADVPN shortcut information between regions. However, remote-as is a BGP neighbor parameter, not an IPsec phase 1 parameter. Consequently, D combines settings belonging to different configuration contexts.

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

The correct answer is C.

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

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

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

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

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

Why the other options are wrong:

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

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

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

So the verified answer is: C.

Intermittent behavior (working sometimes, failing others) points to resource or connectivity fluctuations rather than static misconfigurations.

B. Check that FortiGate is not entering conserve mode:

Reason: When FortiGate enters Conserve Mode (due to high memory usage), it changes its inspection behavior to save resources. Depending on the av-failopen setting, it may either bypass inspection (allowing blocked sites) or drop traffic (blocking valid sites) temporarily until memory recovers. This flapping between states causes intermittent filtering issues.

D. Check that the communication between FortiGate and FortiGuard is stable:

Reason: The Web Filter engine relies on real-time queries to the FortiGuard Distribution Network (FDN) to categorize URLs that are not in the local cache. If the internet connection or the specific path to FortiGuard is unstable (packet loss, latency), queries will time out. This results in " Rating Errors, " which can block or allow traffic unpredictably based on the " Allow websites when a rating error occurs " setting.

Why other options are incorrect:

A: A mismatch in inspection mode (e.g., Profile set to Proxy, Policy set to Flow) is a static configuration error. It would typically result in the profile not being selectable or consistently failing/not applying, rather than working intermittently.

C: If the wrong port is mapped (e.g., HTTP on 8080 is not mapped), the inspection engine will consistently ignore traffic on that port. It would not be intermittent.

The correct answers are C and D.

The key clue is the command itself:

diagnose debug application fssod -1

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

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

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

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

Why the other options are wrong:

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

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

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

So the verified answers are: C, D.

The Internet Key Exchange version 2 (IKEv2) protocol simplifies the negotiation process compared to IKEv1. It is defined by a specific sequence of message exchanges to establish a secure IPsec tunnel.

The correct chronological order of the IKEv2 exchanges is:

IKE_SA_INIT (Initial Exchange):

This is the first exchange. It negotiates the security parameters for the IKE Security Association (IKE SA), sends nonces, and performs the Diffie-Hellman key exchange. At the end of this exchange, the communication is encrypted, but the peers are not yet authenticated.

IKE_AUTH (Authentication Exchange):

This is the second exchange. It authenticates the previous messages, exchanges identities and certificates (if used), and establishes the first Child SA (the actual IPsec Security Association used for data traffic).

CREATE_CHILD_SA (Subsequent Exchanges):

This exchange occurs after the IKE SA and the initial Child SA are established. It is used to create additional Child SAs (for different traffic selectors) or to perform re-keying for the IKE SA or existing Child SAs.

Why other options are incorrect:

A & B: Incorrect because CREATE_CHILD_SA cannot happen before the SA is initialized (IKE_SA_INIT) and authenticated (IKE_AUTH).

D: Incorrect because IKE_AUTH cannot occur before IKE_SA_INIT.

Therefore, the protocol flow is IKE_SA_INIT $\rightarrow$ IKE_AUTH $\rightarrow$ CREATE_CHILD_SA.

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.

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

The correct answer is B.

The study guide explicitly states that slabs are used by the kernel: “The kernel memory slabs are collections of objects with a common purpose. The kernel uses them to store information in memory.”

It also gives the exact calculation method: “Total slab size = available objects x object size” and explains that in the diagnose hardware sysinfo slab output, the columns are active objects, available objects, and object size

From the exhibit:

tcp_session 3 5 1500 ...

available objects = 5

object size = 1500

So:

Total slab size = 5 × 1500 = 7500

That matches option B.

Why the other options are wrong:

A: ip_session 10 10 1408 ... gives 10 × 1408 = 14080, but slabs are associated with the kernel, not user space

C: ip6_session 5 0 1472 ... gives 0 × 1472 = 0, not 1472

D: UDPv6 15 10 1408 ... gives 10 × 1408 = 14080, but again slabs are associated with the kernel, not user space

So the verified answer is B.

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 ADVPN shortcut negotiation begins after traffic from Spoke 1 to Spoke 2 initially travels through the hub. When the hub detects that both spokes can establish a more direct connection, the hub—not Spoke 1—sends the first control message: a shortcut offer to Spoke 1.

The SD-WAN 7.6 Enterprise Administrator Study Guide then states: “Spoke 1 acknowledges the shortcut offer by sending a shortcut query to the hub.” Therefore, the first message that Spoke 1 sends in response is the shortcut query, making option A correct.

The hub subsequently forwards that query to Spoke 2. Spoke 2 responds with a shortcut reply, which the hub forwards back to Spoke 1. After Spoke 1 receives the reply containing the necessary peer information, Spoke 1 and Spoke 2 begin IKE negotiation and establish the dynamic spoke-to-spoke shortcut tunnel. Consequently, the shortcut reply occurs later and originates from Spoke 2, while the offer originates from the hub. “Shortcut forward” describes the hub’s forwarding action rather than Spoke 1’s first response. This behavior is part of Fortinet’s ADVPN shortcut architecture.

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

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

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

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

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

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.

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

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

Analyze Neighbor Status:

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

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

Neighbor 10.127.0.75:

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

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

Determine the Cause:

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

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

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

The correct answer is B.

The study guide explicitly states: “IKE version 2 does not interoperate with IKE version 1, but they share enough of the header format that both versions can unambiguously operate over the same UDP port.”

That directly proves B.

Why the other options are wrong:

A is wrong because the study guide shows authentication methods as Asymmetric for IKEv2 and Symmetric for IKEv1

C is wrong because the study guide does not say they use the same TCP port; instead, it specifically says they can operate over the same UDP port

D is wrong because the study guide states: “IKEv2 does not use the concept of phase 1 or phase 2”, even though FortiOS CLI/GUI still uses those terms for configuration purposes

The traffic matches service 2’s address criteria: 10.0.1.125 belongs to the configured source range 10.0.1.0–10.0.1.255, and 128.66.0.125 belongs to the destination range 128.66.0.0–128.66.255.255. Service 2 lists port7 and port8 as selected SLA members and uses round-robin load balancing.

However, the SD-WAN guide states: “SD-WAN requires a valid route in the forwarding information base (FIB) so the member can be used to steer traffic.” The routing table contains routes through port7 and port8 only for 10.0.1.0/24. It contains no route to 128.66.0.125 through either member.

The only route covering the destination is the default route, which has equal-cost paths through port1 and port2. Consequently, port7 and port8 cannot be used for this flow despite being SLA-selected. FortiGate skips the unusable explicit SD-WAN rule and processes the traffic through the implicit rule using standard FIB routing. Therefore, option A is correct. Options B and C incorrectly assume that selected overrides route availability, while option D is incorrect because valid default routes exist.

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.