100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 380
Select THREE correct elements of a safe remedy-and-evidence plan for the ADVPN spoke-to-spoke shortcut case. Following a production change affecting HelioCare Clinics in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Traffic between two branches traverses a distant hub despite both having eligible underlays. 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.
- Enable and validate the supported ADVPN shortcut behavior under the approved SD-WAN architecture.
- Eligible traffic can use a direct spoke shortcut while retaining hub fallback.
- Simulate a destination change within the selected service and inspect matching service IDs and egress member.
- Add or correct the scoped route to the SD-WAN zone and confirm member selection remains governed by rules.
- Generate branch-to-branch traffic and inspect whether a qualified direct shortcut is established and selected.
Explanation
Correct Answers
B:Correct remediation element: Enable and validate the supported ADVPN shortcut behavior under the approved SD-WAN architecture. It addresses Hub-only forwarding persists without a qualified ADVPN shortcut. [Case R161-C076; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0380.]
C:Eligible traffic can use a direct spoke shortcut while retaining hub fallback. This confirms the case-specific path or security boundary.
F:Correct verification element: Generate branch-to-branch traffic and inspect whether a qualified direct shortcut is established and selected. This independently measures whether the intended change works. [Case R161-C076; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0380.]
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: Eligible traffic can use a direct spoke shortcut while retaining hub fallback. Verify it with: Generate branch-to-branch traffic and inspect whether a qualified direct shortcut is established and selected.
D:That intervention addresses Internet-service destination matching: A SaaS provider changes IP ranges and manually maintained destination subnets become stale. The relevant verification here is: Generate branch-to-branch traffic and inspect whether a qualified direct shortcut is established and selected.
E: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: Enable and validate the supported ADVPN shortcut behavior under the approved SD-WAN architecture. Verify it with: Generate branch-to-branch traffic and inspect whether a qualified direct shortcut is established and selected.
Question 381
Which corrective action MOST DIRECTLY addresses the observed BGP-on-loopback for ADVPN 2.0 problem within the approved change scope? During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Inspect existing session behavior and reevaluation triggers; plan a scoped session reset only if required and safe.
- Account for application identification and learning; use a safe initial match strategy until the flow is classified.
- Use the supported Internet Service Database or application-based match where appropriate for the steering rule.
- Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange.
Explanation
Correct Answer
D:Correct: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The targeted remedy is Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. This addresses the legacy per-overlay bgp model is not the appropriate advpn 2.0 routing design. Confirm it by: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C077; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0381.]
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: Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
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: Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
C: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: Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
Question 382
Which independent diagnostic check best validates that the BGP-on-loopback for ADVPN 2.0 repair works? During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Trace route lookup for the target prefix and compare with the SD-WAN policy match.
- Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
- Compare allowed and denied BGP prefix sets before and after updating the filter.
- Correlate service-rule selection with firewall policy decision for the same five-tuple flow.
Explanation
Correct Answer
B:Correct: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. This directly tests the failure mechanism and the required acceptance evidence: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. [Case R161-C077; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0382.]
Incorrect Answers
A: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: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
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: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
D: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 relevant verification here is: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
Question 383
What observable result would show that the intended BGP-on-loopback for ADVPN 2.0 behavior has been restored? During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Forwarding follows the approved next-hop and service-rule intent without hidden override.
- Dynamic routing supports the intended scalable ADVPN 2.0 deployment.
- The learned prefix resolves to a valid overlay member and carries packets.
- The least-cost eligible member is chosen without violating the agreed service floor.
Explanation
Correct Answer
B:Correct: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. That result demonstrates the requested controlled repair and avoids the failure mode: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design. [Case R161-C077; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0383.]
Incorrect Answers
A:Incorrect for this case: Forwarding follows the approved next-hop and service-rule intent without hidden override. concerns the separate issue of Policy route overriding intended SD-WAN path (A destination uses an unexpected interface despite a healthy specific SD-WAN service rule.). It does not directly establish Dynamic routing supports the intended scalable ADVPN 2.0 deployment. The case-specific evidence is Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C077; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0383.]
C: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: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
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 case-specific requirement is: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
Question 384
Which failure mechanism BEST explains the BGP-on-loopback for ADVPN 2.0 observation before a repair is attempted? During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
- Self-originated local-out traffic is controlled separately from ordinary forwarded flows.
- Broad traffic criteria shadow the more-specific steering intent.
- Duplicate router loopback addresses create identity collision in the overlay.
Explanation
Correct Answer
A:Correct: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C077; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0384.]
Incorrect Answers
B:The SD-WAN local-out control diagnosis does not explain the observed case: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The supported diagnosis is: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
C:The Rule order and overlapping destinations diagnosis does not explain the observed case: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The supported diagnosis is: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
D:The BGP loopback duplicate identity diagnosis does not explain the observed case: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The supported diagnosis is: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
Question 385
Select TWO correct elements of a safe remedy-and-evidence plan for the BGP-on-loopback for ADVPN 2.0 case. During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
- Only payments traffic uses the intended SLA-based preference while unrelated traffic follows the fallback.
- Assign a unique loopback identity to each spoke and update its BGP peer inventory.
- Send otherwise identical packets with two DSCP markings and compare rule matches and member selection.
- Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange.
Explanation
Correct Answers
A:Correct verification element: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. This independently measures whether the intended change works. [Case R161-C077; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0385.]
E:Correct remediation element: Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. It addresses The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design. [Case R161-C077; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0385.]
Incorrect Answers
B:Incorrect for this case: Only payments traffic uses the intended SLA-based preference while unrelated traffic follows the fallback. concerns the separate issue of Specific SD-WAN rule before implicit fallback (A payments application follows the generic implicit balancing rule rather than the approved low-loss circuit.). It does not directly establish Dynamic routing supports the intended scalable ADVPN 2.0 deployment. The case-specific evidence is Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C077; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0385.]
C: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: Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
D: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: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
Question 386
Which corrective action MOST DIRECTLY addresses the observed BGP-on-loopback for ADVPN 2.0 problem within the approved change scope? Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Make the critical application's matching rule effectively precede the broad catch-all service rule.
- Add or correct the scoped route to the SD-WAN zone and confirm member selection remains governed by rules.
- Define a specific application-matching SD-WAN service rule before relying on the implicit strategy.
- Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange.
Explanation
Correct Answer
D:Correct: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The targeted remedy is Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. This addresses the legacy per-overlay bgp model is not the appropriate advpn 2.0 routing design. Confirm it by: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0386.]
Incorrect Answers
A: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: Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
B:Incorrect for this case: Add or correct the scoped route to the SD-WAN zone and confirm member selection remains governed by rules. 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 Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. The case-specific evidence is Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0386.]
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: Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
Question 387
Which independent diagnostic check best validates that the BGP-on-loopback for ADVPN 2.0 repair works? Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
- Simulate a destination change within the selected service and inspect matching service IDs and egress member.
- Compare one established session and one new session after the approved route change.
- Inspect rule diagnostics for eligible members and create a new test session after change.
Explanation
Correct Answer
A:Correct: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. This directly tests the failure mechanism and the required acceptance evidence: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0387.]
Incorrect Answers
B:That intervention addresses Internet-service destination matching: A SaaS provider changes IP ranges and manually maintained destination subnets become stale. The relevant verification here is: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
C: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 relevant verification here is: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
D: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: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
Question 388
What observable result would show that the intended BGP-on-loopback for ADVPN 2.0 behavior has been restored? Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Only payments traffic uses the intended SLA-based preference while unrelated traffic follows the fallback.
- The branch learns and uses the intended private prefix through the overlay.
- Routing remains reachable while hub peering scales more predictably.
- Dynamic routing supports the intended scalable ADVPN 2.0 deployment.
Explanation
Correct Answer
D:Correct: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. That result demonstrates the requested controlled repair and avoids the failure mode: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0388.]
Incorrect Answers
A:Incorrect for this case: Only payments traffic uses the intended SLA-based preference while unrelated traffic follows the fallback. concerns the separate issue of Specific SD-WAN rule before implicit fallback (A payments application follows the generic implicit balancing rule rather than the approved low-loss circuit.). It does not directly establish Dynamic routing supports the intended scalable ADVPN 2.0 deployment. The case-specific evidence is Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0388.]
B: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: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
C: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: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. Verify it with: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
Question 389
Which failure mechanism BEST explains the BGP-on-loopback for ADVPN 2.0 observation before a repair is attempted? Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Hub path selection is not responding to current health or route attributes.
- Tunnel establishment alone does not guarantee route exchange.
- The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
- Firewall policy scope alone cannot create a missing route.
Explanation
Correct Answer
C:Correct: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0389.]
Incorrect Answers
A:The Dual-hub routing failover evidence diagnosis does not explain the observed case: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The supported diagnosis is: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
B:The BGP route visibility after tunnel recovery diagnosis does not explain the observed case: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The supported diagnosis is: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
D:The Static zone route missing diagnosis does not explain the observed case: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. The supported diagnosis is: The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design.
Question 390
Select THREE correct elements of a safe remedy-and-evidence plan for the BGP-on-loopback for ADVPN 2.0 case. Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange.
- Dynamic routing supports the intended scalable ADVPN 2.0 deployment.
- Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
- Observe BGP candidate routes and selected next hop during controlled primary failure.
- Add or correct the scoped route to the SD-WAN zone and confirm member selection remains governed by rules.
- Forwarding follows the approved next-hop and service-rule intent without hidden override.
Explanation
Correct Answers
A:Correct remediation element: Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. It addresses The legacy per-overlay BGP model is not the appropriate ADVPN 2.0 routing design. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0390.]
B:Dynamic routing supports the intended scalable ADVPN 2.0 deployment. This confirms the case-specific path or security boundary.
C:Correct verification element: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. This independently measures whether the intended change works. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0390.]
Incorrect Answers
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 relevant verification here is: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
E:Incorrect for this case: Add or correct the scoped route to the SD-WAN zone and confirm member selection remains governed by rules. 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 Adopt the Fortinet-recommended BGP-on-loopback model with compatible dynamic route exchange. The case-specific evidence is Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0390.]
F:Incorrect for this case: Forwarding follows the approved next-hop and service-rule intent without hidden override. concerns the separate issue of Policy route overriding intended SD-WAN path (A destination uses an unexpected interface despite a healthy specific SD-WAN service rule.). It does not directly establish Dynamic routing supports the intended scalable ADVPN 2.0 deployment. The case-specific evidence is Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. [Case R161-C078; Fortinet task T3; anchors EXAM, ADVPN, FMG_BGP.] [Question R161-Q0390.]
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests