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 59

Question 580

A FortiOS 7.6 review of a managed branch perimeter reports the following condition: Two WAN links meet the same SLA but the business wants the lower-cost eligible member used first. The operator corrected the configuration by choosing to use the Lowest Cost (SLA) rule with appropriate member costs and the required SLA target. 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. Inspect packet drop diagnostics and reverse path for a controlled asymmetric source.
  3. Inspect the installed route and fail the preferred path to confirm backup selection.
  4. Compare health status, service match, and selected member for an affected flow.
  5. 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.

Explanation

Correct Answers

A:

It measures the operational result after the correction to use the Lowest Cost (SLA) rule with appropriate member costs and the required SLA target, and it directly checks the reported condition: two WAN links meet the same SLA but the business wants the lower-cost eligible member used first. For lowest-cost eligible link, 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 two WAN links meet the same SLA but the business wants the lower-cost eligible member used first, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to compare member costs and SLA states and verify the selected member under both pass and fail cases, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

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 lowest-cost eligible link acceptance. For the affected firewall behavior the directly discriminating check is to compare member costs and SLA states and verify the selected member under both pass and fail cases, alongside a review of lowest-cost eligible link rather than reverse-path source validation settings.

C:

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 lowest-cost eligible link acceptance. For the affected firewall behavior the directly discriminating check is to compare member costs and SLA states and verify the selected member under both pass and fail cases, alongside a review of lowest-cost eligible link rather than static route administrative distance settings.

D:

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 lowest-cost eligible link acceptance. For the affected firewall behavior the directly discriminating check is to compare member costs and SLA states and verify the selected member under both pass and fail cases, alongside a review of lowest-cost eligible link rather than sd-wan path diagnostics settings.

Question 581

During FortiOS 7.6 operations at a datacenter security boundary, the evidence is: A video service needs the link with the best observed jitter rather than the least expensive eligible link. The requirement concerns best-quality sd-wan steering while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Inspect the routing table and apply the longest-prefix-match decision before changing the default route.
  2. Review and configure route priority and eligible next hops for the intended tie-breaking behavior.
  3. Configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior.
  4. Choose a supported best-quality strategy with the appropriate jitter quality metric and health checks.

Explanation

Correct Answer

D:

Choosing to choose a supported best-quality strategy with the appropriate jitter quality metric and health checks 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: introduce controlled jitter variation and verify the session steering choice follows the selected metric.

Incorrect Answers

A:

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 best-quality sd-wan steering configuration has a different failure. Evidence for best-quality sd-wan steering requires staff to introduce controlled jitter variation and verify the session steering choice follows the selected metric; the proposed longest-prefix route choice change cannot deliver that best-quality sd-wan steering result by itself.

B:

Reviewing and configure route priority and eligible next hops for the intended tie-breaking behavior would focus the new configuration on static route priority tie-break, for which multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop may be a valid concern, but this best-quality sd-wan steering configuration has a different failure. Evidence for best-quality sd-wan steering requires staff to introduce controlled jitter variation and verify the session steering choice follows the selected metric; the proposed static route priority tie-break change cannot deliver that best-quality sd-wan steering result by itself.

C:

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 best-quality sd-wan steering configuration has a different failure. Evidence for best-quality sd-wan steering requires staff to introduce controlled jitter variation and verify the session steering choice follows the selected metric; the proposed equal-cost multipath forwarding change cannot deliver that best-quality sd-wan steering result by itself.

Question 582

At an enterprise gateway change window, a FortiGate running FortiOS 7.6 has this observation: A video service needs the link with the best observed jitter rather than the least expensive eligible link. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this best-quality sd-wan steering failure?

  1. Assume routes with different preference metrics automatically participate in equal-cost load sharing.
  2. Assume adding another identical route always forces the new one to be preferred.
  3. Assume the default route always wins over a more specific matching route.
  4. Use administrative distance alone as a live per-session jitter quality metric.

Explanation

Correct Answer

D:

The problem arises when administrators use administrative distance alone as a live per-session jitter quality metric, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to choose a supported best-quality strategy with the appropriate jitter quality metric and health checks.

Incorrect Answers

A:

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 best-quality sd-wan steering case. The more specific error here is the choice to use administrative distance alone as a live per-session jitter quality metric; check it by attempting to introduce controlled jitter variation and verify the session steering choice follows the selected metric before making an unrelated equal-cost multipath forwarding change.

B:

The alternative cause involving static route priority tie-break can produce a different failure, for example when multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop; it is not the best-quality sd-wan steering case. The more specific error here is the choice to use administrative distance alone as a live per-session jitter quality metric; check it by attempting to introduce controlled jitter variation and verify the session steering choice follows the selected metric before making an unrelated static route priority tie-break change.

C:

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 best-quality sd-wan steering case. The more specific error here is the choice to use administrative distance alone as a live per-session jitter quality metric; check it by attempting to introduce controlled jitter variation and verify the session steering choice follows the selected metric before making an unrelated longest-prefix route choice change.

Question 583

A FortiOS 7.6 review of a redundant regional firewall pair reports the following condition: A video service needs the link with the best observed jitter rather than the least expensive eligible link. Investigators confirmed this cause: administrators chose to use administrative distance alone as a live per-session jitter quality metric. Which action MOST directly corrects the confirmed error?

  1. Review and configure route priority and eligible next hops for the intended tie-breaking behavior.
  2. Choose a supported best-quality strategy with the appropriate jitter quality metric and health checks.
  3. Configure eligible equal-cost routes and confirm the FortiGate ECMP forwarding behavior.
  4. Use administrative distance alone as a live per-session jitter quality metric.

Explanation

Correct Answer

B:

This addresses best-quality sd-wan steering without needlessly weakening separate security or routing controls. Given the observed condition—a video service needs the link with the best observed jitter rather than the least expensive eligible link—the operator should then introduce controlled jitter variation and verify the session steering choice follows the selected metric.

Incorrect Answers

A:

Changing the mechanism to review and configure route priority and eligible next hops for the intended tie-breaking behavior could be a sensible correction for static route priority tie-break when multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop. The targeted fix is to choose a supported best-quality strategy with the appropriate jitter quality metric and health checks; a review of static route priority tie-break would not, by itself, prove that the team can introduce controlled jitter variation and verify the session steering choice follows the selected metric.

C:

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 choose a supported best-quality strategy with the appropriate jitter quality metric and health checks; a review of equal-cost multipath forwarding would not, by itself, prove that the team can introduce controlled jitter variation and verify the session steering choice follows the selected metric.

D:

The proposal repeats the confirmed best-quality sd-wan steering error by choosing to use administrative distance alone as a live per-session jitter quality metric. A corrective change must instead choose a supported best-quality strategy with the appropriate jitter quality metric and health checks and then produce the measurable result to introduce controlled jitter variation and verify the session steering choice follows the selected metric; repeating the failed setting cannot serve as a repair.

Question 584

During FortiOS 7.6 operations at a remote-office migration, the evidence is: A video service needs the link with the best observed jitter rather than the least expensive eligible link. The incident has been fixed, and the owner wants to prevent a recurrence of the best-quality sd-wan steering problem. Which future change-control rule is MOST appropriate?

  1. 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.
  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 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 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 Answer

C:

This change-control gate requires teams to 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, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to introduce controlled jitter variation and verify the session steering choice follows the selected metric.

Incorrect Answers

A:

A review gate for static route priority tie-break, such as 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, can be useful where multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop, but it is not the approved best-quality sd-wan steering review. The preventive test must enforce that staff will choose a supported best-quality strategy with the appropriate jitter quality metric and health checks and subsequently can introduce controlled jitter variation and verify the session steering choice follows the selected metric; the proposed static route priority tie-break 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 best-quality sd-wan steering review. The preventive test must enforce that staff will choose a supported best-quality strategy with the appropriate jitter quality metric and health checks and subsequently can introduce controlled jitter variation and verify the session steering choice follows the selected metric; the proposed longest-prefix route choice gate would not check that same control.

D:

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 best-quality sd-wan steering review. The preventive test must enforce that staff will choose a supported best-quality strategy with the appropriate jitter quality metric and health checks and subsequently can introduce controlled jitter variation and verify the session steering choice follows the selected metric; the proposed equal-cost multipath forwarding gate would not check that same control.

Question 585

At a monitored business uplink, a FortiGate running FortiOS 7.6 has this observation: A video service needs the link with the best observed jitter rather than the least expensive eligible link. The operator corrected the configuration by choosing to choose a supported best-quality strategy with the appropriate jitter quality metric and health checks. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Check route-table selection after a controlled priority change.
  2. 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.
  3. Trace a destination in the specific prefix and verify the selected outgoing next hop.
  4. Inspect installed routes and sample flow egress distribution under controlled conditions.
  5. Introduce controlled jitter variation and verify the session steering choice follows the selected metric.

Explanation

Correct Answers

B:

The organization already encountered the failure where a video service needs the link with the best observed jitter rather than the least expensive eligible link, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to introduce controlled jitter variation and verify the session steering choice follows the selected metric, this gate checks future revisions without claiming that the current configuration is permanently correct.

E:

It measures the operational result after the correction to choose a supported best-quality strategy with the appropriate jitter quality metric and health checks, and it directly checks the reported condition: a video service needs the link with the best observed jitter rather than the least expensive eligible link. For best-quality sd-wan steering, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

A:

The proposed evidence, to check route-table selection after a controlled priority change, checks static route priority tie-break in a situation such as multiple routes to one prefix have the same distance and a branch is selecting an unexpected next hop, not the required best-quality sd-wan steering acceptance. For the affected firewall behavior the directly discriminating check is to introduce controlled jitter variation and verify the session steering choice follows the selected metric, alongside a review of best-quality sd-wan steering rather than static route priority tie-break settings.

C:

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 best-quality sd-wan steering acceptance. For the affected firewall behavior the directly discriminating check is to introduce controlled jitter variation and verify the session steering choice follows the selected metric, alongside a review of best-quality sd-wan steering rather than longest-prefix route choice settings.

D:

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 best-quality sd-wan steering acceptance. For the affected firewall behavior the directly discriminating check is to introduce controlled jitter variation and verify the session steering choice follows the selected metric, alongside a review of best-quality sd-wan steering rather than equal-cost multipath forwarding settings.

Question 586

A FortiOS 7.6 review of an internal application segment reports the following condition: The organization wants to distribute eligible traffic across two links only while both meet performance SLA. The requirement concerns sla-aware load balancing 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. Enable supported SD-WAN load balancing for members that satisfy the selected SLA.
  3. Configure a viable backup static route and validate primary failure detection and next-hop reachability.
  4. Assign administrative distances to express the intended primary and backup route preference.

Explanation

Correct Answer

B:

Choosing to enable supported SD-WAN load balancing for members that satisfy the selected SLA 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: load-test with both eligible members and repeat after one member fails the SLA.

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 sla-aware load balancing configuration has a different failure. Evidence for sla-aware load balancing requires staff to load-test with both eligible members and repeat after one member fails the SLA; the proposed static route failback change cannot deliver that sla-aware load balancing result by itself.

C:

Configuring a viable backup static route and validate primary failure detection and next-hop reachability would focus the new configuration on backup route continuity, for which a branch should switch to its LTE uplink if the primary static WAN path is unavailable may be a valid concern, but this sla-aware load balancing configuration has a different failure. Evidence for sla-aware load balancing requires staff to load-test with both eligible members and repeat after one member fails the SLA; the proposed backup route continuity change cannot deliver that sla-aware load balancing result by itself.

D:

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 sla-aware load balancing configuration has a different failure. Evidence for sla-aware load balancing requires staff to load-test with both eligible members and repeat after one member fails the SLA; the proposed static route administrative distance change cannot deliver that sla-aware load balancing result by itself.

Question 587

During FortiOS 7.6 operations at a hybrid-network deployment, the evidence is: The organization wants to distribute eligible traffic across two links only while both meet performance SLA. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this sla-aware load balancing failure?

  1. Leave the backup route configured as the permanently best-preferred path.
  2. Treat equal destination masks as sufficient proof of which route should win without reviewing distance.
  3. Use only a single primary route with no eligible alternate next hop.
  4. Spread traffic uniformly across an unhealthy member that fails the required SLA target.

Explanation

Correct Answer

D:

The problem arises when administrators spread traffic uniformly across an unhealthy member that fails the required SLA target, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to enable supported SD-WAN load balancing for members that satisfy the selected SLA.

Incorrect Answers

A:

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 sla-aware load balancing case. The more specific error here is the choice to spread traffic uniformly across an unhealthy member that fails the required SLA target; check it by attempting to load-test with both eligible members and repeat after one member fails the SLA before making an unrelated static route failback change.

B:

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 sla-aware load balancing case. The more specific error here is the choice to spread traffic uniformly across an unhealthy member that fails the required SLA target; check it by attempting to load-test with both eligible members and repeat after one member fails the SLA before making an unrelated static route administrative distance change.

C:

The alternative cause involving backup route continuity can produce a different failure, for example when a branch should switch to its LTE uplink if the primary static WAN path is unavailable; it is not the sla-aware load balancing case. The more specific error here is the choice to spread traffic uniformly across an unhealthy member that fails the required SLA target; check it by attempting to load-test with both eligible members and repeat after one member fails the SLA before making an unrelated backup route continuity change.

Question 588

At an operations incident response, a FortiGate running FortiOS 7.6 has this observation: The organization wants to distribute eligible traffic across two links only while both meet performance SLA. Investigators confirmed this cause: administrators chose to spread traffic uniformly across an unhealthy member that fails the required SLA target. Which action MOST directly corrects the confirmed error?

  1. Spread traffic uniformly across an unhealthy member that fails the required SLA target.
  2. Review route monitoring and effective distance so the preferred route can return after recovery.
  3. Enable supported SD-WAN load balancing for members that satisfy the selected SLA.
  4. Configure a viable backup static route and validate primary failure detection and next-hop reachability.

Explanation

Correct Answer

C:

This addresses sla-aware load balancing without needlessly weakening separate security or routing controls. Given the observed condition—the organization wants to distribute eligible traffic across two links only while both meet performance SLA—the operator should then load-test with both eligible members and repeat after one member fails the SLA.

Incorrect Answers

A:

The proposal repeats the confirmed sla-aware load balancing error by choosing to spread traffic uniformly across an unhealthy member that fails the required SLA target. A corrective change must instead enable supported SD-WAN load balancing for members that satisfy the selected SLA and then produce the measurable result to load-test with both eligible members and repeat after one member fails the SLA; repeating the failed setting cannot serve as a repair.

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 enable supported SD-WAN load balancing for members that satisfy the selected SLA; a review of static route failback would not, by itself, prove that the team can load-test with both eligible members and repeat after one member fails the SLA.

D:

Changing the mechanism to configure a viable backup static route and validate primary failure detection and next-hop reachability could be a sensible correction for backup route continuity when a branch should switch to its LTE uplink if the primary static WAN path is unavailable. The targeted fix is to enable supported SD-WAN load balancing for members that satisfy the selected SLA; a review of backup route continuity would not, by itself, prove that the team can load-test with both eligible members and repeat after one member fails the SLA.

Question 589

A FortiOS 7.6 review of a network segmentation review reports the following condition: The organization wants to distribute eligible traffic across two links only while both meet performance SLA. The incident has been fixed, and the owner wants to prevent a recurrence of the sla-aware load balancing problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for sla-aware load balancing changes and an acceptance check that will load-test with both eligible members and repeat after one member fails the SLA before relevant releases.
  2. 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.
  3. Require peer review for backup route continuity changes and an acceptance check that will disconnect the primary test link and verify connectivity through the backup route before relevant releases.
  4. 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.

Explanation

Correct Answer

A:

This change-control gate requires teams to require peer review for sla-aware load balancing changes and an acceptance check that will load-test with both eligible members and repeat after one member fails the SLA 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 load-test with both eligible members and repeat after one member fails the SLA.

Incorrect Answers

B:

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 sla-aware load balancing review. The preventive test must enforce that staff will enable supported SD-WAN load balancing for members that satisfy the selected SLA and subsequently can load-test with both eligible members and repeat after one member fails the SLA; the proposed static route administrative distance gate would not check that same control.

C:

A review gate for backup route continuity, such as require peer review for backup route continuity changes and an acceptance check that will disconnect the primary test link and verify connectivity through the backup route before relevant releases, can be useful where a branch should switch to its LTE uplink if the primary static WAN path is unavailable, but it is not the approved sla-aware load balancing review. The preventive test must enforce that staff will enable supported SD-WAN load balancing for members that satisfy the selected SLA and subsequently can load-test with both eligible members and repeat after one member fails the SLA; the proposed backup route continuity gate would not check that same control.

D:

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 sla-aware load balancing review. The preventive test must enforce that staff will enable supported SD-WAN load balancing for members that satisfy the selected SLA and subsequently can load-test with both eligible members and repeat after one member fails the SLA; the proposed static route failback gate would not check that same control.

Question 590

During FortiOS 7.6 operations at a managed branch perimeter, the evidence is: The organization wants to distribute eligible traffic across two links only while both meet performance SLA. The operator corrected the configuration by choosing to enable supported SD-WAN load balancing for members that satisfy the selected SLA. 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 the installed route and fail the preferred path to confirm backup selection.
  3. Load-test with both eligible members and repeat after one member fails the SLA.
  4. Require peer review for sla-aware load balancing changes and an acceptance check that will load-test with both eligible members and repeat after one member fails the SLA before relevant releases.
  5. Disconnect the primary test link and verify connectivity through the backup route.

Explanation

Correct Answers

C:

It measures the operational result after the correction to enable supported SD-WAN load balancing for members that satisfy the selected SLA, and it directly checks the reported condition: the organization wants to distribute eligible traffic across two links only while both meet performance SLA. For sla-aware load balancing, 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 the organization wants to distribute eligible traffic across two links only while both meet performance SLA, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to load-test with both eligible members and repeat after one member fails the SLA, this gate checks future revisions without claiming that the current configuration is permanently correct.

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 sla-aware load balancing acceptance. For the affected firewall behavior the directly discriminating check is to load-test with both eligible members and repeat after one member fails the SLA, alongside a review of sla-aware load balancing rather than static route failback settings.

B:

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 sla-aware load balancing acceptance. For the affected firewall behavior the directly discriminating check is to load-test with both eligible members and repeat after one member fails the SLA, alongside a review of sla-aware load balancing rather than static route administrative distance settings.

E:

The proposed evidence, to disconnect the primary test link and verify connectivity through the backup route, checks backup route continuity in a situation such as a branch should switch to its LTE uplink if the primary static WAN path is unavailable, not the required sla-aware load balancing acceptance. For the affected firewall behavior the directly discriminating check is to load-test with both eligible members and repeat after one member fails the SLA, alongside a review of sla-aware load balancing rather than backup route continuity settings.

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