Question 380
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences.
- Sessions over either provider hit the single intended allow policy and retain appropriate inspection
- The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces
- Private traffic may steer between overlays while the Internet firewall policy still targets underlays
- Traffic on private and Internet paths matches their respective intended firewall policies
Explanation
Correct Answer
A:Sessions over either provider hit the single intended allow policy and retain appropriate inspection. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces. It addresses a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. In the reported environment, the missing behavior instead relates to a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. The relevant choice is sessions over either provider hit the single intended allow policy and retain appropriate inspection.
C:Private traffic may steer between overlays while the Internet firewall policy still targets underlays. The outcome for that step belongs to two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. Here the decisive requirement concerns a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences, so sessions over either provider hit the single intended allow policy and retain appropriate inspection is the better fit.
D:Traffic on private and Internet paths matches their respective intended firewall policies. That is a useful action for a different circumstance: a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic. The present case is constrained by a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences; the targeted response is sessions over either provider hit the single intended allow policy and retain appropriate inspection.
Question 381
The team is troubleshooting the following Fortinet 7.6 deployment: A remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. Which specific corrective action should be prioritized?
- Manage and verify the supported SD-WAN hub configuration objects through FortiManager with controlled deployment
- Repair the IPsec tunnel parameters and underlay reachability before debugging private application authorization
- Correct return-path routing and stateful policy consistency for private applications over SPA
- Configure FortiSASE secure private access through the existing SD-WAN hub using the supported connector integration
Explanation
Correct Answer
C:Correct return-path routing and stateful policy consistency for private applications over SPA. Stateful application connectivity depends on viable forward and reverse paths matching security expectations. The configuration alone must be followed by a functioning test: A remote session completes request and response through the intended protected private path.
Incorrect Answers
A:Manage and verify the supported SD-WAN hub configuration objects through FortiManager with controlled deployment. It could be appropriate when a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites. However, that does not resolve the stated condition: a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. A more direct answer is correct return-path routing and stateful policy consistency for private applications over SPA.
B:Repair the IPsec tunnel parameters and underlay reachability before debugging private application authorization. It addresses fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. In the reported environment, the missing behavior instead relates to a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. The relevant choice is correct return-path routing and stateful policy consistency for private applications over SPA.
D:Configure FortiSASE secure private access through the existing SD-WAN hub using the supported connector integration. The outcome for that step belongs to a customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly. Here the decisive requirement concerns a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path, so correct return-path routing and stateful policy consistency for private applications over SPA is the better fit.
Question 382
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? After a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer.
- Inspect IKE negotiation, peer reachability and IPsec tunnel status
- Inspect the connector's configured peer and IKE negotiation destination during connection attempts
- Inspect the denied session's source/destination and matching FortiGate policy ID
- Inspect routing for both source and return destinations and the denied or asymmetric session entries
Explanation
Correct Answer
B:Inspect the connector's configured peer and IKE negotiation destination during connection attempts. This check isolates the relevant control before the change. Peer addressing must match the current hub for an IPsec overlay to negotiate correctly.
Incorrect Answers
A:Inspect IKE negotiation, peer reachability and IPsec tunnel status. It could be appropriate when fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. However, that does not resolve the stated condition: after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer. A more direct answer is inspect the connector's configured peer and IKE negotiation destination during connection attempts.
C:Inspect the denied session's source/destination and matching FortiGate policy ID. That is a useful action for a different circumstance: a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. The present case is constrained by after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer; the targeted response is inspect the connector's configured peer and IKE negotiation destination during connection attempts.
D:Inspect routing for both source and return destinations and the denied or asymmetric session entries. The outcome for that step belongs to a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. Here the decisive requirement concerns after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer, so inspect the connector's configured peer and IKE negotiation destination during connection attempts is the better fit.
Question 383
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? The network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit.
- Under a session-based distribution rule, new connections can spread independently rather than strictly by source IP
- The rule becomes active only once the configured qualifying-member count is satisfied
- A test session with no explicit rule match follows the implicit rule's configured algorithm
- The selected path is the cheapest SLA-compliant member under the current measurements
Explanation
Correct Answer
A:Under a session-based distribution rule, new connections can spread independently rather than strictly by source IP. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The rule becomes active only once the configured qualifying-member count is satisfied. The outcome for that step belongs to after a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy. Here the decisive requirement concerns the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit, so under a session-based distribution rule, new connections can spread independently rather than strictly by source IP is the better fit.
C:A test session with no explicit rule match follows the implicit rule's configured algorithm. That is a useful action for a different circumstance: no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. The present case is constrained by the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit; the targeted response is under a session-based distribution rule, new connections can spread independently rather than strictly by source IP.
D:The selected path is the cheapest SLA-compliant member under the current measurements. It addresses two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. In the reported environment, the missing behavior instead relates to the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. The relevant choice is under a session-based distribution rule, new connections can spread independently rather than strictly by source IP.
Question 384
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites.
- Inspect BGP peering and the hub/PoP routing tables for the specific destination prefix
- Compare internal hostname resolution and direct IP connectivity from the remote endpoint
- Inspect IKE negotiation, peer reachability and IPsec tunnel status
- Inspect FortiManager device status, assigned templates and last successful push
Explanation
Correct Answer
D:Inspect FortiManager device status, assigned templates and last successful push. This check isolates the relevant control before the change. Centralized orchestration can standardize supported configuration across FortiGate hubs while preserving site-specific data.
Incorrect Answers
A:Inspect BGP peering and the hub/PoP routing tables for the specific destination prefix. That is a useful action for a different circumstance: the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. The present case is constrained by a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites; the targeted response is inspect FortiManager device status, assigned templates and last successful push.
B:Compare internal hostname resolution and direct IP connectivity from the remote endpoint. It could be appropriate when a remote user can reach an internal server by private IP but not by its internal hostname through the SPA connection. However, that does not resolve the stated condition: a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites. A more direct answer is inspect FortiManager device status, assigned templates and last successful push.
C:Inspect IKE negotiation, peer reachability and IPsec tunnel status. It addresses fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. In the reported environment, the missing behavior instead relates to a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites. The relevant choice is inspect FortiManager device status, assigned templates and last successful push.
Question 385
At a FortiSASE/SD-WAN site, this issue is reported: An organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. What is the most direct technical change to address the stated requirement?
- Inspect administrative event and change records for the FortiSASE tenant
- Perform a data-residency and jurisdiction review before finalizing supported FortiSASE regions
- Pilot FortiSASE remote-client access through security points of presence with the required web security policy
- Assign role-based administrative permissions aligned with the required responsibilities
Explanation
Correct Answer
B:Perform a data-residency and jurisdiction review before finalizing supported FortiSASE regions. Service routing and jurisdictional obligations are separate from basic tunnel connectivity. The acceptance check should show: The regional configuration and its documented business/legal approval agree with required locations.
Incorrect Answers
A:Inspect administrative event and change records for the FortiSASE tenant. It could be appropriate when an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. However, that does not resolve the stated condition: an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. A more direct answer is perform a data-residency and jurisdiction review before finalizing supported FortiSASE regions.
C:Pilot FortiSASE remote-client access through security points of presence with the required web security policy. The outcome for that step belongs to a large retailer wants to prove that security policy enforcement for mobile employees is cloud-based rather than tied to their nearest on-premises office firewall. Here the decisive requirement concerns an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision, so perform a data-residency and jurisdiction review before finalizing supported FortiSASE regions is the better fit.
D:Assign role-based administrative permissions aligned with the required responsibilities. That is a useful action for a different circumstance: a company needs administrators to troubleshoot access policies without allowing every operator to change identity sources or global settings. The present case is constrained by an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision; the targeted response is perform a data-residency and jurisdiction review before finalizing supported FortiSASE regions.
Question 386
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules.
- Inspect DNS-filter profile configuration and the matching DNS security log
- Inspect inline-CASB application/action criteria and relevant security-event logs
- Inspect the DLP profile match rules and whether the application traffic is decryptable where required
- Inspect the exemption list and SSL inspection mode for the actual traffic
Explanation
Correct Answer
D:Inspect the exemption list and SSL inspection mode for the actual traffic. This check isolates the relevant control before the change. Content inspection of encrypted sessions requires decryptability, except where inspection capabilities specifically work without it.
Incorrect Answers
A:Inspect DNS-filter profile configuration and the matching DNS security log. It addresses a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. In the reported environment, the missing behavior instead relates to a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules. The relevant choice is inspect the exemption list and SSL inspection mode for the actual traffic.
B:Inspect inline-CASB application/action criteria and relevant security-event logs. It could be appropriate when a sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application. However, that does not resolve the stated condition: a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules. A more direct answer is inspect the exemption list and SSL inspection mode for the actual traffic.
C:Inspect the DLP profile match rules and whether the application traffic is decryptable where required. That is a useful action for a different circumstance: a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications. The present case is constrained by a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules; the targeted response is inspect the exemption list and SSL inspection mode for the actual traffic.
Question 387
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up.
- New authorized transactions complete over the backup path during failure testing
- The actual traffic log or session record names the intended selected member
- The incident session record identifies the ISP path active before the outage
- The recorded degradation and selected-member transition correspond to the voice complaint
Explanation
Correct Answer
D:The recorded degradation and selected-member transition correspond to the voice complaint. This is stronger than a saved configuration because it tests the intended operational result. Link-quality and steering events describe path changes that physical link state alone may not explain.
Incorrect Answers
A:New authorized transactions complete over the backup path during failure testing. It could be appropriate when a branch rollout claims reliable failover because the WAN link state changed, but the business owner wants proof that application transactions continued. However, that does not resolve the stated condition: a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. A more direct answer is the recorded degradation and selected-member transition correspond to the voice complaint.
B:The actual traffic log or session record names the intended selected member. That is a useful action for a different circumstance: an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. The present case is constrained by a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up; the targeted response is the recorded degradation and selected-member transition correspond to the voice complaint.
C:The incident session record identifies the ISP path active before the outage. It addresses a team wants to identify which ISP path was used by a specific session before a provider outage. In the reported environment, the missing behavior instead relates to a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. The relevant choice is the recorded degradation and selected-member transition correspond to the voice complaint.
Question 388
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? The WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry.
- Both candidate paths show valid quality samples used by the relevant rule
- New eligible voice sessions choose a link meeting the defined jitter criterion when available
- After an authorized order swap, new eligible flows select the newly preferred equal-cost member
- The reachable target produces valid health samples on both correctly functioning circuits
Explanation
Correct Answer
A:Both candidate paths show valid quality samples used by the relevant rule. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:New eligible voice sessions choose a link meeting the defined jitter criterion when available. That is a useful action for a different circumstance: a voice application performs poorly with high jitter even though packet loss is low on both WANs. The present case is constrained by the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry; the targeted response is both candidate paths show valid quality samples used by the relevant rule.
C:After an authorized order swap, new eligible flows select the newly preferred equal-cost member. The outcome for that step belongs to an operations team sees two SLA-compliant WAN links assigned identical cost values but asks why only the first was elected. Here the decisive requirement concerns the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry, so both candidate paths show valid quality samples used by the relevant rule is the better fit.
D:The reachable target produces valid health samples on both correctly functioning circuits. It addresses a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. In the reported environment, the missing behavior instead relates to the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. The relevant choice is both candidate paths show valid quality samples used by the relevant rule.
Question 389
During implementation, the administrator observes: Users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event. Which intervention targets the described fault rather than an adjacent workflow?
- Investigate authentication/security events, source context and timing before claiming a malware outbreak
- Check the web-filter security log for the URL category, policy and action
- Inspect application-control or inline-CASB security logs and the matched action
- Correlate user and time fields across traffic and relevant threat logs
Explanation
Correct Answer
B:Check the web-filter security log for the URL category, policy and action. Web-filter events concern destination categorization, while IPS events concern detected intrusion patterns. The acceptance check should show: The log shows a category-based web-filter block under the expected policy.
Incorrect Answers
A:Investigate authentication/security events, source context and timing before claiming a malware outbreak. The outcome for that step belongs to a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. Here the decisive requirement concerns users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event, so check the web-filter security log for the URL category, policy and action is the better fit.
C:Inspect application-control or inline-CASB security logs and the matched action. It could be appropriate when security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. However, that does not resolve the stated condition: users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event. A more direct answer is check the web-filter security log for the URL category, policy and action.
D:Correlate user and time fields across traffic and relevant threat logs. That is a useful action for a different circumstance: a FortiSASE security incident spans an employee's proxy session and a possible malware detection one minute later. The present case is constrained by users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event; the targeted response is check the web-filter security log for the URL category, policy and action.
Question 390
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? FortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub.
- An IPsec tunnel becomes established and remains stable before private-app traffic tests
- The internal name resolves to the correct private address and the application connects over SPA
- The remote private destination is learned from the intended hub and forwarded over the VPN
- Each approved hub has consistent overlay and routing settings after verified deployment
Explanation
Correct Answer
A:An IPsec tunnel becomes established and remains stable before private-app traffic tests. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The internal name resolves to the correct private address and the application connects over SPA. It addresses a remote user can reach an internal server by private IP but not by its internal hostname through the SPA connection. In the reported environment, the missing behavior instead relates to fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. The relevant choice is an IPsec tunnel becomes established and remains stable before private-app traffic tests.
C:The remote private destination is learned from the intended hub and forwarded over the VPN. That is a useful action for a different circumstance: a service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel. The present case is constrained by fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub; the targeted response is an IPsec tunnel becomes established and remains stable before private-app traffic tests.
D:Each approved hub has consistent overlay and routing settings after verified deployment. The outcome for that step belongs to a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites. Here the decisive requirement concerns fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub, so an IPsec tunnel becomes established and remains stable before private-app traffic tests is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests