100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 100
Select THREE correct elements of a safe remedy-and-evidence plan for the Branch template variable scope case. During a scoped northern sites deployment across a staged branch cohort, Brookfield Media must commission the planned FortiSASE/SD-WAN control. The operational finding is: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
- Each branch receives the region-appropriate hub set and overlay addressing.
- Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
- Correct per-device or per-group metadata variables before pushing the overlay template.
- New branches inherit consistent region-specific overlay design without manual drift.
- Use appropriately configured active probes when continuous readiness measurements are required.
Explanation
Correct Answers
A:Correct verification element: Review generated configurations for branches in two regions and confirm hub targets and addresses. This independently measures whether the intended change works. [Case R161-C020; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0100.]
B:Each branch receives the region-appropriate hub set and overlay addressing. This confirms the case-specific path or security boundary.
D:Correct remediation element: Correct per-device or per-group metadata variables before pushing the overlay template. It addresses A globally resolved metadata variable overwrote regional differences. [Case R161-C020; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0100.]
Incorrect Answers
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 relevant verification here is: Review generated configurations for branches in two regions and confirm hub targets and addresses.
E:That intervention addresses Overlay scaling via grouped branches: A regional template was manually cloned hundreds of times and different branch groups now have inconsistent hub definitions. The case-specific requirement is: Each branch receives the region-appropriate hub set and overlay addressing. Verify it with: Review generated configurations for branches in two regions and confirm hub targets and addresses.
F:Incorrect for this case: Use appropriately configured active probes when continuous readiness measurements are required. concerns the separate issue of Passive health measurement validity (A low-traffic backup link reports stale quality measurements and is chosen based on old samples.). It does not directly establish Correct per-device or per-group metadata variables before pushing the overlay template. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C020; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0100.]
Question 101
Which corrective action MOST DIRECTLY addresses the observed Branch template variable scope problem within the approved change scope? Following a production change affecting Stonebridge Markets in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates.
- Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway.
- Design separate VRF-aware overlays and routing contexts for the tenants, with explicit permitted interconnection only.
- Correct per-device or per-group metadata variables before pushing the overlay template.
Explanation
Correct Answer
D:Correct: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. The targeted remedy is Correct per-device or per-group metadata variables before pushing the overlay template. This addresses a globally resolved metadata variable overwrote regional differences. Confirm it by: Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0101.]
Incorrect Answers
A:Incorrect for this case: Group branches by intended region and apply an SD-WAN overlay template with scoped metadata variables and review gates. 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 Correct per-device or per-group metadata variables before pushing the overlay template. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0101.]
B:Incorrect for this case: Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway. 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 Correct per-device or per-group metadata variables before pushing the overlay template. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0101.]
C:That intervention addresses MSSP tenant isolation through VRFs: Two managed tenants advertise identical branch subnets and route exchange could expose one tenant to the other. The case-specific requirement is: Correct per-device or per-group metadata variables before pushing the overlay template. Verify it with: Review generated configurations for branches in two regions and confirm hub targets and addresses.
Question 102
Which independent diagnostic check best validates that the Branch template variable scope repair works? Following a production change affecting Stonebridge Markets in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
- Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory.
- Advertise identical test prefixes in both VRFs and check route tables and denied cross-tenant probes.
- Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
Explanation
Correct Answer
A:Correct: Review generated configurations for branches in two regions and confirm hub targets and addresses. This directly tests the failure mechanism and the required acceptance evidence: Each branch receives the region-appropriate hub set and overlay addressing. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0102.]
Incorrect Answers
B:Incorrect for this case: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. concerns the separate issue of Zero-touch device inventory accuracy (Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata.). It does not directly establish Review generated configurations for branches in two regions and confirm hub targets and addresses. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0102.]
C:That intervention addresses MSSP tenant isolation through VRFs: Two managed tenants advertise identical branch subnets and route exchange could expose one tenant to the other. The relevant verification here is: Review generated configurations for branches in two regions and confirm hub targets and addresses.
D:Incorrect for this case: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. concerns the separate issue of Scaled regional address planning (An overlay rollout reuses a loopback range already assigned to spokes in a second region.). It does not directly establish Review generated configurations for branches in two regions and confirm hub targets and addresses. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0102.]
Question 103
What observable result would show that the intended Branch template variable scope behavior has been restored? Following a production change affecting Stonebridge Markets in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- Real-time traffic avoids the member violating jitter tolerance.
- Voice selects an in-SLA path according to the stated steering rule.
- Each branch receives the region-appropriate hub set and overlay addressing.
- Branch applications remain reachable using the authorized secondary path after primary-hub failure.
Explanation
Correct Answer
C:Correct: Each branch receives the region-appropriate hub set and overlay addressing. That result demonstrates the requested controlled repair and avoids the failure mode: A globally resolved metadata variable overwrote regional differences. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0103.]
Incorrect Answers
A: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: Each branch receives the region-appropriate hub set and overlay addressing. Verify it with: Review generated configurations for branches in two regions and confirm hub targets and addresses.
B:Incorrect for this case: Voice selects an in-SLA path according to the stated steering rule. concerns the separate issue of Performance SLA latency threshold (Voice sessions remain on a high-latency WAN link even though another member has lower delay.). It does not directly establish Each branch receives the region-appropriate hub set and overlay addressing. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0103.]
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 Each branch receives the region-appropriate hub set and overlay addressing. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0103.]
Question 104
Which failure mechanism BEST explains the Branch template variable scope observation before a repair is attempted? Following a production change affecting Stonebridge Markets in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- Mismatched serial and site metadata cause a wrong ZTP assignment.
- An all-prefix route leak violates the required tenant boundary.
- Packet-loss-only health checks miss the actual audio impairment.
- A globally resolved metadata variable overwrote regional differences.
Explanation
Correct Answer
D:Correct: A globally resolved metadata variable overwrote regional differences. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0104.]
Incorrect Answers
A:The Zero-touch device inventory accuracy diagnosis does not explain the observed case: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. The supported diagnosis is: A globally resolved metadata variable overwrote regional differences.
B:The VRF route exchange exceptions diagnosis does not explain the observed case: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. The supported diagnosis is: A globally resolved metadata variable overwrote regional differences.
C:The Jitter-based real-time steering diagnosis does not explain the observed case: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. The supported diagnosis is: A globally resolved metadata variable overwrote regional differences.
Question 105
Select TWO correct elements of a safe remedy-and-evidence plan for the Branch template variable scope case. Following a production change affecting Stonebridge Markets in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
- Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway.
- The standby path is evaluated with current health evidence before selection.
- Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
- Correct per-device or per-group metadata variables before pushing the overlay template.
Explanation
Correct Answers
A:Correct verification element: Review generated configurations for branches in two regions and confirm hub targets and addresses. This independently measures whether the intended change works. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0105.]
E:Correct remediation element: Correct per-device or per-group metadata variables before pushing the overlay template. It addresses A globally resolved metadata variable overwrote regional differences. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0105.]
Incorrect Answers
B:Incorrect for this case: Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway. 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 Correct per-device or per-group metadata variables before pushing the overlay template. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0105.]
C:Incorrect for this case: The standby path is evaluated with current health evidence before selection. concerns the separate issue of Passive health measurement validity (A low-traffic backup link reports stale quality measurements and is chosen based on old samples.). It does not directly establish Each branch receives the region-appropriate hub set and overlay addressing. The case-specific evidence is Review generated configurations for branches in two regions and confirm hub targets and addresses. [Case R161-C021; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0105.]
D: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 relevant verification here is: Review generated configurations for branches in two regions and confirm hub targets and addresses.
Question 106
Which corrective action MOST DIRECTLY addresses the observed SD-WAN event visibility problem within the approved change scope? During a scoped eastern region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The change ticket limits modifications to the cloud PoP and private hub path and requires a reversible test.
- Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway.
- Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA.
- 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.
Explanation
Correct Answer
C:Correct: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The targeted remedy is Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard. This addresses absent sd-wan events prevent reliable historical path attribution. Confirm it by: Force a link state change and correlate event timestamps, member identity and affected sessions. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0106.]
Incorrect Answers
A:That intervention addresses Active health-check target selection: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The case-specific requirement is: Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard. Verify it with: Force a link state change and correlate event timestamps, member identity and affected sessions.
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: Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard. Verify it with: Force a link state change and correlate event timestamps, member identity and affected sessions.
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: Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard. Verify it with: Force a link state change and correlate event timestamps, member identity and affected sessions.
Question 107
Which independent diagnostic check best validates that the SD-WAN event visibility repair works? During a scoped eastern region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The change ticket limits modifications to the cloud PoP and private hub path and requires a reversible test.
- Inject variable delay while keeping packet loss constant and compare SLA qualification and routing.
- Force a link state change and correlate event timestamps, member identity and affected sessions.
- Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
- Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
Explanation
Correct Answer
B:Correct: Force a link state change and correlate event timestamps, member identity and affected sessions. This directly tests the failure mechanism and the required acceptance evidence: Operators can reconstruct which member was used and why a failover occurred. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0107.]
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 Force a link state change and correlate event timestamps, member identity and affected sessions. The case-specific evidence is Force a link state change and correlate event timestamps, member identity and affected sessions. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0107.]
C: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 Force a link state change and correlate event timestamps, member identity and affected sessions. The case-specific evidence is Force a link state change and correlate event timestamps, member identity and affected sessions. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0107.]
D: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 relevant verification here is: Force a link state change and correlate event timestamps, member identity and affected sessions.
Question 108
What observable result would show that the intended SD-WAN event visibility behavior has been restored? During a scoped eastern region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The change ticket limits modifications to the cloud PoP and private hub path and requires a reversible test.
- Voice selects an in-SLA path according to the stated steering rule.
- Each tenant reaches its own resources while overlapping prefixes remain isolated.
- Operators can reconstruct which member was used and why a failover occurred.
- Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member.
Explanation
Correct Answer
C:Correct: Operators can reconstruct which member was used and why a failover occurred. That result demonstrates the requested controlled repair and avoids the failure mode: Absent SD-WAN events prevent reliable historical path attribution. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0108.]
Incorrect Answers
A:Incorrect for this case: Voice selects an in-SLA path according to the stated steering rule. concerns the separate issue of Performance SLA latency threshold (Voice sessions remain on a high-latency WAN link even though another member has lower delay.). It does not directly establish Operators can reconstruct which member was used and why a failover occurred. The case-specific evidence is Force a link state change and correlate event timestamps, member identity and affected sessions. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0108.]
B:Incorrect for this case: Each tenant reaches its own resources while overlapping prefixes remain isolated. concerns the separate issue of MSSP tenant isolation through VRFs (Two managed tenants advertise identical branch subnets and route exchange could expose one tenant to the other.). It does not directly establish Operators can reconstruct which member was used and why a failover occurred. The case-specific evidence is Force a link state change and correlate event timestamps, member identity and affected sessions. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0108.]
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 case-specific requirement is: Operators can reconstruct which member was used and why a failover occurred. Verify it with: Force a link state change and correlate event timestamps, member identity and affected sessions.
Question 109
Which failure mechanism BEST explains the SD-WAN event visibility observation before a repair is attempted? During a scoped eastern region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The change ticket limits modifications to the cloud PoP and private hub path and requires a reversible test.
- Mismatched serial and site metadata cause a wrong ZTP assignment.
- Absent SD-WAN events prevent reliable historical path attribution.
- Overly sensitive health thresholds cause path flapping.
- The health check measures only the local gateway, not the required service path.
Explanation
Correct Answer
B:Correct: Absent SD-WAN events prevent reliable historical path attribution. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Force a link state change and correlate event timestamps, member identity and affected sessions. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0109.]
Incorrect Answers
A:The Zero-touch device inventory accuracy diagnosis does not explain the observed case: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The supported diagnosis is: Absent SD-WAN events prevent reliable historical path attribution.
C:The SLA flap reduction diagnosis does not explain the observed case: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The supported diagnosis is: Absent SD-WAN events prevent reliable historical path attribution.
D:The Active health-check target selection diagnosis does not explain the observed case: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The supported diagnosis is: Absent SD-WAN events prevent reliable historical path attribution.
Question 110
Select THREE correct elements of a safe remedy-and-evidence plan for the SD-WAN event visibility case. During a scoped eastern region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The change ticket limits modifications to the cloud PoP and private hub path and requires a reversible test.
- Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard.
- Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory.
- Force a link state change and correlate event timestamps, member identity and affected sessions.
- Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
- Operators can reconstruct which member was used and why a failover occurred.
- Voice selects an in-SLA path according to the stated steering rule.
Explanation
Correct Answers
A:Correct remediation element: Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard. It addresses Absent SD-WAN events prevent reliable historical path attribution. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0110.]
C:Correct verification element: Force a link state change and correlate event timestamps, member identity and affected sessions. This independently measures whether the intended change works. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0110.]
E:Operators can reconstruct which member was used and why a failover occurred. This confirms the case-specific path or security boundary.
Incorrect Answers
B: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: Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard. Verify it with: Force a link state change and correlate event timestamps, member identity and affected sessions.
D: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 Force a link state change and correlate event timestamps, member identity and affected sessions. The case-specific evidence is Force a link state change and correlate event timestamps, member identity and affected sessions. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0110.]
F:Incorrect for this case: Voice selects an in-SLA path according to the stated steering rule. concerns the separate issue of Performance SLA latency threshold (Voice sessions remain on a high-latency WAN link even though another member has lower delay.). It does not directly establish Operators can reconstruct which member was used and why a failover occurred. The case-specific evidence is Force a link state change and correlate event timestamps, member identity and affected sessions. [Case R161-C022; Fortinet task A2; anchors EXAM, DESIGN, FMG_TOPO.] [Question R161-Q0110.]
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests