Question 310
After the authorized change to correct the member gateway and dependent routing configuration to match the currently assigned underlay, which result actually demonstrates that this site's requirement is met? Initial issue: A WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router.
- Internet test flows use a reachable next hop and health probes recover
- The session record shows the intended tunnel and matching permit rule during a successful request
- The hub routing table contains the expected reachable prefixes across the overlay
- The repaired member is both routed and SLA-qualified when its measured performance meets the target
Explanation
Correct Answer
A:Internet test flows use a reachable next hop and health probes recover. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The session record shows the intended tunnel and matching permit rule during a successful request. It addresses an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone. In the reported environment, the missing behavior instead relates to a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. The relevant choice is internet test flows use a reachable next hop and health probes recover.
C:The hub routing table contains the expected reachable prefixes across the overlay. That is a useful action for a different circumstance: remote users can reach an SASE security PoP, but the FortiGate SD-WAN hub never learns the private prefix it should send toward that PoP. The present case is constrained by a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router; the targeted response is internet test flows use a reachable next hop and health probes recover.
D:The repaired member is both routed and SLA-qualified when its measured performance meets the target. 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 WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router, so internet test flows use a reachable next hop and health probes recover is the better fit.
Question 311
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window.
- Treating every blocked website as an IPS exploit event misclassifies the cause
- A device-wide bandwidth chart does not identify one transaction's rule match
- Generating a downloadable report once does not guarantee long-term log retention
- Seeing two green SLA states does not establish the member chosen for the payment flow
Explanation
Correct Answer
C:Generating a downloadable report once does not guarantee long-term log retention. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Treating every blocked website as an IPS exploit event misclassifies the cause. It could be appropriate when users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event. 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 generating a downloadable report once does not guarantee long-term log retention.
B:A device-wide bandwidth chart does not identify one transaction's rule match. The outcome for that step belongs to a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. 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 generating a downloadable report once does not guarantee long-term log retention is the better fit.
D:Seeing two green SLA states does not establish the member chosen for the payment flow. It addresses an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. 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 generating a downloadable report once does not guarantee long-term log retention.
Question 312
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? The SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband.
- Changing Internet steering rules will not correct a mismatched RADIUS shared secret
- A tunnel being up in one direction does not prove reply routing or security state are correct
- Changing an unrelated security inspection profile does not solve geographical path selection
- One global profile cannot safely encode mutually different group-specific connection permissions
Explanation
Correct Answer
C:Changing an unrelated security inspection profile does not solve geographical path selection. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Changing Internet steering rules will not correct a mismatched RADIUS shared secret. It could be appropriate when rADIUS-backed authentication works for a test account on the directory server but fails for FortiSASE users after onboarding. However, that does not resolve the stated condition: the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband. A more direct answer is changing an unrelated security inspection profile does not solve geographical path selection.
B:A tunnel being up in one direction does not prove reply routing or security state are correct. 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 the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband, so changing an unrelated security inspection profile does not solve geographical path selection is the better fit.
D:One global profile cannot safely encode mutually different group-specific connection permissions. It addresses one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. In the reported environment, the missing behavior instead relates to the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband. The relevant choice is changing an unrelated security inspection profile does not solve geographical path selection.
Question 313
At a FortiSASE/SD-WAN site, this issue is reported: A FortiGate has a manual SD-WAN rule preferring WAN2, but a route lookup for the destination has no usable next hop. What is the most direct technical change to address the stated requirement?
- Inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics
- Inspect longest-prefix, administrative distance and route resolution for the affected address first
- Repair the relevant route reachability before attempting to force the rule onto WAN2
- Fix the measured quality or revise a justified SLA threshold instead of treating route presence as proof of eligibility
Explanation
Correct Answer
C:Repair the relevant route reachability before attempting to force the rule onto WAN2. SD-WAN steering acts within the set of paths that routing can actually resolve. The configuration alone must be followed by a functioning test: The destination gains a usable route and a new session follows the intended eligible WAN2 member.
Incorrect Answers
A:Inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics. It addresses an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone. In the reported environment, the missing behavior instead relates to a FortiGate has a manual SD-WAN rule preferring WAN2, but a route lookup for the destination has no usable next hop. The relevant choice is repair the relevant route reachability before attempting to force the rule onto WAN2.
B:Inspect longest-prefix, administrative distance and route resolution for the affected address first. It could be appropriate when a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. However, that does not resolve the stated condition: a FortiGate has a manual SD-WAN rule preferring WAN2, but a route lookup for the destination has no usable next hop. A more direct answer is repair the relevant route reachability before attempting to force the rule onto WAN2.
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 FortiGate has a manual SD-WAN rule preferring WAN2, but a route lookup for the destination has no usable next hop, so repair the relevant route reachability before attempting to force the rule onto WAN2 is the better fit.
Question 314
The team is troubleshooting the following Fortinet 7.6 deployment: A quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail. Which specific corrective action should be prioritized?
- Use a user-traffic or usage report filtered to the month and corresponding cohort
- Compare relevant web-filter security events across defined before-and-after reporting periods
- Run an on-demand report for the incident-specific interval and relevant report type
- Use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence
Explanation
Correct Answer
D:Use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence. Reports provide aggregated trends, while raw event logs support specific incident verification. The acceptance check should show: The summary's anomalous interval can be reconciled with its individual security events.
Incorrect Answers
A:Use a user-traffic or usage report filtered to the month and corresponding cohort. It addresses a department asks which user cohort consumed the most bandwidth across FortiSASE Internet access this month. In the reported environment, the missing behavior instead relates to a quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail. The relevant choice is use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence.
B:Compare relevant web-filter security events across defined before-and-after reporting periods. It could be appropriate when a security officer needs proof that web-category policy violations increased after a recent configuration change. However, that does not resolve the stated condition: a quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail. A more direct answer is use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence.
C:Run an on-demand report for the incident-specific interval and relevant report type. That is a useful action for a different circumstance: during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. The present case is constrained by a quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail; the targeted response is use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence.
Question 315
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel.
- Standard staff cannot disconnect, while the approved IT group has the intended exception
- Only the approved browser Internet access path works for the contractor
- A test SWG SSO user authenticates successfully and follows the intended proxy policy
- Expected inspected HTTPS pages load without untrusted issuer warnings, while inspection events appear in logs
Explanation
Correct Answer
B:Only the approved browser Internet access path works for the contractor. This is stronger than a saved configuration because it tests the intended operational result. The onboarding mode and policy scope should align to browser-based Internet access rather than broad private routing.
Incorrect Answers
A:Standard staff cannot disconnect, while the approved IT group has the intended exception. That is a useful action for a different circumstance: one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. The present case is constrained by a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel; the targeted response is only the approved browser Internet access path works for the contractor.
C:A test SWG SSO user authenticates successfully and follows the intended proxy policy. It could be appropriate when the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. However, that does not resolve the stated condition: a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel. A more direct answer is only the approved browser Internet access path works for the contractor.
D:Expected inspected HTTPS pages load without untrusted issuer warnings, while inspection events appear in logs. The outcome for that step belongs to users report browser certificate warnings immediately after enabling deep inspection for an agentless secure web gateway. Here the decisive requirement concerns a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel, so only the approved browser Internet access path works for the contractor is the better fit.
Question 316
The team is troubleshooting the following Fortinet 7.6 deployment: During branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider. Which specific corrective action should be prioritized?
- Build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate
- Install a valid default route that resolves through the intended SD-WAN zone or member design
- Reference the intended SD-WAN zone for traffic-policy control rather than individual members when using the SD-WAN design
- Complete the backup interface's appropriate DHCP or static IP configuration and gateway settings
Explanation
Correct Answer
D:Complete the backup interface's appropriate DHCP or static IP configuration and gateway settings. An Ethernet carrier signal does not establish layer-3 underlay reachability needed for the SD-WAN path. The acceptance check should show: A sourced probe from the backup interface reaches the provider gateway and test external destinations.
Incorrect Answers
A:Build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate. That is a useful action for a different circumstance: a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. The present case is constrained by during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider; the targeted response is complete the backup interface's appropriate DHCP or static IP configuration and gateway settings.
B:Install a valid default route that resolves through the intended SD-WAN zone or member design. It could be appropriate when a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. However, that does not resolve the stated condition: during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider. A more direct answer is complete the backup interface's appropriate DHCP or static IP configuration and gateway settings.
C:Reference the intended SD-WAN zone for traffic-policy control rather than individual members when using the SD-WAN design. It addresses after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. In the reported environment, the missing behavior instead relates to during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider. The relevant choice is complete the backup interface's appropriate DHCP or static IP configuration and gateway settings.
Question 317
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay.
- A sourced probe from the backup interface reaches the provider gateway and test external destinations
- The policy matches sessions sent through either eligible member of its designated zone
- Operators see per-member health and selection changes during a controlled path impairment test
- Internet testing exits locally and private testing resolves through the intended VPN overlay
Explanation
Correct Answer
D:Internet testing exits locally and private testing resolves through the intended VPN overlay. This is stronger than a saved configuration because it tests the intended operational result. SD-WAN forwarding follows both route reachability and matching policy, so public DIA need not capture private-site routes.
Incorrect Answers
A:A sourced probe from the backup interface reaches the provider gateway and test external destinations. It addresses during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider. In the reported environment, the missing behavior instead relates to a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay. The relevant choice is internet testing exits locally and private testing resolves through the intended VPN overlay.
B:The policy matches sessions sent through either eligible member of its designated zone. It could be appropriate when after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. However, that does not resolve the stated condition: a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay. A more direct answer is internet testing exits locally and private testing resolves through the intended VPN overlay.
C:Operators see per-member health and selection changes during a controlled path impairment test. That is a useful action for a different circumstance: a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. The present case is constrained by a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay; the targeted response is internet testing exits locally and private testing resolves through the intended VPN overlay.
Question 318
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window.
- Inspect log-forwarding destination, connection status and event receipt in the external system
- Inspect the report's user grouping, time range and byte totals
- Inspect report periods, matched category actions and any reporting coverage differences
- Inspect report filters, selected dates and data sources before running it
Explanation
Correct Answer
A:Inspect log-forwarding destination, connection status and event receipt in the external system. The observed evidence guides the targeted repair: Configure supported secure log forwarding to the authorized external logging destination and validate receipt.
Incorrect Answers
B:Inspect the report's user grouping, time range and byte totals. The outcome for that step belongs to a department asks which user cohort consumed the most bandwidth across FortiSASE Internet access this month. 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 inspect log-forwarding destination, connection status and event receipt in the external system is the better fit.
C:Inspect report periods, matched category actions and any reporting coverage differences. It addresses a security officer needs proof that web-category policy violations increased after a recent configuration change. 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 inspect log-forwarding destination, connection status and event receipt in the external system.
D:Inspect report filters, selected dates and data sources before running it. That is a useful action for a different circumstance: during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. The present case is constrained by a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window; the targeted response is inspect log-forwarding destination, connection status and event receipt in the external system.
Question 319
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks.
- A link SLA tweak cannot explain a route that already wins or loses on routing preference
- Lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter
- An allow policy with broad destination 'all' is not an SD-WAN member-selection rule
- Adjusting latency thresholds is ineffective if the voice traffic never matches the rule
Explanation
Correct Answer
A:A link SLA tweak cannot explain a route that already wins or loses on routing preference. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter. It addresses video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. 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 a link SLA tweak cannot explain a route that already wins or loses on routing preference.
C:An allow policy with broad destination 'all' is not an SD-WAN member-selection rule. The outcome for that step belongs to a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. Here the decisive requirement concerns a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks, so a link SLA tweak cannot explain a route that already wins or loses on routing preference is the better fit.
D:Adjusting latency thresholds is ineffective if the voice traffic never matches the rule. 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 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 a link SLA tweak cannot explain a route that already wins or loses on routing preference.
Question 320
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A FortiSASE web policy has a functioning antivirus profile on unencrypted downloads, but it detects only HTTPS domains and cannot inspect malicious downloads inside encrypted sessions.
- Cloning a profile without checking its assignment can cause undesired broad enforcement
- Deep inspection without trusted CA deployment can disrupt legitimate TLS connections
- Assuming an unknown attribute always means compliant can expose protected resources
- An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals
Explanation
Correct Answer
B:Deep inspection without trusted CA deployment can disrupt legitimate TLS connections. The planned change can still miss the requirement if this condition is left unresolved. Certificate inspection sees limited certificate metadata; deep inspection can expose encrypted application content to security profiles.
Incorrect Answers
A:Cloning a profile without checking its assignment can cause undesired broad enforcement. 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 FortiSASE web policy has a functioning antivirus profile on unencrypted downloads, but it detects only HTTPS domains and cannot inspect malicious downloads inside encrypted sessions; the targeted response is deep inspection without trusted CA deployment can disrupt legitimate TLS connections.
C:Assuming an unknown attribute always means compliant can expose protected resources. It could be appropriate when a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable. However, that does not resolve the stated condition: a FortiSASE web policy has a functioning antivirus profile on unencrypted downloads, but it detects only HTTPS domains and cannot inspect malicious downloads inside encrypted sessions. A more direct answer is deep inspection without trusted CA deployment can disrupt legitimate TLS connections.
D:An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals. The outcome for that step belongs to security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks. Here the decisive requirement concerns a FortiSASE web policy has a functioning antivirus profile on unencrypted downloads, but it detects only HTTPS domains and cannot inspect malicious downloads inside encrypted sessions, so deep inspection without trusted CA deployment can disrupt legitimate TLS connections is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests