Fortinet NSE5_SSE_AD-7.6 Practice Test 5 - Prepaway
Practice Exams:

Pass Fortinet NSE5_SSE_AD-7.6 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

NSE5_SSE_AD-7.6 Premium ETE File


  • Premium File 54 Questions & Answers. Last Update: Nov 17, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet NSE5_SSE_AD-7.6 Practice Test 5

Question 40

At Westport Managed Security, the team administers distributed branch WAN topology administration and must test overlay and underlay stability under permitted failure simulations. Operational incident: A newly installed fiber circuit reports its Ethernet port up but cannot carry any branch test traffic. Confirmed observation: Interface diagnostics show the WAN interface has a valid local address while its configured next-hop gateway is outside the provider-assigned reachable network. What remediation-and-validation combination most directly addresses this incident?

  1. Action: Measure an appropriate representative endpoint or service path and bind the corrected health check to the finance steering rule. Proof: A controlled route impairment toward finance is detected before prolonged user loss, while other traffic retains its own policy.
  2. Action: Correct the approved IP addressing and gateway details and verify ordinary underlay reachability before enrolling the link in production steering. Proof: The provider next hop and external test target respond across the repaired link and monitoring can then determine its actual health.
  3. Action: Align the SLA target with measured voice requirements and choose the appropriate service steering rule and eligible links. Proof: During controlled added delay, voice moves to an acceptable member without unnecessary steering of unrelated bulk sessions.
  4. Action: Use an application-appropriate SD-WAN steering strategy and consistent NAT or return-path design for the scoped traffic. Proof: A controlled full login succeeds across failover tests while other independent internet flows retain eligible balancing.

Explanation

Correct Answer

B:

This pair is the bounded choice for Westport Managed Security: Action: Correct the approved IP addressing and gateway details and verify ordinary underlay reachability before enrolling the link in production steering. Proof: The provider next hop and external test target respond across the repaired link and monitoring can then determine its actual health. The underlying issue is: A newly installed fiber circuit reports its Ethernet port up but cannot carry any branch test traffic. Confirm the recorded outcome: The provider next hop and external test target respond across the repaired link and monitoring can then determine its actual health.

Incorrect Answers

A:

Action: Measure an appropriate representative endpoint or service path and bind the corrected health check to the finance steering rule. Proof: A controlled route impairment toward finance is detected before prolonged user loss, while other traffic retains its own policy. The actual issue at Westport Managed Security is: A newly installed fiber circuit reports its Ethernet port up but cannot carry any branch test traffic. The proposed verification does not establish that the required result is: The provider next hop and external test target respond across the repaired link and monitoring can then determine its actual health.

C:

Action: Align the SLA target with measured voice requirements and choose the appropriate service steering rule and eligible links. Proof: During controlled added delay, voice moves to an acceptable member without unnecessary steering of unrelated bulk sessions. The recorded evidence at Westport Managed Security is: Interface diagnostics show the WAN interface has a valid local address while its configured next-hop gateway is outside the provider-assigned reachable network. The correct outcome to measure is: The provider next hop and external test target respond across the repaired link and monitoring can then determine its actual health.

D:

Action: Use an application-appropriate SD-WAN steering strategy and consistent NAT or return-path design for the scoped traffic. Proof: A controlled full login succeeds across failover tests while other independent internet flows retain eligible balancing. The relevant Westport Managed Security observation is: Interface diagnostics show the WAN interface has a valid local address while its configured next-hop gateway is outside the provider-assigned reachable network. Any successful correction still needs to verify: The provider next hop and external test target respond across the repaired link and monitoring can then determine its actual health.

Question 41

For Evergreen Distribution Security, operators support regional FortiGate SD-WAN deployments and are expected to keep WAN member eligibility, business availability and security inspection aligned. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Confirmed observation: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. What scoped change is justified by the observed evidence?

  1. Select a supported trustworthy service-representative monitoring target and validate return path and measurement behavior.
  2. Associate the member with an appropriately authorized zone and update rule references without expanding source access beyond policy.
  3. Correct approved SD-WAN rule order or match scope so the specific media policy is considered first.
  4. Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic.

Explanation

Correct Answer

D:

For Evergreen Distribution Security, the recorded clue is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The bounded correction is: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration. Confirm recovery using this outcome: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Incorrect Answers

A:

Another proposed response centers on: Select a supported trustworthy service-representative monitoring target and validate return path and measurement behavior. The reported Evergreen Distribution Security failure is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The decisive record shows: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.

B:

Another suggested intervention is: Associate the member with an appropriately authorized zone and update rule references without expanding source access beyond policy. It is not sufficient evidence of resolving the Evergreen Distribution Security condition: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The measurable outcome still required is: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

C:

Correct approved SD-WAN rule order or match scope so the specific media policy is considered first. The reported failure at Evergreen Distribution Security is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Its independent recovery check must establish: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Question 42

At Evergreen Distribution Security, the team administers regional FortiGate SD-WAN deployments and must keep WAN member eligibility, business availability and security inspection aligned. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The team must verify the root cause before changing production settings. Which specific observation should determine the next investigation step?

  1. Eligible SD-WAN members include the private overlay inside a catch-all internet steering pool rather than a separately scoped private zone.
  2. The active performance SLA checks select only the older member IDs and omit the new MPLS overlay participant.
  3. The matching SD-WAN rule uses a manual single-member selection and has no approved recovery option for the payment traffic.
  4. Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.

Explanation

Correct Answer

D:

For Evergreen Distribution Security, the decisive evidence is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. It connects the reported failure to the actual operating dependency: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The relevant rule is: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

Incorrect Answers

A:

Eligible SD-WAN members include the private overlay inside a catch-all internet steering pool rather than a separately scoped private zone. It is not the discriminating clue in this record; that clue is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The Evergreen Distribution Security issue is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path.

B:

The active performance SLA checks select only the older member IDs and omit the new MPLS overlay participant. The trace for Evergreen Distribution Security instead establishes: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. This is the clue to the issue actually described.

C:

The matching SD-WAN rule uses a manual single-member selection and has no approved recovery option for the payment traffic. The reported Evergreen Distribution Security fault is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The signal that actually distinguishes it is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.

Question 43

For Evergreen Distribution Security, operators support regional FortiGate SD-WAN deployments and are expected to keep WAN member eligibility, business availability and security inspection aligned. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Confirmed observation: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Proposed controlled action: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. What separate result verifies the change without hiding a second failure?

  1. A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.
  2. During controlled added delay, voice moves to an acceptable member without unnecessary steering of unrelated bulk sessions.
  3. A controlled short-lived impairment does not cause repeated churn but a sustained SLA violation still selects the approved alternative.
  4. Corporate application tests use the private link, and guest traffic uses approved internet breakout without private route reachability.

Explanation

Correct Answer

A:

For Evergreen Distribution Security, an accepted fix must show: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss. The initial diagnostic clue was: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The result therefore tests the stated failure rather than a separate control.

Incorrect Answers

B:

An alternative finding would be: During controlled added delay, voice moves to an acceptable member without unnecessary steering of unrelated bulk sessions. The applicable acceptance criterion at Evergreen Distribution Security is: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss. That result is related to the original issue.

C:

A controlled short-lived impairment does not cause repeated churn but a sustained SLA violation still selects the approved alternative. The recorded clue at Evergreen Distribution Security is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Closure has to validate the corresponding result: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

D:

Corporate application tests use the private link, and guest traffic uses approved internet breakout without private route reachability. That alone would not confirm correction of the Evergreen Distribution Security problem: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The necessary proof is: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Question 44

At Evergreen Distribution Security, the team administers regional FortiGate SD-WAN deployments and must keep WAN member eligibility, business availability and security inspection aligned. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Recorded observation: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Which operational principle governs the documented incident?

  1. Health checks must measure a path relevant to the protected application; unrelated reachable services can hide partial failures.
  2. An interface migration must update higher-layer member references, not merely the physical port configuration.
  3. Federated remote access needs consistent identity-to-policy mapping across the cloud service and private network hub.
  4. A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

Explanation

Correct Answer

D:

A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration. For Evergreen Distribution Security, the supporting evidence is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The reported condition is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path.

Incorrect Answers

A:

Another principle is: Health checks must measure a path relevant to the protected application; unrelated reachable services can hide partial failures. It is not enough to account for the recorded Evergreen Distribution Security evidence: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The applicable rule is: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

B:

An interface migration must update higher-layer member references, not merely the physical port configuration. The documented Evergreen Distribution Security failure is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The case is instead explained by: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

C:

An alternative explanation is: Federated remote access needs consistent identity-to-policy mapping across the cloud service and private network hub. It is not the reason established by the Evergreen Distribution Security clue: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The relevant causal relationship is: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

Question 45

For Evergreen Distribution Security, operators support regional FortiGate SD-WAN deployments and are expected to keep WAN member eligibility, business availability and security inspection aligned. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Confirmed observation: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Which approved change and separate test together resolve the issue?

  1. Action: Associate the member with an appropriately authorized zone and update rule references without expanding source access beyond policy. Proof: An allowed test session can select both approved members under the configured conditions and a denied control session remains denied.
  2. Action: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. Proof: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.
  3. Action: Attach the approved inspection profiles to the applicable allowed branch egress policy and verify both connectivity and enforcement. Proof: A permitted SaaS request succeeds, and a harmless approved test category triggers the intended inspection event in correlated logs.
  4. Action: Advertise or install the authorized branch route through the documented SASE-to-FortiGate integration and check return routing. Proof: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay.

Explanation

Correct Answer

B:

Action: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. Proof: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss. The Evergreen Distribution Security finding is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Independent completion must establish: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Incorrect Answers

A:

Action: Associate the member with an appropriately authorized zone and update rule references without expanding source access beyond policy. Proof: An allowed test session can select both approved members under the configured conditions and a denied control session remains denied. They do not directly establish recovery of the reported Evergreen Distribution Security problem: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Verification requires: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

C:

An alternative option suggests: Action: Attach the approved inspection profiles to the applicable allowed branch egress policy and verify both connectivity and enforcement. Proof: A permitted SaaS request succeeds, and a harmless approved test category triggers the intended inspection event in correlated logs. The documented Evergreen Distribution Security problem calls for a check against: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss. The original clue is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.

D:

Action: Advertise or install the authorized branch route through the documented SASE-to-FortiGate integration and check return routing. Proof: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay. At Evergreen Distribution Security, the actual distinguishing clue is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The related test must establish: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Question 46

At Silverpeak Cloud Services, the team administers distributed branch WAN topology administration and must test overlay and underlay stability under permitted failure simulations. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Confirmed observation: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Which approved correction best addresses the documented root cause?

  1. Separate approved underlay and overlay members or zones as required by the intended traffic classes and verify rule eligibility.
  2. Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic.
  3. Correct the approved IP addressing and gateway details and verify ordinary underlay reachability before enrolling the link in production steering.
  4. Trace the application and source selectors against the rule definition and correct the scoped match if authorized.

Explanation

Correct Answer

B:

The issue at Silverpeak Cloud Services is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. A valid post-change result is: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Incorrect Answers

A:

Although that step is: Separate approved underlay and overlay members or zones as required by the intended traffic classes and verify rule eligibility, the decisive observation here is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. That choice alone does not establish the needed correction at Silverpeak Cloud Services.

C:

The suggested alternative is: Correct the approved IP addressing and gateway details and verify ordinary underlay reachability before enrolling the link in production steering. The case identifies the cause at Silverpeak Cloud Services using: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Implementing that step alone would not verify: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

D:

Another proposed action is: Trace the application and source selectors against the rule definition and correct the scoped match if authorized. In Silverpeak Cloud Services, the relevant evidence is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The focused correction should address the root condition shown by that clue.

Question 47

For Silverpeak Cloud Services, operators support distributed branch WAN topology administration and are expected to test overlay and underlay stability under permitted failure simulations. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The team must verify the root cause before changing production settings. What measured finding directly supports the recorded issue?

  1. Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.
  2. Steering configuration lists the cellular backup with an unexpectedly preferred cost or priority for ordinary business traffic.
  3. Interface diagnostics show the WAN interface has a valid local address while its configured next-hop gateway is outside the provider-assigned reachable network.
  4. Session captures correlate affected application flows with a load-balancing strategy that does not preserve the partner's required source and routing context.

Explanation

Correct Answer

A:

Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. It supports investigation of the Silverpeak Cloud Services issue: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The governing technical reason is: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

Incorrect Answers

B:

Steering configuration lists the cellular backup with an unexpectedly preferred cost or priority for ordinary business traffic. The original Silverpeak Cloud Services observation is instead: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. That is the evidence tied to the stated failure.

C:

Interface diagnostics show the WAN interface has a valid local address while its configured next-hop gateway is outside the provider-assigned reachable network. It does not directly identify the problem reported at Silverpeak Cloud Services. The determining evidence is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.

D:

Session captures correlate affected application flows with a load-balancing strategy that does not preserve the partner's required source and routing context. It does not substantiate the particular Silverpeak Cloud Services condition: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The documented finding is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.

Question 48

At Silverpeak Cloud Services, the team administers distributed branch WAN topology administration and must test overlay and underlay stability under permitted failure simulations. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Confirmed observation: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Proposed controlled action: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. Which independent test would establish that the original problem is resolved?

  1. A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.
  2. The healthy uplink meets the revised check while a deliberately failed link still becomes unavailable to eligible service rules.
  3. With the primary circuit isolated, a monitored authorized session uses the secondary member and recovers when the preferred member returns.
  4. A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay.

Explanation

Correct Answer

A:

The listed result is the right measure for Silverpeak Cloud Services: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss. It verifies the intended effect, whereas the case originally showed: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The relevant principle is: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

Incorrect Answers

B:

The healthy uplink meets the revised check while a deliberately failed link still becomes unavailable to eligible service rules. It is not the evidence needed to close the reported issue. The proper Silverpeak Cloud Services success measure is: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

C:

An alternative test would show: With the primary circuit isolated, a monitored authorized session uses the secondary member and recovers when the preferred member returns. It does not show the required post-change result at Silverpeak Cloud Services: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss. The original finding was: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.

D:

A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay. That is not sufficient to validate the stated Silverpeak Cloud Services failure, supported by: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The required check is: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Question 49

For Silverpeak Cloud Services, operators support distributed branch WAN topology administration and are expected to test overlay and underlay stability under permitted failure simulations. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Recorded observation: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. What platform design concept best accounts for the symptoms?

  1. Failover stability depends on how health samples and recovery are evaluated, not only on the instantaneous metric.
  2. SD-WAN service rules and firewall policies select eligible zones rather than silently using every physical interface.
  3. Stateful applications and their remote peers may depend on stable path and source identity even when links individually work.
  4. A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

Explanation

Correct Answer

D:

A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration. At Silverpeak Cloud Services, the technical clue is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. That explains the reported condition: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path.

Incorrect Answers

A:

Another relationship would be: Failover stability depends on how health samples and recovery are evaluated, not only on the instantaneous metric. It does not account for the issue reported by Silverpeak Cloud Services: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The applicable principle is: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

B:

SD-WAN service rules and firewall policies select eligible zones rather than silently using every physical interface. The key evidence is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. That observation is explained by a different rule: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

C:

Stateful applications and their remote peers may depend on stable path and source identity even when links individually work. The failure at Silverpeak Cloud Services is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The operating rule directly related to that failure is: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

Question 50

At Silverpeak Cloud Services, the team administers distributed branch WAN topology administration and must test overlay and underlay stability under permitted failure simulations. Operational incident: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Confirmed observation: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Which scoped action plus measurable success result should the team choose?

  1. Action: Measure an appropriate representative endpoint or service path and bind the corrected health check to the finance steering rule. Proof: A controlled route impairment toward finance is detected before prolonged user loss, while other traffic retains its own policy.
  2. Action: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. Proof: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.
  3. Action: Create a narrowly scoped firewall policy referencing the appropriate source and SD-WAN destination zone with approved security profiles. Proof: A controlled sanctioned web transaction passes over local internet and an unauthorized source remains denied and logged.
  4. Action: Correct the authorized route filter or discard route for that verified subnet without weakening broader private address protections. Proof: The application prefix resolves to the correct overlay next hop and unrelated intentionally blocked prefixes remain dropped.

Explanation

Correct Answer

B:

This pair is the bounded choice for Silverpeak Cloud Services: Action: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. Proof: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss. The underlying issue is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. Confirm the recorded outcome: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Incorrect Answers

A:

Action: Measure an appropriate representative endpoint or service path and bind the corrected health check to the finance steering rule. Proof: A controlled route impairment toward finance is detected before prolonged user loss, while other traffic retains its own policy. The actual issue at Silverpeak Cloud Services is: A branch policy migration causes unstable default-route selection between a legacy WAN route and the SD-WAN virtual path. The proposed verification does not establish that the required result is: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

C:

Action: Create a narrowly scoped firewall policy referencing the appropriate source and SD-WAN destination zone with approved security profiles. Proof: A controlled sanctioned web transaction passes over local internet and an unauthorized source remains denied and logged. The recorded evidence at Silverpeak Cloud Services is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. The correct outcome to measure is: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

D:

Action: Correct the authorized route filter or discard route for that verified subnet without weakening broader private address protections. Proof: The application prefix resolves to the correct overlay next hop and unrelated intentionally blocked prefixes remain dropped. The relevant Silverpeak Cloud Services observation is: Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. Any successful correction still needs to verify: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests