100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 120
Select THREE correct elements of a safe remedy-and-evidence plan for the Performance SLA latency threshold case. During a scoped western region deployment across a staged branch cohort, HelioCare Clinics must commission the planned FortiSASE/SD-WAN control. The operational finding is: Voice sessions remain on a high-latency WAN link even though another member has lower delay. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
- Voice selects an in-SLA path according to the stated steering rule.
- Design a primary/secondary or active/active dual-hub regional overlay with explicit failover and reachability policy.
- Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA.
- The new member can carry authorized sessions without opening unrelated zones.
- Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
Explanation
Correct Answers
A:Correct verification element: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. This independently measures whether the intended change works. [Case R161-C024; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0120.]
B:Voice selects an in-SLA path according to the stated steering rule. This confirms the case-specific path or security boundary.
D:Correct remediation element: Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. It addresses Traffic steering was not conditioned on application-specific link quality. [Case R161-C024; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0120.]
Incorrect Answers
C:That intervention addresses Dual-hub regional survivability: A newly added region depends on one datacenter hub and remote sites lose their overlay if that hub fails. The case-specific requirement is: Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. Verify it with: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
E: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: Voice selects an in-SLA path according to the stated steering rule. Verify it with: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
F:Incorrect for this case: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. concerns the separate issue of DIA egress segmentation (A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay.). It does not directly establish Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. The case-specific evidence is Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. [Case R161-C024; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0120.]
Question 121
Which corrective action MOST DIRECTLY addresses the observed Performance SLA latency threshold problem within the approved change scope? Following a production change affecting Aster Research in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: Voice sessions remain on a high-latency WAN link even though another member has lower delay. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Set explicit hub selection costs or route preference according to the approved dual-hub policy.
- Correct per-device or per-group metadata variables before pushing the overlay template.
- Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA.
- Restore underlay addressing and reachability before changing overlay encryption or BGP parameters.
Explanation
Correct Answer
C:Correct: Voice sessions remain on a high-latency WAN link even though another member has lower delay. The targeted remedy is Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. This addresses traffic steering was not conditioned on application-specific link quality. Confirm it by: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0121.]
Incorrect Answers
A:That intervention addresses Dual-hub route preference: A secondary hub works during failover but normal traffic returns through it even after the primary is healthy. The case-specific requirement is: Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. Verify it with: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
B: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 case-specific requirement is: Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. Verify it with: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
D:That intervention addresses Underlay prerequisite before IPsec: IPsec tunnels fail to establish at a remote branch because the peer's public underlay address is unreachable. The case-specific requirement is: Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. Verify it with: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
Question 122
Which independent diagnostic check best validates that the Performance SLA latency threshold repair works? Following a production change affecting Aster Research in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: Voice sessions remain on a high-latency WAN link even though another member has lower delay. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Test underlay peer reachability and then verify IKE/IPsec negotiation and overlay routes.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
- Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
- Simulate loss of the regional primary hub and inspect backup tunnel, route and application reachability.
Explanation
Correct Answer
C:Correct: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. This directly tests the failure mechanism and the required acceptance evidence: Voice selects an in-SLA path according to the stated steering rule. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0122.]
Incorrect Answers
A:That intervention addresses Underlay prerequisite before IPsec: IPsec tunnels fail to establish at a remote branch because the peer's public underlay address is unreachable. The relevant verification here is: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
B: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: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
D:That intervention addresses Dual-hub regional survivability: A newly added region depends on one datacenter hub and remote sites lose their overlay if that hub fails. The relevant verification here is: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
Question 123
What observable result would show that the intended Performance SLA latency threshold behavior has been restored? Following a production change affecting Aster Research in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: Voice sessions remain on a high-latency WAN link even though another member has lower delay. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Normal and failover path choices follow the intended hub priority.
- New branches inherit consistent region-specific overlay design without manual drift.
- Voice selects an in-SLA path according to the stated steering rule.
- The secure overlay establishes after the underlay path is restored.
Explanation
Correct Answer
C:Correct: Voice selects an in-SLA path according to the stated steering rule. That result demonstrates the requested controlled repair and avoids the failure mode: Traffic steering was not conditioned on application-specific link quality. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0123.]
Incorrect Answers
A:Incorrect for this case: Normal and failover path choices follow the intended hub priority. concerns the separate issue of Dual-hub route preference (A secondary hub works during failover but normal traffic returns through it even after the primary is healthy.). It does not directly establish Voice selects an in-SLA path according to the stated steering rule. The case-specific evidence is Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0123.]
B: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: Voice selects an in-SLA path according to the stated steering rule. Verify it with: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
D: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 Voice selects an in-SLA path according to the stated steering rule. The case-specific evidence is Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0123.]
Question 124
Which failure mechanism BEST explains the Performance SLA latency threshold observation before a repair is attempted? Following a production change affecting Aster Research in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: Voice sessions remain on a high-latency WAN link even though another member has lower delay. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- An all-prefix route leak violates the required tenant boundary.
- A zone-to-policy mismatch blocks traffic despite physical link state.
- A globally resolved metadata variable overwrote regional differences.
- Traffic steering was not conditioned on application-specific link quality.
Explanation
Correct Answer
D:Correct: Traffic steering was not conditioned on application-specific link quality. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0124.]
Incorrect Answers
A:The VRF route exchange exceptions diagnosis does not explain the observed case: Voice sessions remain on a high-latency WAN link even though another member has lower delay. The supported diagnosis is: Traffic steering was not conditioned on application-specific link quality.
B:The Member zone policy binding diagnosis does not explain the observed case: Voice sessions remain on a high-latency WAN link even though another member has lower delay. The supported diagnosis is: Traffic steering was not conditioned on application-specific link quality.
C:The Branch template variable scope diagnosis does not explain the observed case: Voice sessions remain on a high-latency WAN link even though another member has lower delay. The supported diagnosis is: Traffic steering was not conditioned on application-specific link quality.
Question 125
Select TWO correct elements of a safe remedy-and-evidence plan for the Performance SLA latency threshold case. Following a production change affecting Aster Research in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: Voice sessions remain on a high-latency WAN link even though another member has lower delay. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
- Design separate VRF-aware overlays and routing contexts for the tenants, with explicit permitted interconnection only.
- Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA.
- Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
- A branch receives its intended configuration without importing another branch's identity.
Explanation
Correct Answers
A:Correct verification element: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. This independently measures whether the intended change works. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0125.]
C:Correct remediation element: Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. It addresses Traffic steering was not conditioned on application-specific link quality. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0125.]
Incorrect Answers
B:Incorrect for this case: Design separate VRF-aware overlays and routing contexts for the tenants, with explicit permitted interconnection only. 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 Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. The case-specific evidence is Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0125.]
D:Incorrect for this case: Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy. concerns the separate issue of DIA egress segmentation (A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay.). It does not directly establish Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. The case-specific evidence is Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. [Case R161-C025; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0125.]
E:That intervention addresses Zero-touch device inventory accuracy: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The case-specific requirement is: Voice selects an in-SLA path according to the stated steering rule. Verify it with: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
Question 126
Which corrective action MOST DIRECTLY addresses the observed Active health-check target selection problem within the approved change scope? During a scoped metro branch group deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard.
- Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation.
- Design separate VRF-aware overlays and routing contexts for the tenants, with explicit permitted interconnection only.
- Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway.
Explanation
Correct Answer
D:Correct: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The targeted remedy is Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway. This addresses the health check measures only the local gateway, not the required service path. Confirm it by: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0126.]
Incorrect Answers
A:Incorrect for this case: Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard. concerns the separate issue of SD-WAN event visibility (A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence.). It does not directly establish Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway. The case-specific evidence is Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0126.]
B:That intervention addresses Zero-touch device inventory accuracy: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The case-specific requirement is: Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway. Verify it with: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
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: Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway. Verify it with: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
Question 127
Which independent diagnostic check best validates that the Active health-check target selection repair works? During a scoped metro branch group deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Test underlay peer reachability and then verify IKE/IPsec negotiation and overlay routes.
- Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
- Record the selected hub path before failure, during simulated failure and after recovery.
- Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
Explanation
Correct Answer
B:Correct: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. This directly tests the failure mechanism and the required acceptance evidence: Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0127.]
Incorrect Answers
A:Incorrect for this case: Test underlay peer reachability and then verify IKE/IPsec negotiation and overlay routes. 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 Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. The case-specific evidence is Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0127.]
C:Incorrect for this case: Record the selected hub path before failure, during simulated failure and after recovery. concerns the separate issue of Dual-hub route preference (A secondary hub works during failover but normal traffic returns through it even after the primary is healthy.). It does not directly establish Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. The case-specific evidence is Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0127.]
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: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
Question 128
What observable result would show that the intended Active health-check target selection behavior has been restored? During a scoped metro branch group deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Each branch receives the region-appropriate hub set and overlay addressing.
- A branch receives its intended configuration without importing another branch's identity.
- 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
D:Correct: Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member. That result demonstrates the requested controlled repair and avoids the failure mode: The health check measures only the local gateway, not the required service path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0128.]
Incorrect Answers
A: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 case-specific requirement is: Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member. Verify it with: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
B:Incorrect for this case: A branch receives its intended configuration without importing another branch's identity. 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 Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member. The case-specific evidence is Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0128.]
C: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: Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member. Verify it with: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
Question 129
Which failure mechanism BEST explains the Active health-check target selection observation before a repair is attempted? During a scoped metro branch group deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Single-hub dependency is the unresolved resilience weakness.
- Absent SD-WAN events prevent reliable historical path attribution.
- The health check measures only the local gateway, not the required service path.
- A zone-to-policy mismatch blocks traffic despite physical link state.
Explanation
Correct Answer
C:Correct: The health check measures only the local gateway, not the required service path. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0129.]
Incorrect Answers
A:The Dual-hub regional survivability diagnosis does not explain the observed case: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The supported diagnosis is: The health check measures only the local gateway, not the required service path.
B:The SD-WAN event visibility diagnosis does not explain the observed case: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The supported diagnosis is: The health check measures only the local gateway, not the required service path.
D:Incorrect diagnosis: this describes a different operational mechanism (Member zone policy binding), not the documented observation (A link passes a gateway ping but cannot reach business applications beyond the provider edge.). The supported case diagnosis is The health check measures only the local gateway, not the required service path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0129.]
Question 130
Select THREE correct elements of a safe remedy-and-evidence plan for the Active health-check target selection case. During a scoped metro branch group deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: A link passes a gateway ping but cannot reach business applications beyond the provider edge. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard.
- Internet access uses approved DIA inspection while internal destinations take the private overlay.
- Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member.
- Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway.
- Advertise identical test prefixes in both VRFs and check route tables and denied cross-tenant probes.
- Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
Explanation
Correct Answers
C:Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member. This confirms the case-specific path or security boundary.
D:Correct remediation element: Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway. It addresses The health check measures only the local gateway, not the required service path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0130.]
F:Correct verification element: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. This independently measures whether the intended change works. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0130.]
Incorrect Answers
A:Incorrect for this case: Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard. concerns the separate issue of SD-WAN event visibility (A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence.). It does not directly establish Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway. The case-specific evidence is Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path. [Case R161-C026; Fortinet task A3; anchors EXAM, SLA, DESIGN.] [Question R161-Q0130.]
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 case-specific requirement is: Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member. Verify it with: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
E: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: Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests