Question 620
The team is troubleshooting the following Fortinet 7.6 deployment: A multinational company is activating FortiSASE and must decide which geographical security PoP regions should serve its remote employees. Which specific corrective action should be prioritized?
- Pilot FortiSASE remote-client access through security points of presence with the required web security policy
- Inspect administrative event and change records for the FortiSASE tenant
- Select and document appropriate FortiSASE service regions during provisioning based on users and data-handling requirements
- Verify and apply the required FortiSASE license entitlement for the selected deployment before enabling the features
Explanation
Correct Answer
C:Select and document appropriate FortiSASE service regions during provisioning based on users and data-handling requirements. Regional selection affects where remote users connect and where service processing may occur. The configuration alone must be followed by a functioning test: Pilot users connect to the expected security PoP region and the organization's residency constraints are reviewed.
Incorrect Answers
A:Pilot FortiSASE remote-client access through security points of presence with the required web security policy. It addresses 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. In the reported environment, the missing behavior instead relates to a multinational company is activating FortiSASE and must decide which geographical security PoP regions should serve its remote employees. The relevant choice is select and document appropriate FortiSASE service regions during provisioning based on users and data-handling requirements.
B:Inspect administrative event and change records for the FortiSASE tenant. The outcome for that step belongs to an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. Here the decisive requirement concerns a multinational company is activating FortiSASE and must decide which geographical security PoP regions should serve its remote employees, so select and document appropriate FortiSASE service regions during provisioning based on users and data-handling requirements is the better fit.
D:Verify and apply the required FortiSASE license entitlement for the selected deployment before enabling the features. It could be appropriate when a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. However, that does not resolve the stated condition: a multinational company is activating FortiSASE and must decide which geographical security PoP regions should serve its remote employees. A more direct answer is select and document appropriate FortiSASE service regions during provisioning based on users and data-handling requirements.
Question 621
At a FortiSASE/SD-WAN site, this issue is reported: 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. What is the most direct technical change to address the stated requirement?
- Inspect administrative event and change records for the FortiSASE tenant
- Verify and apply the required FortiSASE license entitlement for the selected deployment before enabling the features
- Verify the FortiManager-to-FortiSASE central-management link and the supported synchronized object types
- Pilot FortiSASE remote-client access through security points of presence with the required web security policy
Explanation
Correct Answer
D:Pilot FortiSASE remote-client access through security points of presence with the required web security policy. Cloud PoPs apply policy on the user path, independent of the user's physical branch location. The acceptance check should show: A remote employee receives the same intended web-filter decision from two distinct locations.
Incorrect Answers
A:Inspect administrative event and change records for the FortiSASE tenant. It addresses an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. In the reported environment, the missing behavior instead relates 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. The relevant choice is pilot FortiSASE remote-client access through security points of presence with the required web security policy.
B:Verify and apply the required FortiSASE license entitlement for the selected deployment before enabling the features. It could be appropriate when a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. However, that does not resolve the stated condition: 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. A more direct answer is pilot FortiSASE remote-client access through security points of presence with the required web security policy.
C:Verify the FortiManager-to-FortiSASE central-management link and the supported synchronized object types. That is a useful action for a different circumstance: fortiSASE configuration is being centrally managed, but changes made in FortiManager do not appear in the remote tenant. The present case is constrained by 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; the targeted response is pilot FortiSASE remote-client access through security points of presence with the required web security policy.
Question 622
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? FortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub.
- Inspect FortiManager device status, assigned templates and last successful push
- Inspect the route and traffic classification for one public SaaS destination and one private server
- Inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet
- Inspect IPsec peers, route exchange and policies for the particular private service
Explanation
Correct Answer
B:Inspect the route and traffic classification for one public SaaS destination and one private server. This check isolates the relevant control before the change. The SASE architecture supports cloud Internet inspection and specific private application connectivity through connectors.
Incorrect Answers
A:Inspect FortiManager device status, assigned templates and last successful push. 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 remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub, so inspect the route and traffic classification for one public SaaS destination and one private server is the better fit.
C:Inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet. It could be appropriate when a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. However, that does not resolve the stated condition: fortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub. A more direct answer is inspect the route and traffic classification for one public SaaS destination and one private server.
D:Inspect IPsec peers, route exchange and policies for the particular private service. That is a useful action for a different circumstance: 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. The present case is constrained by fortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub; the targeted response is inspect the route and traffic classification for one public SaaS destination and one private server.
Question 623
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? The compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it.
- Changing SD-WAN member priority does not explain an application-layer intrusion signature
- A rule configuration screenshot alone is weaker than observed matched-session behavior
- Manually exporting a dashboard once does not meet a recurring reporting requirement
- A single average bandwidth value without time and member context cannot establish the spike's path
Explanation
Correct Answer
C:Manually exporting a dashboard once does not meet a recurring reporting requirement. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Changing SD-WAN member priority does not explain an application-layer intrusion signature. The outcome for that step belongs to a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. Here the decisive requirement concerns the compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it, so manually exporting a dashboard once does not meet a recurring reporting requirement is the better fit.
B:A rule configuration screenshot alone is weaker than observed matched-session behavior. It addresses an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. In the reported environment, the missing behavior instead relates to the compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it. The relevant choice is manually exporting a dashboard once does not meet a recurring reporting requirement.
D:A single average bandwidth value without time and member context cannot establish the spike's path. It could be appropriate when a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. However, that does not resolve the stated condition: the compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it. A more direct answer is manually exporting a dashboard once does not meet a recurring reporting requirement.
Question 624
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used.
- Matching calls select a qualifying WAN during controlled primary-path degradation
- The SaaS service hits its own rule while generic traffic remains under the broad steering rule
- New matching calls are steered toward the better-performing member under the configured metric
- The member change correlates with a documented SLA or eligibility change, not guesswork about policy order
Explanation
Correct Answer
B:The SaaS service hits its own rule while generic traffic remains under the broad steering rule. This is stronger than a saved configuration because it tests the intended operational result. Broad earlier matches can preempt narrower intended steering logic.
Incorrect Answers
A:Matching calls select a qualifying WAN during controlled primary-path degradation. That is a useful action for a different circumstance: a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. 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 the SaaS service hits its own rule while generic traffic remains under the broad steering rule.
C:New matching calls are steered toward the better-performing member under the configured metric. 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 single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used, so the SaaS service hits its own rule while generic traffic remains under the broad steering rule is the better fit.
D:The member change correlates with a documented SLA or eligibility change, not guesswork about policy order. It could be appropriate when an IT team monitors a policy's configuration text but still cannot explain why a selected member changed during a short quality incident. 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 the SaaS service hits its own rule while generic traffic remains under the broad steering rule.
Question 625
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? Two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access.
- Each test application selects the intended member while both remain authorized by the firewall
- The selected path is the cheapest SLA-compliant member under the current measurements
- New payroll sessions choose the configured preferred eligible member
- The SaaS service hits its own rule while generic traffic remains under the broad steering rule
Explanation
Correct Answer
B:The selected path is the cheapest SLA-compliant member under the current measurements. This is stronger than a saved configuration because it tests the intended operational result. The policy uses member cost to choose among links that meet the required performance thresholds.
Incorrect Answers
A:Each test application selects the intended member while both remain authorized by the firewall. That is a useful action for a different circumstance: a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. The present case is constrained by two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access; the targeted response is the selected path is the cheapest SLA-compliant member under the current measurements.
C:New payroll sessions choose the configured preferred eligible member. 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: two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. A more direct answer is the selected path is the cheapest SLA-compliant member under the current measurements.
D:The SaaS service hits its own rule while generic traffic remains under the broad steering rule. The outcome for that step belongs to a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. Here the decisive requirement concerns two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access, so the selected path is the cheapest SLA-compliant member under the current measurements is the better fit.
Question 626
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: Employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone.
- Inspect both user-group policies and the profile groups attached to each
- Inspect the relevant IPS sensor and whether the target policy includes it
- Inspect the effective web-filter profile and category action for the test URL
- Inspect the policy action and Profile Group selection for a representative allowed session
Explanation
Correct Answer
C:Inspect the effective web-filter profile and category action for the test URL. The observed evidence guides the targeted repair: Attach an appropriate web-filter category policy to the matching FortiSASE security profile group.
Incorrect Answers
A:Inspect both user-group policies and the profile groups attached to each. The outcome for that step belongs to a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. Here the decisive requirement concerns employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone, so inspect the effective web-filter profile and category action for the test URL is the better fit.
B:Inspect the relevant IPS sensor and whether the target policy includes it. It could be appropriate when a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. However, that does not resolve the stated condition: employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. A more direct answer is inspect the effective web-filter profile and category action for the test URL.
D:Inspect the policy action and Profile Group selection for a representative allowed session. It addresses 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. In the reported environment, the missing behavior instead relates to employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. The relevant choice is inspect the effective web-filter profile and category action for the test URL.
Question 627
The team is troubleshooting the following Fortinet 7.6 deployment: A regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window. Which specific corrective action should be prioritized?
- Use a user-traffic or usage report filtered to the month and corresponding cohort
- Use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence
- Configure supported secure log forwarding to the authorized external logging destination and validate receipt
- Run an on-demand report for the incident-specific interval and relevant report type
Explanation
Correct Answer
C:Configure supported secure log forwarding to the authorized external logging destination and validate receipt. External forwarding supports a separate retention/compliance workflow beyond dashboards' immediate views. The configuration alone must be followed by a functioning test: Representative traffic and security events arrive at the approved collector with consistent timestamps.
Incorrect Answers
A:Use a user-traffic or usage report filtered to the month and corresponding cohort. It could be appropriate when a department asks which user cohort consumed the most bandwidth across FortiSASE Internet access this month. However, that does not resolve the stated condition: a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window. A more direct answer is configure supported secure log forwarding to the authorized external logging destination and validate receipt.
B:Use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence. It addresses a quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail. In the reported environment, the missing behavior instead relates to a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window. The relevant choice is configure supported secure log forwarding to the authorized external logging destination and validate receipt.
D:Run an on-demand report for the incident-specific interval and relevant report type. The outcome for that step belongs to during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. Here the decisive requirement concerns a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window, so configure supported secure log forwarding to the authorized external logging destination and validate receipt is the better fit.
Question 628
During implementation, the administrator observes: A managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. Which intervention targets the described fault rather than an adjacent workflow?
- Constrain the pilot profile to a narrowly defined test user or endpoint group
- Investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance
- Define the intended compliance predicates explicitly and test missing-value behavior in the supported posture engine
- Refresh endpoint posture reporting and verify the rule's effective match data before relaxing policy
Explanation
Correct Answer
B:Investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance. A compliant posture can require both running antivirus and connected management telemetry. The acceptance check should show: Access follows the intended policy only after the agent reports both required posture conditions.
Incorrect Answers
A:Constrain the pilot profile to a narrowly defined test user or endpoint group. That is a useful action for a different circumstance: an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. The present case is constrained by a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service; the targeted response is investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance.
C:Define the intended compliance predicates explicitly and test missing-value behavior in the supported posture engine. The outcome for that step belongs to a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable. Here the decisive requirement concerns a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service, so investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance is the better fit.
D:Refresh endpoint posture reporting and verify the rule's effective match data before relaxing policy. It could be appropriate when a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings. However, that does not resolve the stated condition: a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. A more direct answer is investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance.
Question 629
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: An organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises.
- Inspect IKE negotiation, peer reachability and IPsec tunnel status
- Inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet
- Inspect advertised prefixes and active routes from both hub connections
- Inspect the denied session's source/destination and matching FortiGate policy ID
Explanation
Correct Answer
C:Inspect advertised prefixes and active routes from both hub connections. The observed evidence guides the targeted repair: Validate hub-specific route advertisement, preference and available SPA connectivity for both hubs.
Incorrect Answers
A: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 an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises. The relevant choice is inspect advertised prefixes and active routes from both hub connections.
B:Inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet. The outcome for that step belongs to a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. Here the decisive requirement concerns an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises, so inspect advertised prefixes and active routes from both hub connections is the better fit.
D:Inspect the denied session's source/destination and matching FortiGate policy ID. It could be appropriate when a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. However, that does not resolve the stated condition: an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises. A more direct answer is inspect advertised prefixes and active routes from both hub connections.
Question 630
At a FortiSASE/SD-WAN site, this issue is reported: A security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. What is the most direct technical change to address the stated requirement?
- Keep the more-specific private route toward the tunnel while using default Internet reachability for public traffic
- Correct the separate firewall-policy match or security action after confirming the route is valid
- Check SNAT and session behavior when rerouting across WAN members, not only link quality
- Fix the measured quality or revise a justified SLA threshold instead of treating route presence as proof of eligibility
Explanation
Correct Answer
B:Correct the separate firewall-policy match or security action after confirming the route is valid. Routing and steering determine path availability, while firewall policy decides whether traffic is permitted. The acceptance check should show: A new allowed test flow uses the selected member and logs the intended permit policy.
Incorrect Answers
A:Keep the more-specific private route toward the tunnel while using default Internet reachability for public traffic. That is a useful action for a different circumstance: a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination. The present case is constrained by a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall; the targeted response is correct the separate firewall-policy match or security action after confirming the route is valid.
C:Check SNAT and session behavior when rerouting across WAN members, not only link quality. It could be appropriate when a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. However, that does not resolve the stated condition: a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. A more direct answer is correct the separate firewall-policy match or security action after confirming the route is valid.
D:Fix the measured quality or revise a justified SLA threshold instead of treating route presence as proof of eligibility. The outcome for that step belongs to an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing. Here the decisive requirement concerns a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall, so correct the separate firewall-policy match or security action after confirming the route is valid is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests