Question 180
During implementation, the administrator observes: The FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. Which intervention targets the described fault rather than an adjacent workflow?
- Validate hub-specific route advertisement, preference and available SPA connectivity for both hubs
- Update connector peer information and ensure the new hub endpoint is reachable
- Check BGP neighbor and private route exchange across the SPA overlay
- Check private-prefix advertisement and hub internal routing as well as the relevant firewall policies
Explanation
Correct Answer
C:Check BGP neighbor and private route exchange across the SPA overlay. IPsec establishes transport, but routing must advertise and resolve the private destination networks. The configuration alone must be followed by a functioning test: Both sides learn the intended private route and a permitted remote session reaches the server.
Incorrect Answers
A:Validate hub-specific route advertisement, preference and available SPA connectivity for both hubs. The outcome for that step belongs to an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises. Here the decisive requirement concerns the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub, so check BGP neighbor and private route exchange across the SPA overlay is the better fit.
B:Update connector peer information and ensure the new hub endpoint is reachable. It could be appropriate when after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer. However, that does not resolve the stated condition: the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. A more direct answer is check BGP neighbor and private route exchange across the SPA overlay.
D:Check private-prefix advertisement and hub internal routing as well as the relevant firewall policies. It addresses a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. In the reported environment, the missing behavior instead relates to the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. The relevant choice is check BGP neighbor and private route exchange across the SPA overlay.
Question 181
For the stated scenario, what is the most important remaining blind spot after the proposed correction? The company requires two healthy members to be available before activating a certain high-availability SD-WAN rule.
- Two virtual members mapped to the same failed provider do not deliver true transport diversity
- Trying to solve policy match by changing member weight leaves the wrong policy interface untouched
- Setting the minimum above the number of installed healthy members can disable the rule entirely
- Moving the tunnel without updating affected route and policy references can preserve the outage
Explanation
Correct Answer
C:Setting the minimum above the number of installed healthy members can disable the rule entirely. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Two virtual members mapped to the same failed provider do not deliver true transport diversity. The outcome for that step belongs to a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. Here the decisive requirement concerns the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule, so setting the minimum above the number of installed healthy members can disable the rule entirely is the better fit.
B:Trying to solve policy match by changing member weight leaves the wrong policy interface untouched. It addresses a FortiGate using zone-based policies shows the original interface port but the administrator cannot select it as a distinct policy destination. In the reported environment, the missing behavior instead relates to the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. The relevant choice is setting the minimum above the number of installed healthy members can disable the rule entirely.
D:Moving the tunnel without updating affected route and policy references can preserve the outage. It could be appropriate when during site migration, the team assigns an overlay tunnel to the ordinary Internet zone, then discovers it is subject to public-web policy handling. However, that does not resolve the stated condition: the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. A more direct answer is setting the minimum above the number of installed healthy members can disable the rule entirely.
Question 182
For a change review, the team proposes to narrow the broad rule's match conditions or change rule order so the SaaS exception can match because: A single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. Which explanation connects the change to the underlying behavior?
- Manual steering makes an intentional member selection instead of dynamically ranking all links by quality
- SD-WAN can distribute eligible session load across members according to its balancing method
- The rule only affects sessions satisfying its configured match conditions
- Broad earlier matches can preempt narrower intended steering logic
Explanation
Correct Answer
D:Broad earlier matches can preempt narrower intended steering logic. It directly explains the need to narrow the broad rule's match conditions or change rule order so the SaaS exception can match. The narrow validation is: The SaaS service hits its own rule while generic traffic remains under the broad steering rule.
Incorrect Answers
A:Manual steering makes an intentional member selection instead of dynamically ranking all links by quality. It could be appropriate when a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. However, that does not resolve the stated condition: a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. A more direct answer is broad earlier matches can preempt narrower intended steering logic.
B:SD-WAN can distribute eligible session load across members according to its balancing method. It addresses a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. In the reported environment, the missing behavior instead relates to a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. The relevant choice is broad earlier matches can preempt narrower intended steering logic.
C:The rule only affects sessions satisfying its configured match conditions. That is a useful action for a different circumstance: fortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration. The present case is constrained by a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used; the targeted response is broad earlier matches can preempt narrower intended steering logic.
Question 183
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? The FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub.
- The private service is accessible to authorized remote users solely via the intended secure connector path
- A remote user reaches the private database through the protected PoP-to-hub path
- The authorized source reaches only its permitted private application and is logged accordingly
- Both sides learn the intended private route and a permitted remote session reaches the server
Explanation
Correct Answer
D:Both sides learn the intended private route and a permitted remote session reaches the server. This is stronger than a saved configuration because it tests the intended operational result. IPsec establishes transport, but routing must advertise and resolve the private destination networks.
Incorrect Answers
A:The private service is accessible to authorized remote users solely via the intended secure connector path. It could be appropriate when a secure private access rollout uses a hub-and-spoke VPN topology and engineers expect private traffic to be accessible without exposing on-prem applications to the public Internet. However, that does not resolve the stated condition: the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. A more direct answer is both sides learn the intended private route and a permitted remote session reaches the server.
B:A remote user reaches the private database through the protected PoP-to-hub path. That is a useful action for a different circumstance: a customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly. The present case is constrained by the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub; the targeted response is both sides learn the intended private route and a permitted remote session reaches the server.
C:The authorized source reaches only its permitted private application and is logged accordingly. It addresses a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. In the reported environment, the missing behavior instead relates to the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. The relevant choice is both sides learn the intended private route and a permitted remote session reaches the server.
Question 184
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it.
- The remote user reaches the target server subnet through the hub with a matching allowed policy
- Failing one hub leaves required private routes reachable over the approved alternate hub
- The private service is accessible to authorized remote users solely via the intended secure connector path
- Each approved hub has consistent overlay and routing settings after verified deployment
Explanation
Correct Answer
A:The remote user reaches the target server subnet through the hub with a matching allowed policy. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Failing one hub leaves required private routes reachable over the approved alternate hub. It addresses an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises. In the reported environment, the missing behavior instead relates to a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. The relevant choice is the remote user reaches the target server subnet through the hub with a matching allowed policy.
C:The private service is accessible to authorized remote users solely via the intended secure connector path. The outcome for that step belongs to a secure private access rollout uses a hub-and-spoke VPN topology and engineers expect private traffic to be accessible without exposing on-prem applications to the public Internet. Here the decisive requirement concerns a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it, so the remote user reaches the target server subnet through the hub with a matching allowed policy is the better fit.
D:Each approved hub has consistent overlay and routing settings after verified deployment. That is a useful action for a different circumstance: a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites. The present case is constrained by a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it; the targeted response is the remote user reaches the target server subnet through the hub with a matching allowed policy.
Question 185
After the authorized change to filter traffic logs by the dedicated rule and compare matching and nonmatching application sessions, which result actually demonstrates that this site's requirement is met? Initial issue: An auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group.
- The selected member and traffic increase are attributable to the actual logged sessions
- The recorded degradation and selected-member transition correspond to the voice complaint
- The incident session record identifies the ISP path active before the outage
- Only approved application sessions match the specialized rule in a controlled test
Explanation
Correct Answer
D:Only approved application sessions match the specialized rule in a controlled test. This is stronger than a saved configuration because it tests the intended operational result. Logged rule IDs and application information can demonstrate the policy's actual scope.
Incorrect Answers
A:The selected member and traffic increase are attributable to the actual logged sessions. That is a useful action for a different circumstance: a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. The present case is constrained by an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group; the targeted response is only approved application sessions match the specialized rule in a controlled test.
B:The recorded degradation and selected-member transition correspond to the voice complaint. It addresses a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. In the reported environment, the missing behavior instead relates to an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. The relevant choice is only approved application sessions match the specialized rule in a controlled test.
C:The incident session record identifies the ISP path active before the outage. It could be appropriate when a team wants to identify which ISP path was used by a specific session before a provider outage. However, that does not resolve the stated condition: an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. A more direct answer is only approved application sessions match the specialized rule in a controlled test.
Question 186
For a change review, the team proposes to define separate, appropriately specific SD-WAN rules for each application's selection criteria because: A policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. Which explanation connects the change to the underlying behavior?
- SD-WAN steering is independent of the permit policy and can choose links using service-specific matches
- The best-quality strategy compares eligible links by the selected measured quality factor
- The implicit rule supplies default member selection when custom rules do not match
- Rule evaluation and match specificity determine which steering action applies to a session
Explanation
Correct Answer
A:SD-WAN steering is independent of the permit policy and can choose links using service-specific matches. This is why the proposed repair addresses the reported behavior; confirm by checking: Each test application selects the intended member while both remain authorized by the firewall.
Incorrect Answers
B:The best-quality strategy compares eligible links by the selected measured quality factor. The outcome for that step belongs to video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. Here the decisive requirement concerns a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision, so sD-WAN steering is independent of the permit policy and can choose links using service-specific matches is the better fit.
C:The implicit rule supplies default member selection when custom rules do not match. It addresses no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. In the reported environment, the missing behavior instead relates to a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. The relevant choice is sD-WAN steering is independent of the permit policy and can choose links using service-specific matches.
D:Rule evaluation and match specificity determine which steering action applies to a session. That is a useful action for a different circumstance: a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. The present case is constrained by a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision; the targeted response is sD-WAN steering is independent of the permit policy and can choose links using service-specific matches.
Question 187
For a change review, the team proposes to inspect longest-prefix, administrative distance and route resolution for the affected address first because: A FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. Which explanation connects the change to the underlying behavior?
- Forwarding to a changed destination requires matching route and permission objects regardless of tunnel state
- A VPN link-up event does not automatically supply every route needed for application destinations
- Health probes cannot succeed through an unreachable gateway even if their target is valid
- The forwarding route decision must be understood before diagnosing member-level quality steering
Explanation
Correct Answer
D:The forwarding route decision must be understood before diagnosing member-level quality steering. It directly explains the need to inspect longest-prefix, administrative distance and route resolution for the affected address first. The narrow validation is: Route lookup consistently identifies the intended next hop before SD-WAN member selection is analyzed.
Incorrect Answers
A:Forwarding to a changed destination requires matching route and permission objects regardless of tunnel state. That is a useful action for a different circumstance: an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change. The present case is constrained by a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks; the targeted response is the forwarding route decision must be understood before diagnosing member-level quality steering.
B:A VPN link-up event does not automatically supply every route needed for application destinations. It could be appropriate when following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub. However, that does not resolve the stated condition: a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. A more direct answer is the forwarding route decision must be understood before diagnosing member-level quality steering.
C:Health probes cannot succeed through an unreachable gateway even if their target is valid. It addresses a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. In the reported environment, the missing behavior instead relates to a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. The relevant choice is the forwarding route decision must be understood before diagnosing member-level quality steering.
Question 188
At a FortiSASE/SD-WAN site, this issue is reported: A remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group. What is the most direct technical change to address the stated requirement?
- Apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events
- Use application control with inline-CASB capability in the relevant FortiSASE inspection profile
- Attach an appropriate web-filter category policy to the matching FortiSASE security profile group
- Attach the required security profile group to the matching Accept policy
Explanation
Correct Answer
D:Attach the required security profile group to the matching Accept policy. FortiSASE applies selected inspection components through profile groups associated with eligible policies. The acceptance check should show: A controlled session produces the intended IPS inspection event under the associated policy.
Incorrect Answers
A:Apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events. It addresses a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. In the reported environment, the missing behavior instead relates to a remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group. The relevant choice is attach the required security profile group to the matching Accept policy.
B:Use application control with inline-CASB capability in the relevant FortiSASE inspection profile. That is a useful action for a different circumstance: a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. The present case is constrained by a remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group; the targeted response is attach the required security profile group to the matching Accept policy.
C:Attach an appropriate web-filter category policy to the matching FortiSASE security profile group. It could be appropriate when employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. However, that does not resolve the stated condition: a remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group. A more direct answer is attach the required security profile group to the matching Accept policy.
Question 189
At a FortiSASE/SD-WAN site, this issue is reported: Video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. What is the most direct technical change to address the stated requirement?
- Use the appropriate Internet Service Database selector within the SD-WAN rule where supported
- Use a Best Quality SD-WAN rule evaluated against the relevant jitter quality metric
- Use a matching SD-WAN rule with a manual member preference for the payroll traffic
- Configure Lowest Cost (SLA) steering with real member costs and the SaaS SLA target
Explanation
Correct Answer
B:Use a Best Quality SD-WAN rule evaluated against the relevant jitter quality metric. The best-quality strategy compares eligible links by the selected measured quality factor. The acceptance check should show: New matching calls are steered toward the better-performing member under the configured metric.
Incorrect Answers
A:Use the appropriate Internet Service Database selector within the SD-WAN rule where supported. The outcome for that step belongs to an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. Here the decisive requirement concerns video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price, so use a Best Quality SD-WAN rule evaluated against the relevant jitter quality metric is the better fit.
C:Use a matching SD-WAN rule with a manual member preference for the payroll traffic. It could be appropriate when a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. However, that does not resolve the stated condition: video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. A more direct answer is use a Best Quality SD-WAN rule evaluated against the relevant jitter quality metric.
D:Configure Lowest Cost (SLA) steering with real member costs and the SaaS SLA target. That is a useful action for a different circumstance: two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. The present case is constrained by video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price; the targeted response is use a Best Quality SD-WAN rule evaluated against the relevant jitter quality metric.
Question 190
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? Security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny.
- Inspect the matched DLP rule, user, application and blocked action
- Inspect the sign-in outcomes, source addresses and account correlation in the audit window
- Search overlapping timestamps, username and application or destination fields in both log types
- Review the cloud application's identified operation and enforcement action
Explanation
Correct Answer
D:Review the cloud application's identified operation and enforcement action. This check isolates the relevant control before the change. Inline SaaS inspection can produce activity-level events distinct from domain-category blocks.
Incorrect Answers
A:Inspect the matched DLP rule, user, application and blocked action. It could be appropriate when an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. However, that does not resolve the stated condition: security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. A more direct answer is review the cloud application's identified operation and enforcement action.
B:Inspect the sign-in outcomes, source addresses and account correlation in the audit window. That is a useful action for a different circumstance: a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. The present case is constrained by security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny; the targeted response is review the cloud application's identified operation and enforcement action.
C:Search overlapping timestamps, username and application or destination fields in both log types. It addresses a FortiSASE security incident spans an employee's proxy session and a possible malware detection one minute later. In the reported environment, the missing behavior instead relates to security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. The relevant choice is review the cloud application's identified operation and enforcement action.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests