Question 110
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use.
- Check probe reachability along each member before attributing failure to transport quality
- Inspect whether the monitored service has sufficient real sessions to supply passive samples
- Review time-aligned SLA transitions and rule/member selection at the failure timestamp
- Inspect the health-check member list and whether the backup reports probe metrics
Explanation
Correct Answer
B:Inspect whether the monitored service has sufficient real sessions to supply passive samples. This check isolates the relevant control before the change. Passive monitoring derives link quality from existing traversing traffic rather than generating active probes.
Incorrect Answers
A:Check probe reachability along each member before attributing failure to transport quality. It could be appropriate when a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. However, that does not resolve the stated condition: a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. A more direct answer is inspect whether the monitored service has sufficient real sessions to supply passive samples.
C:Review time-aligned SLA transitions and rule/member selection at the failure timestamp. The outcome for that step belongs to a branch reports all SD-WAN sessions failed over after a WAN hiccup, but an engineer only checked the link LED and concluded no impairment. Here the decisive requirement concerns a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use, so inspect whether the monitored service has sufficient real sessions to supply passive samples is the better fit.
D:Inspect the health-check member list and whether the backup reports probe metrics. That is a useful action for a different circumstance: the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. The present case is constrained by a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use; the targeted response is inspect whether the monitored service has sufficient real sessions to supply passive samples.
Question 111
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category.
- Malicious test content is detected or blocked according to policy without blocking the entire legitimate site category
- Relevant test HTTPS downloads receive the intended malware or DLP inspection
- Approved collaboration functions succeed while the selected risky transfer operation is blocked
- The intended HTTPS site is inspected without trust warnings, and appropriate security events appear
Explanation
Correct Answer
A:Malicious test content is detected or blocked according to policy without blocking the entire legitimate site category. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Relevant test HTTPS downloads receive the intended malware or DLP inspection. That is a useful action for a different circumstance: a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules. The present case is constrained by a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category; the targeted response is malicious test content is detected or blocked according to policy without blocking the entire legitimate site category.
C:Approved collaboration functions succeed while the selected risky transfer operation is blocked. The outcome for that step belongs to a sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application. Here the decisive requirement concerns a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category, so malicious test content is detected or blocked according to policy without blocking the entire legitimate site category is the better fit.
D:The intended HTTPS site is inspected without trust warnings, and appropriate security events appear. It addresses a browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions. In the reported environment, the missing behavior instead relates to a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category. The relevant choice is malicious test content is detected or blocked according to policy without blocking the entire legitimate site category.
Question 112
The team is troubleshooting the following Fortinet 7.6 deployment: A network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. Which specific corrective action should be prioritized?
- Use SD-WAN traffic logs and member performance/usage views for the same time window
- Search time-bounded session or traffic history rather than relying on the postoutage routing table
- Correlate SD-WAN failover events with representative application traffic/session logs during the test
- Correlate SLA health-event records with routing and session change logs
Explanation
Correct Answer
A:Use SD-WAN traffic logs and member performance/usage views for the same time window. Usage visibility distinguishes aggregate demand from per-member forwarding behavior. The configuration alone must be followed by a functioning test: The selected member and traffic increase are attributable to the actual logged sessions.
Incorrect Answers
B:Search time-bounded session or traffic history rather than relying on the postoutage routing table. That is a useful action for a different circumstance: a team wants to identify which ISP path was used by a specific session before a provider outage. The present case is constrained by a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load; the targeted response is use SD-WAN traffic logs and member performance/usage views for the same time window.
C:Correlate SD-WAN failover events with representative application traffic/session logs during the test. The outcome for that step belongs to a branch rollout claims reliable failover because the WAN link state changed, but the business owner wants proof that application transactions continued. Here the decisive requirement concerns a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load, so use SD-WAN traffic logs and member performance/usage views for the same time window is the better fit.
D:Correlate SLA health-event records with routing and session change logs. It addresses an operator says a VPN application keeps failing over but cannot show whether the trigger was packet loss or a routing change. In the reported environment, the missing behavior instead relates to a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. The relevant choice is use SD-WAN traffic logs and member performance/usage views for the same time window.
Question 113
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy.
- Private traffic may steer between overlays while the Internet firewall policy still targets underlays
- The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces
- A controlled failure of the first tunnel leads private traffic through the second while preserving policy matching
- 5G failover sessions match the same policy as other members in that zone
Explanation
Correct Answer
C:A controlled failure of the first tunnel leads private traffic through the second while preserving policy matching. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:Private traffic may steer between overlays while the Internet firewall policy still targets underlays. It addresses two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. In the reported environment, the missing behavior instead relates to a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy. The relevant choice is a controlled failure of the first tunnel leads private traffic through the second while preserving policy matching.
B:The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces. The outcome for that step belongs to a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. Here the decisive requirement concerns a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy, so a controlled failure of the first tunnel leads private traffic through the second while preserving policy matching is the better fit.
D:5G failover sessions match the same policy as other members in that zone. It could be appropriate when a company adds a new 5G interface but its existing WAN firewall policy covers only a named SD-WAN zone containing the older links. However, that does not resolve the stated condition: a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy. A more direct answer is a controlled failure of the first tunnel leads private traffic through the second while preserving policy matching.
Question 114
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted.
- Filter by user, timestamp and the test file's detected event category
- Filter security logs by event type, application flow and the affected policy
- Inspect distinct affected identities and matched event categories in that window
- Inspect matching URL, category and inspection type at the time of the block
Explanation
Correct Answer
A:Filter by user, timestamp and the test file's detected event category. The observed evidence guides the targeted repair: Inspect relevant antivirus or file-security events in FortiSASE security logs.
Incorrect Answers
B:Filter security logs by event type, application flow and the affected policy. 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 a FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted, so filter by user, timestamp and the test file's detected event category is the better fit.
C:Inspect distinct affected identities and matched event categories in that window. That is a useful action for a different circumstance: a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. The present case is constrained by a FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted; the targeted response is filter by user, timestamp and the test file's detected event category.
D:Inspect matching URL, category and inspection type at the time of the block. It addresses users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event. In the reported environment, the missing behavior instead relates to a FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted. The relevant choice is filter by user, timestamp and the test file's detected event category.
Question 115
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A newly installed branch has healthy ISP links and an SD-WAN zone, yet LAN clients cannot browse because the existing allow policy targets only a former WAN interface.
- Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names
- Inspect whether the VPN tunnel is established and whether routes to private prefixes use the overlay zone
- Inspect the policy's destination interface and the assigned zone of that WAN member
- Inspect the session's policy match and the outbound interface named in the effective policy
Explanation
Correct Answer
D:Inspect the session's policy match and the outbound interface named in the effective policy. This check isolates the relevant control before the change. The firewall policy is a separate permission decision from member selection; a valid SD-WAN path does not itself allow sessions.
Incorrect Answers
A:Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names. It could be appropriate when a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. However, that does not resolve the stated condition: a newly installed branch has healthy ISP links and an SD-WAN zone, yet LAN clients cannot browse because the existing allow policy targets only a former WAN interface. A more direct answer is inspect the session's policy match and the outbound interface named in the effective policy.
B:Inspect whether the VPN tunnel is established and whether routes to private prefixes use the overlay zone. It addresses a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. In the reported environment, the missing behavior instead relates to a newly installed branch has healthy ISP links and an SD-WAN zone, yet LAN clients cannot browse because the existing allow policy targets only a former WAN interface. The relevant choice is inspect the session's policy match and the outbound interface named in the effective policy.
C:Inspect the policy's destination interface and the assigned zone of that WAN member. That is a useful action for a different circumstance: 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. The present case is constrained by a newly installed branch has healthy ISP links and an SD-WAN zone, yet LAN clients cannot browse because the existing allow policy targets only a former WAN interface; the targeted response is inspect the session's policy match and the outbound interface named in the effective policy.
Question 116
For the stated scenario, what is the most important remaining blind spot after the proposed correction? During an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary.
- A total blocked-count widget does not show which identities generated the events
- Using the prior week's scheduled report may omit the relevant incident
- The backup link being alive does not by itself prove the application still works
- Looking only at current green link health can miss a transient past trigger
Explanation
Correct Answer
B:Using the prior week's scheduled report may omit the relevant incident. The planned change can still miss the requirement if this condition is left unresolved. On-demand generation allows a targeted investigation without waiting for the next scheduled run.
Incorrect Answers
A:A total blocked-count widget does not show which identities generated the events. It could be appropriate when a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. However, that does not resolve the stated condition: during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. A more direct answer is using the prior week's scheduled report may omit the relevant incident.
C:The backup link being alive does not by itself prove the application still works. The outcome for that step belongs to a branch rollout claims reliable failover because the WAN link state changed, but the business owner wants proof that application transactions continued. Here the decisive requirement concerns during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary, so using the prior week's scheduled report may omit the relevant incident is the better fit.
D:Looking only at current green link health can miss a transient past trigger. That is a useful action for a different circumstance: an operator says a VPN application keeps failing over but cannot show whether the trigger was packet loss or a routing change. The present case is constrained by during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary; the targeted response is using the prior week's scheduled report may omit the relevant incident.
Question 117
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay.
- A passive-only measurement may lack fresh samples when no relevant application sessions exist
- Moving the tunnel without updating affected route and policy references can preserve the outage
- An overly broad default route must not hide the more-specific private overlay route
- A backup interface absent from monitoring should not be assumed SLA compliant merely because it is up
Explanation
Correct Answer
C:An overly broad default route must not hide the more-specific private overlay route. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:A passive-only measurement may lack fresh samples when no relevant application sessions exist. The outcome for that step belongs to two WAN interfaces show up, but the network manager needs continuous health information even when no users are active. Here the decisive requirement concerns a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay, so an overly broad default route must not hide the more-specific private overlay route is the better fit.
B: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: 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 an overly broad default route must not hide the more-specific private overlay route.
D:A backup interface absent from monitoring should not be assumed SLA compliant merely because it is up. It addresses the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. 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 an overly broad default route must not hide the more-specific private overlay route.
Question 118
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? An employee attempts to upload a restricted customer record to a collaboration app and receives a policy block.
- Review the cloud application's identified operation and enforcement action
- Inspect the sign-in outcomes, source addresses and account correlation in the audit window
- Inspect the matched DLP rule, user, application and blocked action
- Inspect matching URL, category and inspection type at the time of the block
Explanation
Correct Answer
C:Inspect the matched DLP rule, user, application and blocked action. The observed evidence guides the targeted repair: Review DLP or relevant inline SaaS security events for the sensitive-content match.
Incorrect Answers
A:Review the cloud application's identified operation and enforcement action. The outcome for that step belongs to security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. Here the decisive requirement concerns an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block, so inspect the matched DLP rule, user, application and blocked action is the better fit.
B:Inspect the sign-in outcomes, source addresses and account correlation in the audit window. It addresses a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. In the reported environment, the missing behavior instead relates to an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. The relevant choice is inspect the matched DLP rule, user, application and blocked action.
D:Inspect matching URL, category and inspection type at the time of the block. 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: an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. A more direct answer is inspect the matched DLP rule, user, application and blocked action.
Question 119
A proposed repair is to manage and verify the supported SD-WAN hub configuration objects through FortiManager with controlled deployment. Why should that repair work in this particular situation? Context: A company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites.
- Centralized orchestration can standardize supported configuration across FortiGate hubs while preserving site-specific data
- A multi-hub design requires coherent routing as well as tunnel availability to maintain private reachability
- Name resolution is separate from overlay routing and may require explicit private-domain handling
- PoP-to-hub transport can work while destinations behind the hub are still unadvertised or unpermitted
Explanation
Correct Answer
A:Centralized orchestration can standardize supported configuration across FortiGate hubs while preserving site-specific data. This is why the proposed repair addresses the reported behavior; confirm by checking: Each approved hub has consistent overlay and routing settings after verified deployment.
Incorrect Answers
B:A multi-hub design requires coherent routing as well as tunnel availability to maintain private reachability. 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 a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites, so centralized orchestration can standardize supported configuration across FortiGate hubs while preserving site-specific data is the better fit.
C:Name resolution is separate from overlay routing and may require explicit private-domain handling. 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 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 centralized orchestration can standardize supported configuration across FortiGate hubs while preserving site-specific data.
D:PoP-to-hub transport can work while destinations behind the hub are still unadvertised or unpermitted. That is a useful action for a different circumstance: a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. 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 centralized orchestration can standardize supported configuration across FortiGate hubs while preserving site-specific data.
Question 120
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements.
- Changing measured quality produces a corresponding member-selection change for the voice rule
- The lower-cost compliant link is selected; a lower-cost failing link does not automatically win
- Fresh monitoring intervals show quality consistent with the restored circuit and the SLA target
- The monitor updates quality statistics as application sessions traverse the selected WAN
Explanation
Correct Answer
B:The lower-cost compliant link is selected; a lower-cost failing link does not automatically win. This is stronger than a saved configuration because it tests the intended operational result. This strategy elects the lowest-cost member among links meeting the SLA before considering preference ties.
Incorrect Answers
A:Changing measured quality produces a corresponding member-selection change for the voice rule. It could be appropriate when an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit. However, that does not resolve the stated condition: a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements. A more direct answer is the lower-cost compliant link is selected; a lower-cost failing link does not automatically win.
C:Fresh monitoring intervals show quality consistent with the restored circuit and the SLA target. That is a useful action for a different circumstance: a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance. The present case is constrained by a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements; the targeted response is the lower-cost compliant link is selected; a lower-cost failing link does not automatically win.
D:The monitor updates quality statistics as application sessions traverse the selected WAN. The outcome for that step belongs to a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. Here the decisive requirement concerns a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements, so the lower-cost compliant link is selected; a lower-cost failing link does not automatically win is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests