Question 670
During implementation, the administrator observes: A branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. Which intervention targets the described fault rather than an adjacent workflow?
- Define separate, appropriately specific SD-WAN rules for each application's selection criteria
- Use the appropriate Internet Service Database selector within the SD-WAN rule where supported
- Move or refine the billing rule so the specific matching policy is considered before the broad catchall
- Use an appropriate load-balancing strategy and verify how the selected algorithm distributes sessions
Explanation
Correct Answer
D:Use an appropriate load-balancing strategy and verify how the selected algorithm distributes sessions. SD-WAN can distribute eligible session load across members according to its balancing method. The acceptance check should show: New eligible backup sessions spread across both members in line with the chosen algorithm.
Incorrect Answers
A:Define separate, appropriately specific SD-WAN rules for each application's selection criteria. It could be appropriate when a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. 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 use an appropriate load-balancing strategy and verify how the selected algorithm distributes sessions.
B:Use the appropriate Internet Service Database selector within the SD-WAN rule where supported. That is a useful action for a different circumstance: an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. 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 use an appropriate load-balancing strategy and verify how the selected algorithm distributes sessions.
C:Move or refine the billing rule so the specific matching policy is considered before the broad catchall. It addresses a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. In the reported environment, the missing behavior instead relates to a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. The relevant choice is use an appropriate load-balancing strategy and verify how the selected algorithm distributes sessions.
Question 671
The team is troubleshooting the following Fortinet 7.6 deployment: A FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted. Which specific corrective action should be prioritized?
- Investigate authentication/security events, source context and timing before claiming a malware outbreak
- Filter FortiSASE threat events by user identity, policy and time interval
- Inspect relevant antivirus or file-security events in FortiSASE security logs
- Review DLP or relevant inline SaaS security events for the sensitive-content match
Explanation
Correct Answer
C:Inspect relevant antivirus or file-security events in FortiSASE security logs. Threat logs document which inspection component made the deny or detection decision. The configuration alone must be followed by a functioning test: A matching malware event identifies the appropriate inspection control and action.
Incorrect Answers
A:Investigate authentication/security events, source context and timing before claiming a malware outbreak. It could be appropriate when a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. However, that does not resolve the stated condition: a FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted. A more direct answer is inspect relevant antivirus or file-security events in FortiSASE security logs.
B:Filter FortiSASE threat events by user identity, policy and time interval. It addresses a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. 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 inspect relevant antivirus or file-security events in FortiSASE security logs.
D:Review DLP or relevant inline SaaS security events for the sensitive-content match. The outcome for that step belongs to an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. 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 inspect relevant antivirus or file-security events in FortiSASE security logs is the better fit.
Question 672
During implementation, the administrator observes: A custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. Which intervention targets the described fault rather than an adjacent workflow?
- Use a Best Quality SD-WAN rule evaluated against the relevant jitter quality metric
- Use the appropriate Internet Service Database selector within the SD-WAN rule where supported
- Add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member
- Move or refine the billing rule so the specific matching policy is considered before the broad catchall
Explanation
Correct Answer
C:Add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member. An ordinary allow policy decides permission; the steering rule determines eligible egress selection for matched traffic. The configuration alone must be followed by a functioning test: Emergency flows use the intended LTE member without rerouting unrelated Web traffic.
Incorrect Answers
A:Use a Best Quality SD-WAN rule evaluated against the relevant jitter quality 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 custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy, so add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member is the better fit.
B:Use the appropriate Internet Service Database selector within the SD-WAN rule where supported. It could be appropriate when an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. However, that does not resolve the stated condition: a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. A more direct answer is add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member.
D:Move or refine the billing rule so the specific matching policy is considered before the broad catchall. It addresses a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. In the reported environment, the missing behavior instead relates 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. The relevant choice is add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member.
Question 673
At a FortiSASE/SD-WAN site, this issue is reported: A new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. What is the most direct technical change to address the stated requirement?
- Create or assign a narrowly targeted security profile group to the intended user-group policy
- Apply DNS-filter settings where supported to the relevant FortiSASE policy profile
- Review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust
- Review the exemption and narrow it to justified destinations before relying on content-based protection
Explanation
Correct Answer
A:Create or assign a narrowly targeted security profile group to the intended user-group policy. Profile-group selection at policy level can differentiate inspection by user cohort. The configuration alone must be followed by a functioning test: Only the targeted cohort receives the block, and other approved users retain expected access.
Incorrect Answers
B:Apply DNS-filter settings where supported to the relevant FortiSASE policy profile. That is a useful action for a different circumstance: a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. The present case is constrained by a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule; the targeted response is create or assign a narrowly targeted security profile group to the intended user-group policy.
C:Review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust. It addresses an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. In the reported environment, the missing behavior instead relates to a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. The relevant choice is create or assign a narrowly targeted security profile group to the intended user-group policy.
D:Review the exemption and narrow it to justified destinations before relying on content-based protection. The outcome for that step belongs to a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules. Here the decisive requirement concerns a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule, so create or assign a narrowly targeted security profile group to the intended user-group policy is the better fit.
Question 674
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule.
- Inspect the effective web-filter profile and category action for the test URL
- Inspect the DLP profile match rules and whether the application traffic is decryptable where required
- Inspect policy rule order, matching user group and attached security profile group
- Inspect the presented certificate chain and local trusted CA store
Explanation
Correct Answer
C:Inspect policy rule order, matching user group and attached security profile group. The observed evidence guides the targeted repair: Create or assign a narrowly targeted security profile group to the intended user-group policy.
Incorrect Answers
A:Inspect the effective web-filter profile and category action for the test URL. 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 new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. A more direct answer is inspect policy rule order, matching user group and attached security profile group.
B:Inspect the DLP profile match rules and whether the application traffic is decryptable where required. It addresses a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications. In the reported environment, the missing behavior instead relates to a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. The relevant choice is inspect policy rule order, matching user group and attached security profile group.
D:Inspect the presented certificate chain and local trusted CA store. 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 new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule, so inspect policy rule order, matching user group and attached security profile group is the better fit.
Question 675
During implementation, the administrator observes: A voice application performs poorly with high jitter even though packet loss is low on both WANs. Which intervention targets the described fault rather than an adjacent workflow?
- Set the rule's supported minimum SLA-meeting member count to two
- Review live probe status and allow new samples to establish post-maintenance link quality
- Define a jitter SLA threshold and reference that health target in the voice steering rule
- Use supported passive health measurements from real application sessions where sufficient sessions exist
Explanation
Correct Answer
C:Define a jitter SLA threshold and reference that health target in the voice steering rule. Jitter is a separate quality dimension; low packet loss does not guarantee acceptable voice timing. The configuration alone must be followed by a functioning test: New eligible voice sessions choose a link meeting the defined jitter criterion when available.
Incorrect Answers
A:Set the rule's supported minimum SLA-meeting member count to two. It addresses the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. In the reported environment, the missing behavior instead relates to a voice application performs poorly with high jitter even though packet loss is low on both WANs. The relevant choice is define a jitter SLA threshold and reference that health target in the voice steering rule.
B:Review live probe status and allow new samples to establish post-maintenance link quality. The outcome for that step belongs to a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance. Here the decisive requirement concerns a voice application performs poorly with high jitter even though packet loss is low on both WANs, so define a jitter SLA threshold and reference that health target in the voice steering rule is the better fit.
D:Use supported passive health measurements from real application sessions where sufficient sessions exist. It could be appropriate when a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. However, that does not resolve the stated condition: a voice application performs poorly with high jitter even though packet loss is low on both WANs. A more direct answer is define a jitter SLA threshold and reference that health target in the voice steering rule.
Question 676
Given this incident — A security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. — the administrator plans to apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events. Which technical principle justifies it?
- Profile-group selection at policy level can differentiate inspection by user cohort
- Intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation
- Granular SaaS application controls distinguish an operation within an app from simply permitting the app's domain
- FortiSASE applies selected inspection components through profile groups associated with eligible policies
Explanation
Correct Answer
B:Intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation. It directly explains the need to apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events. The narrow validation is: A controlled security test produces the expected IPS event or block decision.
Incorrect Answers
A:Profile-group selection at policy level can differentiate inspection by user cohort. It could be appropriate when a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. However, that does not resolve the stated condition: a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. A more direct answer is intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation.
C:Granular SaaS application controls distinguish an operation within an app from simply permitting the app's domain. 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 security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE, so intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation is the better fit.
D:FortiSASE applies selected inspection components through profile groups associated with eligible policies. That is a useful action for a different circumstance: a remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group. The present case is constrained by a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE; the targeted response is intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation.
Question 677
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it.
- Changing an unrelated security inspection profile does not solve geographical path selection
- A traffic log showing an allowed website request is not proof of who edited the policy
- Shared administrator credentials obscure individual change attribution even when policies are technically valid
- A successful ping to the hub interface does not establish end-to-end private-network access
Explanation
Correct Answer
D:A successful ping to the hub interface does not establish end-to-end private-network access. The planned change can still miss the requirement if this condition is left unresolved. PoP-to-hub transport can work while destinations behind the hub are still unadvertised or unpermitted.
Incorrect Answers
A:Changing an unrelated security inspection profile does not solve geographical path selection. It addresses the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband. In the reported environment, the missing behavior instead relates to a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. The relevant choice is a successful ping to the hub interface does not establish end-to-end private-network access.
B:A traffic log showing an allowed website request is not proof of who edited the policy. That is a useful action for a different circumstance: an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. The present case is constrained by a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it; the targeted response is a successful ping to the hub interface does not establish end-to-end private-network access.
C:Shared administrator credentials obscure individual change attribution even when policies are technically valid. It could be appropriate when one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. However, that does not resolve the stated condition: a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. A more direct answer is a successful ping to the hub interface does not establish end-to-end private-network access.
Question 678
A proposed repair is to define the supported endpoint vulnerability or posture-tag condition and enforce it in the private-access policy. Why should that repair work in this particular situation? Context: A remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications.
- Group-scoped endpoint profiles enable different device behavior for different organizational roles
- Endpoint profiles are assigned to AD or non-AD groups based on their configured match conditions
- Vulnerability-aware device posture can restrict endpoints independently of the user identity check
- Endpoint posture requirements differentiate compliant and noncompliant devices independently of user authentication
Explanation
Correct Answer
C:Vulnerability-aware device posture can restrict endpoints independently of the user identity check. This is why the proposed repair addresses the reported behavior; confirm by checking: A patched test endpoint receives the compliant tag while a deliberately vulnerable test endpoint receives the intended restriction.
Incorrect Answers
A:Group-scoped endpoint profiles enable different device behavior for different organizational roles. It could be appropriate when one employee group is permitted removable media use while everyone else must be restricted by endpoint policy. However, that does not resolve the stated condition: a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. A more direct answer is vulnerability-aware device posture can restrict endpoints independently of the user identity check.
B:Endpoint profiles are assigned to AD or non-AD groups based on their configured match conditions. It addresses a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. In the reported environment, the missing behavior instead relates to a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. The relevant choice is vulnerability-aware device posture can restrict endpoints independently of the user identity check.
D:Endpoint posture requirements differentiate compliant and noncompliant devices independently of user authentication. The outcome for that step belongs to a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions. Here the decisive requirement concerns a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications, so vulnerability-aware device posture can restrict endpoints independently of the user identity check is the better fit.
Question 679
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load.
- Filter SD-WAN health and session logs to the user flow and disruption timestamps
- Inspect transaction timestamps and log status on both sides of the impairment
- Inspect time-aligned per-member bytes or sessions and the corresponding flow log fields
- Review the payment session's egress and rule ID instead of only the SLA dashboard
Explanation
Correct Answer
C:Inspect time-aligned per-member bytes or sessions and the corresponding flow log fields. The observed evidence guides the targeted repair: Use SD-WAN traffic logs and member performance/usage views for the same time window.
Incorrect Answers
A:Filter SD-WAN health and session logs to the user flow and disruption timestamps. It addresses a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. In the reported environment, the missing behavior instead relates to a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. The relevant choice is inspect time-aligned per-member bytes or sessions and the corresponding flow log fields.
B:Inspect transaction timestamps and log status on both sides of the impairment. It could be appropriate when a branch rollout claims reliable failover because the WAN link state changed, but the business owner wants proof that application transactions continued. However, that does not resolve the stated condition: a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. A more direct answer is inspect time-aligned per-member bytes or sessions and the corresponding flow log fields.
D:Review the payment session's egress and rule ID instead of only the SLA dashboard. The outcome for that step belongs to an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. 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 inspect time-aligned per-member bytes or sessions and the corresponding flow log fields is the better fit.
Question 680
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription.
- After an approved region or steering correction, affected users reach an appropriate PoP with improved path latency
- A remote employee receives the same intended web-filter decision from two distinct locations
- The appropriate capability is visible and usable after entitlement verification and provisioning
- The audit record identifies the account and event corresponding to the deployed change
Explanation
Correct Answer
C:The appropriate capability is visible and usable after entitlement verification and provisioning. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:After an approved region or steering correction, affected users reach an appropriate PoP with improved path latency. It addresses the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband. In the reported environment, the missing behavior instead relates to a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. The relevant choice is the appropriate capability is visible and usable after entitlement verification and provisioning.
B:A remote employee receives the same intended web-filter decision from two distinct locations. The outcome for that step belongs 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. Here the decisive requirement concerns a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription, so the appropriate capability is visible and usable after entitlement verification and provisioning is the better fit.
D:The audit record identifies the account and event corresponding to the deployed change. It could be appropriate when an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. However, that does not resolve the stated condition: a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. A more direct answer is the appropriate capability is visible and usable after entitlement verification and provisioning.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests