Sign in
Home/Fortinet/Secure Networking 7.6 Architect/Free questions

Fortinet NSE 7 - Secure Networking 7.6 Architect — Free Practice Questions

10 free sample questions from a bank of 97, with the correct answers and explanations. No signup required — start practising right now.

1In the context of SD-WAN, the terms underlay and overlay are commonly used to categorize links. Which two statements about underlay and overlay links are correct? (Choose two.)
  • Overlay links provide routing flexibility.
  • Only wired connections can be used as underlay links.
  • A VLAN is a type of overlay link.
  • FortiLink interface is considered an underlay link.
  • Wireless connections can be used to build overlay links.
Answer: A, E

The short version

A and E — overlays add routing flexibility and can be built over wireless as well as wired transport.

Key concepts in this question

  • Underlay: the transport network (MPLS, broadband, LTE/5G, satellite) carrying packets between sites.
  • Overlay: a logical tunnel, normally IPsec, built across one or more underlays.
  • Transport independence: the overlay works over wired or wireless paths.

Why A and E are correct

Because overlays are logical tunnels, FortiGate can steer traffic into them dynamically using SD-WAN rules, SLA probes, and policy. That separation from physical transport provides routing flexibility. LTE, 5G, and satellite can carry the tunnel like a wired circuit, so wireless connections are valid overlay transport and E is correct.

Why the others are wrong

  • B. Underlays are not limited to wired media; wireless WAN links are common.
  • C. A VLAN is Layer 2 segmentation, not an SD-WAN overlay tunnel.
  • D. FortiLink connects a FortiGate to FortiSwitch/FortiAP; it is not an underlay WAN link.

NSE7_FSN_AR-7.6 exam tip

Underlay = transport, overlay = logical tunnel. Any transport, including wireless, can sit below an overlay.

2You have a FortiGate configuration with three user-defined SD-WAN zones and two members in each of these zones. One SD-WAN member is no longer in use in health-check and SD-WAN rules. You want to delete it. What happens if you delete the SD-WAN member from the FortiGate GUI?
  • FortiGate accepts the SD-WAN member deletion with no further action.
  • FortiGate displays an error message. SD-WAN zones must contain at least two members.
  • FortiGate accepts the deletion and removes static routes as required.
  • FortiGate accepts the deletion and places the member in the default SD-WAN zone.
Answer: A

The short version

A — an unreferenced SD-WAN member is deleted cleanly with no extra action.

Key concepts in this question

  • Member references: health checks, SD-WAN rules, and firewall policies can depend on a member.
  • Zone membership: SD-WAN zones have no fixed member count.
  • Delete validation: FortiGate checks dependencies before removing an interface from a zone.

Why A is correct

The member is no longer used by any health check or SD-WAN rule, so no dependency blocks its removal. FortiGate accepts the deletion and removes the interface from the zone. The remaining members stay unchanged, and no automatic route or zone reassignment occurs because nothing still points at the deleted member.

Why the others are wrong

  • B. There is no two-member minimum. A zone can be reduced to one member.
  • C. Deleting an SD-WAN member does not trigger static-route cleanup; static routes are independent objects.
  • D. FortiGate does not move a deleted member into the default SD-WAN zone; it removes it.

NSE7_FSN_AR-7.6 exam tip

If nothing references the member, deletion just succeeds. No minimum and no automatic route cleanup.

3Refer to the exhibits. An OSPF peer is advertising route 172.16.52.0/24. The local FortiGate is configured with an inbound distribution list that allows the 172.16.0.0/14 network to be injected into its routing table. However, the 172.16.52.0/24 subnet cannot be seen in the FIB. Which two steps can the administrator of the local FortiGate take to ensure that the advertised 172.16.52.0/24 subnet will be injected into the routing table? (Choose two.)
Fortinet NSE 7 - Secure Networking 7.6 Architect question 3
  • Modify the default prefix-list behavior from implicit deny to implicit allow.
  • Change the ge value to 17.
  • Add another entry to the prefix list to specifically allow the 172.16.52.0/24 network.
  • Change the le value to 16.
Answer: B, C

The short version

B and C — the prefix list matches only the exact /16, so open it with ge 17 or add an explicit /24 entry.

Key concepts in this question

  • Prefix-list matching: with ge and le unset, an entry matches only the exact prefix length.
  • ge/le range: ge sets the minimum mask length and le the maximum; a /24 needs a range including 24.
  • Implicit deny: a prefix list ends with an implicit deny that cannot be changed to implicit allow.

Why B and C are correct

The exhibit shows set prefix 172.16.0.0 255.255.0.0 with unset ge and unset le, which matches only /16. The advertised 172.16.52.0/24 therefore fails the distribute list and never reaches the FIB. Changing ge to 17 matches every subnet of 172.16.0.0/16 with a mask from /17 through /32, including /24. Alternatively, an entry for 172.16.52.0/24 permits it directly.

Why the others are wrong

  • A. FortiOS prefix lists always end with an implicit deny; that cannot be switched to implicit allow.
  • D. Setting le to 16 restricts the match to /16 or shorter masks, so a /24 still does not match.

NSE7_FSN_AR-7.6 exam tip

Unset ge and le mean exact length only. To permit more-specific routes, set ge to the desired minimum mask.

4Refer to the exhibit. An ADVPN network is shown. You must configure an ADVPN using IBGP for each local region and EBGP across regions to connect Overlay 1 with Overlay 2. Which two options must you configure in the Hub2Hub BGP peering? (Choose two.)
Fortinet NSE 7 - Secure Networking 7.6 Architect question 4
  • set. ebgp-enforce-multihop enable
  • set. ibgp-enforce-multihop advpn
  • set. attribute-unchanged next-hop
  • set. next-hop-self enable
Answer: A, C

The short version

A and C — the inter-region Hub2Hub eBGP peering needs multihop and must preserve the original next hop.

Key concepts in this question

  • iBGP inside a region, eBGP between regions: Hub A is AS 65100 and Hub B is AS 65200, so Hub2Hub is eBGP.
  • Multihop peering: the hubs peer over 10.255.255.1 and .2, which are not directly connected.
  • Next-hop preservation: attribute-unchanged keeps the advertising spoke's next hop for shortcut selection.

Why A and C are correct

Because the hubs are in different ASes and peer across overlay addresses, not a directly connected link, ebgp-enforce-multihop enable is required to establish the eBGP session. With attribute-unchanged next-hop, the hubs do not rewrite the next hop when advertising routes between regions. Spokes therefore get the original next hop needed to build direct ADVPN shortcuts.

Why the others are wrong

  • B. ibgp-enforce-multihop advpn applies to iBGP, but Hub2Hub between AS 65100 and AS 65200 is eBGP.
  • D. next-hop-self would replace the original next hop with the hub's address, preventing correct shortcut selection.

NSE7_FSN_AR-7.6 exam tip

Hub-to-hub across ASes = eBGP multihop plus unchanged next hop; never next-hop-self.

5Refer to the exhibit. You want to configure SD-WAN on a network, as shown in the exhibit. The network contains many FortiGate devices. Some are used as next-generation firewalls (NGFW), and some are installed with extensions such as FortiSwitch, FortiAP, or FortiExtender. Which factors should you consider when planning your deployment?
Fortinet NSE 7 - Secure Networking 7.6 Architect question 5
  • You should exclude the FortiGate devices with FortiLink connection from the SD-WAN topology.
  • You should build multiple SD-WAN topologies. Each topology should contain only one type of extension.
  • You can build an SD-WAN topology that includes all devices. The hubs can be FortiGate devices with FortiExtender.
  • You can build an SD-WAN topology that includes all devices. The hubs must be devices without extensions.
Answer: C

The short version

C — one SD-WAN topology can include every device, and a hub may have a FortiExtender.

Key concepts in this question

  • Mixed topology: NGFW-only sites and sites with FortiSwitch, FortiAP, or FortiExtender can share one design.
  • Hub role: any supported FortiGate can be a hub; extension hardware does not disqualify it.
  • FortiExtender: provides cellular or additional WAN connectivity usable as an SD-WAN member.

Why C is correct

The exhibit shows a FortiExtender hub alongside branches with FortiSwitches, FortiAPs, and plain FortiGates. FortiManager can model all these roles in one SD-WAN topology. A FortiExtender-equipped FortiGate can be a hub, using the extender as a WAN path, while other devices join as spokes. There is no need to split the design by extension type or keep extensions off hubs.

Why the others are wrong

  • A. FortiLink-connected FortiGates are normal SD-WAN participants; do not exclude them.
  • B. Multiple topologies are not required; a topology may mix extension types.
  • D. Hubs need not be extension-free; a FortiExtender-equipped FortiGate is valid.

NSE7_FSN_AR-7.6 exam tip

Do not split by extension type. One topology can mix all devices, and hubs can carry FortiExtender.

6Refer to the exhibit. For your ZTP deployment, you review the CSV file shown in exhibit and note that it is missing important information. Which two elements must you change before you can import it into FortiManager? (Choose two.)
Fortinet NSE 7 - Secure Networking 7.6 Architect question 6
  • You must define a name for each device.
  • You must define a value for each device and each user-defined metadata variable.
  • You must associate a device blueprint with each device.
  • You must define a value for each device and each metadata variable that defines an IP address.
Answer: A, C

The short version

A and C — every ZTP row needs a device name and an associated device blueprint.

Key concepts in this question

  • Device name: identifies each FortiGate in FortiManager and in the provisioning record.
  • Device blueprint: tells FortiManager which model/template logic and configuration plan to apply.
  • Metadata: optional variables for site-specific values; they do not all need a value.

Why A and C are correct

The CSV shows the last row, FGVM02TM24010735, with an empty name field while other rows have names such as branch1_fgt. A ZTP import needs a name for each device, so that row must be completed. The file also lacks a blueprint association for each device; FortiManager must know which blueprint governs each entry for correct provisioning. Adding the names and a blueprint per device makes the file importable.

Why the others are wrong

  • B. User-defined metadata is optional; not every custom variable needs a value.
  • D. Metadata defining an IP address does not always require a value. Unused interfaces can remain blank or inherit defaults.

NSE7_FSN_AR-7.6 exam tip

For a ZTP CSV, check the two identifiers first: a unique device name and a valid blueprint assignment.

7Which two troubleshooting steps should you perform if you encounter issues with intermittent web filter behavior? (Choose two.)
  • Check that the inspection mode configured for the web filter profile matches that of the firewall policy where it is applied.
  • Check that the correct port is mapped to HTTP in the Protocol Options.
  • Check that the communication between FortiGate and FortiGuard is stable.
  • Check that FortiGate is not entering conserve mode.
Answer: C, D

The short version

C and D — intermittent web filtering points to unstable FortiGuard communication or conserve mode.

Key concepts in this question

  • FortiGuard rating lookup: web filter decisions depend on category and rating responses.
  • Conserve mode: memory pressure disables or bypasses resource-heavy inspection features.
  • Intermittent versus deterministic faults: configuration mismatches fail consistently; flaky behavior suggests reachability or resource pressure.

Why C and D are correct

If FortiGuard connectivity is unstable, some rating requests succeed and others time out, so the same site may be handled inconsistently. When FortiGate enters conserve mode, memory-saving actions can stop or bypass proxy and content inspection, so filtering works until resources tighten. Checking both addresses the two common causes.

Why the others are wrong

  • A. An inspection-mode mismatch between profile and policy is a configuration error; it prevents consistent operation rather than causing random failure.
  • B. Incorrect HTTP port mapping in Protocol Options can break protocol detection, but it is static and does not explain intermittent behavior.

NSE7_FSN_AR-7.6 exam tip

Intermittent filtering: test FortiGuard reachability first, then check for conserve mode.

8Refer to the exhibit. The output of diagnose sys session list command is shown. If the HA ID for the primary device is 0, what happens if the primary fails and the secondary becomes the primary?
Fortinet NSE 7 - Secure Networking 7.6 Architect question 8
  • The session state is preserved but the kernel will re-evaluate the session because the routing information will be flushed.
  • The session is synchronized with the secondary device, however, because application control is applied, the session is marked dirty and has to be re-evaluated after failover.
  • The session will be removed from the session table of the secondary device because the TCP session is not yet fully established.
  • The session continues to permit traffic on the new primary device after failover, without requiring the client to restart the session with the server.
Answer: D

The short version

D — the synchronized session continues on the new primary without the client restarting.

Key concepts in this question

  • proto_state=01: in this output the TCP session is ESTABLISHED, not SYN_SENT; the connection has been up for 73 seconds.
  • synced flag: proves the session was synchronized from the primary to the secondary.
  • HA failover: the secondary takes over the primary HA ID and continues forwarding synchronized sessions.

Why D is correct

The output shows proto_state=01 with duration=73 and the synced flag. This is an established TCP session that has been synchronized to the secondary. On failover, the secondary already has the session state, including NAT and forwarding information. Traffic therefore continues through the new primary without tearing down the connection, and the client need not restart.

Why the others are wrong

  • A. The state is preserved, but failover does not force kernel re-evaluation solely because routing information changes.
  • B. Application control is not applied: the output shows app_list=0 and app=0, so the session is not marked dirty by application control.
  • C. This is the key trap: proto_state=01 is ESTABLISHED, not SYN_SENT, and synced proves the session was copied to the secondary. It is not removed for being unestablished.

NSE7_FSN_AR-7.6 exam tip

Read proto_state with synced. ESTABLISHED plus synced means seamless failover; SYN_SENT would not sync.

9Refer to the exhibit. How does FortiGate handle the traffic with the source IP address 10.0.1.125 and the destination IP address 128.66.0.125?
Fortinet NSE 7 - Secure Networking 7.6 Architect question 9
  • FortiGate routes the traffic flow according to the forwarding information base (FIB).
  • FortiGate drops the traffic flow.
  • FortiGate steers the traffic flow through port7.
  • FortiGate load balances the traffic flow through port7 and port8.
Answer: A

The short version

A — neither member has a route to the destination, so FortiGate falls back to the FIB.

Key concepts in this question

  • Member route check: a member is eligible only with a valid route to the destination.
  • Service2 match: source 10.0.1.0/24 and destination 128.66.0.0/24 select the rule, whose members are port7 and port8.
  • FIB fallback: when no member can forward the flow, normal routing-table lookup decides egress.

Why A is correct

Traffic from 10.0.1.125 to 128.66.0.125 matches Service2, whose members are port7 and port8. The table shows only connected 10.0.1.0/24 and 10.0.2.0/24 on those ports; there is no route to 128.66.0.125 through either. FortiOS therefore cannot select those members. The default route via port1/port2 remains available, so FortiGate performs a normal FIB lookup.

Why the others are wrong

  • B. The flow is not dropped; the default route via port1/port2 provides a path.
  • C. Port7 has no route to 128.66.0.125, so Service2 cannot steer traffic out of port7.
  • D. Load balancing is impossible because both members fail the same route check.

NSE7_FSN_AR-7.6 exam tip

An SD-WAN rule cannot override the routing table; if its members lack a route, the flow uses the FIB.

10You use the FortiManager SD-WAN overlay orchestrator to prepare an SD-WAN deployment. Using information provided through the SD-WAN overlay template wizard, FortiManager creates templates that are ready to install on the spoke and hub devices. Which three templates are created by the SD-WAN overlay orchestrator for a spoke device? (Choose three.)
  • CLI template
  • Static route template
  • Rules template
  • BGP template
  • IPsec tunnel template
Answer: A, D, E

The short version

A, D and E — the spoke bundle is a CLI template, a BGP template, and an IPsec tunnel template.

Key concepts in this question

  • SD-WAN overlay orchestrator: FortiManager wizard that builds hub and spoke configuration from topology inputs.
  • CLI template: carries device-specific and role-specific commands.
  • BGP template: configures underlay and overlay BGP peering.
  • IPsec tunnel template: creates Phase 1 and Phase 2 definitions for overlay tunnels.

Why A, D and E are correct

For a spoke, it generates a CLI template for device customization, a BGP template for dynamic routing, and an IPsec tunnel template for overlay connections. Together they provide local settings, routing adjacency, and encrypted tunnels. The wizard builds the spoke configuration without static-route or rules templates.

Why the others are wrong

  • B. The orchestrator uses dynamic BGP routing, so a static route template is not in the generated spoke set.
  • C. A rules template is not created for the spoke; SD-WAN rule and policy design is separate.

NSE7_FSN_AR-7.6 exam tip

Remember the spoke trio: CLI, BGP, IPsec tunnel. Static routes and rules templates are not in it.

Want the full bank of 97 questions for Fortinet NSE 7 - Secure Networking 7.6 Architect? See all practice exams.