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 52

Question 510

At a managed branch perimeter, a FortiGate running FortiOS 7.6 has this observation: An administrator expects a default route to carry traffic even though a specific connected or static route matches the same destination more closely. The operator corrected the configuration by choosing to inspect the routing table and apply the longest-prefix-match decision before changing the default route. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. 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.
  2. Trace the destination and confirm ARP or neighbor resolution on the intended egress.
  3. Test probe delivery and confirm the SLA health state changes as expected.
  4. Inspect packet drop diagnostics and reverse path for a controlled asymmetric source.
  5. Trace a destination in the specific prefix and verify the selected outgoing next hop.

Explanation

Correct Answers

A:

The organization already encountered the failure where an administrator expects a default route to carry traffic even though a specific connected or static route matches the same destination more closely, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to trace a destination in the specific prefix and verify the selected outgoing next hop, this gate checks future revisions without claiming that the current configuration is permanently correct.

E:

It measures the operational result after the correction to inspect the routing table and apply the longest-prefix-match decision before changing the default route, and it directly checks the reported condition: an administrator expects a default route to carry traffic even though a specific connected or static route matches the same destination more closely. For longest-prefix route choice, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

B:

The proposed evidence, to trace the destination and confirm ARP or neighbor resolution on the intended egress, checks static route egress interface in a situation such as a new static route points to a WAN interface different from the network that reaches its next-hop gateway, not the required longest-prefix route choice acceptance. For the affected firewall behavior the directly discriminating check is to trace a destination in the specific prefix and verify the selected outgoing next hop, alongside a review of longest-prefix route choice rather than static route egress interface settings.

C:

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 longest-prefix route choice acceptance. For the affected firewall behavior the directly discriminating check is to trace a destination in the specific prefix and verify the selected outgoing next hop, alongside a review of longest-prefix route choice rather than sd-wan health-check reachability settings.

D:

The proposed evidence, to inspect packet drop diagnostics and reverse path for a controlled asymmetric source, checks reverse-path source validation in a situation such as packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant, not the required longest-prefix route choice acceptance. For the affected firewall behavior the directly discriminating check is to trace a destination in the specific prefix and verify the selected outgoing next hop, alongside a review of longest-prefix route choice rather than reverse-path source validation settings.

Question 511

A FortiOS 7.6 review of a datacenter security boundary reports the following condition: Two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances. The requirement concerns static route administrative distance while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior.
  2. Use the Lowest Cost (SLA) rule with appropriate member costs and the required SLA target.
  3. Assign administrative distances to express the intended primary and backup route preference.
  4. Configure a properly scoped blackhole route to prevent fallback for that protected destination.

Explanation

Correct Answer

C:

Choosing to assign administrative distances to express the intended primary and backup route preference 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 the installed route and fail the preferred path to confirm backup selection.

Incorrect Answers

A:

Configuring eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior would focus the new configuration on equal-cost multipath forwarding, for which a policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally may be a valid concern, but this static route administrative distance configuration has a different failure. Evidence for static route administrative distance requires staff to inspect the installed route and fail the preferred path to confirm backup selection; the proposed equal-cost multipath forwarding change cannot deliver that static route administrative distance result by itself.

B:

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 static route administrative distance configuration has a different failure. Evidence for static route administrative distance requires staff to inspect the installed route and fail the preferred path to confirm backup selection; the proposed lowest-cost eligible link change cannot deliver that static route administrative distance result by itself.

D:

Configuring a properly scoped blackhole route to prevent fallback for that protected destination would focus the new configuration on blackhole route protection, for which an intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent may be a valid concern, but this static route administrative distance configuration has a different failure. Evidence for static route administrative distance requires staff to inspect the installed route and fail the preferred path to confirm backup selection; the proposed blackhole route protection change cannot deliver that static route administrative distance result by itself.

Question 512

During FortiOS 7.6 operations at an enterprise gateway change window, the evidence is: Two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this static route administrative distance 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. Always choose a cheaper link even when it fails the application's performance SLA.
  4. Depend on the default internet route to handle sensitive private tunnel destinations.

Explanation

Correct Answer

A:

The problem arises when administrators treat equal destination masks as sufficient proof of which route should win without reviewing distance, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to assign administrative distances to express the intended primary and backup route preference.

Incorrect Answers

B:

The alternative cause involving equal-cost multipath forwarding can produce a different failure, for example when a policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally; it is not the static route administrative distance case. The more specific error here is the choice to treat equal destination masks as sufficient proof of which route should win without reviewing distance; check it by attempting to inspect the installed route and fail the preferred path to confirm backup selection before making an unrelated equal-cost multipath forwarding 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 static route administrative distance case. The more specific error here is the choice to treat equal destination masks as sufficient proof of which route should win without reviewing distance; check it by attempting to inspect the installed route and fail the preferred path to confirm backup selection before making an unrelated lowest-cost eligible link change.

D:

The alternative cause involving blackhole route protection can produce a different failure, for example when an intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent; it is not the static route administrative distance case. The more specific error here is the choice to treat equal destination masks as sufficient proof of which route should win without reviewing distance; check it by attempting to inspect the installed route and fail the preferred path to confirm backup selection before making an unrelated blackhole route protection change.

Question 513

At a redundant regional firewall pair, a FortiGate running FortiOS 7.6 has this observation: Two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances. Investigators confirmed this cause: administrators chose to treat equal destination masks as sufficient proof of which route should win without reviewing distance. Which action MOST directly corrects the confirmed error?

  1. Configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior.
  2. Assign administrative distances to express the intended primary and backup route preference.
  3. Use the Lowest Cost (SLA) rule with appropriate member costs and the required SLA target.
  4. Treat equal destination masks as sufficient proof of which route should win without reviewing distance.

Explanation

Correct Answer

B:

This addresses static route administrative distance without needlessly weakening separate security or routing controls. Given the observed condition—two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances—the operator should then inspect the installed route and fail the preferred path to confirm backup selection.

Incorrect Answers

A:

Changing the mechanism to configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior could be a sensible correction for equal-cost multipath forwarding when a policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally. The targeted fix is to assign administrative distances to express the intended primary and backup route preference; a review of equal-cost multipath forwarding would not, by itself, prove that the team can inspect the installed route and fail the preferred path to confirm backup selection.

C:

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 assign administrative distances to express the intended primary and backup route preference; a review of lowest-cost eligible link would not, by itself, prove that the team can inspect the installed route and fail the preferred path to confirm backup selection.

D:

The proposal repeats the confirmed static route administrative distance error by choosing to treat equal destination masks as sufficient proof of which route should win without reviewing distance. A corrective change must instead assign administrative distances to express the intended primary and backup route preference and then produce the measurable result to inspect the installed route and fail the preferred path to confirm backup selection; repeating the failed setting cannot serve as a repair.

Question 514

A FortiOS 7.6 review of a remote-office migration reports the following condition: Two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances. The incident has been fixed, and the owner wants to prevent a recurrence of the static route administrative distance 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 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 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.
  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

D:

This change-control gate requires teams to 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, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to inspect the installed route and fail the preferred path to confirm backup selection.

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 static route administrative distance review. The preventive test must enforce that staff will assign administrative distances to express the intended primary and backup route preference and subsequently can inspect the installed route and fail the preferred path to confirm backup selection; the proposed lowest-cost eligible link gate would not check that same control.

B:

A review gate for equal-cost multipath forwarding, such as 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, can be useful where a policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally, but it is not the approved static route administrative distance review. The preventive test must enforce that staff will assign administrative distances to express the intended primary and backup route preference and subsequently can inspect the installed route and fail the preferred path to confirm backup selection; the proposed equal-cost multipath forwarding gate would not check that same control.

C:

A review gate for blackhole route protection, such as 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, can be useful where an intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent, but it is not the approved static route administrative distance review. The preventive test must enforce that staff will assign administrative distances to express the intended primary and backup route preference and subsequently can inspect the installed route and fail the preferred path to confirm backup selection; the proposed blackhole route protection gate would not check that same control.

Question 515

During FortiOS 7.6 operations at a monitored business uplink, the evidence is: Two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances. The operator corrected the configuration by choosing to assign administrative distances to express the intended primary and backup route preference. 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. Withdraw the intended tunnel route and verify the protected prefix is not sent to the internet.
  3. Compare member costs and SLA states and verify the selected member under both pass and fail cases.
  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.
  5. Inspect the installed route and fail the preferred path to confirm backup selection.

Explanation

Correct Answers

D:

The organization already encountered the failure where two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to inspect the installed route and fail the preferred path to confirm backup selection, this gate checks future revisions without claiming that the current configuration is permanently correct.

E:

It measures the operational result after the correction to assign administrative distances to express the intended primary and backup route preference, and it directly checks the reported condition: two static routes cover the same prefix and traffic uses the less preferred ISP according to the configured distances. For static route administrative distance, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

A:

The proposed evidence, to inspect installed routes and sample flow egress distribution under controlled conditions, checks equal-cost multipath forwarding in a situation such as a policy intends traffic sharing across equal eligible static next hops, but the installed routes do not qualify equally, not the required static route administrative distance acceptance. For the affected firewall behavior the directly discriminating check is to inspect the installed route and fail the preferred path to confirm backup selection, alongside a review of static route administrative distance rather than equal-cost multipath forwarding settings.

B:

The proposed evidence, to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet, checks blackhole route protection in a situation such as an intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent, not the required static route administrative distance acceptance. For the affected firewall behavior the directly discriminating check is to inspect the installed route and fail the preferred path to confirm backup selection, alongside a review of static route administrative distance rather than blackhole route protection settings.

C:

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 static route administrative distance acceptance. For the affected firewall behavior the directly discriminating check is to inspect the installed route and fail the preferred path to confirm backup selection, alongside a review of static route administrative distance rather than lowest-cost eligible link settings.

Question 516

At an internal application segment, a FortiGate running FortiOS 7.6 has this observation: Multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop. The requirement concerns static route priority tie-break while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Review route monitoring and effective distance so the preferred route can return after recovery.
  2. Review and configure route priority and eligible next hops for the intended tie-breaking behavior.
  3. Choose a supported best-quality strategy with the appropriate jitter quality metric and health checks.
  4. Review reverse-path checking mode and the return-route topology before considering a justified adjustment.

Explanation

Correct Answer

B:

Choosing to review and configure route priority and eligible next hops for the intended tie-breaking 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: check route-table selection after a controlled priority change.

Incorrect Answers

A:

Reviewing route monitoring and effective distance so the preferred route can return after recovery would focus the new configuration on static route failback, for which a recovered primary link is available but traffic stays on a less preferred backup route unexpectedly may be a valid concern, but this static route priority tie-break configuration has a different failure. Evidence for static route priority tie-break requires staff to check route-table selection after a controlled priority change; the proposed static route failback change cannot deliver that static route priority tie-break result by itself.

C:

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 static route priority tie-break configuration has a different failure. Evidence for static route priority tie-break requires staff to check route-table selection after a controlled priority change; the proposed best-quality sd-wan steering change cannot deliver that static route priority tie-break result by itself.

D:

Reviewing reverse-path checking mode and the return-route topology before considering a justified adjustment would focus the new configuration on reverse-path source validation, for which packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant may be a valid concern, but this static route priority tie-break configuration has a different failure. Evidence for static route priority tie-break requires staff to check route-table selection after a controlled priority change; the proposed reverse-path source validation change cannot deliver that static route priority tie-break result by itself.

Question 517

A FortiOS 7.6 review of a hybrid-network deployment reports the following condition: Multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this static route priority tie-break failure?

  1. Use administrative distance alone as a live per-session jitter quality metric.
  2. Leave the backup route configured as the permanently best-preferred path.
  3. Disable source validation globally as the first response without confirming the route asymmetry.
  4. Assume adding another identical route always forces the new one to be preferred.

Explanation

Correct Answer

D:

The problem arises when administrators assume adding another identical route always forces the new one to be preferred, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to review and configure route priority and eligible next hops for the intended tie-breaking behavior.

Incorrect Answers

A:

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 static route priority tie-break case. The more specific error here is the choice to assume adding another identical route always forces the new one to be preferred; check it by attempting to check route-table selection after a controlled priority change before making an unrelated best-quality sd-wan steering change.

B:

The alternative cause involving static route failback can produce a different failure, for example when a recovered primary link is available but traffic stays on a less preferred backup route unexpectedly; it is not the static route priority tie-break case. The more specific error here is the choice to assume adding another identical route always forces the new one to be preferred; check it by attempting to check route-table selection after a controlled priority change before making an unrelated static route failback change.

C:

The alternative cause involving reverse-path source validation can produce a different failure, for example when packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant; it is not the static route priority tie-break case. The more specific error here is the choice to assume adding another identical route always forces the new one to be preferred; check it by attempting to check route-table selection after a controlled priority change before making an unrelated reverse-path source validation change.

Question 518

During FortiOS 7.6 operations at an operations incident response, the evidence is: Multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop. Investigators confirmed this cause: administrators chose to assume adding another identical route always forces the new one to be preferred. 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. Review route monitoring and effective distance so the preferred route can return after recovery.
  3. Assume adding another identical route always forces the new one to be preferred.
  4. Review and configure route priority and eligible next hops for the intended tie-breaking behavior.

Explanation

Correct Answer

D:

This addresses static route priority tie-break without needlessly weakening separate security or routing controls. Given the observed condition—multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop—the operator should then check route-table selection after a controlled priority change.

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 review and configure route priority and eligible next hops for the intended tie-breaking behavior; a review of best-quality sd-wan steering would not, by itself, prove that the team can check route-table selection after a controlled priority change.

B:

Changing the mechanism to review route monitoring and effective distance so the preferred route can return after recovery could be a sensible correction for static route failback when a recovered primary link is available but traffic stays on a less preferred backup route unexpectedly. The targeted fix is to review and configure route priority and eligible next hops for the intended tie-breaking behavior; a review of static route failback would not, by itself, prove that the team can check route-table selection after a controlled priority change.

C:

The proposal repeats the confirmed static route priority tie-break error by choosing to assume adding another identical route always forces the new one to be preferred. A corrective change must instead review and configure route priority and eligible next hops for the intended tie-breaking behavior and then produce the measurable result to check route-table selection after a controlled priority change; repeating the failed setting cannot serve as a repair.

Question 519

At a network segmentation review, a FortiGate running FortiOS 7.6 has this observation: Multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop. The incident has been fixed, and the owner wants to prevent a recurrence of the static route priority tie-break problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for static route failback changes and an acceptance check that will restore the primary link and inspect route selection and session behavior for new flows before relevant releases.
  2. Require peer review for static route priority tie-break changes and an acceptance check that will check route-table selection after a controlled priority change before relevant releases.
  3. 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.
  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.

Explanation

Correct Answer

B:

This change-control gate requires teams to require peer review for static route priority tie-break changes and an acceptance check that will check route-table selection after a controlled priority change 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 check route-table selection after a controlled priority change.

Incorrect Answers

A:

A review gate for static route failback, such as require peer review for static route failback changes and an acceptance check that will restore the primary link and inspect route selection and session behavior for new flows before relevant releases, can be useful where a recovered primary link is available but traffic stays on a less preferred backup route unexpectedly, but it is not the approved static route priority tie-break review. The preventive test must enforce that staff will review and configure route priority and eligible next hops for the intended tie-breaking behavior and subsequently can check route-table selection after a controlled priority change; the proposed static route failback gate would not check that same control.

C:

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 static route priority tie-break review. The preventive test must enforce that staff will review and configure route priority and eligible next hops for the intended tie-breaking behavior and subsequently can check route-table selection after a controlled priority change; the proposed best-quality sd-wan steering gate would not check that same control.

D:

A review gate for reverse-path source validation, such as 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, can be useful where packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant, but it is not the approved static route priority tie-break review. The preventive test must enforce that staff will review and configure route priority and eligible next hops for the intended tie-breaking behavior and subsequently can check route-table selection after a controlled priority change; the proposed reverse-path source validation gate would not check that same control.

Question 520

A FortiOS 7.6 review of a managed branch perimeter reports the following condition: Multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop. The operator corrected the configuration by choosing to review and configure route priority and eligible next hops for the intended tie-breaking behavior. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Restore the primary link and inspect route selection and session behavior for new flows.
  2. Inspect packet drop diagnostics and reverse path for a controlled asymmetric source.
  3. Require peer review for static route priority tie-break changes and an acceptance check that will check route-table selection after a controlled priority change before relevant releases.
  4. Check route-table selection after a controlled priority change.
  5. Introduce controlled jitter variation and verify the session steering choice follows the selected metric.

Explanation

Correct Answers

C:

The organization already encountered the failure where multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to check route-table selection after a controlled priority change, this gate checks future revisions without claiming that the current configuration is permanently correct.

D:

It measures the operational result after the correction to review and configure route priority and eligible next hops for the intended tie-breaking behavior, and it directly checks the reported condition: multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop. For static route priority tie-break, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

A:

The proposed evidence, to restore the primary link and inspect route selection and session behavior for new flows, checks static route failback in a situation such as a recovered primary link is available but traffic stays on a less preferred backup route unexpectedly, not the required static route priority tie-break acceptance. For the affected firewall behavior the directly discriminating check is to check route-table selection after a controlled priority change, alongside a review of static route priority tie-break rather than static route failback settings.

B:

The proposed evidence, to inspect packet drop diagnostics and reverse path for a controlled asymmetric source, checks reverse-path source validation in a situation such as packets from an asymmetric network are dropped after forwarding routes change and anti-spoofing behavior is relevant, not the required static route priority tie-break acceptance. For the affected firewall behavior the directly discriminating check is to check route-table selection after a controlled priority change, alongside a review of static route priority tie-break rather than reverse-path source validation settings.

E:

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 static route priority tie-break acceptance. For the affected firewall behavior the directly discriminating check is to check route-table selection after a controlled priority change, alongside a review of static route priority tie-break rather than best-quality sd-wan steering settings.

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