100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 220
Select THREE correct elements of a safe remedy-and-evidence plan for the Internet-service destination matching case. Following a production change affecting Harborlight Industrial in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: A SaaS provider changes IP ranges and manually maintained destination subnets become stale. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Investigate encapsulation overhead and path MTU/MSS handling for the affected overlay.
- The service policy follows the maintained application/destination identity instead of stale static subnets.
- Use the supported Internet Service Database or application-based match where appropriate for the steering rule.
- Simulate a destination change within the selected service and inspect matching service IDs and egress member.
- Compare advertised and received routes for the missing private prefix and confirm forwarding.
- Eligible traffic can use a direct spoke shortcut while retaining hub fallback.
Explanation
Correct Answers
B:The service policy follows the maintained application/destination identity instead of stale static subnets. This confirms the case-specific path or security boundary.
C:Correct remediation element: Use the supported Internet Service Database or application-based match where appropriate for the steering rule. It addresses Static IP lists no longer represent the intended SaaS service. [Case R161-C044; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0220.]
D:Correct verification element: Simulate a destination change within the selected service and inspect matching service IDs and egress member. This independently measures whether the intended change works. [Case R161-C044; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0220.]
Incorrect Answers
A:That intervention addresses IPsec tunnel MTU impact: Large application payloads stall over an IPsec overlay while small pings pass. The case-specific requirement is: Use the supported Internet Service Database or application-based match where appropriate for the steering rule. Verify it with: Simulate a destination change within the selected service and inspect matching service IDs and egress member.
E:That intervention addresses BGP route visibility after tunnel recovery: IPsec becomes healthy but a private subnet remains unreachable because its prefix was never advertised. The relevant verification here is: Simulate a destination change within the selected service and inspect matching service IDs and egress member.
F:That intervention addresses ADVPN spoke-to-spoke shortcut: Traffic between two branches traverses a distant hub despite both having eligible underlays. The case-specific requirement is: The service policy follows the maintained application/destination identity instead of stale static subnets. Verify it with: Simulate a destination change within the selected service and inspect matching service IDs and egress member.
Question 221
Which corrective action MOST DIRECTLY addresses the observed SD-WAN local-out control problem within the approved change scope? During a scoped cross-border operations deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The change ticket limits modifications to the affected production application and requires a reversible test.
- Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub.
- Make the protected traffic selectors match the approved overlay encryption scope.
- Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service.
- Validate health signaling and route preference over both hub overlays, then correct the preference condition.
Explanation
Correct Answer
C:Correct: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The targeted remedy is Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. This addresses self-originated local-out traffic is controlled separately from ordinary forwarded flows. Confirm it by: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0221.]
Incorrect Answers
A:That intervention addresses Overlay BGP loopback scalability: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The case-specific requirement is: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
B:That intervention addresses IPsec selector scope: IKE phase one succeeds but traffic selectors prevent the intended private subnet from crossing the overlay. The case-specific requirement is: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
D:That intervention addresses Dual-hub routing failover evidence: A spoke sees both hub routes but continues preferring the failed region when the primary becomes unhealthy. The case-specific requirement is: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
Question 222
Which independent diagnostic check best validates that the SD-WAN local-out control repair works? During a scoped cross-border operations deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The change ticket limits modifications to the affected production application and requires a reversible test.
- Compare one established session and one new session after the approved route change.
- Inspect peer endpoints and next-hop resolution after both spokes connect concurrently.
- Trace route lookup for the target prefix and compare with the SD-WAN policy match.
- Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
Explanation
Correct Answer
D:Correct: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. This directly tests the failure mechanism and the required acceptance evidence: Local service traffic follows its approved egress without changing customer session routing. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0222.]
Incorrect Answers
A:Incorrect for this case: Compare one established session and one new session after the approved route change. concerns the separate issue of Session persistence after route change (Existing SNAT flows remain on the old egress after a route change while new sessions use the new link.). It does not directly establish Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. The case-specific evidence is Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0222.]
B:That intervention addresses BGP loopback duplicate identity: Two spokes share a loopback address, causing unstable BGP peering and route attribution. The relevant verification here is: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
C:That intervention addresses Policy route overriding intended SD-WAN path: A destination uses an unexpected interface despite a healthy specific SD-WAN service rule. The relevant verification here is: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
Question 223
What observable result would show that the intended SD-WAN local-out control behavior has been restored? During a scoped cross-border operations deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The change ticket limits modifications to the affected production application and requires a reversible test.
- Operators distinguish session persistence from a failed routing-policy update.
- Dynamic routing supports the intended scalable ADVPN 2.0 deployment.
- The destination resolves through the intended zone and authorized member.
- Local service traffic follows its approved egress without changing customer session routing.
Explanation
Correct Answer
D:Correct: Local service traffic follows its approved egress without changing customer session routing. That result demonstrates the requested controlled repair and avoids the failure mode: Self-originated local-out traffic is controlled separately from ordinary forwarded flows. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0223.]
Incorrect Answers
A:That intervention addresses Session persistence after route change: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The case-specific requirement is: Local service traffic follows its approved egress without changing customer session routing. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
B:That intervention addresses BGP-on-loopback for ADVPN 2.0: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The case-specific requirement is: Local service traffic follows its approved egress without changing customer session routing. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
C:Incorrect for this case: The destination resolves through the intended zone and authorized member. concerns the separate issue of Static zone route missing (A security policy allows traffic on an SD-WAN zone but its destination has no usable route through that zone.). It does not directly establish Local service traffic follows its approved egress without changing customer session routing. The case-specific evidence is Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0223.]
Question 224
Which failure mechanism BEST explains the SD-WAN local-out control observation before a repair is attempted? During a scoped cross-border operations deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The change ticket limits modifications to the affected production application and requires a reversible test.
- Unequal route policies across overlays cause reachability changes during failover.
- Self-originated local-out traffic is controlled separately from ordinary forwarded flows.
- Hub-only forwarding persists without a qualified ADVPN shortcut.
- The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
Explanation
Correct Answer
B:Correct: Self-originated local-out traffic is controlled separately from ordinary forwarded flows. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0224.]
Incorrect Answers
A:The Per-overlay route consistency diagnosis does not explain the observed case: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The supported diagnosis is: Self-originated local-out traffic is controlled separately from ordinary forwarded flows.
C:Incorrect diagnosis: this describes a different operational mechanism (ADVPN spoke-to-spoke shortcut), not the documented observation (FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic.). The supported case diagnosis is Self-originated local-out traffic is controlled separately from ordinary forwarded flows. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0224.]
D:The BGP-on-loopback for ADVPN 2.0 diagnosis does not explain the observed case: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The supported diagnosis is: Self-originated local-out traffic is controlled separately from ordinary forwarded flows.
Question 225
Select TWO correct elements of a safe remedy-and-evidence plan for the SD-WAN local-out control case. During a scoped cross-border operations deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The change ticket limits modifications to the affected production application and requires a reversible test.
- Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
- Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service.
- Compare one established session and one new session after the approved route change.
- Add or correct the scoped route to the SD-WAN zone and confirm member selection remains governed by rules.
- The learned prefix resolves to a valid overlay member and carries packets.
Explanation
Correct Answers
A:Correct verification element: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. This independently measures whether the intended change works. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0225.]
B:Correct remediation element: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. It addresses Self-originated local-out traffic is controlled separately from ordinary forwarded flows. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0225.]
Incorrect Answers
C:Incorrect for this case: Compare one established session and one new session after the approved route change. concerns the separate issue of Session persistence after route change (Existing SNAT flows remain on the old egress after a route change while new sessions use the new link.). It does not directly establish Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. The case-specific evidence is Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. [Case R161-C045; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0225.]
D:That intervention addresses Static zone route missing: A security policy allows traffic on an SD-WAN zone but its destination has no usable route through that zone. The case-specific requirement is: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
E:That intervention addresses Overlay route recursive next hop: A BGP-learned LAN prefix appears in the control plane but fails recursive resolution to a usable tunnel. The case-specific requirement is: Local service traffic follows its approved egress without changing customer session routing. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
Question 226
Which corrective action MOST DIRECTLY addresses the observed SD-WAN local-out control problem within the approved change scope? Following a production change affecting Cedarline Retail in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. Unrelated services are still operating, so the immediate response must isolate the failing control for the cloud PoP and private hub path without disabling unrelated protections.
- Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service.
- Align route advertisement and preferred-path policy across both reviewed overlays.
- Enable and validate the supported ADVPN shortcut behavior under the approved SD-WAN architecture.
- Investigate encapsulation overhead and path MTU/MSS handling for the affected overlay.
Explanation
Correct Answer
A:Correct: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The targeted remedy is Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. This addresses self-originated local-out traffic is controlled separately from ordinary forwarded flows. Confirm it by: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. [Case R161-C046; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0226.]
Incorrect Answers
B:That intervention addresses Per-overlay route consistency: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The case-specific requirement is: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
C:That intervention addresses ADVPN spoke-to-spoke shortcut: Traffic between two branches traverses a distant hub despite both having eligible underlays. The case-specific requirement is: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
D:That intervention addresses IPsec tunnel MTU impact: Large application payloads stall over an IPsec overlay while small pings pass. The case-specific requirement is: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
Question 227
Which independent diagnostic check best validates that the SD-WAN local-out control repair works? Following a production change affecting Cedarline Retail in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. Unrelated services are still operating, so the immediate response must isolate the failing control for the cloud PoP and private hub path without disabling unrelated protections.
- Fail over each overlay individually and inspect forward and return paths for the same application flow.
- Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
- Compare allowed and denied BGP prefix sets before and after updating the filter.
- Disable the primary-hub path and check secondary SA, route and private-app reachability.
Explanation
Correct Answer
B:Correct: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. This directly tests the failure mechanism and the required acceptance evidence: Local service traffic follows its approved egress without changing customer session routing. [Case R161-C046; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0227.]
Incorrect Answers
A:That intervention addresses Per-overlay route consistency: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The relevant verification here is: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
C:That intervention addresses BGP filtering for tenant scope: Two SD-WAN sites exchange too many prefixes and a branch learns another tenant's private networks. The relevant verification here is: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
D:That intervention addresses Dual-hub IPsec continuity: The primary hub tunnel is healthy but the secondary tunnel was never provisioned, defeating the recovery plan. The relevant verification here is: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
Question 228
What observable result would show that the intended SD-WAN local-out control behavior has been restored? Following a production change affecting Cedarline Retail in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. Unrelated services are still operating, so the immediate response must isolate the failing control for the cloud PoP and private hub path without disabling unrelated protections.
- Only intended site routes propagate without exposing unrelated tenant networks.
- The tunnel establishes using the intended approved cryptography.
- The destination resolves through the intended zone and authorized member.
- Local service traffic follows its approved egress without changing customer session routing.
Explanation
Correct Answer
D:Correct: Local service traffic follows its approved egress without changing customer session routing. That result demonstrates the requested controlled repair and avoids the failure mode: Self-originated local-out traffic is controlled separately from ordinary forwarded flows. [Case R161-C046; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0228.]
Incorrect Answers
A:That intervention addresses BGP filtering for tenant scope: Two SD-WAN sites exchange too many prefixes and a branch learns another tenant's private networks. The case-specific requirement is: Local service traffic follows its approved egress without changing customer session routing. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
B:That intervention addresses IKE negotiation dependency: An IPsec overlay tunnel fails because peer proposals have no common acceptable IKE parameters. The case-specific requirement is: Local service traffic follows its approved egress without changing customer session routing. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
C:Incorrect for this case: The destination resolves through the intended zone and authorized member. concerns the separate issue of Static zone route missing (A security policy allows traffic on an SD-WAN zone but its destination has no usable route through that zone.). It does not directly establish Local service traffic follows its approved egress without changing customer session routing. The case-specific evidence is Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. [Case R161-C046; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0228.]
Question 229
Which failure mechanism BEST explains the SD-WAN local-out control observation before a repair is attempted? Following a production change affecting Cedarline Retail in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. Unrelated services are still operating, so the immediate response must isolate the failing control for the cloud PoP and private hub path without disabling unrelated protections.
- Encapsulation overhead can create a packet-size-dependent path failure.
- The new NAT boundary blocks or changes the required IKE/IPsec transport path.
- Hub-only forwarding persists without a qualified ADVPN shortcut.
- Self-originated local-out traffic is controlled separately from ordinary forwarded flows.
Explanation
Correct Answer
D:Correct: Self-originated local-out traffic is controlled separately from ordinary forwarded flows. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. [Case R161-C046; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0229.]
Incorrect Answers
A:The IPsec tunnel MTU impact diagnosis does not explain the observed case: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The supported diagnosis is: Self-originated local-out traffic is controlled separately from ordinary forwarded flows.
B:The IPsec NAT traversal diagnosis diagnosis does not explain the observed case: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The supported diagnosis is: Self-originated local-out traffic is controlled separately from ordinary forwarded flows.
C:Incorrect diagnosis: this describes a different operational mechanism (ADVPN spoke-to-spoke shortcut), not the documented observation (FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic.). The supported case diagnosis is Self-originated local-out traffic is controlled separately from ordinary forwarded flows. [Case R161-C046; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0229.]
Question 230
Select THREE correct elements of a safe remedy-and-evidence plan for the SD-WAN local-out control case. Following a production change affecting Cedarline Retail in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. Unrelated services are still operating, so the immediate response must isolate the failing control for the cloud PoP and private hub path without disabling unrelated protections.
- The branch learns and uses the intended private prefix through the overlay.
- Inspect the route table, zone route and member for the destination prefix.
- Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service.
- Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
- Local service traffic follows its approved egress without changing customer session routing.
- Assign a unique loopback identity to each spoke and update its BGP peer inventory.
Explanation
Correct Answers
C:Correct remediation element: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. It addresses Self-originated local-out traffic is controlled separately from ordinary forwarded flows. [Case R161-C046; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0230.]
D:Correct verification element: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence. This independently measures whether the intended change works. [Case R161-C046; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0230.]
E:Local service traffic follows its approved egress without changing customer session routing. This confirms the case-specific path or security boundary.
Incorrect Answers
A:That intervention addresses BGP route visibility after tunnel recovery: IPsec becomes healthy but a private subnet remains unreachable because its prefix was never advertised. The case-specific requirement is: Local service traffic follows its approved egress without changing customer session routing. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
B:That intervention addresses Static zone route missing: A security policy allows traffic on an SD-WAN zone but its destination has no usable route through that zone. The relevant verification here is: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
F:That intervention addresses BGP loopback duplicate identity: Two spokes share a loopback address, causing unstable BGP peering and route attribution. The case-specific requirement is: Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service. Verify it with: Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests