100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 20
Select THREE correct elements of a safe remedy-and-evidence plan for the Scaled regional address planning case. During a scoped northern sites deployment across a staged branch cohort, Northbank Logistics must commission the planned FortiSASE/SD-WAN control. The operational finding is: An overlay rollout reuses a loopback range already assigned to spokes in a second region. The change ticket limits modifications to the cloud PoP and private hub path and requires a reversible test.
- Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
- Each node has unique tunnel and loopback addressing for stable routing.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
- Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory.
- The new member can carry authorized sessions without opening unrelated zones.
- Use representative reachable SLA probe targets that test the relevant upstream path rather than only the first gateway.
Explanation
Correct Answers
A:Correct verification element: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. This independently measures whether the intended change works. [Case R161-C004; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0020.]
B:Each node has unique tunnel and loopback addressing for stable routing. This confirms the case-specific path or security boundary.
D:Correct remediation element: Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory. It addresses Overlapping overlay and loopback allocations break unambiguous next-hop resolution. [Case R161-C004; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0020.]
Incorrect Answers
C:That intervention addresses Branch template variable scope: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. The relevant verification here is: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
E:Incorrect for this case: The new member can carry authorized sessions without opening unrelated zones. concerns the separate issue of 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.). It does not directly establish Each node has unique tunnel and loopback addressing for stable routing. The case-specific evidence is Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. [Case R161-C004; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0020.]
F: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: Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory. Verify it with: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
Question 21
Which corrective action MOST DIRECTLY addresses the observed Scaled regional address planning problem within the approved change scope? Following a production change affecting Seaboard Financial in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay rollout reuses a loopback range already assigned to spokes in a second region. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Enable and retain SD-WAN event and traffic logging, with a monitored operational dashboard.
- Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory.
- Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA.
- Separate DIA underlay egress from protected overlay traffic through zones, routes and security policies.
Explanation
Correct Answer
B:Correct: An overlay rollout reuses a loopback range already assigned to spokes in a second region. The targeted remedy is Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory. This addresses overlapping overlay and loopback allocations break unambiguous next-hop resolution. Confirm it by: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0021.]
Incorrect Answers
A:That intervention addresses SD-WAN event visibility: A branch's WAN failover happened overnight but its operations team has only interface counters, not path-change evidence. The case-specific requirement is: Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory. Verify it with: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
C:Incorrect for this case: Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. 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 Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory. The case-specific evidence is Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0021.]
D:That intervention addresses DIA egress segmentation: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The case-specific requirement is: Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory. Verify it with: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
Question 22
Which independent diagnostic check best validates that the Scaled regional address planning repair works? Following a production change affecting Seaboard Financial in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay rollout reuses a loopback range already assigned to spokes in a second region. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Inspect the zone membership and policy hit logs while generating a representative permitted session.
- Record the selected hub path before failure, during simulated failure and after recovery.
- Test underlay peer reachability and then verify IKE/IPsec negotiation and overlay routes.
- Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
Explanation
Correct Answer
D:Correct: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. This directly tests the failure mechanism and the required acceptance evidence: Each node has unique tunnel and loopback addressing for stable routing. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0022.]
Incorrect Answers
A:Incorrect for this case: Inspect the zone membership and policy hit logs while generating a representative permitted session. concerns the separate issue of 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.). It does not directly establish Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. The case-specific evidence is Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0022.]
B: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 Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. The case-specific evidence is Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0022.]
C: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: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
Question 23
What observable result would show that the intended Scaled regional address planning behavior has been restored? Following a production change affecting Seaboard Financial in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay rollout reuses a loopback range already assigned to spokes in a second region. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Real-time traffic avoids the member violating jitter tolerance.
- Each branch receives the region-appropriate hub set and overlay addressing.
- Each node has unique tunnel and loopback addressing for stable routing.
- Internet access uses approved DIA inspection while internal destinations take the private overlay.
Explanation
Correct Answer
C:Correct: Each node has unique tunnel and loopback addressing for stable routing. That result demonstrates the requested controlled repair and avoids the failure mode: Overlapping overlay and loopback allocations break unambiguous next-hop resolution. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0023.]
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 node has unique tunnel and loopback addressing for stable routing. Verify it with: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
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: Each node has unique tunnel and loopback addressing for stable routing. Verify it with: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
D:That intervention addresses DIA egress segmentation: A branch sends trusted internal application traffic directly to the public internet instead of the protected overlay. The case-specific requirement is: Each node has unique tunnel and loopback addressing for stable routing. Verify it with: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
Question 24
Which failure mechanism BEST explains the Scaled regional address planning observation before a repair is attempted? Following a production change affecting Seaboard Financial in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay rollout reuses a loopback range already assigned to spokes in a second region. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Overly sensitive health thresholds cause path flapping.
- Traffic steering was not conditioned on application-specific link quality.
- Overlapping overlay and loopback allocations break unambiguous next-hop resolution.
- A globally resolved metadata variable overwrote regional differences.
Explanation
Correct Answer
C:Correct: Overlapping overlay and loopback allocations break unambiguous next-hop resolution. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0024.]
Incorrect Answers
A:The SLA flap reduction diagnosis does not explain the observed case: An overlay rollout reuses a loopback range already assigned to spokes in a second region. The supported diagnosis is: Overlapping overlay and loopback allocations break unambiguous next-hop resolution.
B:Incorrect diagnosis: this describes a different operational mechanism (Performance SLA latency threshold), not the documented observation (An overlay rollout reuses a loopback range already assigned to spokes in a second region.). The supported case diagnosis is Overlapping overlay and loopback allocations break unambiguous next-hop resolution. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0024.]
D:The Branch template variable scope diagnosis does not explain the observed case: An overlay rollout reuses a loopback range already assigned to spokes in a second region. The supported diagnosis is: Overlapping overlay and loopback allocations break unambiguous next-hop resolution.
Question 25
Select TWO correct elements of a safe remedy-and-evidence plan for the Scaled regional address planning case. Following a production change affecting Seaboard Financial in its cross-border operations, a network team receives repeatable user-impact reports. Its fault evidence is: An overlay rollout reuses a loopback range already assigned to spokes in a second region. Unrelated services are still operating, so the immediate response must isolate the failing control for a controlled device cohort without disabling unrelated protections.
- Sustained failures trigger rerouting without excess oscillation on brief jitter spikes.
- Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
- Force a link state change and correlate event timestamps, member identity and affected sessions.
- Correct per-device or per-group metadata variables before pushing the overlay template.
- Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory.
Explanation
Correct Answers
B:Correct verification element: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. This independently measures whether the intended change works. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0025.]
E:Correct remediation element: Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory. It addresses Overlapping overlay and loopback allocations break unambiguous next-hop resolution. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0025.]
Incorrect Answers
A:Incorrect for this case: Sustained failures trigger rerouting without excess oscillation on brief jitter spikes. concerns the separate issue of SLA flap reduction (An unstable WAN member oscillates across the configured quality threshold, repeatedly moving new sessions.). It does not directly establish Each node has unique tunnel and loopback addressing for stable routing. The case-specific evidence is Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0025.]
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 relevant verification here is: Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs.
D:Incorrect for this case: Correct per-device or per-group metadata variables before pushing the overlay template. concerns the separate issue of Branch template variable scope (An overlay template places all branches into the same region because a group variable is resolved at the wrong scope.). It does not directly establish Allocate unique overlay and loopback address ranges before template deployment, then validate against the inventory. The case-specific evidence is Compare generated hub and spoke address maps across both regions and check for duplicated interface IPs. [Case R161-C005; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0025.]
Question 26
Which corrective action MOST DIRECTLY addresses the observed Zero-touch device inventory accuracy problem within the approved change scope? During a scoped eastern region deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Assign the member to the intended SD-WAN zone and update the appropriate policy interface scope.
- Set explicit hub selection costs or route preference according to the approved dual-hub policy.
- Restore underlay addressing and reachability before changing overlay encryption or BGP parameters.
- Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation.
Explanation
Correct Answer
D:Correct: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The targeted remedy is Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation. This addresses mismatched serial and site metadata cause a wrong ztp assignment. Confirm it by: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0026.]
Incorrect Answers
A:Incorrect for this case: Assign the member to the intended SD-WAN zone and update the appropriate policy interface scope. concerns the separate issue of 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.). It does not directly establish Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation. The case-specific evidence is Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0026.]
B:Incorrect for this case: Set explicit hub selection costs or route preference according to the approved dual-hub policy. 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 Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation. The case-specific evidence is Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0026.]
C: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: Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation. Verify it with: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory.
Question 27
Which independent diagnostic check best validates that the Zero-touch device inventory accuracy repair works? During a scoped eastern region deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory.
- Generate a quiet period, then inspect freshness and confidence of per-member SLA measurements.
- Trace one internet destination and one private-prefix destination and inspect egress interface and matching policy.
- Review generated configurations for branches in two regions and confirm hub targets and addresses.
Explanation
Correct Answer
A:Correct: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. This directly tests the failure mechanism and the required acceptance evidence: A branch receives its intended configuration without importing another branch's identity. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0027.]
Incorrect Answers
B:Incorrect for this case: Generate a quiet period, then inspect freshness and confidence of per-member SLA measurements. 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 Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. The case-specific evidence is Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0027.]
C: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 Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. The case-specific evidence is Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0027.]
D:That intervention addresses Branch template variable scope: An overlay template places all branches into the same region because a group variable is resolved at the wrong scope. The relevant verification here is: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory.
Question 28
What observable result would show that the intended Zero-touch device inventory accuracy behavior has been restored? During a scoped eastern region deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- The standby path is evaluated with current health evidence before selection.
- The new member can carry authorized sessions without opening unrelated zones.
- Operators can reconstruct which member was used and why a failover occurred.
- A branch receives its intended configuration without importing another branch's identity.
Explanation
Correct Answer
D:Correct: A branch receives its intended configuration without importing another branch's identity. That result demonstrates the requested controlled repair and avoids the failure mode: Mismatched serial and site metadata cause a wrong ZTP assignment. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0028.]
Incorrect Answers
A:That intervention addresses Passive health measurement validity: A low-traffic backup link reports stale quality measurements and is chosen based on old samples. The case-specific requirement is: A branch receives its intended configuration without importing another branch's identity. Verify it with: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory.
B:Incorrect for this case: The new member can carry authorized sessions without opening unrelated zones. concerns the separate issue of 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.). It does not directly establish A branch receives its intended configuration without importing another branch's identity. The case-specific evidence is Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0028.]
C:Incorrect for this case: Operators can reconstruct which member was used and why a failover occurred. 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 A branch receives its intended configuration without importing another branch's identity. The case-specific evidence is Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0028.]
Question 29
Which failure mechanism BEST explains the Zero-touch device inventory accuracy observation before a repair is attempted? During a scoped eastern region deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Mismatched serial and site metadata cause a wrong ZTP assignment.
- A zone-to-policy mismatch blocks traffic despite physical link state.
- Packet-loss-only health checks miss the actual audio impairment.
- Overly sensitive health thresholds cause path flapping.
Explanation
Correct Answer
A:Correct: Mismatched serial and site metadata cause a wrong ZTP assignment. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0029.]
Incorrect Answers
B:The Member zone policy binding diagnosis does not explain the observed case: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The supported diagnosis is: Mismatched serial and site metadata cause a wrong ZTP assignment.
C:The Jitter-based real-time steering diagnosis does not explain the observed case: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The supported diagnosis is: Mismatched serial and site metadata cause a wrong ZTP assignment.
D:The SLA flap reduction diagnosis does not explain the observed case: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The supported diagnosis is: Mismatched serial and site metadata cause a wrong ZTP assignment.
Question 30
Select THREE correct elements of a safe remedy-and-evidence plan for the Zero-touch device inventory accuracy case. During a scoped eastern region deployment across a staged branch cohort, Ironleaf Agriculture must commission the planned FortiSASE/SD-WAN control. The operational finding is: Branch devices are shipped but the deployment CSV associates serial numbers with the wrong site metadata. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- The new member can carry authorized sessions without opening unrelated zones.
- Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation.
- Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA.
- Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory.
- A branch receives its intended configuration without importing another branch's identity.
- Test underlay peer reachability and then verify IKE/IPsec negotiation and overlay routes.
Explanation
Correct Answers
B:Correct remediation element: Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation. It addresses Mismatched serial and site metadata cause a wrong ZTP assignment. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0030.]
D:Correct verification element: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. This independently measures whether the intended change works. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0030.]
E:A branch receives its intended configuration without importing another branch's identity. This confirms the case-specific path or security boundary.
Incorrect Answers
A:Incorrect for this case: The new member can carry authorized sessions without opening unrelated zones. concerns the separate issue of 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.). It does not directly establish A branch receives its intended configuration without importing another branch's identity. The case-specific evidence is Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0030.]
C:Incorrect for this case: Apply a voice-specific SD-WAN rule tied to a measured latency/jitter performance SLA. 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 Correct the device blueprint, CSV device identity and branch-group mapping before ZTP activation. The case-specific evidence is Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory. [Case R161-C006; Fortinet task A1; anchors EXAM, FMG_PLANNING, FMG_TOPOLOGY.] [Question R161-Q0030.]
F: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: Onboard a staged device and compare its installed site variables, serial and hub association with the approved inventory.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests