100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 430
Select THREE correct elements of a safe remedy-and-evidence plan for the Security profile behavior on overlay case. Following a production change affecting Ironleaf Agriculture in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: An IPsec tunnel passes routing tests but a new security policy silently drops an approved intersite protocol. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- The new circuit becomes eligible for the specified traffic instead of remaining unused.
- Correlate a permitted flow's policy ID, UTM decision and tunnel forwarding log.
- Define a specific application-matching SD-WAN service rule before relying on the implicit strategy.
- Approved tunnel traffic passes the intended controls rather than bypassing inspection.
- Review the matching tunnel firewall policy and security profiles without disabling unrelated inspection globally.
- Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.
Explanation
Correct Answers
B:Correct verification element: Correlate a permitted flow's policy ID, UTM decision and tunnel forwarding log. This independently measures whether the intended change works. [Case R161-C086; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0430.]
D:Approved tunnel traffic passes the intended controls rather than bypassing inspection. This confirms the case-specific path or security boundary.
E:Correct remediation element: Review the matching tunnel firewall policy and security profiles without disabling unrelated inspection globally. It addresses Security-policy inspection is the actual blocker, not IKE or BGP state. [Case R161-C086; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0430.]
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: Approved tunnel traffic passes the intended controls rather than bypassing inspection. Verify it with: Correlate a permitted flow's policy ID, UTM decision and tunnel forwarding log.
C: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: Review the matching tunnel firewall policy and security profiles without disabling unrelated inspection globally. Verify it with: Correlate a permitted flow's policy ID, UTM decision and tunnel forwarding log.
F: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 relevant verification here is: Correlate a permitted flow's policy ID, UTM decision and tunnel forwarding log.
Question 431
Which corrective action MOST DIRECTLY addresses the observed Per-overlay route consistency problem within the approved change scope? During a scoped remote campus corridor deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The change ticket limits modifications to the affected production application and requires a reversible test.
- Preserve the approved security policy boundary and repair only the actual permitted firewall path after confirming SD-WAN egress.
- Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub.
- Account for application identification and learning; use a safe initial match strategy until the flow is classified.
- Align route advertisement and preferred-path policy across both reviewed overlays.
Explanation
Correct Answer
D:Correct: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The targeted remedy is Align route advertisement and preferred-path policy across both reviewed overlays. This addresses unequal route policies across overlays cause reachability changes during failover. Confirm it by: Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0431.]
Incorrect Answers
A:That intervention addresses Steering policy versus firewall permission: An engineer adds an SD-WAN rule but a restricted application remains blocked at the firewall policy layer. The case-specific requirement is: Align route advertisement and preferred-path policy across both reviewed overlays. Verify it with: Fail over each overlay individually and inspect forward and return paths for the same application flow.
B:Incorrect for this case: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. concerns the separate issue of Overlay BGP loopback scalability (A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly.). It does not directly establish Align route advertisement and preferred-path policy across both reviewed overlays. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0431.]
C:Incorrect for this case: Account for application identification and learning; use a safe initial match strategy until the flow is classified. 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 Align route advertisement and preferred-path policy across both reviewed overlays. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0431.]
Question 432
Which independent diagnostic check best validates that the Per-overlay route consistency repair works? During a scoped remote campus corridor deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. 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.
- Send otherwise identical packets with two DSCP markings and compare rule matches and member selection.
- Fail over each overlay individually and inspect forward and return paths for the same application flow.
- Test an inexpensive out-of-SLA member against a more expensive in-SLA member and observe choice.
Explanation
Correct Answer
C:Correct: Fail over each overlay individually and inspect forward and return paths for the same application flow. This directly tests the failure mechanism and the required acceptance evidence: The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0432.]
Incorrect Answers
A:That intervention addresses Application learning before classification: A newly introduced application is initially unidentified, so flows take an unexpected fallback member. The relevant verification here is: Fail over each overlay individually and inspect forward and return paths for the same application flow.
B:That intervention addresses DSCP-aware application steering: Priority voice packets use the ordinary bulk-data member because the existing service rule ignores markings. The relevant verification here is: Fail over each overlay individually and inspect forward and return paths for the same application flow.
D: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: Fail over each overlay individually and inspect forward and return paths for the same application flow.
Question 433
What observable result would show that the intended Per-overlay route consistency behavior has been restored? During a scoped remote campus corridor deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The change ticket limits modifications to the affected production application and requires a reversible test.
- The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required.
- The vendor gets the required egress control without forcing all traffic onto one member.
- Application-specific steering occurs once matching information is available without assuming immediate identification.
- Critical SaaS uses its dedicated policy without changing generic web behavior.
Explanation
Correct Answer
A:Correct: The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. That result demonstrates the requested controlled repair and avoids the failure mode: Unequal route policies across overlays cause reachability changes during failover. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0433.]
Incorrect Answers
B: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: The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. Verify it with: Fail over each overlay individually and inspect forward and return paths for the same application flow.
C:Incorrect for this case: Application-specific steering occurs once matching information is available without assuming immediate identification. 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 The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0433.]
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: The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. Verify it with: Fail over each overlay individually and inspect forward and return paths for the same application flow.
Question 434
Which failure mechanism BEST explains the Per-overlay route consistency observation before a repair is attempted? During a scoped remote campus corridor deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. 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.
- A generic dynamic steering strategy cannot guarantee fixed vendor egress.
- Session state can retain prior egress choices after routing changes.
- The member is healthy but excluded from service-rule candidates.
Explanation
Correct Answer
A:Correct: Unequal route policies across overlays cause reachability changes during failover. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0434.]
Incorrect Answers
B:The Manual strategy for fixed egress diagnosis does not explain the observed case: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The supported diagnosis is: Unequal route policies across overlays cause reachability changes during failover.
C:The Session persistence after route change diagnosis does not explain the observed case: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The supported diagnosis is: Unequal route policies across overlays cause reachability changes during failover.
D:The Rule monitoring after topology change diagnosis does not explain the observed case: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The supported diagnosis is: Unequal route policies across overlays cause reachability changes during failover.
Question 435
Select TWO correct elements of a safe remedy-and-evidence plan for the Per-overlay route consistency case. During a scoped remote campus corridor deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The change ticket limits modifications to the affected production application and requires a reversible test.
- Marked voice follows the selected policy while ordinary packets retain the default behavior.
- Fail over each overlay individually and inspect forward and return paths for the same application flow.
- Use a lowest-cost strategy conditioned on qualified SLA members instead of price alone.
- Align route advertisement and preferred-path policy across both reviewed overlays.
- Inspect the BGP next hop, recursive route and data-plane egress for a test LAN destination.
Explanation
Correct Answers
B:Correct verification element: Fail over each overlay individually and inspect forward and return paths for the same application flow. This independently measures whether the intended change works. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0435.]
D:Correct remediation element: Align route advertisement and preferred-path policy across both reviewed overlays. It addresses Unequal route policies across overlays cause reachability changes during failover. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0435.]
Incorrect Answers
A:That intervention addresses DSCP-aware application steering: Priority voice packets use the ordinary bulk-data member because the existing service rule ignores markings. The case-specific requirement is: The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. Verify it with: Fail over each overlay individually and inspect forward and return paths for the same application flow.
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 case-specific requirement is: Align route advertisement and preferred-path policy across both reviewed overlays. Verify it with: Fail over each overlay individually and inspect forward and return paths for the same application flow.
E:Incorrect for this case: Inspect the BGP next hop, recursive route and data-plane egress for a test LAN destination. concerns the separate issue of Overlay route recursive next hop (A BGP-learned LAN prefix appears in the control plane but fails recursive resolution to a usable tunnel.). It does not directly establish Fail over each overlay individually and inspect forward and return paths for the same application flow. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C087; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0435.]
Question 436
Which corrective action MOST DIRECTLY addresses the observed Per-overlay route consistency problem within the approved change scope? Following a production change affecting Harborlight Industrial in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. 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.
- Align route advertisement and preferred-path policy across both reviewed overlays.
- Use the supported Internet Service Database or application-based match where appropriate for the steering rule.
- Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub.
- Create a narrowly scoped manual interface-selection rule for that vendor flow, with documented failure behavior.
Explanation
Correct Answer
A:Correct: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The targeted remedy is Align route advertisement and preferred-path policy across both reviewed overlays. This addresses unequal route policies across overlays cause reachability changes during failover. Confirm it by: Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0436.]
Incorrect Answers
B: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: Align route advertisement and preferred-path policy across both reviewed overlays. Verify it with: Fail over each overlay individually and inspect forward and return paths for the same application flow.
C:Incorrect for this case: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. concerns the separate issue of Overlay BGP loopback scalability (A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly.). It does not directly establish Align route advertisement and preferred-path policy across both reviewed overlays. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0436.]
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: Align route advertisement and preferred-path policy across both reviewed overlays. Verify it with: Fail over each overlay individually and inspect forward and return paths for the same application flow.
Question 437
Which independent diagnostic check best validates that the Per-overlay route consistency repair works? Following a production change affecting Harborlight Industrial in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. 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 service-rule match details and outgoing member for a payments flow and an unrelated flow.
- Inspect peer endpoints and next-hop resolution after both spokes connect concurrently.
- Inspect the BGP next hop, recursive route and data-plane egress for a test LAN destination.
- Fail over each overlay individually and inspect forward and return paths for the same application flow.
Explanation
Correct Answer
D:Correct: Fail over each overlay individually and inspect forward and return paths for the same application flow. This directly tests the failure mechanism and the required acceptance evidence: The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0437.]
Incorrect Answers
A: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: Fail over each overlay individually and inspect forward and return paths for the same application flow.
B:Incorrect for this case: Inspect peer endpoints and next-hop resolution after both spokes connect concurrently. concerns the separate issue of BGP loopback duplicate identity (Two spokes share a loopback address, causing unstable BGP peering and route attribution.). It does not directly establish Fail over each overlay individually and inspect forward and return paths for the same application flow. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0437.]
C:Incorrect for this case: Inspect the BGP next hop, recursive route and data-plane egress for a test LAN destination. concerns the separate issue of Overlay route recursive next hop (A BGP-learned LAN prefix appears in the control plane but fails recursive resolution to a usable tunnel.). It does not directly establish Fail over each overlay individually and inspect forward and return paths for the same application flow. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0437.]
Question 438
What observable result would show that the intended Per-overlay route consistency behavior has been restored? Following a production change affecting Harborlight Industrial in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. 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.
- Application-specific steering occurs once matching information is available without assuming immediate identification.
- Local service traffic follows its approved egress without changing customer session routing.
- The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required.
Explanation
Correct Answer
D:Correct: The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. That result demonstrates the requested controlled repair and avoids the failure mode: Unequal route policies across overlays cause reachability changes during failover. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0438.]
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: The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. Verify it with: Fail over each overlay individually and inspect forward and return paths for the same application flow.
B:Incorrect for this case: Application-specific steering occurs once matching information is available without assuming immediate identification. 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 The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0438.]
C:Incorrect for this case: Local service traffic follows its approved egress without changing customer session routing. concerns the separate issue of SD-WAN local-out control (FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic.). It does not directly establish The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0438.]
Question 439
Which failure mechanism BEST explains the Per-overlay route consistency observation before a repair is attempted? Following a production change affecting Harborlight Industrial in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. 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.
- Static IP lists no longer represent the intended SaaS service.
- The route is learned but its next hop cannot resolve to an active tunnel.
- Broad traffic criteria shadow the more-specific steering intent.
- Unequal route policies across overlays cause reachability changes during failover.
Explanation
Correct Answer
D:Correct: Unequal route policies across overlays cause reachability changes during failover. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0439.]
Incorrect Answers
A:The Internet-service destination matching diagnosis does not explain the observed case: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The supported diagnosis is: Unequal route policies across overlays cause reachability changes during failover.
B:The Overlay route recursive next hop diagnosis does not explain the observed case: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The supported diagnosis is: Unequal route policies across overlays cause reachability changes during failover.
C:The Rule order and overlapping destinations diagnosis does not explain the observed case: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The supported diagnosis is: Unequal route policies across overlays cause reachability changes during failover.
Question 440
Select THREE correct elements of a safe remedy-and-evidence plan for the Per-overlay route consistency case. Following a production change affecting Harborlight Industrial in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. 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.
- Align route advertisement and preferred-path policy across both reviewed overlays.
- Inspect peer endpoints and next-hop resolution after both spokes connect concurrently.
- The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required.
- Account for application identification and learning; use a safe initial match strategy until the flow is classified.
- Local service traffic follows its approved egress without changing customer session routing.
Explanation
Correct Answers
A:Correct verification element: Fail over each overlay individually and inspect forward and return paths for the same application flow. This independently measures whether the intended change works. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0440.]
B:Correct remediation element: Align route advertisement and preferred-path policy across both reviewed overlays. It addresses Unequal route policies across overlays cause reachability changes during failover. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0440.]
D:The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. This confirms the case-specific path or security boundary.
Incorrect Answers
C:Incorrect for this case: Inspect peer endpoints and next-hop resolution after both spokes connect concurrently. concerns the separate issue of BGP loopback duplicate identity (Two spokes share a loopback address, causing unstable BGP peering and route attribution.). It does not directly establish Fail over each overlay individually and inspect forward and return paths for the same application flow. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0440.]
E:Incorrect for this case: Account for application identification and learning; use a safe initial match strategy until the flow is classified. 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 Align route advertisement and preferred-path policy across both reviewed overlays. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0440.]
F:Incorrect for this case: Local service traffic follows its approved egress without changing customer session routing. concerns the separate issue of SD-WAN local-out control (FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic.). It does not directly establish The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required. The case-specific evidence is Fail over each overlay individually and inspect forward and return paths for the same application flow. [Case R161-C088; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0440.]
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests