Fortinet NSE5_SSE_AD-7.6 Practice Test 14
Question 130
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A live trading desk reports frequent path switches during transient congestion although the backup never sustains a meaningful quality advantage. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Instead configure: Separate members into correctly scoped SD-WAN zones and update referencing routes and rules for each approved traffic class.
- Correct the fault by: Tune supported health-check recovery and failure detection or hold-down settings according to measured application needs.
- Use the shortcut: Eliminate health probes entirely so quality degradation cannot trigger steering.
- Instead collect: Test ARP or neighbor resolution, interface-address details, and routed reachability to the specified WAN gateway.
- Test the diagnosis with: Correlate per-member SLA transition timestamps with the user-visible session switch events.
Explanation
Correct Answer
B:Probes and state-change timing can cause unnecessary member flapping if transitions react to momentary threshold crossings. The expected result is: Path changes happen for sustained quality events rather than every transient probe deviation.
E:Probes and state-change timing can cause unnecessary member flapping if transitions react to momentary threshold crossings. This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
Incorrect Answers
A:This concerns a different operational control (Dedicated transport segmentation) and can be sensible in its own incident, but the reported link-flap hysteresis problem requires a more direct response. Instead configure: Separate members into correctly scoped SD-WAN zones and update referencing routes and rules for each approved traffic class.
C:That option would use the shortcut: Eliminate health probes entirely so quality degradation cannot trigger steering, but it addresses a different concern. Probes and state-change timing can cause unnecessary member flapping if transitions react to momentary threshold crossings.
D:This concerns a different operational control (Underlay reachability) and can be sensible in its own incident, but the reported link-flap hysteresis problem requires a more direct response.
Question 131
A team configured a working loss SLA but a business-critical SD-WAN rule never references that SLA and continues choosing the cheapest unhealthy circuit. An initial suggestion was to assume creating an SLA object automatically rewrites every existing SD-WAN rule. Which implementation or configuration decision most directly corrects the stated problem? Select ONE best answer.
- Add the eligible wan2 interface as an SD-WAN member with its correct gateway and transport settings.
- Correct the WAN next-hop, addressing and reachability for that specific member before treating it as usable.
- Assume creating an SLA object automatically rewrites every existing SD-WAN rule.
- Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached.
Explanation
Correct Answer
D:A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
Incorrect Answers
A:A physically working WAN interface does not participate in SD-WAN member selection until it is configured as a member. That addresses an alternative control; the reported Fortinet requirement instead calls for: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached.
B:An SD-WAN member needs functional Layer 3 underlay connectivity; administrative membership does not repair an incorrect upstream gateway. That addresses an alternative control; the reported Fortinet requirement instead calls for: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached.
C:That option would assume creating an SLA object automatically rewrites every existing SD-WAN rule, but it addresses a different concern. A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision. The direct remedial step is: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached.
Question 132
Consider this FortiSASE/SD-WAN 7.6 operational report: A team configured a working loss SLA but a business-critical SD-WAN rule never references that SLA and continues choosing the cheapest unhealthy circuit. The engineering proposal is: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached. Which technical principle best explains the expected behavior and why the direct correction is necessary? Select ONE best answer.
- Eligible member selection is constrained by configured zone references; grouping is part of the forwarding design rather than display-only metadata.
- A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
- A reachable next hop on the actual transport is prerequisite to valid SLA probes and forwarding.
- Transport segmentation depends on actual member-zone and policy references, not on friendly interface names.
Explanation
Correct Answer
B:A satisfactory result would be: The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
Incorrect Answers
A:Applied to the observed case: A finance branch's internet zone contains only the expensive primary link, though the low-cost backup circuit was intended to be available during outages. That addresses an alternative control; the reported Fortinet requirement instead calls for: A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
C:Applied to the observed case: A branch backup uplink uses DHCP, but its configured SD-WAN member retains a stale manually entered next hop after the lease changed. That addresses an alternative control; the reported Fortinet requirement instead calls for: A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
D:The principle explains why the proposed direct fix is necessary: Separate members into correctly scoped SD-WAN zones and update referencing routes and rules for each approved traffic class. That addresses an alternative control; the reported Fortinet requirement instead calls for: A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
Question 133
The on-call engineer is evaluating the following behavior before changing production configuration: A team configured a working loss SLA but a business-critical SD-WAN rule never references that SLA and continues choosing the cheapest unhealthy circuit. What evidence should the engineer gather FIRST to distinguish the suspected fault from unrelated issues? Select ONE best answer.
- Compare live WAN address and lease data with member gateway and packet capture toward that next hop.
- Inspect the matched SD-WAN rule's strategy and SLA references alongside the live candidate-member results.
- Inspect each member's zone assignment alongside the matched firewall policy, route and SD-WAN rule zone references.
- Cross-reference member zone IDs with rule output zones and the intended branch internet policy scope.
Explanation
Correct Answer
B:A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision. This observation directly distinguishes the reported performance-sla rule binding problem from unrelated network or SASE symptoms.
Incorrect Answers
A:This concerns a different operational control (Member gateway mismatch) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
C:Zone membership scopes the members that zone-referencing policies and selection rules can use; link health alone cannot bridge a zone mismatch. That addresses an alternative control; the reported Fortinet requirement instead calls for: Inspect the matched SD-WAN rule's strategy and SLA references alongside the live candidate-member results.
D:This concerns a different operational control (Interface-to-zone scope) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
Question 134
After the authorized response to this incident, the operator must validate the effect: A team configured a working loss SLA but a business-critical SD-WAN rule never references that SLA and continues choosing the cheapest unhealthy circuit. Which result would most directly demonstrate that the change achieved its intended outcome? Select ONE best answer.
- The backup becomes selectable for the intended traffic without placing unrelated links in that policy scope.
- Approved client browsing sessions match the intended allow policy and leave via an eligible SD-WAN member with usable source addressing.
- The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
- The correct next-hop responds and the member can forward controlled traffic through its ISP.
Explanation
Correct Answer
C:The required mechanism is: A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
Incorrect Answers
A:This concerns a different operational control (Member-zone grouping) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
B:The required mechanism is: SD-WAN path selection does not replace the FortiGate firewall decision or outbound source-NAT requirements for client internet sessions. That addresses an alternative control; the reported Fortinet requirement instead calls for: The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
D:This concerns a different operational control (Underlay reachability) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
Question 135
An operations ticket describes this condition: A team configured a working loss SLA but a business-critical SD-WAN rule never references that SLA and continues choosing the cheapest unhealthy circuit. The team needs to address the underlying fault and gather conclusive evidence. Which proposed correction-and-evidence pair offers the most defensible way to close this case? Select ONE best answer.
- Correct: Add the eligible wan2 interface as an SD-WAN member with its correct gateway and transport settings. Verify: Compare the WAN interface state and gateway reachability against the SD-WAN member list and member IDs.
- Correct: Separate members into correctly scoped SD-WAN zones and update referencing routes and rules for each approved traffic class. Verify: Trace a representative protected flow's matched firewall policy, SD-WAN rule, zone and candidate members.
- Correct: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached. Verify: Inspect the matched SD-WAN rule's strategy and SLA references alongside the live candidate-member results.
- Correct: Create or correct the appropriately scoped LAN-to-SD-WAN-zone firewall allow policy and its required NAT settings. Verify: Inspect firewall policy lookup and traffic-log policy ID for a representative LAN client's failed outbound flow.
Explanation
Correct Answer
C:A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision. The change should demonstrate: The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
Incorrect Answers
A:This concerns a different operational control (SD-WAN interface membership) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
B:This concerns a different operational control (Dedicated transport segmentation) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
D:This concerns a different operational control (Direct internet access policy) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
Question 136
A branch has correct latency probes in the dashboard, yet its voice-steering rule still uses a manual member preference without SLA qualification. An initial suggestion was to assume creating an SLA object automatically rewrites every existing SD-WAN rule. What is the most appropriate targeted intervention before expanding the incident scope? Select ONE best answer.
- Assume creating an SLA object automatically rewrites every existing SD-WAN rule.
- Separate members into correctly scoped SD-WAN zones and update referencing routes and rules for each approved traffic class.
- Add the eligible wan2 interface as an SD-WAN member with its correct gateway and transport settings.
- Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached.
Explanation
Correct Answer
D:A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
Incorrect Answers
A:That option would assume creating an SLA object automatically rewrites every existing SD-WAN rule, but it addresses a different concern. A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision. The deciding evidence is: Inspect the matched SD-WAN rule's strategy and SLA references alongside the live candidate-member results.
B:This concerns a different operational control (Dedicated transport segmentation) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
C:This concerns a different operational control (SD-WAN interface membership) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
Question 137
Consider this FortiSASE/SD-WAN 7.6 operational report: A branch has correct latency probes in the dashboard, yet its voice-steering rule still uses a manual member preference without SLA qualification. The engineering proposal is: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached. Which mechanism most directly accounts for the reported failure? Select ONE best answer.
- A physically working WAN interface does not participate in SD-WAN member selection until it is configured as a member.
- A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
- Zone membership scopes the members that zone-referencing policies and selection rules can use; link health alone cannot bridge a zone mismatch.
- Eligible member selection is constrained by configured zone references; grouping is part of the forwarding design rather than display-only metadata.
Explanation
Correct Answer
B:A satisfactory result would be: The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
Incorrect Answers
A:Applied to the observed case: A distributor added a second ISP circuit on port wan2, yet only wan1 appears in the branch SD-WAN member inventory during rollout. That addresses an alternative control; the reported Fortinet requirement instead calls for: A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
C:This concerns a different operational control (Member-zone grouping) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
D:This concerns a different operational control (Interface-to-zone scope) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
Question 138
The on-call engineer is evaluating the following behavior before changing production configuration: A branch has correct latency probes in the dashboard, yet its voice-steering rule still uses a manual member preference without SLA qualification. Which targeted prechange observation would test the working diagnosis most decisively? Select ONE best answer.
- Inspect the matched SD-WAN rule's strategy and SLA references alongside the live candidate-member results.
- Compare the WAN interface state and gateway reachability against the SD-WAN member list and member IDs.
- Compare live WAN address and lease data with member gateway and packet capture toward that next hop.
- Cross-reference member zone IDs with rule output zones and the intended branch internet policy scope.
Explanation
Correct Answer
A:A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision. If confirmed, the targeted intervention is: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached.
Incorrect Answers
B:A physically working WAN interface does not participate in SD-WAN member selection until it is configured as a member. That addresses an alternative control; the reported Fortinet requirement instead calls for: Inspect the matched SD-WAN rule's strategy and SLA references alongside the live candidate-member results.
C:This concerns a different operational control (Member gateway mismatch) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
D:Eligible member selection is constrained by configured zone references; grouping is part of the forwarding design rather than display-only metadata. That addresses an alternative control; the reported Fortinet requirement instead calls for: Inspect the matched SD-WAN rule's strategy and SLA references alongside the live candidate-member results.
Question 139
After the authorized response to this incident, the operator must validate the effect: A branch has correct latency probes in the dashboard, yet its voice-steering rule still uses a manual member preference without SLA qualification. What should be recorded as the strongest postchange acceptance evidence? Select ONE best answer.
- Approved client browsing sessions match the intended allow policy and leave via an eligible SD-WAN member with usable source addressing.
- The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
- The intended set of links becomes selectable for that zone while excluded links remain isolated.
- Protected traffic only considers authorized private-transport members, while ordinary internet traffic uses its approved zone.
Explanation
Correct Answer
B:The required mechanism is: A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision.
Incorrect Answers
A:This concerns a different operational control (Direct internet access policy) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
C:The required mechanism is: Eligible member selection is constrained by configured zone references; grouping is part of the forwarding design rather than display-only metadata. That addresses an alternative control; the reported Fortinet requirement instead calls for: The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
D:The required mechanism is: Transport segmentation depends on actual member-zone and policy references, not on friendly interface names. That addresses an alternative control; the reported Fortinet requirement instead calls for: The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
Question 140
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A branch has correct latency probes in the dashboard, yet its voice-steering rule still uses a manual member preference without SLA qualification. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Instead collect: Test ARP or neighbor resolution, interface-address details, and routed reachability to the specified WAN gateway.
- Test the diagnosis with: Inspect the matched SD-WAN rule's strategy and SLA references alongside the live candidate-member results.
- Use the shortcut: Assume creating an SLA object automatically rewrites every existing SD-WAN rule.
- Instead configure: Add the eligible wan2 interface as an SD-WAN member with its correct gateway and transport settings.
- Correct the fault by: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached.
Explanation
Correct Answer
B:A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision. The expected result is: The named application uses members evaluated against its SLA target instead of ignoring the recorded quality condition.
E:A health-check object by itself does not dictate steering; traffic must match a rule that consumes the relevant SLA decision. This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
Incorrect Answers
A:This concerns a different operational control (Underlay reachability) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response.
C:The direct remedial step is: Bind the appropriate performance SLA to the matching SD-WAN selection strategy and verify the rule is reached.
D:This concerns a different operational control (SD-WAN interface membership) and can be sensible in its own incident, but the reported performance-sla rule binding problem requires a more direct response. Instead configure: Add the eligible wan2 interface as an SD-WAN member with its correct gateway and transport settings.