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 54

Question 530

During FortiOS 7.6 operations at a managed branch perimeter, the evidence is: A static route exists in configuration but traffic cannot reach its specified next-hop gateway. The operator corrected the configuration by choosing to correct next-hop reachability and interface selection rather than focusing only on route syntax. 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 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.
  3. Inspect the matched SD-WAN service ID for a fresh application session.
  4. Restore the primary link and inspect route selection and session behavior for new flows.
  5. Ping the next-hop using the intended source interface and inspect installed route status.

Explanation

Correct Answers

B:

The organization already encountered the failure where a static route exists in configuration but traffic cannot reach its specified next-hop gateway, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to ping the next-hop using the intended source interface and inspect installed route status, this gate checks future revisions without claiming that the current configuration is permanently correct.

E:

It measures the operational result after the correction to correct next-hop reachability and interface selection rather than focusing only on route syntax, and it directly checks the reported condition: a static route exists in configuration but traffic cannot reach its specified next-hop gateway. For unreachable static gateway, 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 the route table and selected SD-WAN member for a routed session, checks sd-wan static-route prerequisite in a situation such as an SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path, not the required unreachable static gateway acceptance. For the affected firewall behavior the directly discriminating check is to ping the next-hop using the intended source interface and inspect installed route status, alongside a review of unreachable static gateway rather than sd-wan static-route prerequisite 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 unreachable static gateway acceptance. For the affected firewall behavior the directly discriminating check is to ping the next-hop using the intended source interface and inspect installed route status, alongside a review of unreachable static gateway rather than sd-wan service rule matching settings.

D:

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 unreachable static gateway acceptance. For the affected firewall behavior the directly discriminating check is to ping the next-hop using the intended source interface and inspect installed route status, alongside a review of unreachable static gateway rather than static route failback settings.

Question 531

At a datacenter security boundary, a FortiGate running FortiOS 7.6 has this observation: A new static route points to a WAN interface different from the network that reaches its next-hop gateway. The requirement concerns static route egress interface while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Differentiate existing-session pinning from new-session path selection when testing SD-WAN changes.
  2. Bind the route to the correct interface and reachable gateway for that destination.
  3. Use the intended SD-WAN zone in relevant firewall policies and route configuration.
  4. Set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link.

Explanation

Correct Answer

B:

Choosing to bind the route to the correct interface and reachable gateway for that destination 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: trace the destination and confirm ARP or neighbor resolution on the intended egress.

Incorrect Answers

A:

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 static route egress interface configuration has a different failure. Evidence for static route egress interface requires staff to trace the destination and confirm ARP or neighbor resolution on the intended egress; the proposed sd-wan session persistence change cannot deliver that static route egress interface result by itself.

C:

Using the intended SD-WAN zone in relevant firewall policies and route configuration would focus the new configuration on sd-wan interface zones, for which two WAN links are added to SD-WAN but policies still reference an unrelated physical interface and cannot match the logical path may be a valid concern, but this static route egress interface configuration has a different failure. Evidence for static route egress interface requires staff to trace the destination and confirm ARP or neighbor resolution on the intended egress; the proposed sd-wan interface zones change cannot deliver that static route egress interface result by itself.

D:

Setting performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link would focus the new configuration on performance sla packet loss, for which voice calls degrade on a high-loss WAN link while another member meets the application SLA may be a valid concern, but this static route egress interface configuration has a different failure. Evidence for static route egress interface requires staff to trace the destination and confirm ARP or neighbor resolution on the intended egress; the proposed performance sla packet loss change cannot deliver that static route egress interface result by itself.

Question 532

A FortiOS 7.6 review of an enterprise gateway change window reports the following condition: A new static route points to a WAN interface different from the network that reaches its next-hop gateway. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this static route egress interface failure?

  1. Choose the lowest nominal interface cost without considering packet-loss SLA failure.
  2. Select an interface whose link cannot resolve the configured next hop.
  3. Assume a recovered link immediately migrates every established session without disruption.
  4. Create SD-WAN members but leave the forwarding policy tied to a nonselected interface.

Explanation

Correct Answer

B:

The problem arises when administrators select an interface whose link cannot resolve the configured next hop, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to bind the route to the correct interface and reachable gateway for that destination.

Incorrect Answers

A:

The alternative cause involving performance sla packet loss can produce a different failure, for example when voice calls degrade on a high-loss WAN link while another member meets the application SLA; it is not the static route egress interface case. The more specific error here is the choice to select an interface whose link cannot resolve the configured next hop; check it by attempting to trace the destination and confirm ARP or neighbor resolution on the intended egress before making an unrelated performance sla packet loss change.

C:

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 static route egress interface case. The more specific error here is the choice to select an interface whose link cannot resolve the configured next hop; check it by attempting to trace the destination and confirm ARP or neighbor resolution on the intended egress before making an unrelated sd-wan session persistence change.

D:

The alternative cause involving sd-wan interface zones can produce a different failure, for example when two WAN links are added to SD-WAN but policies still reference an unrelated physical interface and cannot match the logical path; it is not the static route egress interface case. The more specific error here is the choice to select an interface whose link cannot resolve the configured next hop; check it by attempting to trace the destination and confirm ARP or neighbor resolution on the intended egress before making an unrelated sd-wan interface zones change.

Question 533

During FortiOS 7.6 operations at a redundant regional firewall pair, the evidence is: A new static route points to a WAN interface different from the network that reaches its next-hop gateway. Investigators confirmed this cause: administrators chose to select an interface whose link cannot resolve the configured next hop. Which action MOST directly corrects the confirmed error?

  1. Select an interface whose link cannot resolve the configured next hop.
  2. Set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link.
  3. Bind the route to the correct interface and reachable gateway for that destination.
  4. Differentiate existing-session pinning from new-session path selection when testing SD-WAN changes.

Explanation

Correct Answer

C:

This addresses static route egress interface without needlessly weakening separate security or routing controls. Given the observed condition—a new static route points to a WAN interface different from the network that reaches its next-hop gateway—the operator should then trace the destination and confirm ARP or neighbor resolution on the intended egress.

Incorrect Answers

A:

The proposal repeats the confirmed static route egress interface error by choosing to select an interface whose link cannot resolve the configured next hop. A corrective change must instead bind the route to the correct interface and reachable gateway for that destination and then produce the measurable result to trace the destination and confirm ARP or neighbor resolution on the intended egress; repeating the failed setting cannot serve as a repair.

B:

Changing the mechanism to set performance SLA targets for loss, latency, and jitter and steer the voice service to a healthy link could be a sensible correction for performance sla packet loss when voice calls degrade on a high-loss WAN link while another member meets the application SLA. The targeted fix is to bind the route to the correct interface and reachable gateway for that destination; a review of performance sla packet loss would not, by itself, prove that the team can trace the destination and confirm ARP or neighbor resolution on the intended egress.

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 bind the route to the correct interface and reachable gateway for that destination; a review of sd-wan session persistence would not, by itself, prove that the team can trace the destination and confirm ARP or neighbor resolution on the intended egress.

Question 534

At a remote-office migration, a FortiGate running FortiOS 7.6 has this observation: A new static route points to a WAN interface different from the network that reaches its next-hop gateway. The incident has been fixed, and the owner wants to prevent a recurrence of the static route egress interface problem. Which future change-control rule is MOST appropriate?

  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. 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.
  3. 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.
  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.

Explanation

Correct Answer

B:

This change-control gate requires teams to 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, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to trace the destination and confirm ARP or neighbor resolution on the intended egress.

Incorrect Answers

A:

A review gate for performance sla packet loss, such as require peer review for performance sla packet loss changes and an acceptance check that will measure link health under controlled loss and verify the voice rule selects an eligible member before relevant releases, can be useful where voice calls degrade on a high-loss WAN link while another member meets the application SLA, but it is not the approved static route egress interface review. The preventive test must enforce that staff will bind the route to the correct interface and reachable gateway for that destination and subsequently can trace the destination and confirm ARP or neighbor resolution on the intended egress; the proposed performance sla packet loss gate would not check that same control.

C:

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 static route egress interface review. The preventive test must enforce that staff will bind the route to the correct interface and reachable gateway for that destination and subsequently can trace the destination and confirm ARP or neighbor resolution on the intended egress; the proposed sd-wan session persistence gate would not check that same control.

D:

A review gate for sd-wan interface zones, such as 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, can be useful where two WAN links are added to SD-WAN but policies still reference an unrelated physical interface and cannot match the logical path, but it is not the approved static route egress interface review. The preventive test must enforce that staff will bind the route to the correct interface and reachable gateway for that destination and subsequently can trace the destination and confirm ARP or neighbor resolution on the intended egress; the proposed sd-wan interface zones gate would not check that same control.

Question 535

A FortiOS 7.6 review of a monitored business uplink reports the following condition: A new static route points to a WAN interface different from the network that reaches its next-hop gateway. The operator corrected the configuration by choosing to bind the route to the correct interface and reachable gateway for that destination. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. 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.
  2. Trace the destination and confirm ARP or neighbor resolution on the intended egress.
  3. Measure link health under controlled loss and verify the voice rule selects an eligible member.
  4. Create fresh and persistent sessions and compare their selected SD-WAN members.
  5. Inspect matched policy and SD-WAN zone for an allowed test flow.

Explanation

Correct Answers

A:

The organization already encountered the failure where a new static route points to a WAN interface different from the network that reaches its next-hop gateway, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to trace the destination and confirm ARP or neighbor resolution on the intended egress, this gate checks future revisions without claiming that the current configuration is permanently correct.

B:

It measures the operational result after the correction to bind the route to the correct interface and reachable gateway for that destination, and it directly checks the reported condition: a new static route points to a WAN interface different from the network that reaches its next-hop gateway. For static route egress interface, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

C:

The proposed evidence, to measure link health under controlled loss and verify the voice rule selects an eligible member, checks performance sla packet loss in a situation such as voice calls degrade on a high-loss WAN link while another member meets the application SLA, not the required static route egress interface acceptance. For the affected firewall behavior the directly discriminating check is to trace the destination and confirm ARP or neighbor resolution on the intended egress, alongside a review of static route egress interface rather than performance sla packet loss settings.

D:

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 static route egress interface acceptance. For the affected firewall behavior the directly discriminating check is to trace the destination and confirm ARP or neighbor resolution on the intended egress, alongside a review of static route egress interface rather than sd-wan session persistence settings.

E:

The proposed evidence, to inspect matched policy and SD-WAN zone for an allowed test flow, checks sd-wan interface zones in a situation such as two WAN links are added to SD-WAN but policies still reference an unrelated physical interface and cannot match the logical path, not the required static route egress interface acceptance. For the affected firewall behavior the directly discriminating check is to trace the destination and confirm ARP or neighbor resolution on the intended egress, alongside a review of static route egress interface rather than sd-wan interface zones settings.

Question 536

During FortiOS 7.6 operations at an internal application segment, the evidence is: An intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent. The requirement concerns blackhole route protection while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Configure a properly scoped blackhole route to prevent fallback for that protected destination.
  2. Configure an applicable route toward the SD-WAN zone along with the SD-WAN rule.
  3. Inspect SD-WAN health check status and service-rule decision output for representative flows.
  4. Validate health-check target reachability, source path, and member monitoring before reintroducing the member.

Explanation

Correct Answer

A:

Choosing to configure a properly scoped blackhole route to prevent fallback for that protected destination 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: withdraw the intended tunnel route and verify the protected prefix is not sent to the internet.

Incorrect Answers

B:

Configuring an applicable route toward the SD-WAN zone along with the SD-WAN rule would focus the new configuration on sd-wan static-route prerequisite, for which an SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path may be a valid concern, but this blackhole route protection configuration has a different failure. Evidence for blackhole route protection requires staff to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet; the proposed sd-wan static-route prerequisite change cannot deliver that blackhole route protection result by itself.

C:

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 blackhole route protection configuration has a different failure. Evidence for blackhole route protection requires staff to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet; the proposed sd-wan path diagnostics change cannot deliver that blackhole route protection result by itself.

D:

Selecting validate health-check target reachability, source path, and member monitoring before reintroducing the member would focus the new configuration on sd-wan health-check reachability, for which a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable may be a valid concern, but this blackhole route protection configuration has a different failure. Evidence for blackhole route protection requires staff to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet; the proposed sd-wan health-check reachability change cannot deliver that blackhole route protection result by itself.

Question 537

At a hybrid-network deployment, a FortiGate running FortiOS 7.6 has this observation: An intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this blackhole route protection failure?

  1. Depend on the default internet route to handle sensitive private tunnel destinations.
  2. Treat interface carrier as proof that all health-check destinations are reachable.
  3. Diagnose the wrong egress member from physical interface link lights alone.
  4. Assume the existence of an SD-WAN service rule creates all necessary forwarding routes.

Explanation

Correct Answer

A:

The problem arises when administrators depend on the default internet route to handle sensitive private tunnel destinations, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to configure a properly scoped blackhole route to prevent fallback for that protected destination.

Incorrect Answers

B:

The alternative cause involving sd-wan health-check reachability can produce a different failure, for example when a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable; it is not the blackhole route protection case. The more specific error here is the choice to depend on the default internet route to handle sensitive private tunnel destinations; check it by attempting to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet before making an unrelated sd-wan health-check reachability change.

C:

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 blackhole route protection case. The more specific error here is the choice to depend on the default internet route to handle sensitive private tunnel destinations; check it by attempting to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet before making an unrelated sd-wan path diagnostics change.

D:

The alternative cause involving sd-wan static-route prerequisite can produce a different failure, for example when an SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path; it is not the blackhole route protection case. The more specific error here is the choice to depend on the default internet route to handle sensitive private tunnel destinations; check it by attempting to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet before making an unrelated sd-wan static-route prerequisite change.

Question 538

A FortiOS 7.6 review of an operations incident response reports the following condition: An intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent. Investigators confirmed this cause: administrators chose to depend on the default internet route to handle sensitive private tunnel destinations. Which action MOST directly corrects the confirmed error?

  1. Inspect SD-WAN health check status and service-rule decision output for representative flows.
  2. Validate health-check target reachability, source path, and member monitoring before reintroducing the member.
  3. Configure a properly scoped blackhole route to prevent fallback for that protected destination.
  4. Depend on the default internet route to handle sensitive private tunnel destinations.

Explanation

Correct Answer

C:

This addresses blackhole route protection without needlessly weakening separate security or routing controls. Given the observed condition—an intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent—the operator should then withdraw the intended tunnel route and verify the protected prefix is not sent to the internet.

Incorrect Answers

A:

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 configure a properly scoped blackhole route to prevent fallback for that protected destination; a review of sd-wan path diagnostics would not, by itself, prove that the team can withdraw the intended tunnel route and verify the protected prefix is not sent to the internet.

B:

Changing the mechanism to validate health-check target reachability, source path, and member monitoring before reintroducing the member could be a sensible correction for sd-wan health-check reachability when a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable. The targeted fix is to configure a properly scoped blackhole route to prevent fallback for that protected destination; a review of sd-wan health-check reachability would not, by itself, prove that the team can withdraw the intended tunnel route and verify the protected prefix is not sent to the internet.

D:

The proposal repeats the confirmed blackhole route protection error by choosing to depend on the default internet route to handle sensitive private tunnel destinations. A corrective change must instead configure a properly scoped blackhole route to prevent fallback for that protected destination and then produce the measurable result to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet; repeating the failed setting cannot serve as a repair.

Question 539

During FortiOS 7.6 operations at a network segmentation review, the evidence is: An intentionally disallowed destination prefix is leaking over a catch-all WAN route when its specific tunnel is absent. The incident has been fixed, and the owner wants to prevent a recurrence of the blackhole route protection 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 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.
  3. 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.
  4. Require peer review for sd-wan health-check reachability changes and an acceptance check that will test probe delivery and confirm the SLA health state changes as expected before relevant releases.

Explanation

Correct Answer

B:

This change-control gate requires teams to 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, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to withdraw the intended tunnel route and verify the protected prefix is not sent to the internet.

Incorrect Answers

A:

A review gate for sd-wan static-route prerequisite, such as 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, can be useful where an SD-WAN rule exists but traffic never enters the SD-WAN zone because routing lacks an eligible path, but it is not the approved blackhole route protection review. The preventive test must enforce that staff will configure a properly scoped blackhole route to prevent fallback for that protected destination and subsequently can withdraw the intended tunnel route and verify the protected prefix is not sent to the internet; the proposed sd-wan static-route prerequisite gate would not check that same control.

C:

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 blackhole route protection review. The preventive test must enforce that staff will configure a properly scoped blackhole route to prevent fallback for that protected destination and subsequently can withdraw the intended tunnel route and verify the protected prefix is not sent to the internet; the proposed sd-wan path diagnostics gate would not check that same control.

D:

A review gate for sd-wan health-check reachability, such as require peer review for sd-wan health-check reachability changes and an acceptance check that will test probe delivery and confirm the SLA health state changes as expected before relevant releases, can be useful where a WAN circuit is physically up but its SD-WAN health check is marked dead because probe targets are unreachable, but it is not the approved blackhole route protection review. The preventive test must enforce that staff will configure a properly scoped blackhole route to prevent fallback for that protected destination and subsequently can withdraw the intended tunnel route and verify the protected prefix is not sent to the internet; the proposed sd-wan health-check reachability gate would not check that same control.

Question 540

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

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

Explanation

Correct Answers

D:

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

E:

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

Incorrect Answers

A:

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

B:

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

C:

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

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