100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 50
Select THREE correct elements of a safe remedy-and-evidence plan for the Overlay scaling via grouped branches case. During a scoped metro branch group deployment across a staged branch cohort, Cedarline Retail must commission the planned FortiSASE/SD-WAN control. The operational finding is: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. The change ticket limits modifications to the cloud PoP and private hub path and requires a reversible test.
- Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates.
- Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA.
- Sustained failures trigger rerouting without excess oscillation on brief jitter spikes.
- New branches inherit consistent region-specific overlay design without manual drift.
- Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
- Inject variable delay while keeping packet loss constant and compare SLA qualification and routing.
Explanation
Correct Answers
A:Correct remediation element: Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. It addresses Per-branch template cloning produced inconsistent topology metadata. [Case R161-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0050.]
D:New branches inherit consistent region-specific overlay design without manual drift. This confirms the case-specific path or security boundary.
E:Correct verification element: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. This independently measures whether the intended change works. [Case R161-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0050.]
Incorrect Answers
B:That intervention addresses Performance SLA latency threshold: Voice sessions remain on a high-latency WAN link even though another member has lower delay. The case-specific requirement is: Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. Verify it with: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
C:Incorrect for this case: Sustained failures trigger rerouting without excess oscillation on brief jitter spikes. concerns the separate issue of SLA flap reduction (An unstable WAN member oscillates across the configured quality threshold, repeatedly moving new sessions.). It does not directly establish New branches inherit consistent region-specific overlay design without manual drift. The case-specific evidence is Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0050.]
F:That intervention addresses Jitter-based real-time steering: Two links meet a packet-loss limit but one has unstable delay and produces choppy audio. The relevant verification here is: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
Question 51
Which corrective action MOST DIRECTLY addresses the observed Overlay scaling via grouped branches problem within the approved change scope? Following a production change affecting Pinehaven Distribution in its central region, a network team receives repeatable user-impact reports. Its fault evidence is: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard.
- Tune supported SLA monitoring and link state-change behavior to avoid reacting to transient probe noise.
- Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates.
- Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies.
Explanation
Correct Answer
C:Correct: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. The targeted remedy is Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. This addresses per-branch template cloning produced inconsistent topology metadata. Confirm it by: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0051.]
Incorrect Answers
A:That intervention addresses SD-WAN event visibility: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The case-specific requirement is: Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. Verify it with: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
B:That intervention addresses SLA flap reduction: An unstable WAN member oscillates across the configured quality threshold, repeatedly moving new sessions. The case-specific requirement is: Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. Verify it with: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
D:That intervention addresses DIA egress segmentation: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The case-specific requirement is: Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. Verify it with: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
Question 52
Which independent diagnostic check best validates that the Overlay scaling via grouped branches repair works? Following a production change affecting Pinehaven Distribution in its central region, a network team receives repeatable user-impact reports. Its fault evidence is: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
- Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
- Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
Explanation
Correct Answer
C:Correct: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. This directly tests the failure mechanism and the required acceptance evidence: New branches inherit consistent region-specific overlay design without manual drift. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0052.]
Incorrect Answers
A:Incorrect for this case: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. concerns the separate issue of Active health-check target selection (A link passes a gateway ping but cannot reach business applications beyond the provider edge.). It does not directly establish Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. The case-specific evidence is Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0052.]
B:That intervention addresses DIA egress segmentation: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The relevant verification here is: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
D:That intervention addresses Branch template variable scope: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. The relevant verification here is: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
Question 53
What observable result would show that the intended Overlay scaling via grouped branches behavior has been restored? Following a production change affecting Pinehaven Distribution in its central region, a network team receives repeatable user-impact reports. Its fault evidence is: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Sustained failures trigger rerouting without excess oscillation on brief jitter spikes.
- Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member.
- The secure overlay establishes after the underlay path is restored.
- New branches inherit consistent region-specific overlay design without manual drift.
Explanation
Correct Answer
D:Correct: New branches inherit consistent region-specific overlay design without manual drift. That result demonstrates the requested controlled repair and avoids the failure mode: Per-branch template cloning produced inconsistent topology metadata. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0053.]
Incorrect Answers
A:Incorrect for this case: Sustained failures trigger rerouting without excess oscillation on brief jitter spikes. concerns the separate issue of SLA flap reduction (An unstable WAN member oscillates across the configured quality threshold, repeatedly moving new sessions.). It does not directly establish New branches inherit consistent region-specific overlay design without manual drift. The case-specific evidence is Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0053.]
B:Incorrect for this case: Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member. concerns the separate issue of Active health-check target selection (A link passes a gateway ping but cannot reach business applications beyond the provider edge.). It does not directly establish New branches inherit consistent region-specific overlay design without manual drift. The case-specific evidence is Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0053.]
C:Incorrect for this case: The secure overlay establishes after the underlay path is restored. concerns the separate issue of Underlay prerequisite before IPsec (IPsec tunnels fail to establish at a remote branch because the peer's public underlay address is unreachable.). It does not directly establish New branches inherit consistent region-specific overlay design without manual drift. The case-specific evidence is Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0053.]
Question 54
Which failure mechanism BEST explains the Overlay scaling via grouped branches observation before a repair is attempted? Following a production change affecting Pinehaven Distribution in its central region, a network team receives repeatable user-impact reports. Its fault evidence is: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Per-branch template cloning produced inconsistent topology metadata.
- Packet-loss-only health checks miss the actual audio impairment.
- A zone-to-policy mismatch blocks traffic despite physical link state.
- Hub preference policy is missing or inconsistent after reconvergence.
Explanation
Correct Answer
A:Correct: Per-branch template cloning produced inconsistent topology metadata. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0054.]
Incorrect Answers
B:The Jitter-based real-time steering diagnosis does not explain the observed case: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. The supported diagnosis is: Per-branch template cloning produced inconsistent topology metadata.
C:The Member zone policy binding diagnosis does not explain the observed case: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. The supported diagnosis is: Per-branch template cloning produced inconsistent topology metadata.
D:The Dual-hub route preference diagnosis does not explain the observed case: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. The supported diagnosis is: Per-branch template cloning produced inconsistent topology metadata.
Question 55
Select TWO correct elements of a safe remedy-and-evidence plan for the Overlay scaling via grouped branches case. Following a production change affecting Pinehaven Distribution in its central region, a network team receives repeatable user-impact reports. Its fault evidence is: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates.
- The new member can carry authorized sessions without opening unrelated zones.
- Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
- Correct per-device or per-group metadata variables before pushing the overlay template.
- Run short and sustained impairments and count member state changes before and after tuning.
Explanation
Correct Answers
A:Correct remediation element: Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. It addresses Per-branch template cloning produced inconsistent topology metadata. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0055.]
C:Correct verification element: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. This independently measures whether the intended change works. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0055.]
Incorrect Answers
B:That intervention addresses Member zone policy binding: A new WAN interface is physically up but traffic remains blocked because the firewall policy references a different SD-WAN zone. The case-specific requirement is: New branches inherit consistent region-specific overlay design without manual drift. Verify it with: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
D:Incorrect for this case: Correct per-device or per-group metadata variables before pushing the overlay template. concerns the separate issue of Branch template variable scope (An overlay template places all branches into the same region because a group variable is resolved at the wrong scope.). It does not directly establish Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. The case-specific evidence is Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0055.]
E:Incorrect for this case: Run short and sustained impairments and count member state changes before and after tuning. concerns the separate issue of SLA flap reduction (An unstable WAN member oscillates across the configured quality threshold, repeatedly moving new sessions.). It does not directly establish Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. The case-specific evidence is Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency. [Case R161-C011; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0055.]
Question 56
Which corrective action MOST DIRECTLY addresses the observed DIA egress segmentation problem within the approved change scope? During a scoped northern sites deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies.
- Include jitter in the application SLA and steer real-time sessions to the member meeting that criterion.
- Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory.
- Tune supported SLA monitoring and link state-change behavior to avoid reacting to transient probe noise.
Explanation
Correct Answer
A:Correct: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The targeted remedy is Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies. This addresses underlay and overlay path roles were conflated in the branch forwarding policy. Confirm it by: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0056.]
Incorrect Answers
B:That intervention addresses Jitter-based real-time steering: Two links meet a packet-loss limit but one has unstable delay and produces choppy audio. The case-specific requirement is: Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies. Verify it with: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
C:That intervention addresses Scaled regional address planning: An overlay rollout reuses a loopback range already assigned to spokes in a second region. The case-specific requirement is: Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies. Verify it with: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
D:That intervention addresses SLA flap reduction: An unstable WAN member oscillates across the configured quality threshold, repeatedly moving new sessions. The case-specific requirement is: Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies. Verify it with: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
Question 57
Which independent diagnostic check best validates that the DIA egress segmentation repair works? During a scoped northern sites deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Inject variable delay while keeping packet loss constant and compare SLA qualification and routing.
- Simulate loss of the regional primary hub and inspect backup tunnel, route and application reachability.
- Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
- Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
Explanation
Correct Answer
C:Correct: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. This directly tests the failure mechanism and the required acceptance evidence: Internet access uses approved DIA inspection while internal destinations take the private overlay. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0057.]
Incorrect Answers
A:Incorrect for this case: Inject variable delay while keeping packet loss constant and compare SLA qualification and routing. concerns the separate issue of Jitter-based real-time steering (Two links meet a packet-loss limit but one has unstable delay and produces choppy audio.). It does not directly establish Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. The case-specific evidence is Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0057.]
B:Incorrect for this case: Simulate loss of the regional primary hub and inspect backup tunnel, route and application reachability. concerns the separate issue of Dual-hub regional survivability (A newly added region depends on one datacenter hub and remote sites lose their overlay if that hub fails.). It does not directly establish Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. The case-specific evidence is Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0057.]
D:That intervention addresses Active health-check target selection: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The relevant verification here is: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
Question 58
What observable result would show that the intended DIA egress segmentation behavior has been restored? During a scoped northern sites deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- New branches inherit consistent region-specific overlay design without manual drift.
- Only the approved shared-service route is reachable across the isolation boundary.
- Sustained failures trigger rerouting without excess oscillation on brief jitter spikes.
- Internet access uses approved DIA inspection while internal destinations take the private overlay.
Explanation
Correct Answer
D:Correct: Internet access uses approved DIA inspection while internal destinations take the private overlay. That result demonstrates the requested controlled repair and avoids the failure mode: Underlay and overlay path roles were conflated in the branch forwarding policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0058.]
Incorrect Answers
A:Incorrect for this case: New branches inherit consistent region-specific overlay design without manual drift. concerns the separate issue of Overlay scaling via grouped branches (A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions.). It does not directly establish Internet access uses approved DIA inspection while internal destinations take the private overlay. The case-specific evidence is Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0058.]
B:That intervention addresses VRF route exchange exceptions: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. The case-specific requirement is: Internet access uses approved DIA inspection while internal destinations take the private overlay. Verify it with: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
C:That intervention addresses SLA flap reduction: An unstable WAN member oscillates across the configured quality threshold, repeatedly moving new sessions. The case-specific requirement is: Internet access uses approved DIA inspection while internal destinations take the private overlay. Verify it with: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
Question 59
Which failure mechanism BEST explains the DIA egress segmentation observation before a repair is attempted? During a scoped northern sites deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Traffic steering was not conditioned on application-specific link quality.
- Underlay and overlay path roles were conflated in the branch forwarding policy.
- Per-branch template cloning produced inconsistent topology metadata.
- Overlapping overlay and loopback allocations break unambiguous next-hop resolution.
Explanation
Correct Answer
B:Correct: Underlay and overlay path roles were conflated in the branch forwarding policy. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0059.]
Incorrect Answers
A:The Performance SLA latency threshold diagnosis does not explain the observed case: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The supported diagnosis is: Underlay and overlay path roles were conflated in the branch forwarding policy.
C:Incorrect diagnosis: this describes a different operational mechanism (Overlay scaling via grouped branches), not the documented observation (A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay.). The supported case diagnosis is Underlay and overlay path roles were conflated in the branch forwarding policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0059.]
D:The Scaled regional address planning diagnosis does not explain the observed case: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The supported diagnosis is: Underlay and overlay path roles were conflated in the branch forwarding policy.
Question 60
Select THREE correct elements of a safe remedy-and-evidence plan for the DIA egress segmentation case. During a scoped northern sites deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Generate a quiet period, then inspect freshness and confidence of per-member SLA measurements.
- Internet access uses approved DIA inspection while internal destinations take the private overlay.
- Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA.
- Branch applications remain reachable using the authorized secondary path after primary-hub failure.
- Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
- Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies.
Explanation
Correct Answers
B:Internet access uses approved DIA inspection while internal destinations take the private overlay. This confirms the case-specific path or security boundary.
E:Correct verification element: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. This independently measures whether the intended change works. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0060.]
F:Correct remediation element: Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies. It addresses Underlay and overlay path roles were conflated in the branch forwarding policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0060.]
Incorrect Answers
A:That intervention addresses Passive health measurement validity: A low-traffic backup link reports stale quality measurements and is chosen based on old samples. The relevant verification here is: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
C:That intervention addresses Performance SLA latency threshold: Voice sessions remain on a high-latency WAN link even though another member has lower delay. The case-specific requirement is: Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies. Verify it with: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
D:Incorrect for this case: Branch applications remain reachable using the authorized secondary path after primary-hub failure. concerns the separate issue of Dual-hub regional survivability (A newly added region depends on one datacenter hub and remote sites lose their overlay if that hub fails.). It does not directly establish Internet access uses approved DIA inspection while internal destinations take the private overlay. The case-specific evidence is Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. [Case R161-C012; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0060.]
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests