100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 40
Select THREE correct elements of a safe remedy-and-evidence plan for the VRF route exchange exceptions case. During a scoped western region deployment across a staged branch cohort, Harborlight Industrial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member.
- Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard.
- Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
- Only the approved shared-service route is reachable across the isolation boundary.
- Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules.
Explanation
Correct Answers
C:Correct verification element: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. This independently measures whether the intended change works. [Case R161-C008; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0040.]
E:Only the approved shared-service route is reachable across the isolation boundary. This confirms the case-specific path or security boundary.
F:Correct remediation element: Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules. It addresses An all-prefix route leak violates the required tenant boundary. [Case R161-C008; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0040.]
Incorrect Answers
A: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 Only the approved shared-service route is reachable across the isolation boundary. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C008; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0040.]
B: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 narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C008; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0040.]
D:Incorrect for this case: Review generated configurations for branches in two regions and confirm hub targets and addresses. 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 Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C008; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0040.]
Question 41
Which corrective action MOST DIRECTLY addresses the observed VRF route exchange exceptions problem within the approved change scope? Following a production change affecting Redvale Manufacturing in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- Include jitter in the application SLA and steer real-time sessions to the member meeting that criterion.
- Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies.
- Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules.
- Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard.
Explanation
Correct Answer
C:Correct: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. The targeted remedy is Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules. This addresses an all-prefix route leak violates the required tenant boundary. Confirm it by: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0041.]
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: Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules. Verify it with: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
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: Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules. Verify it with: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
D: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 narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0041.]
Question 42
Which independent diagnostic check best validates that the VRF route exchange exceptions repair works? Following a production change affecting Redvale Manufacturing in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions.
- Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
- Run short and sustained impairments and count member state changes before and after tuning.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
Explanation
Correct Answer
B:Correct: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. This directly tests the failure mechanism and the required acceptance evidence: Only the approved shared-service route is reachable across the isolation boundary. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0042.]
Incorrect Answers
A:Incorrect for this case: Impose controlled latency on the preferred link and inspect SLA status plus selected member for new voice sessions. 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 Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0042.]
C:That intervention addresses SLA flap reduction: An unstable WAN member oscillates across the configured quality threshold, repeatedly moving new sessions. The relevant verification here is: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
D:Incorrect for this case: Review generated configurations for branches in two regions and confirm hub targets and addresses. 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 Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0042.]
Question 43
What observable result would show that the intended VRF route exchange exceptions behavior has been restored? Following a production change affecting Redvale Manufacturing in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- The new member can carry authorized sessions without opening unrelated zones.
- Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member.
- The standby path is evaluated with current health evidence before selection.
- Only the approved shared-service route is reachable across the isolation boundary.
Explanation
Correct Answer
D:Correct: Only the approved shared-service route is reachable across the isolation boundary. That result demonstrates the requested controlled repair and avoids the failure mode: An all-prefix route leak violates the required tenant boundary. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0043.]
Incorrect Answers
A: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: Only the approved shared-service route is reachable across the isolation boundary. Verify it with: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
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 Only the approved shared-service route is reachable across the isolation boundary. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0043.]
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 Only the approved shared-service route is reachable across the isolation boundary. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0043.]
Question 44
Which failure mechanism BEST explains the VRF route exchange exceptions observation before a repair is attempted? Following a production change affecting Redvale Manufacturing in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- An all-prefix route leak violates the required tenant boundary.
- Absent SD-WAN events prevent reliable historical path attribution.
- Passive measurements depend on active user sessions and can become stale.
- Hub preference policy is missing or inconsistent after reconvergence.
Explanation
Correct Answer
A:Correct: An all-prefix route leak violates the required tenant boundary. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0044.]
Incorrect Answers
B:The SD-WAN event visibility diagnosis does not explain the observed case: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. The supported diagnosis is: An all-prefix route leak violates the required tenant boundary.
C:The Passive health measurement validity diagnosis does not explain the observed case: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. The supported diagnosis is: An all-prefix route leak violates the required tenant boundary.
D:The Dual-hub route preference diagnosis does not explain the observed case: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. The supported diagnosis is: An all-prefix route leak violates the required tenant boundary.
Question 45
Select TWO correct elements of a safe remedy-and-evidence plan for the VRF route exchange exceptions case. Following a production change affecting Redvale Manufacturing in its coastal district, a network team receives repeatable user-impact reports. Its fault evidence is: A shared services segment must be reachable from two VRF-isolated tenants but unrestricted leaking is prohibited. Unrelated services are still operating, so the immediate response must isolate the failing control for the affected production application without disabling unrelated protections.
- Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules.
- Tune supported SLA monitoring and link state-change behavior to avoid reacting to transient probe noise.
- Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
- The standby path is evaluated with current health evidence before selection.
- Inject variable delay while keeping packet loss constant and compare SLA qualification and routing.
Explanation
Correct Answers
A:Correct remediation element: Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules. It addresses An all-prefix route leak violates the required tenant boundary. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0045.]
C:Correct verification element: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. This independently measures whether the intended change works. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0045.]
Incorrect Answers
B:Incorrect for this case: Tune supported SLA monitoring and link state-change behavior to avoid reacting to transient probe noise. 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 Use narrowly scoped route-leaking or controlled shared-services access with explicit permitted prefixes and firewall rules. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0045.]
D: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 Only the approved shared-service route is reachable across the isolation boundary. The case-specific evidence is Test the approved shared-service prefix and a prohibited tenant prefix from each VRF. [Case R161-C009; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0045.]
E: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: Test the approved shared-service prefix and a prohibited tenant prefix from each VRF.
Question 46
Which corrective action MOST DIRECTLY addresses the observed Overlay scaling via grouped branches problem within the approved change scope? 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.
- Use appropriately configured active probes when continuous readiness measurements are required.
- Correct per-device or per-group metadata variables before pushing the overlay template.
- Assign the member to the intended SD-WAN zone and update the appropriate policy interface scope.
Explanation
Correct Answer
A: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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0046.]
Incorrect Answers
B:That intervention addresses Passive health measurement validity: A low-traffic backup link reports stale quality measurements and is chosen based on old samples. 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: 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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0046.]
D: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: 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 47
Which independent diagnostic check best validates that the Overlay scaling via grouped branches repair works? 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.
- Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
- Run short and sustained impairments and count member state changes before and after tuning.
- Disconnect upstream service while keeping the gateway alive; inspect health-check state and selected path.
- Generate a quiet period, then inspect freshness and confidence of per-member SLA measurements.
Explanation
Correct Answer
A: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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0047.]
Incorrect Answers
B: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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0047.]
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 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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0047.]
D: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: Compare generated branch configuration for representative devices in each group and verify hub/overlay consistency.
Question 48
What observable result would show that the intended Overlay scaling via grouped branches behavior has been restored? 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.
- Voice selects an in-SLA path according to the stated steering rule.
- New branches inherit consistent region-specific overlay design without manual drift.
- The secure overlay establishes after the underlay path is restored.
- Unusable upstream connectivity is detected instead of being mistaken for a healthy WAN member.
Explanation
Correct Answer
B: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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0048.]
Incorrect Answers
A: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: 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.
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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0048.]
D: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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0048.]
Question 49
Which failure mechanism BEST explains the Overlay scaling via grouped branches observation before a repair is attempted? 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.
- Traffic steering was not conditioned on application-specific link quality.
- Overly sensitive health thresholds cause path flapping.
- A globally resolved metadata variable overwrote regional differences.
- Per-branch template cloning produced inconsistent topology metadata.
Explanation
Correct Answer
D: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-C010; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0049.]
Incorrect Answers
A:The Performance SLA latency threshold 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.
B:The SLA flap reduction 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 Branch template variable scope 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 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.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests