Question 70
After the authorized change to review DLP or relevant inline SaaS security events for the sensitive-content match, which result actually demonstrates that this site's requirement is met? Initial issue: An employee attempts to upload a restricted customer record to a collaboration app and receives a policy block.
- The log identifies the disallowed in-app action while permitted app sessions remain visible
- A DLP event links the restricted content pattern to the denied upload
- The incident report accurately distinguishes failed-authentication patterns from malware findings
- The log shows a category-based web-filter block under the expected policy
Explanation
Correct Answer
B:A DLP event links the restricted content pattern to the denied upload. This is stronger than a saved configuration because it tests the intended operational result. DLP incidents identify content-rule enforcement distinct from simple URL or authentication failures.
Incorrect Answers
A:The log identifies the disallowed in-app action while permitted app sessions remain visible. That is a useful action for a different circumstance: security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. The present case is constrained by an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block; the targeted response is a DLP event links the restricted content pattern to the denied upload.
C:The incident report accurately distinguishes failed-authentication patterns from malware findings. The outcome for that step belongs to a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. Here the decisive requirement concerns an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block, so a DLP event links the restricted content pattern to the denied upload is the better fit.
D:The log shows a category-based web-filter block under the expected policy. 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 a DLP event links the restricted content pattern to the denied upload.
Question 71
During implementation, the administrator observes: A remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. Which intervention targets the described fault rather than an adjacent workflow?
- Apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events
- Review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust
- Create a separate security profile group and assign it only to the intended allow policy
- Deploy the appropriate FortiSASE inspection root certificate using a trusted endpoint-management method
Explanation
Correct Answer
C:Create a separate security profile group and assign it only to the intended allow policy. Security profile groups bundle inspection settings and can be selected per eligible traffic policy. The configuration alone must be followed by a functioning test: Only the intended group triggers the stricter web-filter behavior in logged tests.
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 employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. The relevant choice is create a separate security profile group and assign it only to the intended allow policy.
B:Review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust. It could be appropriate when an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. However, that does not resolve the stated condition: a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. A more direct answer is create a separate security profile group and assign it only to the intended allow policy.
D:Deploy the appropriate FortiSASE inspection root certificate using a trusted endpoint-management method. The outcome for that step belongs to a browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions. Here the decisive requirement concerns a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access, so create a separate security profile group and assign it only to the intended allow policy is the better fit.
Question 72
During implementation, the administrator observes: A sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application. Which intervention targets the described fault rather than an adjacent workflow?
- Apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events
- Use the supported inline-CASB application controls to target the specific file-transfer activity
- Review the exemption and narrow it to justified destinations before relying on content-based protection
- Attach an appropriate web-filter category policy to the matching FortiSASE security profile group
Explanation
Correct Answer
B:Use the supported inline-CASB application controls to target the specific file-transfer activity. Granular SaaS application controls distinguish an operation within an app from simply permitting the app's domain. The acceptance check should show: Approved collaboration functions succeed while the selected risky transfer operation is blocked.
Incorrect Answers
A:Apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events. The outcome for that step belongs to a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. Here the decisive requirement concerns a sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application, so use the supported inline-CASB application controls to target the specific file-transfer activity is the better fit.
C:Review the exemption and narrow it to justified destinations before relying on content-based protection. 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 sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application; the targeted response is use the supported inline-CASB application controls to target the specific file-transfer activity.
D: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 sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application. A more direct answer is use the supported inline-CASB application controls to target the specific file-transfer activity.
Question 73
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail.
- An ordinary allowed traffic log may omit the specific malware reason without the security event
- Changing SD-WAN member priority does not explain an application-layer intrusion signature
- A single average bandwidth value without time and member context cannot establish the spike's path
- A chart without accessible underlying event details cannot independently explain the suspected incident
Explanation
Correct Answer
D:A chart without accessible underlying event details cannot independently explain the suspected incident. The planned change can still miss the requirement if this condition is left unresolved. Reports provide aggregated trends, while raw event logs support specific incident verification.
Incorrect Answers
A:An ordinary allowed traffic log may omit the specific malware reason without the security event. It could be appropriate when a FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted. 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 a chart without accessible underlying event details cannot independently explain the suspected incident.
B:Changing SD-WAN member priority does not explain an application-layer intrusion signature. It addresses a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. 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 a chart without accessible underlying event details cannot independently explain the suspected incident.
C:A single average bandwidth value without time and member context cannot establish the spike's path. 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 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 a chart without accessible underlying event details cannot independently explain the suspected incident.
Question 74
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link.
- Check source address on an actual session and compare with the rule source selector
- Inspect the implicit or explicit rule's balance algorithm and the member session counters
- Compare cost settings with the qualifying SLA result for both members
- Review implicit strategy and active member selection for the unmatched test session
Explanation
Correct Answer
B:Inspect the implicit or explicit rule's balance algorithm and the member session counters. This check isolates the relevant control before the change. SD-WAN can distribute eligible session load across members according to its balancing method.
Incorrect Answers
A:Check source address on an actual session and compare with the rule source selector. It could be appropriate when fortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration. However, that does not resolve the stated condition: a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. A more direct answer is inspect the implicit or explicit rule's balance algorithm and the member session counters.
C:Compare cost settings with the qualifying SLA result for both members. 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 a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link; the targeted response is inspect the implicit or explicit rule's balance algorithm and the member session counters.
D:Review implicit strategy and active member selection for the unmatched test session. The outcome for that step belongs to no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. Here the decisive requirement concerns a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link, so inspect the implicit or explicit rule's balance algorithm and the member session counters is the better fit.
Question 75
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? The team sees a route via an SD-WAN zone but no actual WAN member is healthy under it.
- The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces
- Private application traffic matches the intended overlay policy after the zone correction
- Sessions over either provider hit the single intended allow policy and retain appropriate inspection
- A restored member carries test packets and is visible in the rule's active selection
Explanation
Correct Answer
D:A restored member carries test packets and is visible in the rule's active selection. This is stronger than a saved configuration because it tests the intended operational result. Routing through an SD-WAN zone requires a member capable of carrying traffic after health and reachability checks.
Incorrect Answers
A:The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces. It addresses a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. In the reported environment, the missing behavior instead relates to the team sees a route via an SD-WAN zone but no actual WAN member is healthy under it. The relevant choice is a restored member carries test packets and is visible in the rule's active selection.
B:Private application traffic matches the intended overlay policy after the zone correction. 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 team sees a route via an SD-WAN zone but no actual WAN member is healthy under it. A more direct answer is a restored member carries test packets and is visible in the rule's active selection.
C:Sessions over either provider hit the single intended allow policy and retain appropriate inspection. That is a useful action for a different circumstance: a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. The present case is constrained by the team sees a route via an SD-WAN zone but no actual WAN member is healthy under it; the targeted response is a restored member carries test packets and is visible in the rule's active selection.
Question 76
During implementation, the administrator observes: 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. Which intervention targets the described fault rather than an adjacent workflow?
- Use new test sessions and inspect the existing-session table separately when validating failover
- Inspect longest-prefix, administrative distance and route resolution for the affected address first
- Provide an Internet default route that resolves through the SD-WAN design before testing policy steering
- Troubleshoot BGP neighbor establishment and route advertisement over the SPA overlay
Explanation
Correct Answer
D:Troubleshoot BGP neighbor establishment and route advertisement over the SPA overlay. The FortiSASE-to-hub integration uses IPsec transport and routing information to reach private networks. The acceptance check should show: The hub routing table contains the expected reachable prefixes across the overlay.
Incorrect Answers
A:Use new test sessions and inspect the existing-session table separately when validating failover. It addresses a provider outage removes a member's usable path, yet operators continue testing sessions that were established before the outage. In the reported environment, the missing behavior instead relates to 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 relevant choice is troubleshoot BGP neighbor establishment and route advertisement over the SPA overlay.
B:Inspect longest-prefix, administrative distance and route resolution for the affected address first. That is a useful action for a different circumstance: a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. The present case is constrained by 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 targeted response is troubleshoot BGP neighbor establishment and route advertisement over the SPA overlay.
C:Provide an Internet default route that resolves through the SD-WAN design before testing policy steering. It could be appropriate when an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. However, that does not resolve the stated condition: 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. A more direct answer is troubleshoot BGP neighbor establishment and route advertisement over the SPA overlay.
Question 77
A proposed repair is to inspect and reconcile policy routing with SD-WAN route and rule evaluation before predicting the egress member. Why should that repair work in this particular situation? Context: An internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule.
- Policy routes can affect forwarding independently of ordinary destination route and member preference
- A usable member requires a valid layer-3 next hop, not just a physically active interface
- Routing and steering determine path availability, while firewall policy decides whether traffic is permitted
- The FortiSASE-to-hub integration uses IPsec transport and routing information to reach private networks
Explanation
Correct Answer
A:Policy routes can affect forwarding independently of ordinary destination route and member preference. This is why the proposed repair addresses the reported behavior; confirm by checking: The observed egress follows the final documented routing and SD-WAN policy design.
Incorrect Answers
B:A usable member requires a valid layer-3 next hop, not just a physically active interface. It addresses a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. In the reported environment, the missing behavior instead relates to an internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule. The relevant choice is policy routes can affect forwarding independently of ordinary destination route and member preference.
C:Routing and steering determine path availability, while firewall policy decides whether traffic is permitted. The outcome for that step belongs to a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. Here the decisive requirement concerns an internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule, so policy routes can affect forwarding independently of ordinary destination route and member preference is the better fit.
D:The FortiSASE-to-hub integration uses IPsec transport and routing information to reach private networks. 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 an internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule; the targeted response is policy routes can affect forwarding independently of ordinary destination route and member preference.
Question 78
The team is troubleshooting the following Fortinet 7.6 deployment: A company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions. Which specific corrective action should be prioritized?
- Configure the supported endpoint compliance or posture criteria and associate them with the appropriate access treatment
- Refresh endpoint posture reporting and verify the rule's effective match data before relaxing policy
- Constrain the pilot profile to a narrowly defined test user or endpoint group
- Stage the baseline through a limited pilot group and validate enforcement before broader rollout
Explanation
Correct Answer
A:Configure the supported endpoint compliance or posture criteria and associate them with the appropriate access treatment. Endpoint posture requirements differentiate compliant and noncompliant devices independently of user authentication. The configuration alone must be followed by a functioning test: A protected test endpoint receives normal access while a noncompliant one is restricted as designed.
Incorrect Answers
B:Refresh endpoint posture reporting and verify the rule's effective match data before relaxing policy. The outcome for that step belongs to a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings. Here the decisive requirement concerns a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions, so configure the supported endpoint compliance or posture criteria and associate them with the appropriate access treatment is the better fit.
C:Constrain the pilot profile to a narrowly defined test user or endpoint group. It addresses an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. In the reported environment, the missing behavior instead relates to a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions. The relevant choice is configure the supported endpoint compliance or posture criteria and associate them with the appropriate access treatment.
D:Stage the baseline through a limited pilot group and validate enforcement before broader rollout. That is a useful action for a different circumstance: an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once. The present case is constrained by a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions; the targeted response is configure the supported endpoint compliance or posture criteria and associate them with the appropriate access treatment.
Question 79
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? 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.
- Inspect the health-check member list and whether the backup reports probe metrics
- Compare measured jitter for each member with the voice SLA target rather than only checking packet loss
- Review time-aligned SLA transitions and rule/member selection at the failure timestamp
- Inspect configured member costs, measured SLA target results and the selected rule
Explanation
Correct Answer
C:Review time-aligned SLA transitions and rule/member selection at the failure timestamp. The observed evidence guides the targeted repair: Correlate SLA health-check events with member selection and session logs around the incident time.
Incorrect Answers
A:Inspect the health-check member list and whether the backup reports probe metrics. It could be appropriate when the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. However, that does not resolve the stated condition: 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. A more direct answer is review time-aligned SLA transitions and rule/member selection at the failure timestamp.
B:Compare measured jitter for each member with the voice SLA target rather than only checking packet loss. It addresses a voice application performs poorly with high jitter even though packet loss is low on both WANs. In the reported environment, the missing behavior instead relates 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. The relevant choice is review time-aligned SLA transitions and rule/member selection at the failure timestamp.
D:Inspect configured member costs, measured SLA target results and the selected rule. The outcome for that step belongs to a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements. Here the decisive requirement concerns 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, so review time-aligned SLA transitions and rule/member selection at the failure timestamp is the better fit.
Question 80
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops.
- Choosing the closest PoP without checking statutory data-location requirements can violate the design goal
- An allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access
- A browser-only SWG proxy configuration does not replace full endpoint agent management
- An ordinary Internet access policy at the SASE PoP does not automatically create private-site connectivity
Explanation
Correct Answer
C:A browser-only SWG proxy configuration does not replace full endpoint agent management. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Choosing the closest PoP without checking statutory data-location requirements can violate the design goal. It could be appropriate when a multinational company is activating FortiSASE and must decide which geographical security PoP regions should serve its remote employees. However, that does not resolve the stated condition: a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops. A more direct answer is a browser-only SWG proxy configuration does not replace full endpoint agent management.
B:An allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access. 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 workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops, so a browser-only SWG proxy configuration does not replace full endpoint agent management is the better fit.
D:An ordinary Internet access policy at the SASE PoP does not automatically create private-site connectivity. It addresses a customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly. In the reported environment, the missing behavior instead relates to a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops. The relevant choice is a browser-only SWG proxy configuration does not replace full endpoint agent management.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests