Question 690
After the authorized change to place the MPLS and Internet members in distinct SD-WAN zones and target each zone in the appropriate policy, which result actually demonstrates that this site's requirement is met? Initial issue: A branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic.
- The ISP interface is listed as a member and selected by a matching SD-WAN rule
- Traffic on private and Internet paths matches their respective intended firewall policies
- Internet flows use the correct ISP zone and inspection profile without touching private-overlay policies
- A controlled failure of the first tunnel leads private traffic through the second while preserving policy matching
Explanation
Correct Answer
B:Traffic on private and Internet paths matches their respective intended firewall policies. This is stronger than a saved configuration because it tests the intended operational result. Zones provide policy-level grouping, making distinct inspection by transport class possible.
Incorrect Answers
A:The ISP interface is listed as a member and selected by a matching SD-WAN rule. That is a useful action for a different circumstance: a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. The present case is constrained by a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic; the targeted response is traffic on private and Internet paths matches their respective intended firewall policies.
C:Internet flows use the correct ISP zone and inspection profile without touching private-overlay policies. The outcome for that step belongs to a deployment requires public Internet from a third ISP, and the operator wants to manage it independently without applying the private overlay's IPS policy. Here the decisive requirement concerns a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic, so traffic on private and Internet paths matches their respective intended firewall policies is the better fit.
D:A controlled failure of the first tunnel leads private traffic through the second while preserving policy matching. It could be appropriate when a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy. However, that does not resolve the stated condition: a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic. A more direct answer is traffic on private and Internet paths matches their respective intended firewall policies.
Question 691
During implementation, the administrator observes: 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. Which intervention targets the described fault rather than an adjacent workflow?
- Check SNAT and session behavior when rerouting across WAN members, not only link quality
- Inspect and reconcile policy routing with SD-WAN route and rule evaluation before predicting the egress member
- Fix the measured quality or revise a justified SLA threshold instead of treating route presence as proof of eligibility
- Correct the separate firewall-policy match or security action after confirming the route is valid
Explanation
Correct Answer
B:Inspect and reconcile policy routing with SD-WAN route and rule evaluation before predicting the egress member. Policy routes can affect forwarding independently of ordinary destination route and member preference. The acceptance check should show: The observed egress follows the final documented routing and SD-WAN policy design.
Incorrect Answers
A:Check SNAT and session behavior when rerouting across WAN members, not only link quality. It could be appropriate when a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. However, that does not resolve the stated condition: 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. A more direct answer is inspect and reconcile policy routing with SD-WAN route and rule evaluation before predicting the egress member.
C:Fix the measured quality or revise a justified SLA threshold instead of treating route presence as proof of eligibility. The outcome for that step belongs to an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing. Here the decisive requirement concerns 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 inspect and reconcile policy routing with SD-WAN route and rule evaluation before predicting the egress member is the better fit.
D:Correct the separate firewall-policy match or security action after confirming the route is valid. That is a useful action for a different circumstance: a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. 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 inspect and reconcile policy routing with SD-WAN route and rule evaluation before predicting the egress member.
Question 692
For a change review, the team proposes to add both WAN interfaces as SD-WAN members in an appropriate zone before defining the steering rule because: A new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering. Which explanation connects the change to the underlying behavior?
- A specific steering rule explains the egress decision more reliably than assuming interface order alone
- Steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates
- SD-WAN forwarding follows both route reachability and matching policy, so public DIA need not capture private-site routes
- SD-WAN views tie member selection to quality data rather than only link-up state
Explanation
Correct Answer
B:Steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates. It directly explains the need to add both WAN interfaces as SD-WAN members in an appropriate zone before defining the steering rule. The narrow validation is: Both circuits appear as selectable members and a test flow follows the matching steering rule.
Incorrect Answers
A:A specific steering rule explains the egress decision more reliably than assuming interface order alone. That is a useful action for a different circumstance: a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session. The present case is constrained by a new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering; the targeted response is steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates.
C:SD-WAN forwarding follows both route reachability and matching policy, so public DIA need not capture private-site routes. The outcome for that step belongs to a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay. Here the decisive requirement concerns a new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering, so steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates is the better fit.
D:SD-WAN views tie member selection to quality data rather than only link-up state. It could be appropriate when a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. However, that does not resolve the stated condition: a new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering. A more direct answer is steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates.
Question 693
Given this incident — Security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. — the administrator plans to inspect application-control or inline-CASB security logs and the matched action. Which technical principle justifies it?
- Inline SaaS inspection can produce activity-level events distinct from domain-category blocks
- Web-filter events concern destination categorization, while IPS events concern detected intrusion patterns
- Attribution requires security-event context rather than relying on tenant-wide totals
- Failed logins are identity events and need separate interpretation from content-inspection threats
Explanation
Correct Answer
A:Inline SaaS inspection can produce activity-level events distinct from domain-category blocks. This is why the proposed repair addresses the reported behavior; confirm by checking: The log identifies the disallowed in-app action while permitted app sessions remain visible.
Incorrect Answers
B:Web-filter events concern destination categorization, while IPS events concern detected intrusion patterns. That is a useful action for a different circumstance: users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event. The present case is constrained by security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny; the targeted response is inline SaaS inspection can produce activity-level events distinct from domain-category blocks.
C:Attribution requires security-event context rather than relying on tenant-wide totals. 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 security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. The relevant choice is inline SaaS inspection can produce activity-level events distinct from domain-category blocks.
D:Failed logins are identity events and need separate interpretation from content-inspection threats. 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 security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny, so inline SaaS inspection can produce activity-level events distinct from domain-category blocks is the better fit.
Question 694
Given this incident — 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 administrator plans to correlate SLA health-check events with member selection and session logs around the incident time. Which technical principle justifies it?
- The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA
- Measured SLA state affects a rule only when that rule's selection logic actually uses it
- SLA loss checks can disqualify a degraded path even when the physical carrier remains established
- SLA-driven steering can respond to packet loss, delay or probe failure without physical link-down events
Explanation
Correct Answer
D:SLA-driven steering can respond to packet loss, delay or probe failure without physical link-down events. It directly explains the need to correlate SLA health-check events with member selection and session logs around the incident time. The narrow validation is: The logged SLA failure aligns with the observed traffic path change.
Incorrect Answers
A:The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA. That is a useful action for a different circumstance: the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. The present case is constrained by 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 targeted response is sLA-driven steering can respond to packet loss, delay or probe failure without physical link-down events.
B:Measured SLA state affects a rule only when that rule's selection logic actually uses it. 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 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 sLA-driven steering can respond to packet loss, delay or probe failure without physical link-down events.
C:SLA loss checks can disqualify a degraded path even when the physical carrier remains established. It addresses a remote kiosk experiences intermittent missing packets despite its interface staying up. 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 sLA-driven steering can respond to packet loss, delay or probe failure without physical link-down events.
Question 695
The team is troubleshooting the following Fortinet 7.6 deployment: A NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. Which specific corrective action should be prioritized?
- Install or correct the private route to resolve through the proper overlay zone and enforce its firewall policy
- Keep the more-specific private route toward the tunnel while using default Internet reachability for public traffic
- Inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics
- Check SNAT and session behavior when rerouting across WAN members, not only link quality
Explanation
Correct Answer
D:Check SNAT and session behavior when rerouting across WAN members, not only link quality. A change of egress public IP can affect remote-session continuity even when a new path is reachable. The acceptance check should show: Fresh connections successfully establish through the chosen ISP's correct translated source.
Incorrect Answers
A:Install or correct the private route to resolve through the proper overlay zone and enforce its firewall policy. That is a useful action for a different circumstance: following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub. The present case is constrained by a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address; the targeted response is check SNAT and session behavior when rerouting across WAN members, not only link quality.
B:Keep the more-specific private route toward the tunnel while using default Internet reachability for public traffic. It could be appropriate when a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination. However, that does not resolve the stated condition: a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. A more direct answer is check SNAT and session behavior when rerouting across WAN members, not only link quality.
C:Inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics. It addresses an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone. In the reported environment, the missing behavior instead relates to a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. The relevant choice is check SNAT and session behavior when rerouting across WAN members, not only link quality.
Question 696
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? 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.
- An interface being electrically up does not disprove a past end-to-end health failure
- An overly broad default route must not hide the more-specific private overlay route
- A static route pointing to a zone does not automatically populate that zone with members
- Changing an SLA target cannot compensate for a policy that still denies or misses the traffic
Explanation
Correct Answer
A:An interface being electrically up does not disprove a past end-to-end health failure. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:An overly broad default route must not hide the more-specific private overlay route. That is a useful action for a different circumstance: a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay. The present case is constrained by 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 targeted response is an interface being electrically up does not disprove a past end-to-end health failure.
C:A static route pointing to a zone does not automatically populate that zone with members. The outcome for that step belongs to a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. 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 an interface being electrically up does not disprove a past end-to-end health failure is the better fit.
D:Changing an SLA target cannot compensate for a policy that still denies or misses the traffic. It addresses 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. 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 an interface being electrically up does not disprove a past end-to-end health failure.
Question 697
The team plans to inspect the IPS detection event and its signature/action details before modifying access policy for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A remote client receives an intrusion-prevention alert while accessing an internal application through SASE.
- Manually exporting a dashboard once does not meet a recurring reporting requirement
- A rule configuration screenshot alone is weaker than observed matched-session behavior
- Changing SD-WAN member priority does not explain an application-layer intrusion signature
- Assuming a single filtered-screen export includes all tenant history can omit relevant evidence
Explanation
Correct Answer
C:Changing SD-WAN member priority does not explain an application-layer intrusion signature. 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. It could be appropriate when the compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it. However, that does not resolve the stated condition: a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. A more direct answer is changing SD-WAN member priority does not explain an application-layer intrusion signature.
B:A rule configuration screenshot alone is weaker than observed matched-session behavior. The outcome for that step belongs to an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. Here the decisive requirement concerns a remote client receives an intrusion-prevention alert while accessing an internal application through SASE, so changing SD-WAN member priority does not explain an application-layer intrusion signature is the better fit.
D:Assuming a single filtered-screen export includes all tenant history can omit relevant evidence. It addresses an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export. In the reported environment, the missing behavior instead relates to a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. The relevant choice is changing SD-WAN member priority does not explain an application-layer intrusion signature.
Question 698
A proposed repair is to define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions. Why should that repair work in this particular situation? Context: An administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch.
- The firewall policy is a separate permission decision from member selection; a valid SD-WAN path does not itself allow sessions
- Physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss
- SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes
- Member preference combined with failure detection limits routine use of a metered backup path
Explanation
Correct Answer
C:SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes. This is why the proposed repair addresses the reported behavior; confirm by checking: A simulated congested WAN changes eligible conferencing path selection while bulk traffic follows its own rule.
Incorrect Answers
A:The firewall policy is a separate permission decision from member selection; a valid SD-WAN path does not itself allow sessions. It addresses 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. In the reported environment, the missing behavior instead relates to an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. The relevant choice is sD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes.
B:Physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss. The outcome for that step belongs to a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit. Here the decisive requirement concerns an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch, so sD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes is the better fit.
D:Member preference combined with failure detection limits routine use of a metered backup path. It could be appropriate when a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. However, that does not resolve the stated condition: an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. A more direct answer is sD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes.
Question 699
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions.
- The intended HTTPS site is inspected without trust warnings, and appropriate security events appear
- Approved collaboration functions succeed while the selected risky transfer operation is blocked
- Relevant test HTTPS downloads receive the intended malware or DLP inspection
- A representative synthetic-sensitive-data upload is restricted and logged by DLP
Explanation
Correct Answer
A:The intended HTTPS site is inspected without trust warnings, and appropriate security events appear. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B: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 browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions, so the intended HTTPS site is inspected without trust warnings, and appropriate security events appear is the better fit.
C: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 browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions; the targeted response is the intended HTTPS site is inspected without trust warnings, and appropriate security events appear.
D:A representative synthetic-sensitive-data upload is restricted and logged by DLP. 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 browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions. The relevant choice is the intended HTTPS site is inspected without trust warnings, and appropriate security events appear.
Question 700
After the authorized change to create an overlay-only SD-WAN zone and place the two VPN tunnel interfaces within it, which result actually demonstrates that this site's requirement is met? Initial issue: Two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout.
- A single zone policy covers sessions egressing via any eligible member assigned to that zone
- Private application traffic matches the intended overlay policy after the zone correction
- Private traffic may steer between overlays while the Internet firewall policy still targets underlays
- Sessions over either provider hit the single intended allow policy and retain appropriate inspection
Explanation
Correct Answer
C:Private traffic may steer between overlays while the Internet firewall policy still targets underlays. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:A single zone policy covers sessions egressing via any eligible member assigned to that zone. The outcome for that step belongs to a FortiGate using zone-based policies shows the original interface port but the administrator cannot select it as a distinct policy destination. Here the decisive requirement concerns two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout, so private traffic may steer between overlays while the Internet firewall policy still targets underlays is the better fit.
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: two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. A more direct answer is private traffic may steer between overlays while the Internet firewall policy still targets underlays.
D:Sessions over either provider hit the single intended allow policy and retain appropriate inspection. It addresses a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. In the reported environment, the missing behavior instead relates to two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. The relevant choice is private traffic may steer between overlays while the Internet firewall policy still targets underlays.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests