100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 310
Select THREE correct elements of a safe remedy-and-evidence plan for the BGP filtering for tenant scope case. Following a production change affecting Mistral Education in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: Two SD-WAN sites exchange too many prefixes and a branch learns another tenant's private networks. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Compare allowed and denied BGP prefix sets before and after updating the filter.
- Preserve the approved security policy boundary and repair only the actual permitted firewall path after confirming SD-WAN egress.
- Large application sessions complete without dropping due to effective MTU limits.
- Only intended site routes propagate without exposing unrelated tenant networks.
- Inspect rule diagnostics for eligible members and create a new test session after change.
- Apply prefix-list/route-map restrictions to advertise only authorized tenant prefixes.
Explanation
Correct Answers
A:Correct verification element: Compare allowed and denied BGP prefix sets before and after updating the filter. This independently measures whether the intended change works. [Case R161-C062; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0310.]
D:Only intended site routes propagate without exposing unrelated tenant networks. This confirms the case-specific path or security boundary.
F:Correct remediation element: Apply prefix-list/route-map restrictions to advertise only authorized tenant prefixes. It addresses Overly permissive advertisements cross the tenant boundary. [Case R161-C062; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0310.]
Incorrect Answers
B:Incorrect for this case: Preserve the approved security policy boundary and repair only the actual permitted firewall path after confirming SD-WAN egress. concerns the separate issue of Steering policy versus firewall permission (An engineer adds an SD-WAN rule but a restricted application remains blocked at the firewall policy layer.). It does not directly establish Apply prefix-list/route-map restrictions to advertise only authorized tenant prefixes. The case-specific evidence is Compare allowed and denied BGP prefix sets before and after updating the filter. [Case R161-C062; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0310.]
C:That intervention addresses IPsec tunnel MTU impact: Large application payloads stall over an IPsec overlay while small pings pass. The case-specific requirement is: Only intended site routes propagate without exposing unrelated tenant networks. Verify it with: Compare allowed and denied BGP prefix sets before and after updating the filter.
E:That intervention addresses Rule monitoring after topology change: A new circuit was added but no sessions move to it even though it meets the SLA. The relevant verification here is: Compare allowed and denied BGP prefix sets before and after updating the filter.
Question 311
Which corrective action MOST DIRECTLY addresses the observed Session persistence after route change problem within the approved change scope? During a scoped remote campus corridor deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The change ticket limits modifications to the affected production application and requires a reversible test.
- Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe.
- Align supported IKE versions and cryptographic proposals under the approved security baseline on both peers.
- Investigate encapsulation overhead and path MTU/MSS handling for the affected overlay.
- Make the critical application's matching rule effectively precede the broad catch-all service rule.
Explanation
Correct Answer
A:Correct: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The targeted remedy is Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. This addresses session state can retain prior egress choices after routing changes. Confirm it by: Compare one established session and one new session after the approved route change. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0311.]
Incorrect Answers
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: Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. Verify it with: Compare one established session and one new session after the approved route change.
C:That intervention addresses IPsec tunnel MTU impact: Large application payloads stall over an IPsec overlay while small pings pass. The case-specific requirement is: Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. Verify it with: Compare one established session and one new session after the approved route change.
D:That intervention addresses Rule order and overlapping destinations: A broad internet-services rule captures a critical SaaS application before its more specific policy. The case-specific requirement is: Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. Verify it with: Compare one established session and one new session after the approved route change.
Question 312
Which independent diagnostic check best validates that the Session persistence after route change repair works? During a scoped remote campus corridor deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The change ticket limits modifications to the affected production application and requires a reversible test.
- Compare first-flow and subsequent-flow application IDs and selected service rule.
- Compare small and large test payloads and observe fragmentation or MSS negotiation after a scoped change.
- Compare one established session and one new session after the approved route change.
- Inspect NAT detection and IKE tunnel establishment while capturing traffic on the NAT uplink.
Explanation
Correct Answer
C:Correct: Compare one established session and one new session after the approved route change. This directly tests the failure mechanism and the required acceptance evidence: Operators distinguish session persistence from a failed routing-policy update. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0312.]
Incorrect Answers
A:Incorrect for this case: Compare first-flow and subsequent-flow application IDs and selected service rule. concerns the separate issue of Application learning before classification (A newly introduced application is initially unidentified, so flows take an unexpected fallback member.). It does not directly establish Compare one established session and one new session after the approved route change. The case-specific evidence is Compare one established session and one new session after the approved route change. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0312.]
B:That intervention addresses IPsec tunnel MTU impact: Large application payloads stall over an IPsec overlay while small pings pass. The relevant verification here is: Compare one established session and one new session after the approved route change.
D:That intervention addresses IPsec NAT traversal diagnosis: An IPsec peer is reachable but tunnels fail after moving behind a NAT-enabled uplink. The relevant verification here is: Compare one established session and one new session after the approved route change.
Question 313
What observable result would show that the intended Session persistence after route change behavior has been restored? During a scoped remote campus corridor deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. 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.
- The new circuit becomes eligible for the specified traffic instead of remaining unused.
- The tunnel establishes using the intended approved cryptography.
- Only payments traffic uses the intended SLA-based preference while unrelated traffic follows the fallback.
Explanation
Correct Answer
A:Correct: Operators distinguish session persistence from a failed routing-policy update. That result demonstrates the requested controlled repair and avoids the failure mode: Session state can retain prior egress choices after routing changes. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0313.]
Incorrect Answers
B:That intervention addresses Rule monitoring after topology change: A new circuit was added but no sessions move to it even though it meets the SLA. The case-specific requirement is: Operators distinguish session persistence from a failed routing-policy update. Verify it with: Compare one established session and one new session after the approved route change.
C: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: Operators distinguish session persistence from a failed routing-policy update. Verify it with: Compare one established session and one new session after the approved route change.
D:That intervention addresses Specific SD-WAN rule before implicit fallback: A payments application follows the generic implicit balancing rule rather than the approved low-loss circuit. The case-specific requirement is: Operators distinguish session persistence from a failed routing-policy update. Verify it with: Compare one established session and one new session after the approved route change.
Question 314
Which failure mechanism BEST explains the Session persistence after route change observation before a repair is attempted? During a scoped remote campus corridor deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The change ticket limits modifications to the affected production application and requires a reversible test.
- No specific rule matched the application, leaving implicit steering in control.
- Peer IKE proposal mismatch prevents establishment despite reachable underlays.
- Session state can retain prior egress choices after routing changes.
- The new NAT boundary blocks or changes the required IKE/IPsec transport path.
Explanation
Correct Answer
C:Correct: Session state can retain prior egress choices after routing changes. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Compare one established session and one new session after the approved route change. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0314.]
Incorrect Answers
A:The Specific SD-WAN rule before implicit fallback diagnosis does not explain the observed case: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The supported diagnosis is: Session state can retain prior egress choices after routing changes.
B:The IKE negotiation dependency diagnosis does not explain the observed case: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The supported diagnosis is: Session state can retain prior egress choices after routing changes.
D:Incorrect diagnosis: this describes a different operational mechanism (IPsec NAT traversal diagnosis), not the documented observation (Existing SNAT flows remain on the old egress after a route change while new sessions use the new link.). The supported case diagnosis is Session state can retain prior egress choices after routing changes. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0314.]
Question 315
Select TWO correct elements of a safe remedy-and-evidence plan for the Session persistence after route change case. During a scoped remote campus corridor deployment across a staged branch cohort, Bluewater Freight must commission the planned FortiSASE/SD-WAN control. The operational finding is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. 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.
- Send otherwise identical packets with two DSCP markings and compare rule matches and member selection.
- Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe.
- Create a narrowly scoped manual interface-selection rule for that vendor flow, with documented failure behavior.
- Approved tunnel traffic passes the intended controls rather than bypassing inspection.
Explanation
Correct Answers
A:Correct verification element: Compare one established session and one new session after the approved route change. This independently measures whether the intended change works. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0315.]
C:Correct remediation element: Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. It addresses Session state can retain prior egress choices after routing changes. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0315.]
Incorrect Answers
B:Incorrect for this case: Send otherwise identical packets with two DSCP markings and compare rule matches and member selection. concerns the separate issue of DSCP-aware application steering (Priority voice packets use the ordinary bulk-data member because the existing service rule ignores markings.). It does not directly establish Compare one established session and one new session after the approved route change. The case-specific evidence is Compare one established session and one new session after the approved route change. [Case R161-C063; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0315.]
D:That intervention addresses Manual strategy for fixed egress: A regulated vendor demands a known egress interface rather than opportunistic best-quality switching. The case-specific requirement is: Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. Verify it with: Compare one established session and one new session after the approved route change.
E:That intervention addresses Security profile behavior on overlay: An IPsec tunnel passes routing tests but a new security policy silently drops an approved intersite protocol. The case-specific requirement is: Operators distinguish session persistence from a failed routing-policy update. Verify it with: Compare one established session and one new session after the approved route change.
Question 316
Which corrective action MOST DIRECTLY addresses the observed Session persistence after route change problem within the approved change scope? Following a production change affecting Cedarline Retail in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. 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.
- Check the selected rule's candidate-member list and priorities, then add the intended member to the rule scope.
- Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe.
- Use a lowest-cost strategy conditioned on qualified SLA members instead of price alone.
- Use the supported Internet Service Database or application-based match where appropriate for the steering rule.
Explanation
Correct Answer
B:Correct: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The targeted remedy is Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. This addresses session state can retain prior egress choices after routing changes. Confirm it by: Compare one established session and one new session after the approved route change. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0316.]
Incorrect Answers
A:That intervention addresses Rule monitoring after topology change: A new circuit was added but no sessions move to it even though it meets the SLA. The case-specific requirement is: Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. Verify it with: Compare one established session and one new session after the approved route change.
C:Incorrect for this case: Use a lowest-cost strategy conditioned on qualified SLA members instead of price alone. concerns the separate issue of Lowest-cost strategy with SLA floor (A branch chooses the cheapest circuit even when it misses the required application latency target.). It does not directly establish Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. The case-specific evidence is Compare one established session and one new session after the approved route change. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0316.]
D:That intervention addresses Internet-service destination matching: A SaaS provider changes IP ranges and manually maintained destination subnets become stale. The case-specific requirement is: Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. Verify it with: Compare one established session and one new session after the approved route change.
Question 317
Which independent diagnostic check best validates that the Session persistence after route change repair works? Following a production change affecting Cedarline Retail in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. 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.
- Compare one established session and one new session after the approved route change.
- Send otherwise identical packets with two DSCP markings and compare rule matches and member selection.
- Test an inexpensive out-of-SLA member against a more expensive in-SLA member and observe choice.
- Compare first-flow and subsequent-flow application IDs and selected service rule.
Explanation
Correct Answer
A:Correct: Compare one established session and one new session after the approved route change. This directly tests the failure mechanism and the required acceptance evidence: Operators distinguish session persistence from a failed routing-policy update. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0317.]
Incorrect Answers
B:Incorrect for this case: Send otherwise identical packets with two DSCP markings and compare rule matches and member selection. concerns the separate issue of DSCP-aware application steering (Priority voice packets use the ordinary bulk-data member because the existing service rule ignores markings.). It does not directly establish Compare one established session and one new session after the approved route change. The case-specific evidence is Compare one established session and one new session after the approved route change. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0317.]
C:That intervention addresses Lowest-cost strategy with SLA floor: A branch chooses the cheapest circuit even when it misses the required application latency target. The relevant verification here is: Compare one established session and one new session after the approved route change.
D:Incorrect for this case: Compare first-flow and subsequent-flow application IDs and selected service rule. concerns the separate issue of Application learning before classification (A newly introduced application is initially unidentified, so flows take an unexpected fallback member.). It does not directly establish Compare one established session and one new session after the approved route change. The case-specific evidence is Compare one established session and one new session after the approved route change. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0317.]
Question 318
What observable result would show that the intended Session persistence after route change behavior has been restored? Following a production change affecting Cedarline Retail in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. 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.
- Permitted private subnets traverse the established overlay without widening selectors unnecessarily.
- Application-specific steering occurs once matching information is available without assuming immediate identification.
- Critical SaaS uses its dedicated policy without changing generic web behavior.
- Operators distinguish session persistence from a failed routing-policy update.
Explanation
Correct Answer
D:Correct: Operators distinguish session persistence from a failed routing-policy update. That result demonstrates the requested controlled repair and avoids the failure mode: Session state can retain prior egress choices after routing changes. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0318.]
Incorrect Answers
A: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: Operators distinguish session persistence from a failed routing-policy update. Verify it with: Compare one established session and one new session after the approved route change.
B:That intervention addresses Application learning before classification: A newly introduced application is initially unidentified, so flows take an unexpected fallback member. The case-specific requirement is: Operators distinguish session persistence from a failed routing-policy update. Verify it with: Compare one established session and one new session after the approved route change.
C:That intervention addresses Rule order and overlapping destinations: A broad internet-services rule captures a critical SaaS application before its more specific policy. The case-specific requirement is: Operators distinguish session persistence from a failed routing-policy update. Verify it with: Compare one established session and one new session after the approved route change.
Question 319
Which failure mechanism BEST explains the Session persistence after route change observation before a repair is attempted? Following a production change affecting Cedarline Retail in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. 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.
- Application-based selection depends on identification that may not exist at the first packets.
- The new NAT boundary blocks or changes the required IKE/IPsec transport path.
- The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
- Session state can retain prior egress choices after routing changes.
Explanation
Correct Answer
D:Correct: Session state can retain prior egress choices after routing changes. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Compare one established session and one new session after the approved route change. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0319.]
Incorrect Answers
A:The Application learning before classification diagnosis does not explain the observed case: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The supported diagnosis is: Session state can retain prior egress choices after routing changes.
B:Incorrect diagnosis: this describes a different operational mechanism (IPsec NAT traversal diagnosis), not the documented observation (Existing SNAT flows remain on the old egress after a route change while new sessions use the new link.). The supported case diagnosis is Session state can retain prior egress choices after routing changes. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0319.]
C:The BGP-on-loopback for ADVPN 2.0 diagnosis does not explain the observed case: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. The supported diagnosis is: Session state can retain prior egress choices after routing changes.
Question 320
Select THREE correct elements of a safe remedy-and-evidence plan for the Session persistence after route change case. Following a production change affecting Cedarline Retail in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Existing SNAT flows remain on the old egress after a route change while new sessions use the new link. 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.
- Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe.
- Operators distinguish session persistence from a failed routing-policy update.
- Compare one established session and one new session after the approved route change.
- Use a lowest-cost strategy conditioned on qualified SLA members instead of price alone.
- The service policy follows the maintained application/destination identity instead of stale static subnets.
- Check service-rule match details and outgoing member for a payments flow and an unrelated flow.
Explanation
Correct Answers
A:Correct remediation element: Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. It addresses Session state can retain prior egress choices after routing changes. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0320.]
B:Operators distinguish session persistence from a failed routing-policy update. This confirms the case-specific path or security boundary.
C:Correct verification element: Compare one established session and one new session after the approved route change. This independently measures whether the intended change works. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0320.]
Incorrect Answers
D:Incorrect for this case: Use a lowest-cost strategy conditioned on qualified SLA members instead of price alone. concerns the separate issue of Lowest-cost strategy with SLA floor (A branch chooses the cheapest circuit even when it misses the required application latency target.). It does not directly establish Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe. The case-specific evidence is Compare one established session and one new session after the approved route change. [Case R161-C064; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0320.]
E:That intervention addresses Internet-service destination matching: A SaaS provider changes IP ranges and manually maintained destination subnets become stale. The case-specific requirement is: Operators distinguish session persistence from a failed routing-policy update. Verify it with: Compare one established session and one new session after the approved route change.
F:That intervention addresses Specific SD-WAN rule before implicit fallback: A payments application follows the generic implicit balancing rule rather than the approved low-loss circuit. The relevant verification here is: Compare one established session and one new session after the approved route change.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests