Question 720
The team is troubleshooting the following Fortinet 7.6 deployment: A single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. Which specific corrective action should be prioritized?
- Narrow the broad rule's match conditions or change rule order so the SaaS exception can match
- Use a matching SD-WAN rule with a manual member preference for the payroll traffic
- Reduce the required qualifying-member minimum only if the availability design permits it, or restore a third qualifying member
- Verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required
Explanation
Correct Answer
A:Narrow the broad rule's match conditions or change rule order so the SaaS exception can match. Broad earlier matches can preempt narrower intended steering logic. The configuration alone must be followed by a functioning test: The SaaS service hits its own rule while generic traffic remains under the broad steering rule.
Incorrect Answers
B:Use a matching SD-WAN rule with a manual member preference for the payroll traffic. The outcome for that step belongs to a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. Here the decisive requirement concerns a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used, so narrow the broad rule's match conditions or change rule order so the SaaS exception can match is the better fit.
C:Reduce the required qualifying-member minimum only if the availability design permits it, or restore a third qualifying member. It addresses after a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy. In the reported environment, the missing behavior instead relates to a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. The relevant choice is narrow the broad rule's match conditions or change rule order so the SaaS exception can match.
D:Verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required. That is a useful action for a different circumstance: the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. The present case is constrained by a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used; the targeted response is narrow the broad rule's match conditions or change rule order so the SaaS exception can match.
Question 721
The team plans to create a separate security profile group and assign it only to the intended allow policy for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access.
- Successful SAML authentication alone does not prove acceptable endpoint security posture
- Changing a FortiGate WAN gateway does not influence FortiSASE endpoint-profile assignment
- Editing the shared default profile can affect other user groups unintentionally
- An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals
Explanation
Correct Answer
C:Editing the shared default profile can affect other user groups unintentionally. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Successful SAML authentication alone does not prove acceptable endpoint security posture. It could be appropriate when a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions. 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 editing the shared default profile can affect other user groups unintentionally.
B:Changing a FortiGate WAN gateway does not influence FortiSASE endpoint-profile assignment. The outcome for that step belongs to a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. Here the decisive requirement concerns a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access, so editing the shared default profile can affect other user groups unintentionally is the better fit.
D:An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals. It addresses security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks. 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 editing the shared default profile can affect other user groups unintentionally.
Question 722
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile.
- Inspect the chosen pilot population and measured compliance results before expansion
- Inspect assigned groups and effective profile for a pilot and a nonpilot device
- Check user-group membership, intended profile priority and effective endpoint assignment
- Inspect the latest FortiClient compliance attributes and the matched rule
Explanation
Correct Answer
C:Check user-group membership, intended profile priority and effective endpoint assignment. The observed evidence guides the targeted repair: Correct the user/group targeting of the intended endpoint profile and synchronize membership.
Incorrect Answers
A:Inspect the chosen pilot population and measured compliance results before expansion. It could be appropriate when an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once. However, that does not resolve the stated condition: a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. A more direct answer is check user-group membership, intended profile priority and effective endpoint assignment.
B:Inspect assigned groups and effective profile for a pilot and a nonpilot device. The outcome for that step belongs to an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. Here the decisive requirement concerns a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile, so check user-group membership, intended profile priority and effective endpoint assignment is the better fit.
D:Inspect the latest FortiClient compliance attributes and the matched rule. It addresses a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings. In the reported environment, the missing behavior instead relates to a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. The relevant choice is check user-group membership, intended profile priority and effective endpoint assignment.
Question 723
At a FortiSASE/SD-WAN site, this issue is reported: A security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider. What is the most direct technical change to address the stated requirement?
- Reduce the required qualifying-member minimum only if the availability design permits it, or restore a third qualifying member
- Add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member
- Use the supported application or Internet-service matching criteria for the intended conference traffic
- Use a matching SD-WAN rule with a manual member preference for the payroll traffic
Explanation
Correct Answer
C:Use the supported application or Internet-service matching criteria for the intended conference traffic. Application-aware matching can distinguish a known service from unrelated flows on shared infrastructure. The configuration alone must be followed by a functioning test: Conference sessions match the dedicated rule while unrelated services do not.
Incorrect Answers
A:Reduce the required qualifying-member minimum only if the availability design permits it, or restore a third qualifying member. It addresses after a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy. In the reported environment, the missing behavior instead relates to a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider. The relevant choice is use the supported application or Internet-service matching criteria for the intended conference traffic.
B:Add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member. 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 security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider, so use the supported application or Internet-service matching criteria for the intended conference traffic is the better fit.
D:Use a matching SD-WAN rule with a manual member preference for the payroll traffic. It could be appropriate when a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. However, that does not resolve the stated condition: a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider. A more direct answer is use the supported application or Internet-service matching criteria for the intended conference traffic.
Question 724
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor.
- Keeping unconditional manual preference can repeatedly favor a degraded but connected member
- Changing an SD-WAN member weight cannot overturn an explicit deny policy
- A perfect application match still fails without valid forwarding reachability
- A static route table screenshot alone cannot establish past per-session forwarding
Explanation
Correct Answer
A:Keeping unconditional manual preference can repeatedly favor a degraded but connected member. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Changing an SD-WAN member weight cannot overturn an explicit deny policy. It addresses a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. In the reported environment, the missing behavior instead relates to a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. The relevant choice is keeping unconditional manual preference can repeatedly favor a degraded but connected member.
C:A perfect application match still fails without valid forwarding reachability. The outcome for that step belongs to an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. Here the decisive requirement concerns a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor, so keeping unconditional manual preference can repeatedly favor a degraded but connected member is the better fit.
D:A static route table screenshot alone cannot establish past per-session forwarding. That is a useful action for a different circumstance: 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. The present case is constrained by a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor; the targeted response is keeping unconditional manual preference can repeatedly favor a degraded but connected member.
Question 725
After the authorized change to configure a latency target in the performance SLA and bind it to the call-center rule, which result actually demonstrates that this site's requirement is met? Initial issue: A call-center SLA must avoid any WAN link whose one-way delay is above an agreed threshold.
- The rule activates only while at least two members satisfy its required SLA
- The logged SLA failure aligns with the observed traffic path change
- Traffic uses a link that meets the configured latency threshold when one is available
- The monitored members report latency, loss and jitter while the branch is idle
Explanation
Correct Answer
C:Traffic uses a link that meets the configured latency threshold when one is available. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:The rule activates only while at least two members satisfy its required SLA. 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 call-center SLA must avoid any WAN link whose one-way delay is above an agreed threshold. The relevant choice is traffic uses a link that meets the configured latency threshold when one is available.
B:The logged SLA failure aligns with the observed traffic path change. 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 call-center SLA must avoid any WAN link whose one-way delay is above an agreed threshold, so traffic uses a link that meets the configured latency threshold when one is available is the better fit.
D:The monitored members report latency, loss and jitter while the branch is idle. It could be appropriate when two WAN interfaces show up, but the network manager needs continuous health information even when no users are active. However, that does not resolve the stated condition: a call-center SLA must avoid any WAN link whose one-way delay is above an agreed threshold. A more direct answer is traffic uses a link that meets the configured latency threshold when one is available.
Question 726
The team plans to use FortiSASE SPA with a supported FortiGate hub connection for the approved private network prefixes for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? An organization needs private TCP and UDP access to multiple office services without publishing public listener ports.
- An Internet-only SWG proxy is not equivalent to routed private UDP application access
- Deep-inspection exemptions can interfere with SWG SSO flows under this configuration
- Giving everyone the top administrative role would bypass the separation-of-duties goal
- Disabling all certificate verification would undermine the identity-trust boundary instead of repairing it
Explanation
Correct Answer
A:An Internet-only SWG proxy is not equivalent to routed private UDP application access. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Deep-inspection exemptions can interfere with SWG SSO flows under this configuration. That is a useful action for a different circumstance: the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. The present case is constrained by an organization needs private TCP and UDP access to multiple office services without publishing public listener ports; the targeted response is an Internet-only SWG proxy is not equivalent to routed private UDP application access.
C:Giving everyone the top administrative role would bypass the separation-of-duties goal. The outcome for that step belongs to a company needs administrators to troubleshoot access policies without allowing every operator to change identity sources or global settings. Here the decisive requirement concerns an organization needs private TCP and UDP access to multiple office services without publishing public listener ports, so an Internet-only SWG proxy is not equivalent to routed private UDP application access is the better fit.
D:Disabling all certificate verification would undermine the identity-trust boundary instead of repairing it. It addresses a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. In the reported environment, the missing behavior instead relates to an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. The relevant choice is an Internet-only SWG proxy is not equivalent to routed private UDP application access.
Question 727
During implementation, the administrator observes: No custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. Which intervention targets the described fault rather than an adjacent workflow?
- Inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs
- Switch to a quality-aware strategy with a matching SLA requirement for the application
- Verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required
- Move or refine the billing rule so the specific matching policy is considered before the broad catchall
Explanation
Correct Answer
A:Inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs. The implicit rule supplies default member selection when custom rules do not match. The configuration alone must be followed by a functioning test: A test session with no explicit rule match follows the implicit rule's configured algorithm.
Incorrect Answers
B:Switch to a quality-aware strategy with a matching SLA requirement for the application. The outcome for that step belongs to a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. Here the decisive requirement concerns no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member, so inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs is the better fit.
C:Verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required. That is a useful action for a different circumstance: the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. The present case is constrained by no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member; the targeted response is inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs.
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 no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. The relevant choice is inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs.
Question 728
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used.
- Adding more SLA targets to the later rule cannot help while it is never evaluated for matching traffic
- A perfect application match still fails without valid forwarding reachability
- Preserving an established remote TCP session across different NAT public IPs cannot be assumed
- Assuming every established TCP session seamlessly survives a path or SNAT address change is unsafe
Explanation
Correct Answer
A:Adding more SLA targets to the later rule cannot help while it is never evaluated for matching traffic. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:A perfect application match still fails without valid forwarding reachability. It addresses an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. In the reported environment, the missing behavior instead relates to a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. The relevant choice is adding more SLA targets to the later rule cannot help while it is never evaluated for matching traffic.
C:Preserving an established remote TCP session across different NAT public IPs cannot be assumed. The outcome for that step belongs to a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. Here the decisive requirement concerns a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used, so adding more SLA targets to the later rule cannot help while it is never evaluated for matching traffic is the better fit.
D:Assuming every established TCP session seamlessly survives a path or SNAT address change is unsafe. That is a useful action for a different circumstance: a provider outage removes a member's usable path, yet operators continue testing sessions that were established before the outage. The present case is constrained by a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used; the targeted response is adding more SLA targets to the later rule cannot help while it is never evaluated for matching traffic.
Question 729
A proposed repair is to use Lowest Cost (SLA) steering with relevant performance targets and appropriate member costs. Why should that repair work in this particular situation? Context: A finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements.
- A live transport can fail an application's quality threshold without becoming administratively down
- Performance SLA thresholds mark which members satisfy a particular application's quality needs
- SLA loss checks can disqualify a degraded path even when the physical carrier remains established
- This strategy elects the lowest-cost member among links meeting the SLA before considering preference ties
Explanation
Correct Answer
D:This strategy elects the lowest-cost member among links meeting the SLA before considering preference ties. It directly explains the need to use Lowest Cost (SLA) steering with relevant performance targets and appropriate member costs. The narrow validation is: The lower-cost compliant link is selected; a lower-cost failing link does not automatically win.
Incorrect Answers
A:A live transport can fail an application's quality threshold without becoming administratively down. It addresses an SD-WAN operator sees a link marked alive but the performance SLA map shows it misses the configured voice target. In the reported environment, the missing behavior instead relates to a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements. The relevant choice is this strategy elects the lowest-cost member among links meeting the SLA before considering preference ties.
B:Performance SLA thresholds mark which members satisfy a particular application's quality needs. It could be appropriate when a call-center SLA must avoid any WAN link whose one-way delay is above an agreed threshold. 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 this strategy elects the lowest-cost member among links meeting the SLA before considering preference ties.
C:SLA loss checks can disqualify a degraded path even when the physical carrier remains established. That is a useful action for a different circumstance: a remote kiosk experiences intermittent missing packets despite its interface staying up. 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 this strategy elects the lowest-cost member among links meeting the SLA before considering preference ties.
Question 730
The team plans to analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up.
- Manually exporting a dashboard once does not meet a recurring reporting requirement
- Treating every blocked website as an IPS exploit event misclassifies the cause
- An interface-up log cannot establish which member carried a specific session
- Treating all errors as virus detections can send responders down the wrong path
Explanation
Correct Answer
C:An interface-up log cannot establish which member carried a specific session. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Manually exporting a dashboard once does not meet a recurring reporting requirement. The outcome for that step belongs to the compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it. Here the decisive requirement concerns a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up, so an interface-up log cannot establish which member carried a specific session is the better fit.
B:Treating every blocked website as an IPS exploit event misclassifies the cause. 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 branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. The relevant choice is an interface-up log cannot establish which member carried a specific session.
D:Treating all errors as virus detections can send responders down the wrong path. 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 branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. A more direct answer is an interface-up log cannot establish which member carried a specific session.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests