100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 590
Select THREE correct elements of a safe remedy-and-evidence plan for the Mixed edge and remote-user segmentation case. Following a production change affecting Harborlight Industrial in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: Branch LAN-extension traffic and individual remote-user traffic share FortiSASE but need different access restrictions. Unrelated services are still operating, so the immediate response must isolate the failing control for the cloud PoP and private hub path without disabling unrelated protections.
- Compare a branch device and an agent-based laptop against the same restricted destination.
- Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP.
- Protected browser sessions pass through the cloud proxy without requiring an endpoint agent.
- Use a supported dedicated public IP egress capability with validated policy and licensing assumptions.
- Create separate policy identities/scopes for site-based edge sessions and individual remote-user sessions.
- Each traffic population receives its appropriate policy without accidental role inheritance.
Explanation
Correct Answers
A:Correct verification element: Compare a branch device and an agent-based laptop against the same restricted destination. This independently measures whether the intended change works. [Case R161-C118; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0590.]
E:Correct remediation element: Create separate policy identities/scopes for site-based edge sessions and individual remote-user sessions. It addresses A single undifferentiated source identity causes access-policy overlap. [Case R161-C118; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0590.]
F:Each traffic population receives its appropriate policy without accidental role inheritance. This confirms the case-specific path or security boundary.
Incorrect Answers
B:Incorrect for this case: Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP. concerns the separate issue of Private TCP and UDP application access (Remote workers need access to a private UDP-dependent application hosted behind an SD-WAN hub.). It does not directly establish Compare a branch device and an agent-based laptop against the same restricted destination. The case-specific evidence is Compare a branch device and an agent-based laptop against the same restricted destination. [Case R161-C118; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0590.]
C:Incorrect for this case: Protected browser sessions pass through the cloud proxy without requiring an endpoint agent. concerns the separate issue of Agentless browser-only internet access (A contractor uses a device on which the enterprise cannot install FortiClient but must secure browser traffic.). It does not directly establish Each traffic population receives its appropriate policy without accidental role inheritance. The case-specific evidence is Compare a branch device and an agent-based laptop against the same restricted destination. [Case R161-C118; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0590.]
D:That intervention addresses Dedicated public egress IP requirement: A SaaS vendor permits traffic only from a preapproved public address but users traverse changing cloud egress. The case-specific requirement is: Create separate policy identities/scopes for site-based edge sessions and individual remote-user sessions. Verify it with: Compare a branch device and an agent-based laptop against the same restricted destination.
Question 591
Which corrective action MOST DIRECTLY addresses the observed SPA route propagation through dual hubs problem within the approved change scope? During a scoped remote campus corridor deployment across a staged branch cohort, Redvale Manufacturing must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Use the supported FortiClient agent-based SIA mode with the appropriate endpoint profile and FortiSASE security policy.
- Use the vendor-supported tenant and service provisioning workflow with customer-specific administrator scope.
- Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays.
- Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy.
Explanation
Correct Answer
C:Correct: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The targeted remedy is Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. This addresses cloud spa routes were configured only for the primary hub. Confirm it by: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0591.]
Incorrect Answers
A:That intervention addresses Agent-based remote-user secure internet access: Managed laptops require full-tunnel policy enforcement when users browse from unmanaged networks. The case-specific requirement is: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
B:That intervention addresses MSSP customer provisioning separation: An MSSP operator is onboarding two customers with different licenses, policies and delegated admins. The case-specific requirement is: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
D:That intervention addresses Site on-ramp for nonagent branch users: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The case-specific requirement is: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
Question 592
Which independent diagnostic check best validates that the SPA route propagation through dual hubs repair works? During a scoped remote campus corridor deployment across a staged branch cohort, Redvale Manufacturing must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Read the observed public source IP from a SaaS request in each intended user region.
- Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
- Send traffic from an agentless branch host and check the edge-to-PoP transport and applied SIA security policy.
- Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP.
Explanation
Correct Answer
B:Correct: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. This directly tests the failure mechanism and the required acceptance evidence: Both normal and failover hubs advertise viable private application paths to PoPs. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0592.]
Incorrect Answers
A:That intervention addresses Dedicated public egress IP requirement: A SaaS vendor permits traffic only from a preapproved public address but users traverse changing cloud egress. The relevant verification here is: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
C:That intervention addresses Site-based SIA for edge branches: A remote branch has many IoT devices that cannot run individual endpoint agents but need inspected internet access. The relevant verification here is: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
D:Incorrect for this case: Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP. concerns the separate issue of Private TCP and UDP application access (Remote workers need access to a private UDP-dependent application hosted behind an SD-WAN hub.). It does not directly establish Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0592.]
Question 593
What observable result would show that the intended SPA route propagation through dual hubs behavior has been restored? During a scoped remote campus corridor deployment across a staged branch cohort, Redvale Manufacturing must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- The intended private subnet has a viable overlay route from the user's PoP.
- Branch devices receive centrally enforced cloud internet inspection without agents on every host.
- Both normal and failover hubs advertise viable private application paths to PoPs.
- The site gains approved SIA through the configured edge device within its supported feature scope.
Explanation
Correct Answer
C:Correct: Both normal and failover hubs advertise viable private application paths to PoPs. That result demonstrates the requested controlled repair and avoids the failure mode: Cloud SPA routes were configured only for the primary hub. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0593.]
Incorrect Answers
A:That intervention addresses FortiSASE PoP reachability to hub private routes: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The case-specific requirement is: Both normal and failover hubs advertise viable private application paths to PoPs. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
B:That intervention addresses Site-based SIA for edge branches: A remote branch has many IoT devices that cannot run individual endpoint agents but need inspected internet access. The case-specific requirement is: Both normal and failover hubs advertise viable private application paths to PoPs. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
D:That intervention addresses Branch FortiAP as SASE edge: An isolated satellite office uses supported FortiAP edge equipment and wants cloud inspection without a local full FortiGate stack. The case-specific requirement is: Both normal and failover hubs advertise viable private application paths to PoPs. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
Question 594
Which failure mechanism BEST explains the SPA route propagation through dual hubs observation before a repair is attempted? During a scoped remote campus corridor deployment across a staged branch cohort, Redvale Manufacturing must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- A browser-only proxy is not equivalent to the requested managed full-tunnel mode.
- A disconnected SASE tenant cannot automatically learn protected WAN routes.
- Cloud SPA routes were configured only for the primary hub.
- A single undifferentiated source identity causes access-policy overlap.
Explanation
Correct Answer
C:Correct: Cloud SPA routes were configured only for the primary hub. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0594.]
Incorrect Answers
A:The Agent-based remote-user secure internet access diagnosis does not explain the observed case: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The supported diagnosis is: Cloud SPA routes were configured only for the primary hub.
B:The FortiSASE as SD-WAN spoke diagnosis does not explain the observed case: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The supported diagnosis is: Cloud SPA routes were configured only for the primary hub.
D:Incorrect diagnosis: this describes a different operational mechanism (Mixed edge and remote-user segmentation), not the documented observation (An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter.). The supported case diagnosis is Cloud SPA routes were configured only for the primary hub. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0594.]
Question 595
Select TWO correct elements of a safe remedy-and-evidence plan for the SPA route propagation through dual hubs case. During a scoped remote campus corridor deployment across a staged branch cohort, Redvale Manufacturing must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
- Separate SIA and SPA use cases with explicit destination classifications and the appropriate FortiSASE and hub controls.
- Remote users retain secure private access through the approved secondary hub.
- Inspect chosen PoP region and data-flow documentation for a geographically restricted test cohort.
- Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays.
Explanation
Correct Answers
A:Correct verification element: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. This independently measures whether the intended change works. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0595.]
E:Correct remediation element: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. It addresses Cloud SPA routes were configured only for the primary hub. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0595.]
Incorrect Answers
B:That intervention addresses Selective private versus internet access: Remote users must send general web traffic to cloud inspection but private application traffic over approved SPA. The case-specific requirement is: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
C:That intervention addresses Dual-hub SPA resilience: A remote-user SPA design has two datacenters but only the primary hub is associated with the SASE integration. The case-specific requirement is: Both normal and failover hubs advertise viable private application paths to PoPs. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
D:Incorrect for this case: Inspect chosen PoP region and data-flow documentation for a geographically restricted test cohort. concerns the separate issue of Sovereign access-point selection (A tenant's security architecture requires traffic inspection to remain within approved geographic PoPs.). It does not directly establish Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C119; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0595.]
Question 596
Which corrective action MOST DIRECTLY addresses the observed SPA route propagation through dual hubs problem within the approved change scope? Following a production change affecting Bluewater Freight in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix.
- Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays.
- Create separate policy identities/scopes for site-based edge sessions and individual remote-user sessions.
- Validate the supported FortiAP edge/branch on-ramp deployment model and configure its approved FortiSASE uplink.
Explanation
Correct Answer
B:Correct: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The targeted remedy is Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. This addresses cloud spa routes were configured only for the primary hub. Confirm it by: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0596.]
Incorrect Answers
A:That intervention addresses FortiSASE PoP reachability to hub private routes: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The case-specific requirement is: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
C:That intervention addresses Mixed edge and remote-user segmentation: Branch LAN-extension traffic and individual remote-user traffic share FortiSASE but need different access restrictions. The case-specific requirement is: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
D:That intervention addresses Branch FortiAP as SASE edge: An isolated satellite office uses supported FortiAP edge equipment and wants cloud inspection without a local full FortiGate stack. The case-specific requirement is: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
Question 597
Which independent diagnostic check best validates that the SPA route propagation through dual hubs repair works? Following a production change affecting Bluewater Freight in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Compare a branch device and an agent-based laptop against the same restricted destination.
- Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
- Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP.
- Inspect chosen PoP region and data-flow documentation for a geographically restricted test cohort.
Explanation
Correct Answer
B:Correct: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. This directly tests the failure mechanism and the required acceptance evidence: Both normal and failover hubs advertise viable private application paths to PoPs. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0597.]
Incorrect Answers
A:That intervention addresses Mixed edge and remote-user segmentation: Branch LAN-extension traffic and individual remote-user traffic share FortiSASE but need different access restrictions. The relevant verification here is: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
C:Incorrect for this case: Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP. concerns the separate issue of Private TCP and UDP application access (Remote workers need access to a private UDP-dependent application hosted behind an SD-WAN hub.). It does not directly establish Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0597.]
D:Incorrect for this case: Inspect chosen PoP region and data-flow documentation for a geographically restricted test cohort. concerns the separate issue of Sovereign access-point selection (A tenant's security architecture requires traffic inspection to remain within approved geographic PoPs.). It does not directly establish Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0597.]
Question 598
What observable result would show that the intended SPA route propagation through dual hubs behavior has been restored? Following a production change affecting Bluewater Freight in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- The cloud edge participates in authorized private routing while the hub policy remains in control.
- Agentless branch terminals inherit approved cloud enforcement through the edge.
- Both normal and failover hubs advertise viable private application paths to PoPs.
- Each traffic population receives its appropriate policy without accidental role inheritance.
Explanation
Correct Answer
C:Correct: Both normal and failover hubs advertise viable private application paths to PoPs. That result demonstrates the requested controlled repair and avoids the failure mode: Cloud SPA routes were configured only for the primary hub. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0598.]
Incorrect Answers
A:That intervention addresses FortiSASE as SD-WAN spoke: An enterprise wants SASE PoPs to participate in its existing hub-and-spoke routing rather than build unrelated public paths. The case-specific requirement is: Both normal and failover hubs advertise viable private application paths to PoPs. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
B:Incorrect for this case: Agentless branch terminals inherit approved cloud enforcement through the edge. concerns the separate issue of Site on-ramp for nonagent branch users (A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support.). It does not directly establish Both normal and failover hubs advertise viable private application paths to PoPs. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0598.]
D:That intervention addresses Mixed edge and remote-user segmentation: Branch LAN-extension traffic and individual remote-user traffic share FortiSASE but need different access restrictions. The case-specific requirement is: Both normal and failover hubs advertise viable private application paths to PoPs. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
Question 599
Which failure mechanism BEST explains the SPA route propagation through dual hubs observation before a repair is attempted? Following a production change affecting Bluewater Freight in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Cloud SPA routes were configured only for the primary hub.
- Cloud-user authentication alone does not create private SD-WAN reachability.
- A single undifferentiated source identity causes access-policy overlap.
- Treating the access point as an arbitrary full-featured FortiGate substitutes unsupported edge assumptions.
Explanation
Correct Answer
A:Correct: Cloud SPA routes were configured only for the primary hub. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0599.]
Incorrect Answers
B:The FortiSASE PoP reachability to hub private routes diagnosis does not explain the observed case: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The supported diagnosis is: Cloud SPA routes were configured only for the primary hub.
C:Incorrect diagnosis: this describes a different operational mechanism (Mixed edge and remote-user segmentation), not the documented observation (An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter.). The supported case diagnosis is Cloud SPA routes were configured only for the primary hub. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0599.]
D:The Branch FortiAP as SASE edge diagnosis does not explain the observed case: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The supported diagnosis is: Cloud SPA routes were configured only for the primary hub.
Question 600
Select THREE correct elements of a safe remedy-and-evidence plan for the SPA route propagation through dual hubs case. Following a production change affecting Bluewater Freight in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP.
- Both normal and failover hubs advertise viable private application paths to PoPs.
- Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays.
- Agentless branch terminals inherit approved cloud enforcement through the edge.
- Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
- Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs.
Explanation
Correct Answers
B:Both normal and failover hubs advertise viable private application paths to PoPs. This confirms the case-specific path or security boundary.
C:Correct remediation element: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. It addresses Cloud SPA routes were configured only for the primary hub. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0600.]
E:Correct verification element: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. This independently measures whether the intended change works. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0600.]
Incorrect Answers
A:Incorrect for this case: Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP. concerns the separate issue of Private TCP and UDP application access (Remote workers need access to a private UDP-dependent application hosted behind an SD-WAN hub.). It does not directly establish Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0600.]
D:Incorrect for this case: Agentless branch terminals inherit approved cloud enforcement through the edge. concerns the separate issue of Site on-ramp for nonagent branch users (A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support.). It does not directly establish Both normal and failover hubs advertise viable private application paths to PoPs. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0600.]
F:That intervention addresses FortiSASE as SD-WAN spoke: An enterprise wants SASE PoPs to participate in its existing hub-and-spoke routing rather than build unrelated public paths. The case-specific requirement is: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests