Fortinet NSE7_SSE_AR-26 Exam Dumps, Practice Test Questions

100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

Fortinet NSE7_SSE_AR-26  Premium File
$76.99
$69.99

NSE7_SSE_AR-26 Premium File

  • Premium File: 50 Questions & Answers. Last update: Nov 5, 2026
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

NSE7_SSE_AR-26 Premium File

Fortinet NSE7_SSE_AR-26  Premium File
  • Premium File: 50 Questions & Answers. Last update: Nov 5, 2026
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$76.99
$69.99

Fortinet NSE7_SSE_AR-26 Practice Test 27

Question 260

Select THREE correct elements of a safe remedy-and-evidence plan for the Steering policy versus firewall permission case. Following a production change affecting Cedarline Retail in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: An engineer adds an SD-WAN rule but a restricted application remains blocked at the firewall policy layer. 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.

  1. Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.
  2. Preserve the approved security policy boundary and repair only the actual permitted firewall path after confirming SD-WAN egress.
  3. Correlate service-rule selection with firewall policy decision for the same five-tuple flow.
  4. The destination resolves through the intended zone and authorized member.
  5. Steering and security authorization both pass for permitted traffic without broadening access.
  6. Provision and monitor the secondary-hub IPsec overlay using the same reviewed topology scope.

Explanation

Correct Answers

B:

Correct remediation element: Preserve the approved security policy boundary and repair only the actual permitted firewall path after confirming SD-WAN egress. It addresses SD-WAN path selection does not itself grant firewall permission. [Case R161-C052; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0260.]

C:

Correct verification element: Correlate service-rule selection with firewall policy decision for the same five-tuple flow. This independently measures whether the intended change works. [Case R161-C052; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0260.]

E:

Steering and security authorization both pass for permitted traffic without broadening access. This confirms the case-specific path or security boundary.

Incorrect Answers

A:

Incorrect for this case: Review BGP peering over loopbacks and test shortcut routing in two underlay conditions. concerns the separate issue of BGP-on-loopback for ADVPN 2.0 (A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements.). It does not directly establish Correlate service-rule selection with firewall policy decision for the same five-tuple flow. The case-specific evidence is Correlate service-rule selection with firewall policy decision for the same five-tuple flow. [Case R161-C052; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0260.]

D:

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 Steering and security authorization both pass for permitted traffic without broadening access. The case-specific evidence is Correlate service-rule selection with firewall policy decision for the same five-tuple flow. [Case R161-C052; Fortinet task T1; anchors EXAM, RULE, LOCALOUT.] [Question R161-Q0260.]

F:

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 case-specific requirement is: Preserve the approved security policy boundary and repair only the actual permitted firewall path after confirming SD-WAN egress. Verify it with: Correlate service-rule selection with firewall policy decision for the same five-tuple flow.

Question 261

Which corrective action MOST DIRECTLY addresses the observed Overlay BGP loopback scalability problem within the approved change scope? During a scoped cross-border operations deployment across a staged branch cohort, Juniper Transit Services must commission the planned FortiSASE/SD-WAN control. The operational finding is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The change ticket limits modifications to a controlled device cohort and requires a reversible test.

  1. Check the selected rule's candidate-member list and priorities, then add the intended member to the rule scope.
  2. Use the supported Internet Service Database or application-based match where appropriate for the steering rule.
  3. Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub.
  4. Make the protected traffic selectors match the approved overlay encryption scope.

Explanation

Correct Answer

C:

Correct: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The targeted remedy is Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. This addresses per-overlay bgp adjacencies multiply the hub's control-plane burden. Confirm it by: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0261.]

Incorrect Answers

A:

Incorrect for this case: Check the selected rule's candidate-member list and priorities, then add the intended member to the rule scope. concerns the separate issue of Rule monitoring after topology change (A new circuit was added but no sessions move to it even though it meets the SLA.). It does not directly establish Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. The case-specific evidence is Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0261.]

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: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

D:

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: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Question 262

Which independent diagnostic check best validates that the Overlay BGP loopback scalability repair works? During a scoped cross-border operations deployment across a staged branch cohort, Juniper Transit Services must commission the planned FortiSASE/SD-WAN control. The operational finding is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The change ticket limits modifications to a controlled device cohort and requires a reversible test.

  1. Check service-rule match details and outgoing member for a payments flow and an unrelated flow.
  2. Generate both critical-SaaS and ordinary internet sessions and identify the first matching SD-WAN rule.
  3. Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.
  4. Observe the self-originated logging session's source and egress interface without using forwarded user traffic as evidence.

Explanation

Correct Answer

C:

Correct: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. This directly tests the failure mechanism and the required acceptance evidence: Routing remains reachable while hub peering scales more predictably. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0262.]

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: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

B:

That intervention addresses Rule order and overlapping destinations: A broad internet-services rule captures a critical SaaS application before its more specific policy. The relevant verification here is: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

D:

That intervention addresses SD-WAN local-out control: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The relevant verification here is: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Question 263

What observable result would show that the intended Overlay BGP loopback scalability behavior has been restored? During a scoped cross-border operations deployment across a staged branch cohort, Juniper Transit Services must commission the planned FortiSASE/SD-WAN control. The operational finding is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The change ticket limits modifications to a controlled device cohort and requires a reversible test.

  1. Eligible traffic can use a direct spoke shortcut while retaining hub fallback.
  2. Routing remains reachable while hub peering scales more predictably.
  3. Permitted private subnets traverse the established overlay without widening selectors unnecessarily.
  4. The tunnel establishes using the intended approved cryptography.

Explanation

Correct Answer

B:

Correct: Routing remains reachable while hub peering scales more predictably. That result demonstrates the requested controlled repair and avoids the failure mode: Per-overlay BGP adjacencies multiply the hub's control-plane burden. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0263.]

Incorrect Answers

A:

Incorrect for this case: Eligible traffic can use a direct spoke shortcut while retaining hub fallback. concerns the separate issue of ADVPN spoke-to-spoke shortcut (Traffic between two branches traverses a distant hub despite both having eligible underlays.). It does not directly establish Routing remains reachable while hub peering scales more predictably. The case-specific evidence is Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0263.]

C:

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: Routing remains reachable while hub peering scales more predictably. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

D:

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: Routing remains reachable while hub peering scales more predictably. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Question 264

Which failure mechanism BEST explains the Overlay BGP loopback scalability observation before a repair is attempted? During a scoped cross-border operations deployment across a staged branch cohort, Juniper Transit Services must commission the planned FortiSASE/SD-WAN control. The operational finding is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The change ticket limits modifications to a controlled device cohort and requires a reversible test.

  1. Per-overlay BGP adjacencies multiply the hub's control-plane burden.
  2. The service rule lacks the classification needed to distinguish marked traffic.
  3. SD-WAN path selection does not itself grant firewall permission.
  4. Unconditional cost preference disregards the app's SLA requirement.

Explanation

Correct Answer

A:

Correct: Per-overlay BGP adjacencies multiply the hub's control-plane burden. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0264.]

Incorrect Answers

B:

The DSCP-aware application steering diagnosis does not explain the observed case: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The supported diagnosis is: Per-overlay BGP adjacencies multiply the hub's control-plane burden.

C:

The Steering policy versus firewall permission diagnosis does not explain the observed case: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The supported diagnosis is: Per-overlay BGP adjacencies multiply the hub's control-plane burden.

D:

The Lowest-cost strategy with SLA floor diagnosis does not explain the observed case: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The supported diagnosis is: Per-overlay BGP adjacencies multiply the hub's control-plane burden.

Question 265

Select TWO correct elements of a safe remedy-and-evidence plan for the Overlay BGP loopback scalability case. During a scoped cross-border operations deployment across a staged branch cohort, Juniper Transit Services must commission the planned FortiSASE/SD-WAN control. The operational finding is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The change ticket limits modifications to a controlled device cohort and requires a reversible test.

  1. Dynamic routing supports the intended scalable ADVPN 2.0 deployment.
  2. Simulate a destination change within the selected service and inspect matching service IDs and egress member.
  3. Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.
  4. Create a narrowly scoped manual interface-selection rule for that vendor flow, with documented failure behavior.
  5. Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub.

Explanation

Correct Answers

C:

Correct verification element: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. This independently measures whether the intended change works. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0265.]

E:

Correct remediation element: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. It addresses Per-overlay BGP adjacencies multiply the hub's control-plane burden. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0265.]

Incorrect Answers

A:

Incorrect for this case: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. concerns the separate issue of BGP-on-loopback for ADVPN 2.0 (A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements.). It does not directly establish Routing remains reachable while hub peering scales more predictably. The case-specific evidence is Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C053; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0265.]

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: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

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: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Question 266

Which corrective action MOST DIRECTLY addresses the observed Overlay BGP loopback scalability problem within the approved change scope? Following a production change affecting Brookfield Media in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.

  1. Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub.
  2. Check the selected rule's candidate-member list and priorities, then add the intended member to the rule scope.
  3. Review the matching tunnel firewall policy and security profiles without disabling unrelated inspection globally.
  4. Configure the supported local-out routing/SD-WAN egress settings for that FortiGate service.

Explanation

Correct Answer

A:

Correct: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The targeted remedy is Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. This addresses per-overlay bgp adjacencies multiply the hub's control-plane burden. Confirm it by: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0266.]

Incorrect Answers

B:

Incorrect for this case: Check the selected rule's candidate-member list and priorities, then add the intended member to the rule scope. concerns the separate issue of Rule monitoring after topology change (A new circuit was added but no sessions move to it even though it meets the SLA.). It does not directly establish Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. The case-specific evidence is Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0266.]

C:

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: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

D:

That intervention addresses SD-WAN local-out control: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The case-specific requirement is: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Question 267

Which independent diagnostic check best validates that the Overlay BGP loopback scalability repair works? Following a production change affecting Brookfield Media in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.

  1. Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.
  2. Test an inexpensive out-of-SLA member against a more expensive in-SLA member and observe choice.
  3. Inspect rule diagnostics for eligible members and create a new test session after change.
  4. Review BGP peering over loopbacks and test shortcut routing in two underlay conditions.

Explanation

Correct Answer

A:

Correct: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. This directly tests the failure mechanism and the required acceptance evidence: Routing remains reachable while hub peering scales more predictably. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0267.]

Incorrect Answers

B:

Incorrect for this case: Test an inexpensive out-of-SLA member against a more expensive in-SLA member and observe choice. 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 Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. The case-specific evidence is Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0267.]

C:

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: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

D:

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 relevant verification here is: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Question 268

What observable result would show that the intended Overlay BGP loopback scalability behavior has been restored? Following a production change affecting Brookfield Media in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.

  1. Local service traffic follows its approved egress without changing customer session routing.
  2. Eligible traffic can use a direct spoke shortcut while retaining hub fallback.
  3. Routing remains reachable while hub peering scales more predictably.
  4. The same approved prefixes remain reachable through either viable overlay with symmetric forwarding where required.

Explanation

Correct Answer

C:

Correct: Routing remains reachable while hub peering scales more predictably. That result demonstrates the requested controlled repair and avoids the failure mode: Per-overlay BGP adjacencies multiply the hub's control-plane burden. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0268.]

Incorrect Answers

A:

That intervention addresses SD-WAN local-out control: FortiGate-generated FortiAnalyzer traffic exits a circuit reserved for customer application traffic. The case-specific requirement is: Routing remains reachable while hub peering scales more predictably. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

B:

Incorrect for this case: Eligible traffic can use a direct spoke shortcut while retaining hub fallback. concerns the separate issue of ADVPN spoke-to-spoke shortcut (Traffic between two branches traverses a distant hub despite both having eligible underlays.). It does not directly establish Routing remains reachable while hub peering scales more predictably. The case-specific evidence is Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0268.]

D:

That intervention addresses Per-overlay route consistency: Two IPsec overlays advertise inconsistent site prefixes, so recovery produces asymmetric routing. The case-specific requirement is: Routing remains reachable while hub peering scales more predictably. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Question 269

Which failure mechanism BEST explains the Overlay BGP loopback scalability observation before a repair is attempted? Following a production change affecting Brookfield Media in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.

  1. Broad traffic criteria shadow the more-specific steering intent.
  2. A generic dynamic steering strategy cannot guarantee fixed vendor egress.
  3. Per-overlay BGP adjacencies multiply the hub's control-plane burden.
  4. Missing backup tunnel configuration leaves a hidden single point of failure.

Explanation

Correct Answer

C:

Correct: Per-overlay BGP adjacencies multiply the hub's control-plane burden. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0269.]

Incorrect Answers

A:

The Rule order and overlapping destinations diagnosis does not explain the observed case: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The supported diagnosis is: Per-overlay BGP adjacencies multiply the hub's control-plane burden.

B:

The Manual strategy for fixed egress diagnosis does not explain the observed case: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The supported diagnosis is: Per-overlay BGP adjacencies multiply the hub's control-plane burden.

D:

The Dual-hub IPsec continuity diagnosis does not explain the observed case: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. The supported diagnosis is: Per-overlay BGP adjacencies multiply the hub's control-plane burden.

Question 270

Select THREE correct elements of a safe remedy-and-evidence plan for the Overlay BGP loopback scalability case. Following a production change affecting Brookfield Media in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A spoke creates a separate iBGP adjacency for every overlay tunnel and the hub's session count grows quickly. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.

  1. Test an inexpensive out-of-SLA member against a more expensive in-SLA member and observe choice.
  2. Routing remains reachable while hub peering scales more predictably.
  3. Dynamic routing supports the intended scalable ADVPN 2.0 deployment.
  4. Make the critical application's matching rule effectively precede the broad catch-all service rule.
  5. Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub.
  6. Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Explanation

Correct Answers

B:

Routing remains reachable while hub peering scales more predictably. This confirms the case-specific path or security boundary.

E:

Correct remediation element: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. It addresses Per-overlay BGP adjacencies multiply the hub's control-plane burden. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0270.]

F:

Correct verification element: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. This independently measures whether the intended change works. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0270.]

Incorrect Answers

A:

Incorrect for this case: Test an inexpensive out-of-SLA member against a more expensive in-SLA member and observe choice. 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 Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. The case-specific evidence is Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0270.]

C:

Incorrect for this case: Dynamic routing supports the intended scalable ADVPN 2.0 deployment. concerns the separate issue of BGP-on-loopback for ADVPN 2.0 (A new ADVPN 2.0 design uses BGP per overlay and fails the supported architecture requirements.). It does not directly establish Routing remains reachable while hub peering scales more predictably. The case-specific evidence is Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays. [Case R161-C054; Fortinet task T2; anchors EXAM, BGP, SDWAN.] [Question R161-Q0270.]

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: Use the FortiOS-supported BGP-on-loopback design with a controlled adjacency per hub. Verify it with: Count BGP sessions and inspect loopback next-hop resolution across two WAN overlays.

Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.