Practice Exams:

Fortinet NSE4_FGT_AD-7.6 Dumps

EXAM: Fortinet NSE 4 - FortiOS 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

NSE4_FGT_AD-7.6 Premium ETE File


  • Premium File 94 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet NSE4_FGT_AD-7.6 Practice Test 55

Question 540

At a managed branch perimeter, a FortiGate running FortiOS 7.6 has this observation: An intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent. The operator corrected the configuration by choosing to configure a properly scoped blackhole route to prevent fallback for that protected destination. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Test probe delivery and confirm the SLA health state changes as expected.
  2. Check the route table and selected SD-WAN member for a routed session.
  3. Compare health status, service match, and selected member for an affected flow.
  4. Withdraw the intended tunnel route and verify the protected prefix is not sent to the internet.
  5. Require peer review for blackhole route protection changes and an acceptance check that will withdraw the intended tunnel route and verify the protected prefix is not sent to the internet before relevant releases.

Explanation

Correct Answers

D:

It measures the operational result after the correction to configure a properly scoped blackhole route to prevent fallback for that protected destination, and it directly checks the reported condition: an intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent. For blackhole route protection, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

E:

The organization already encountered the failure where an intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

A:

The proposed evidence, to test probe delivery and confirm the SLA health state changes as expected, checks sd-wan health-check reachability in a situation such as a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable, not the required blackhole route protection acceptance. For the affected firewall behavior the directly discriminating check is to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet, alongside a review of blackhole route protection rather than sd-wan health-check reachability settings.

B:

The proposed evidence, to check the route table and selected SD-WAN member for a routed session, checks sd-wan static-route prerequisite in a situation such as an SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path, not the required blackhole route protection acceptance. For the affected firewall behavior the directly discriminating check is to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet, alongside a review of blackhole route protection rather than sd-wan static-route prerequisite settings.

C:

The proposed evidence, to compare health status, service match, and selected member for an affected flow, checks sd-wan path diagnostics in a situation such as two provider paths seem healthy but one set of applications consistently uses an unexpected member, not the required blackhole route protection acceptance. For the affected firewall behavior the directly discriminating check is to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet, alongside a review of blackhole route protection rather than sd-wan path diagnostics settings.

Question 541

A FortiOS 7.6 review of a datacenter security boundary reports the following condition: Packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant. The requirement concerns reverse-path source validation while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link.
  2. Review reverse-path checking mode and the return-route topology before considering a justified adjustment.
  3. Use the Lowest Cost (SLA) rule with appropriate member costs and the required SLA target.
  4. Inspect the routing table and apply the longest-prefix-match decision before changing the default route.

Explanation

Correct Answer

B:

Choosing to review reverse-path checking mode and the return-route topology before considering a justified adjustment changes the component implicated by that observation, rather than masking the symptom through a different firewall feature. Operators can substantiate the choice by carrying out this test: inspect packet drop diagnostics and reverse path for a controlled asymmetric source.

Incorrect Answers

A:

Setting performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link would focus the new configuration on performance sla packet loss, for which voice calls degrade on a high-loss WAN link while another member meets the application SLA may be a valid concern, but this reverse-path source validation configuration has a different failure. Evidence for reverse-path source validation requires staff to inspect packet drop diagnostics and reverse path for a controlled asymmetric source; the proposed performance sla packet loss change cannot deliver that reverse-path source validation result by itself.

C:

Using the Lowest Cost (SLA) rule with appropriate member costs and the required SLA target would focus the new configuration on lowest-cost eligible link, for which two WAN links meet the same SLA but the business wants the lower-cost eligible member used first may be a valid concern, but this reverse-path source validation configuration has a different failure. Evidence for reverse-path source validation requires staff to inspect packet drop diagnostics and reverse path for a controlled asymmetric source; the proposed lowest-cost eligible link change cannot deliver that reverse-path source validation result by itself.

D:

Inspecting the routing table and apply the longest-prefix-match decision before changing the default route would focus the new configuration on longest-prefix route choice, for which an administrator expects a default route to carry traffic even though a specific connected or static route matches the same destination more closely may be a valid concern, but this reverse-path source validation configuration has a different failure. Evidence for reverse-path source validation requires staff to inspect packet drop diagnostics and reverse path for a controlled asymmetric source; the proposed longest-prefix route choice change cannot deliver that reverse-path source validation result by itself.

Question 542

During FortiOS 7.6 operations at an enterprise gateway change window, the evidence is: Packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this reverse-path source validation failure?

  1. Choose the lowest nominal interface cost without considering packet-loss SLA failure.
  2. Assume the default route always wins over a more specific matching route.
  3. Always choose a cheaper link even when it fails the application's performance SLA.
  4. Disable source validation globally as the first response without confirming the route asymmetry.

Explanation

Correct Answer

D:

The problem arises when administrators disable source validation globally as the first response without confirming the route asymmetry, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to review reverse-path checking mode and the return-route topology before considering a justified adjustment.

Incorrect Answers

A:

The alternative cause involving performance sla packet loss can produce a different failure, for example when voice calls degrade on a high-loss WAN link while another member meets the application SLA; it is not the reverse-path source validation case. The more specific error here is the choice to disable source validation globally as the first response without confirming the route asymmetry; check it by attempting to inspect packet drop diagnostics and reverse path for a controlled asymmetric source before making an unrelated performance sla packet loss change.

B:

The alternative cause involving longest-prefix route choice can produce a different failure, for example when an administrator expects a default route to carry traffic even though a specific connected or static route matches the same destination more closely; it is not the reverse-path source validation case. The more specific error here is the choice to disable source validation globally as the first response without confirming the route asymmetry; check it by attempting to inspect packet drop diagnostics and reverse path for a controlled asymmetric source before making an unrelated longest-prefix route choice change.

C:

The alternative cause involving lowest-cost eligible link can produce a different failure, for example when two WAN links meet the same SLA but the business wants the lower-cost eligible member used first; it is not the reverse-path source validation case. The more specific error here is the choice to disable source validation globally as the first response without confirming the route asymmetry; check it by attempting to inspect packet drop diagnostics and reverse path for a controlled asymmetric source before making an unrelated lowest-cost eligible link change.

Question 543

At a redundant regional firewall pair, a FortiGate running FortiOS 7.6 has this observation: Packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant. Investigators confirmed this cause: administrators chose to disable source validation globally as the first response without confirming the route asymmetry. Which action MOST directly corrects the confirmed error?

  1. Inspect the routing table and apply the longest-prefix-match decision before changing the default route.
  2. Use the Lowest Cost (SLA) rule with appropriate member costs and the required SLA target.
  3. Disable source validation globally as the first response without confirming the route asymmetry.
  4. Review reverse-path checking mode and the return-route topology before considering a justified adjustment.

Explanation

Correct Answer

D:

This addresses reverse-path source validation without needlessly weakening separate security or routing controls. Given the observed condition—packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant—the operator should then inspect packet drop diagnostics and reverse path for a controlled asymmetric source.

Incorrect Answers

A:

Changing the mechanism to inspect the routing table and apply the longest-prefix-match decision before changing the default route could be a sensible correction for longest-prefix route choice when an administrator expects a default route to carry traffic even though a specific connected or static route matches the same destination more closely. The targeted fix is to review reverse-path checking mode and the return-route topology before considering a justified adjustment; a review of longest-prefix route choice would not, by itself, prove that the team can inspect packet drop diagnostics and reverse path for a controlled asymmetric source.

B:

Changing the mechanism to use the Lowest Cost (SLA) rule with appropriate member costs and the required SLA target could be a sensible correction for lowest-cost eligible link when two WAN links meet the same SLA but the business wants the lower-cost eligible member used first. The targeted fix is to review reverse-path checking mode and the return-route topology before considering a justified adjustment; a review of lowest-cost eligible link would not, by itself, prove that the team can inspect packet drop diagnostics and reverse path for a controlled asymmetric source.

C:

The proposal repeats the confirmed reverse-path source validation error by choosing to disable source validation globally as the first response without confirming the route asymmetry. A corrective change must instead review reverse-path checking mode and the return-route topology before considering a justified adjustment and then produce the measurable result to inspect packet drop diagnostics and reverse path for a controlled asymmetric source; repeating the failed setting cannot serve as a repair.

Question 544

A FortiOS 7.6 review of a remote-office migration reports the following condition: Packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant. The incident has been fixed, and the owner wants to prevent a recurrence of the reverse-path source validation problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for lowest-cost eligible link changes and an acceptance check that will compare member costs and SLA states and verify the selected member under both pass and fail cases before relevant releases.
  2. Require peer review for longest-prefix route choice changes and an acceptance check that will trace a destination in the specific prefix and verify the selected outgoing next hop before relevant releases.
  3. Require peer review for reverse-path source validation changes and an acceptance check that will inspect packet drop diagnostics and reverse path for a controlled asymmetric source before relevant releases.
  4. Require peer review for performance sla packet loss changes and an acceptance check that will measure link health under controlled loss and verify the voice rule selects an eligible member before relevant releases.

Explanation

Correct Answer

C:

This change-control gate requires teams to require peer review for reverse-path source validation changes and an acceptance check that will inspect packet drop diagnostics and reverse path for a controlled asymmetric source before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to inspect packet drop diagnostics and reverse path for a controlled asymmetric source.

Incorrect Answers

A:

A review gate for lowest-cost eligible link, such as require peer review for lowest-cost eligible link changes and an acceptance check that will compare member costs and SLA states and verify the selected member under both pass and fail cases before relevant releases, can be useful where two WAN links meet the same SLA but the business wants the lower-cost eligible member used first, but it is not the approved reverse-path source validation review. The preventive test must enforce that staff will review reverse-path checking mode and the return-route topology before considering a justified adjustment and subsequently can inspect packet drop diagnostics and reverse path for a controlled asymmetric source; the proposed lowest-cost eligible link gate would not check that same control.

B:

A review gate for longest-prefix route choice, such as require peer review for longest-prefix route choice changes and an acceptance check that will trace a destination in the specific prefix and verify the selected outgoing next hop before relevant releases, can be useful where an administrator expects a default route to carry traffic even though a specific connected or static route matches the same destination more closely, but it is not the approved reverse-path source validation review. The preventive test must enforce that staff will review reverse-path checking mode and the return-route topology before considering a justified adjustment and subsequently can inspect packet drop diagnostics and reverse path for a controlled asymmetric source; the proposed longest-prefix route choice gate would not check that same control.

D:

A review gate for performance sla packet loss, such as require peer review for performance sla packet loss changes and an acceptance check that will measure link health under controlled loss and verify the voice rule selects an eligible member before relevant releases, can be useful where voice calls degrade on a high-loss WAN link while another member meets the application SLA, but it is not the approved reverse-path source validation review. The preventive test must enforce that staff will review reverse-path checking mode and the return-route topology before considering a justified adjustment and subsequently can inspect packet drop diagnostics and reverse path for a controlled asymmetric source; the proposed performance sla packet loss gate would not check that same control.

Question 545

During FortiOS 7.6 operations at a monitored business uplink, the evidence is: Packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant. The operator corrected the configuration by choosing to review reverse-path checking mode and the return-route topology before considering a justified adjustment. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Compare member costs and SLA states and verify the selected member under both pass and fail cases.
  2. Trace a destination in the specific prefix and verify the selected outgoing next hop.
  3. Inspect packet drop diagnostics and reverse path for a controlled asymmetric source.
  4. Require peer review for reverse-path source validation changes and an acceptance check that will inspect packet drop diagnostics and reverse path for a controlled asymmetric source before relevant releases.
  5. Measure link health under controlled loss and verify the voice rule selects an eligible member.

Explanation

Correct Answers

C:

It measures the operational result after the correction to review reverse-path checking mode and the return-route topology before considering a justified adjustment, and it directly checks the reported condition: packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant. For reverse-path source validation, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

D:

The organization already encountered the failure where packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to inspect packet drop diagnostics and reverse path for a controlled asymmetric source, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

A:

The proposed evidence, to compare member costs and SLA states and verify the selected member under both pass and fail cases, checks lowest-cost eligible link in a situation such as two WAN links meet the same SLA but the business wants the lower-cost eligible member used first, not the required reverse-path source validation acceptance. For the affected firewall behavior the directly discriminating check is to inspect packet drop diagnostics and reverse path for a controlled asymmetric source, alongside a review of reverse-path source validation rather than lowest-cost eligible link settings.

B:

The proposed evidence, to trace a destination in the specific prefix and verify the selected outgoing next hop, checks longest-prefix route choice in a situation such as an administrator expects a default route to carry traffic even though a specific connected or static route matches the same destination more closely, not the required reverse-path source validation acceptance. For the affected firewall behavior the directly discriminating check is to inspect packet drop diagnostics and reverse path for a controlled asymmetric source, alongside a review of reverse-path source validation rather than longest-prefix route choice settings.

E:

The proposed evidence, to measure link health under controlled loss and verify the voice rule selects an eligible member, checks performance sla packet loss in a situation such as voice calls degrade on a high-loss WAN link while another member meets the application SLA, not the required reverse-path source validation acceptance. For the affected firewall behavior the directly discriminating check is to inspect packet drop diagnostics and reverse path for a controlled asymmetric source, alongside a review of reverse-path source validation rather than performance sla packet loss settings.

Question 546

At an internal application segment, a FortiGate running FortiOS 7.6 has this observation: A policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally. The requirement concerns equal-cost multipath forwarding while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Validate health-check target reachability, source path, and member monitoring before reintroducing the member.
  2. Configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior.
  3. Assign administrative distances to express the intended primary and backup route preference.
  4. Choose a supported best-quality strategy with the appropriate jitter quality metric and health checks.

Explanation

Correct Answer

B:

Choosing to configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior changes the component implicated by that observation, rather than masking the symptom through a different firewall feature. Operators can substantiate the choice by carrying out this test: inspect installed routes and sample flow egress distribution under controlled conditions.

Incorrect Answers

A:

Selecting validate health-check target reachability, source path, and member monitoring before reintroducing the member would focus the new configuration on sd-wan health-check reachability, for which a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable may be a valid concern, but this equal-cost multipath forwarding configuration has a different failure. Evidence for equal-cost multipath forwarding requires staff to inspect installed routes and sample flow egress distribution under controlled conditions; the proposed sd-wan health-check reachability change cannot deliver that equal-cost multipath forwarding result by itself.

C:

Selecting assign administrative distances to express the intended primary and backup route preference would focus the new configuration on static route administrative distance, for which two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances may be a valid concern, but this equal-cost multipath forwarding configuration has a different failure. Evidence for equal-cost multipath forwarding requires staff to inspect installed routes and sample flow egress distribution under controlled conditions; the proposed static route administrative distance change cannot deliver that equal-cost multipath forwarding result by itself.

D:

Selecting choose a supported best-quality strategy with the appropriate jitter quality metric and health checks would focus the new configuration on best-quality sd-wan steering, for which a video service needs the link with the best observed jitter rather than the least expensive eligible link may be a valid concern, but this equal-cost multipath forwarding configuration has a different failure. Evidence for equal-cost multipath forwarding requires staff to inspect installed routes and sample flow egress distribution under controlled conditions; the proposed best-quality sd-wan steering change cannot deliver that equal-cost multipath forwarding result by itself.

Question 547

A FortiOS 7.6 review of a hybrid-network deployment reports the following condition: A policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this equal-cost multipath forwarding failure?

  1. Treat equal destination masks as sufficient proof of which route should win without reviewing distance.
  2. Assume routes with different preference metrics automatically participate in equal-cost load sharing.
  3. Treat interface carrier as proof that all health-check destinations are reachable.
  4. Use administrative distance alone as a live per-session jitter quality metric.

Explanation

Correct Answer

B:

The problem arises when administrators assume routes with different preference metrics automatically participate in equal-cost load sharing, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior.

Incorrect Answers

A:

The alternative cause involving static route administrative distance can produce a different failure, for example when two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances; it is not the equal-cost multipath forwarding case. The more specific error here is the choice to assume routes with different preference metrics automatically participate in equal-cost load sharing; check it by attempting to inspect installed routes and sample flow egress distribution under controlled conditions before making an unrelated static route administrative distance change.

C:

The alternative cause involving sd-wan health-check reachability can produce a different failure, for example when a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable; it is not the equal-cost multipath forwarding case. The more specific error here is the choice to assume routes with different preference metrics automatically participate in equal-cost load sharing; check it by attempting to inspect installed routes and sample flow egress distribution under controlled conditions before making an unrelated sd-wan health-check reachability change.

D:

The alternative cause involving best-quality sd-wan steering can produce a different failure, for example when a video service needs the link with the best observed jitter rather than the least expensive eligible link; it is not the equal-cost multipath forwarding case. The more specific error here is the choice to assume routes with different preference metrics automatically participate in equal-cost load sharing; check it by attempting to inspect installed routes and sample flow egress distribution under controlled conditions before making an unrelated best-quality sd-wan steering change.

Question 548

During FortiOS 7.6 operations at an operations incident response, the evidence is: A policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally. Investigators confirmed this cause: administrators chose to assume routes with different preference metrics automatically participate in equal-cost load sharing. Which action MOST directly corrects the confirmed error?

  1. Choose a supported best-quality strategy with the appropriate jitter quality metric and health checks.
  2. Assume routes with different preference metrics automatically participate in equal-cost load sharing.
  3. Configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior.
  4. Assign administrative distances to express the intended primary and backup route preference.

Explanation

Correct Answer

C:

This addresses equal-cost multipath forwarding without needlessly weakening separate security or routing controls. Given the observed condition—a policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally—the operator should then inspect installed routes and sample flow egress distribution under controlled conditions.

Incorrect Answers

A:

Changing the mechanism to choose a supported best-quality strategy with the appropriate jitter quality metric and health checks could be a sensible correction for best-quality sd-wan steering when a video service needs the link with the best observed jitter rather than the least expensive eligible link. The targeted fix is to configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior; a review of best-quality sd-wan steering would not, by itself, prove that the team can inspect installed routes and sample flow egress distribution under controlled conditions.

B:

The proposal repeats the confirmed equal-cost multipath forwarding error by choosing to assume routes with different preference metrics automatically participate in equal-cost load sharing. A corrective change must instead configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior and then produce the measurable result to inspect installed routes and sample flow egress distribution under controlled conditions; repeating the failed setting cannot serve as a repair.

D:

Changing the mechanism to assign administrative distances to express the intended primary and backup route preference could be a sensible correction for static route administrative distance when two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances. The targeted fix is to configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior; a review of static route administrative distance would not, by itself, prove that the team can inspect installed routes and sample flow egress distribution under controlled conditions.

Question 549

At a network segmentation review, a FortiGate running FortiOS 7.6 has this observation: A policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally. The incident has been fixed, and the owner wants to prevent a recurrence of the equal-cost multipath forwarding problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for best-quality sd-wan steering changes and an acceptance check that will introduce controlled jitter variation and verify the session steering choice follows the selected metric before relevant releases.
  2. Require peer review for equal-cost multipath forwarding changes and an acceptance check that will inspect installed routes and sample flow egress distribution under controlled conditions before relevant releases.
  3. Require peer review for sd-wan health-check reachability changes and an acceptance check that will test probe delivery and confirm the SLA health state changes as expected before relevant releases.
  4. Require peer review for static route administrative distance changes and an acceptance check that will inspect the installed route and fail the preferred path to confirm backup selection before relevant releases.

Explanation

Correct Answer

B:

This change-control gate requires teams to require peer review for equal-cost multipath forwarding changes and an acceptance check that will inspect installed routes and sample flow egress distribution under controlled conditions before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to inspect installed routes and sample flow egress distribution under controlled conditions.

Incorrect Answers

A:

A review gate for best-quality sd-wan steering, such as require peer review for best-quality sd-wan steering changes and an acceptance check that will introduce controlled jitter variation and verify the session steering choice follows the selected metric before relevant releases, can be useful where a video service needs the link with the best observed jitter rather than the least expensive eligible link, but it is not the approved equal-cost multipath forwarding review. The preventive test must enforce that staff will configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior and subsequently can inspect installed routes and sample flow egress distribution under controlled conditions; the proposed best-quality sd-wan steering gate would not check that same control.

C:

A review gate for sd-wan health-check reachability, such as require peer review for sd-wan health-check reachability changes and an acceptance check that will test probe delivery and confirm the SLA health state changes as expected before relevant releases, can be useful where a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable, but it is not the approved equal-cost multipath forwarding review. The preventive test must enforce that staff will configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior and subsequently can inspect installed routes and sample flow egress distribution under controlled conditions; the proposed sd-wan health-check reachability gate would not check that same control.

D:

A review gate for static route administrative distance, such as require peer review for static route administrative distance changes and an acceptance check that will inspect the installed route and fail the preferred path to confirm backup selection before relevant releases, can be useful where two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances, but it is not the approved equal-cost multipath forwarding review. The preventive test must enforce that staff will configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior and subsequently can inspect installed routes and sample flow egress distribution under controlled conditions; the proposed static route administrative distance gate would not check that same control.

Question 550

A FortiOS 7.6 review of a managed branch perimeter reports the following condition: A policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally. The operator corrected the configuration by choosing to configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Inspect installed routes and sample flow egress distribution under controlled conditions.
  2. Test probe delivery and confirm the SLA health state changes as expected.
  3. Introduce controlled jitter variation and verify the session steering choice follows the selected metric.
  4. Inspect the installed route and fail the preferred path to confirm backup selection.
  5. Require peer review for equal-cost multipath forwarding changes and an acceptance check that will inspect installed routes and sample flow egress distribution under controlled conditions before relevant releases.

Explanation

Correct Answers

A:

It measures the operational result after the correction to configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior, and it directly checks the reported condition: a policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally. For equal-cost multipath forwarding, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

E:

The organization already encountered the failure where a policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to inspect installed routes and sample flow egress distribution under controlled conditions, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

B:

The proposed evidence, to test probe delivery and confirm the SLA health state changes as expected, checks sd-wan health-check reachability in a situation such as a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable, not the required equal-cost multipath forwarding acceptance. For the affected firewall behavior the directly discriminating check is to inspect installed routes and sample flow egress distribution under controlled conditions, alongside a review of equal-cost multipath forwarding rather than sd-wan health-check reachability settings.

C:

The proposed evidence, to introduce controlled jitter variation and verify the session steering choice follows the selected metric, checks best-quality sd-wan steering in a situation such as a video service needs the link with the best observed jitter rather than the least expensive eligible link, not the required equal-cost multipath forwarding acceptance. For the affected firewall behavior the directly discriminating check is to inspect installed routes and sample flow egress distribution under controlled conditions, alongside a review of equal-cost multipath forwarding rather than best-quality sd-wan steering settings.

D:

The proposed evidence, to inspect the installed route and fail the preferred path to confirm backup selection, checks static route administrative distance in a situation such as two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances, not the required equal-cost multipath forwarding acceptance. For the affected firewall behavior the directly discriminating check is to inspect installed routes and sample flow egress distribution under controlled conditions, alongside a review of equal-cost multipath forwarding rather than static route administrative distance settings.

Fortinet NSE 4 - FortiOS 7.6 Administrator (NSE4_FGT_AD-7.6) Practice Tests