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 57

Question 560

During FortiOS 7.6 operations at a managed branch perimeter, the evidence is: Two WAN links are added to SD-WAN but policies still reference an unrelated physical interface and cannot match the logical path. The operator corrected the configuration by choosing to use the intended SD-WAN zone in relevant firewall policies and route configuration. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Introduce controlled jitter variation and verify the session steering choice follows the selected metric.
  2. Inspect matched policy and SD-WAN zone for an allowed test flow.
  3. Inspect the matched SD-WAN service ID for a fresh application session.
  4. Require peer review for sd-wan interface zones changes and an acceptance check that will inspect matched policy and SD-WAN zone for an allowed test flow before relevant releases.
  5. Disconnect the primary test link and verify connectivity through the backup route.

Explanation

Correct Answers

B:

It measures the operational result after the correction to use the intended SD-WAN zone in relevant firewall policies and route configuration, and it directly checks the reported condition: two WAN links are added to SD-WAN but policies still reference an unrelated physical interface and cannot match the logical path. For sd-wan interface zones, 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 two WAN links are added to SD-WAN but policies still reference an unrelated physical interface and cannot match the logical path, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to inspect matched policy and SD-WAN zone for an allowed test flow, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

A:

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 sd-wan interface zones acceptance. For the affected firewall behavior the directly discriminating check is to inspect matched policy and SD-WAN zone for an allowed test flow, alongside a review of sd-wan interface zones rather than best-quality sd-wan steering settings.

C:

The proposed evidence, to inspect the matched SD-WAN service ID for a fresh application session, checks sd-wan service rule matching in a situation such as an application uses the implicit SD-WAN rule because a custom traffic matching rule uses the wrong destination or service criteria, not the required sd-wan interface zones acceptance. For the affected firewall behavior the directly discriminating check is to inspect matched policy and SD-WAN zone for an allowed test flow, alongside a review of sd-wan interface zones rather than sd-wan service rule matching 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 sd-wan interface zones acceptance. For the affected firewall behavior the directly discriminating check is to inspect matched policy and SD-WAN zone for an allowed test flow, alongside a review of sd-wan interface zones rather than backup route continuity settings.

Question 561

At a datacenter security boundary, a FortiGate running FortiOS 7.6 has this observation: An SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path. The requirement concerns sd-wan static-route prerequisite while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Configure an applicable route toward the SD-WAN zone along with the SD-WAN rule.
  2. Correct next-hop reachability and interface selection rather than focusing only on route syntax.
  3. Differentiate existing-session pinning from new-session path selection when testing SD-WAN changes.
  4. Enable supported SD-WAN load balancing for members that satisfy the selected SLA.

Explanation

Correct Answer

A:

Choosing to configure an applicable route toward the SD-WAN zone along with the SD-WAN rule 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 the route table and selected SD-WAN member for a routed session.

Incorrect Answers

B:

Selecting correct next-hop reachability and interface selection rather than focusing only on route syntax would focus the new configuration on unreachable static gateway, for which a static route exists in configuration but traffic cannot reach its specified next-hop gateway may be a valid concern, but this sd-wan static-route prerequisite configuration has a different failure. Evidence for sd-wan static-route prerequisite requires staff to check the route table and selected SD-WAN member for a routed session; the proposed unreachable static gateway change cannot deliver that sd-wan static-route prerequisite result by itself.

C:

Selecting differentiate existing-session pinning from new-session path selection when testing SD-WAN changes would focus the new configuration on sd-wan session persistence, for which long-lived application sessions do not instantly move to a recovered preferred uplink even though new sessions do may be a valid concern, but this sd-wan static-route prerequisite configuration has a different failure. Evidence for sd-wan static-route prerequisite requires staff to check the route table and selected SD-WAN member for a routed session; the proposed sd-wan session persistence change cannot deliver that sd-wan static-route prerequisite result by itself.

D:

Enabling supported SD-WAN load balancing for members that satisfy the selected SLA would focus the new configuration on sla-aware load balancing, for which the organization wants to distribute eligible traffic across two links only while both meet performance SLA may be a valid concern, but this sd-wan static-route prerequisite configuration has a different failure. Evidence for sd-wan static-route prerequisite requires staff to check the route table and selected SD-WAN member for a routed session; the proposed sla-aware load balancing change cannot deliver that sd-wan static-route prerequisite result by itself.

Question 562

A FortiOS 7.6 review of an enterprise gateway change window reports the following condition: An SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this sd-wan static-route prerequisite failure?

  1. Assume a recovered link immediately migrates every established session without disruption.
  2. Assume the existence of an SD-WAN service rule creates all necessary forwarding routes.
  3. Spread traffic uniformly across an unhealthy member that fails the required SLA target.
  4. Specify a gateway address unreachable from the chosen egress network.

Explanation

Correct Answer

B:

The problem arises when administrators assume the existence of an SD-WAN service rule creates all necessary forwarding routes, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to configure an applicable route toward the SD-WAN zone along with the SD-WAN rule.

Incorrect Answers

A:

The alternative cause involving sd-wan session persistence can produce a different failure, for example when long-lived application sessions do not instantly move to a recovered preferred uplink even though new sessions do; it is not the sd-wan static-route prerequisite case. The more specific error here is the choice to assume the existence of an SD-WAN service rule creates all necessary forwarding routes; check it by attempting to check the route table and selected SD-WAN member for a routed session before making an unrelated sd-wan session persistence change.

C:

The alternative cause involving sla-aware load balancing can produce a different failure, for example when the organization wants to distribute eligible traffic across two links only while both meet performance SLA; it is not the sd-wan static-route prerequisite case. The more specific error here is the choice to assume the existence of an SD-WAN service rule creates all necessary forwarding routes; check it by attempting to check the route table and selected SD-WAN member for a routed session before making an unrelated sla-aware load balancing change.

D:

The alternative cause involving unreachable static gateway can produce a different failure, for example when a static route exists in configuration but traffic cannot reach its specified next-hop gateway; it is not the sd-wan static-route prerequisite case. The more specific error here is the choice to assume the existence of an SD-WAN service rule creates all necessary forwarding routes; check it by attempting to check the route table and selected SD-WAN member for a routed session before making an unrelated unreachable static gateway change.

Question 563

During FortiOS 7.6 operations at a redundant regional firewall pair, the evidence is: An SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path. Investigators confirmed this cause: administrators chose to assume the existence of an SD-WAN service rule creates all necessary forwarding routes. Which action MOST directly corrects the confirmed error?

  1. Correct next-hop reachability and interface selection rather than focusing only on route syntax.
  2. Configure an applicable route toward the SD-WAN zone along with the SD-WAN rule.
  3. Assume the existence of an SD-WAN service rule creates all necessary forwarding routes.
  4. Differentiate existing-session pinning from new-session path selection when testing SD-WAN changes.

Explanation

Correct Answer

B:

This addresses sd-wan static-route prerequisite without needlessly weakening separate security or routing controls. Given the observed condition—an SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path—the operator should then check the route table and selected SD-WAN member for a routed session.

Incorrect Answers

A:

Changing the mechanism to correct next-hop reachability and interface selection rather than focusing only on route syntax could be a sensible correction for unreachable static gateway when a static route exists in configuration but traffic cannot reach its specified next-hop gateway. The targeted fix is to configure an applicable route toward the SD-WAN zone along with the SD-WAN rule; a review of unreachable static gateway would not, by itself, prove that the team can check the route table and selected SD-WAN member for a routed session.

C:

The proposal repeats the confirmed sd-wan static-route prerequisite error by choosing to assume the existence of an SD-WAN service rule creates all necessary forwarding routes. A corrective change must instead configure an applicable route toward the SD-WAN zone along with the SD-WAN rule and then produce the measurable result to check the route table and selected SD-WAN member for a routed session; repeating the failed setting cannot serve as a repair.

D:

Changing the mechanism to differentiate existing-session pinning from new-session path selection when testing SD-WAN changes could be a sensible correction for sd-wan session persistence when long-lived application sessions do not instantly move to a recovered preferred uplink even though new sessions do. The targeted fix is to configure an applicable route toward the SD-WAN zone along with the SD-WAN rule; a review of sd-wan session persistence would not, by itself, prove that the team can check the route table and selected SD-WAN member for a routed session.

Question 564

At a remote-office migration, a FortiGate running FortiOS 7.6 has this observation: An SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path. The incident has been fixed, and the owner wants to prevent a recurrence of the sd-wan static-route prerequisite problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for sd-wan static-route prerequisite changes and an acceptance check that will check the route table and selected SD-WAN member for a routed session before relevant releases.
  2. Require peer review for sd-wan session persistence changes and an acceptance check that will create fresh and persistent sessions and compare their selected SD-WAN members before relevant releases.
  3. 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.
  4. Require peer review for unreachable static gateway changes and an acceptance check that will ping the next-hop using the intended source interface and inspect installed route status before relevant releases.

Explanation

Correct Answer

A:

This change-control gate requires teams to require peer review for sd-wan static-route prerequisite changes and an acceptance check that will check the route table and selected SD-WAN member for a routed session 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 the route table and selected SD-WAN member for a routed session.

Incorrect Answers

B:

A review gate for sd-wan session persistence, such as require peer review for sd-wan session persistence changes and an acceptance check that will create fresh and persistent sessions and compare their selected SD-WAN members before relevant releases, can be useful where long-lived application sessions do not instantly move to a recovered preferred uplink even though new sessions do, but it is not the approved sd-wan static-route prerequisite review. The preventive test must enforce that staff will configure an applicable route toward the SD-WAN zone along with the SD-WAN rule and subsequently can check the route table and selected SD-WAN member for a routed session; the proposed sd-wan session persistence gate would not check that same control.

C:

A review gate for sla-aware load balancing, such as 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, can be useful where the organization wants to distribute eligible traffic across two links only while both meet performance SLA, but it is not the approved sd-wan static-route prerequisite review. The preventive test must enforce that staff will configure an applicable route toward the SD-WAN zone along with the SD-WAN rule and subsequently can check the route table and selected SD-WAN member for a routed session; the proposed sla-aware load balancing gate would not check that same control.

D:

A review gate for unreachable static gateway, such as require peer review for unreachable static gateway changes and an acceptance check that will ping the next-hop using the intended source interface and inspect installed route status before relevant releases, can be useful where a static route exists in configuration but traffic cannot reach its specified next-hop gateway, but it is not the approved sd-wan static-route prerequisite review. The preventive test must enforce that staff will configure an applicable route toward the SD-WAN zone along with the SD-WAN rule and subsequently can check the route table and selected SD-WAN member for a routed session; the proposed unreachable static gateway gate would not check that same control.

Question 565

A FortiOS 7.6 review of a monitored business uplink reports the following condition: An SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path. The operator corrected the configuration by choosing to configure an applicable route toward the SD-WAN zone along with the SD-WAN rule. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Check the route table and selected SD-WAN member for a routed session.
  2. Require peer review for sd-wan static-route prerequisite changes and an acceptance check that will check the route table and selected SD-WAN member for a routed session before relevant releases.
  3. Create fresh and persistent sessions and compare their selected SD-WAN members.
  4. Ping the next-hop using the intended source interface and inspect installed route status.
  5. Load-test with both eligible members and repeat after one member fails the SLA.

Explanation

Correct Answers

A:

It measures the operational result after the correction to configure an applicable route toward the SD-WAN zone along with the SD-WAN rule, and it directly checks the reported condition: an SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path. For sd-wan static-route prerequisite, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

B:

The organization already encountered the failure where an SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to check the route table and selected SD-WAN member for a routed session, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

C:

The proposed evidence, to create fresh and persistent sessions and compare their selected SD-WAN members, checks sd-wan session persistence in a situation such as long-lived application sessions do not instantly move to a recovered preferred uplink even though new sessions do, not the required sd-wan static-route prerequisite acceptance. For the affected firewall behavior the directly discriminating check is to check the route table and selected SD-WAN member for a routed session, alongside a review of sd-wan static-route prerequisite rather than sd-wan session persistence settings.

D:

The proposed evidence, to ping the next-hop using the intended source interface and inspect installed route status, checks unreachable static gateway in a situation such as a static route exists in configuration but traffic cannot reach its specified next-hop gateway, not the required sd-wan static-route prerequisite acceptance. For the affected firewall behavior the directly discriminating check is to check the route table and selected SD-WAN member for a routed session, alongside a review of sd-wan static-route prerequisite rather than unreachable static gateway settings.

E:

The proposed evidence, to load-test with both eligible members and repeat after one member fails the SLA, checks sla-aware load balancing in a situation such as the organization wants to distribute eligible traffic across two links only while both meet performance SLA, not the required sd-wan static-route prerequisite acceptance. For the affected firewall behavior the directly discriminating check is to check the route table and selected SD-WAN member for a routed session, alongside a review of sd-wan static-route prerequisite rather than sla-aware load balancing settings.

Question 566

During FortiOS 7.6 operations at an internal application segment, the evidence is: Voice calls degrade on a high-loss WAN link while another member meets the application SLA. The requirement concerns performance sla packet loss 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. Inspect SD-WAN health check status and service-rule decision output for representative flows.
  3. Correct the SD-WAN service rule selectors and evaluate rule ordering for the application.
  4. Bind the route to the correct interface and reachable gateway for that destination.

Explanation

Correct Answer

A:

Choosing to set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link 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: measure link health under controlled loss and verify the voice rule selects an eligible member.

Incorrect Answers

B:

Inspecting SD-WAN health check status and service-rule decision output for representative flows would focus the new configuration on sd-wan path diagnostics, for which two provider paths seem healthy but one set of applications consistently uses an unexpected member may be a valid concern, but this performance sla packet loss configuration has a different failure. Evidence for performance sla packet loss requires staff to measure link health under controlled loss and verify the voice rule selects an eligible member; the proposed sd-wan path diagnostics change cannot deliver that performance sla packet loss result by itself.

C:

Selecting correct the SD-WAN service rule selectors and evaluate rule ordering for the application would focus the new configuration on sd-wan service rule matching, for which an application uses the implicit SD-WAN rule because a custom traffic matching rule uses the wrong destination or service criteria may be a valid concern, but this performance sla packet loss configuration has a different failure. Evidence for performance sla packet loss requires staff to measure link health under controlled loss and verify the voice rule selects an eligible member; the proposed sd-wan service rule matching change cannot deliver that performance sla packet loss result by itself.

D:

Selecting bind the route to the correct interface and reachable gateway for that destination would focus the new configuration on static route egress interface, for which a new static route points to a WAN interface different from the network that reaches its next-hop gateway may be a valid concern, but this performance sla packet loss configuration has a different failure. Evidence for performance sla packet loss requires staff to measure link health under controlled loss and verify the voice rule selects an eligible member; the proposed static route egress interface change cannot deliver that performance sla packet loss result by itself.

Question 567

At a hybrid-network deployment, a FortiGate running FortiOS 7.6 has this observation: Voice calls degrade on a high-loss WAN link while another member meets the application SLA. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this performance sla packet loss failure?

  1. Assume a named service rule applies to all traffic regardless of its match conditions.
  2. Select an interface whose link cannot resolve the configured next hop.
  3. Choose the lowest nominal interface cost without considering packet-loss SLA failure.
  4. Diagnose the wrong egress member from physical interface link lights alone.

Explanation

Correct Answer

C:

The problem arises when administrators choose the lowest nominal interface cost without considering packet-loss SLA failure, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link.

Incorrect Answers

A:

The alternative cause involving sd-wan service rule matching can produce a different failure, for example when an application uses the implicit SD-WAN rule because a custom traffic matching rule uses the wrong destination or service criteria; it is not the performance sla packet loss case. The more specific error here is the choice to choose the lowest nominal interface cost without considering packet-loss SLA failure; check it by attempting to measure link health under controlled loss and verify the voice rule selects an eligible member before making an unrelated sd-wan service rule matching change.

B:

The alternative cause involving static route egress interface can produce a different failure, for example when a new static route points to a WAN interface different from the network that reaches its next-hop gateway; it is not the performance sla packet loss case. The more specific error here is the choice to choose the lowest nominal interface cost without considering packet-loss SLA failure; check it by attempting to measure link health under controlled loss and verify the voice rule selects an eligible member before making an unrelated static route egress interface change.

D:

The alternative cause involving sd-wan path diagnostics can produce a different failure, for example when two provider paths seem healthy but one set of applications consistently uses an unexpected member; it is not the performance sla packet loss case. The more specific error here is the choice to choose the lowest nominal interface cost without considering packet-loss SLA failure; check it by attempting to measure link health under controlled loss and verify the voice rule selects an eligible member before making an unrelated sd-wan path diagnostics change.

Question 568

A FortiOS 7.6 review of an operations incident response reports the following condition: Voice calls degrade on a high-loss WAN link while another member meets the application SLA. Investigators confirmed this cause: administrators chose to choose the lowest nominal interface cost without considering packet-loss SLA failure. Which action MOST directly corrects the confirmed error?

  1. Bind the route to the correct interface and reachable gateway for that destination.
  2. Choose the lowest nominal interface cost without considering packet-loss SLA failure.
  3. Inspect SD-WAN health check status and service-rule decision output for representative flows.
  4. Set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link.

Explanation

Correct Answer

D:

This addresses performance sla packet loss without needlessly weakening separate security or routing controls. Given the observed condition—voice calls degrade on a high-loss WAN link while another member meets the application SLA—the operator should then measure link health under controlled loss and verify the voice rule selects an eligible member.

Incorrect Answers

A:

Changing the mechanism to bind the route to the correct interface and reachable gateway for that destination could be a sensible correction for static route egress interface when a new static route points to a WAN interface different from the network that reaches its next-hop gateway. The targeted fix is to set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link; a review of static route egress interface would not, by itself, prove that the team can measure link health under controlled loss and verify the voice rule selects an eligible member.

B:

The proposal repeats the confirmed performance sla packet loss error by choosing to choose the lowest nominal interface cost without considering packet-loss SLA failure. A corrective change must instead set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link and then produce the measurable result to measure link health under controlled loss and verify the voice rule selects an eligible member; repeating the failed setting cannot serve as a repair.

C:

Changing the mechanism to inspect SD-WAN health check status and service-rule decision output for representative flows could be a sensible correction for sd-wan path diagnostics when two provider paths seem healthy but one set of applications consistently uses an unexpected member. The targeted fix is to set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link; a review of sd-wan path diagnostics would not, by itself, prove that the team can measure link health under controlled loss and verify the voice rule selects an eligible member.

Question 569

During FortiOS 7.6 operations at a network segmentation review, the evidence is: Voice calls degrade on a high-loss WAN link while another member meets the application SLA. The incident has been fixed, and the owner wants to prevent a recurrence of the performance sla packet loss problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for sd-wan path diagnostics changes and an acceptance check that will compare health status, service match, and selected member for an affected flow before relevant releases.
  2. 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.
  3. Require peer review for sd-wan service rule matching changes and an acceptance check that will inspect the matched SD-WAN service ID for a fresh application session before relevant releases.
  4. Require peer review for static route egress interface changes and an acceptance check that will trace the destination and confirm ARP or neighbor resolution on the intended egress before relevant releases.

Explanation

Correct Answer

B:

This change-control gate requires teams to 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, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to measure link health under controlled loss and verify the voice rule selects an eligible member.

Incorrect Answers

A:

A review gate for sd-wan path diagnostics, such as require peer review for sd-wan path diagnostics changes and an acceptance check that will compare health status, service match, and selected member for an affected flow before relevant releases, can be useful where two provider paths seem healthy but one set of applications consistently uses an unexpected member, but it is not the approved performance sla packet loss review. The preventive test must enforce that staff will set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link and subsequently can measure link health under controlled loss and verify the voice rule selects an eligible member; the proposed sd-wan path diagnostics gate would not check that same control.

C:

A review gate for sd-wan service rule matching, such as require peer review for sd-wan service rule matching changes and an acceptance check that will inspect the matched SD-WAN service ID for a fresh application session before relevant releases, can be useful where an application uses the implicit SD-WAN rule because a custom traffic matching rule uses the wrong destination or service criteria, but it is not the approved performance sla packet loss review. The preventive test must enforce that staff will set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link and subsequently can measure link health under controlled loss and verify the voice rule selects an eligible member; the proposed sd-wan service rule matching gate would not check that same control.

D:

A review gate for static route egress interface, such as require peer review for static route egress interface changes and an acceptance check that will trace the destination and confirm ARP or neighbor resolution on the intended egress before relevant releases, can be useful where a new static route points to a WAN interface different from the network that reaches its next-hop gateway, but it is not the approved performance sla packet loss review. The preventive test must enforce that staff will set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link and subsequently can measure link health under controlled loss and verify the voice rule selects an eligible member; the proposed static route egress interface gate would not check that same control.

Question 570

At a managed branch perimeter, a FortiGate running FortiOS 7.6 has this observation: Voice calls degrade on a high-loss WAN link while another member meets the application SLA. The operator corrected the configuration by choosing to set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. 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.
  2. Compare health status, service match, and selected member for an affected flow.
  3. Measure link health under controlled loss and verify the voice rule selects an eligible member.
  4. Trace the destination and confirm ARP or neighbor resolution on the intended egress.
  5. Inspect the matched SD-WAN service ID for a fresh application session.

Explanation

Correct Answers

A:

The organization already encountered the failure where voice calls degrade on a high-loss WAN link while another member meets the application SLA, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to measure link health under controlled loss and verify the voice rule selects an eligible member, this gate checks future revisions without claiming that the current configuration is permanently correct.

C:

It measures the operational result after the correction to set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link, and it directly checks the reported condition: voice calls degrade on a high-loss WAN link while another member meets the application SLA. For performance sla packet loss, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

B:

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 performance sla packet loss acceptance. For the affected firewall behavior the directly discriminating check is to measure link health under controlled loss and verify the voice rule selects an eligible member, alongside a review of performance sla packet loss rather than sd-wan path diagnostics settings.

D:

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 performance sla packet loss acceptance. For the affected firewall behavior the directly discriminating check is to measure link health under controlled loss and verify the voice rule selects an eligible member, alongside a review of performance sla packet loss rather than static route egress interface settings.

E:

The proposed evidence, to inspect the matched SD-WAN service ID for a fresh application session, checks sd-wan service rule matching in a situation such as an application uses the implicit SD-WAN rule because a custom traffic matching rule uses the wrong destination or service criteria, not the required performance sla packet loss acceptance. For the affected firewall behavior the directly discriminating check is to measure link health under controlled loss and verify the voice rule selects an eligible member, alongside a review of performance sla packet loss rather than sd-wan service rule matching settings.

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