Fortinet NSE5_SSE_AD-7.6 Practice Test 35 - 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 35

Question 340

At Westport Managed Security, the team administers enterprise edge transport policy and route governance and must verify rule hits, correct route decisions and application availability. Operational incident: Remote clients can resolve a service DNS name but requests are denied after a reorganization of WAN zones. Confirmed observation: Policy route tracing shows traffic leaves toward a newly named SD-WAN zone not referenced in the authorized security policy. What remediation-and-validation combination most directly addresses this incident?

  1. Action: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. Proof: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.
  2. 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.
  3. Action: Update the scoped security rule's destination zone and confirm the intended route and inspection settings. Proof: Approved client requests complete across the revised zone while unauthorized client test traffic remains denied and logged.
  4. Action: Correct source-interface or source-address choices through supported probe and interface settings after verifying the actual routed path. Proof: The same test target responds to probes via the correct member without changing the approved health thresholds.

Explanation

Correct Answer

C:

The option addresses the actual fault and includes measurable proof: Action: Update the scoped security rule's destination zone and confirm the intended route and inspection settings. Proof: Approved client requests complete across the revised zone while unauthorized client test traffic remains denied and logged. The case evidence at Westport Managed Security is: Policy route tracing shows traffic leaves toward a newly named SD-WAN zone not referenced in the authorized security policy. The acceptance target is: Approved client requests complete across the revised zone while unauthorized client test traffic remains denied and logged.

Incorrect Answers

A:

Action: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. Proof: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. The actual issue at Westport Managed Security is: Remote clients can resolve a service DNS name but requests are denied after a reorganization of WAN zones. The proposed verification does not establish that the required result is: Approved client requests complete across the revised zone while unauthorized client test traffic remains denied and logged.

B:

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. It is not sufficient proof of resolution for the stated Westport Managed Security incident: Remote clients can resolve a service DNS name but requests are denied after a reorganization of WAN zones.

D:

Action: Correct source-interface or source-address choices through supported probe and interface settings after verifying the actual routed path. Proof: The same test target responds to probes via the correct member without changing the approved health thresholds. The relevant Westport Managed Security observation is: Policy route tracing shows traffic leaves toward a newly named SD-WAN zone not referenced in the authorized security policy. Any successful correction still needs to verify: Approved client requests complete across the revised zone while unauthorized client test traffic remains denied and logged.

Question 341

For Evergreen Distribution Security, operators support business application SD-WAN steering and routing and are expected to preserve least-privilege access and predictable return paths. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Confirmed observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. What scoped change is justified by the observed evidence?

  1. Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change.
  2. Apply a documented alternative-member and health-aware strategy while preserving payment segmentation and return-path requirements.
  3. Correct approved SD-WAN rule order or match scope so the specific media policy is considered first.
  4. Validate the actual SASE-to-hub source and identity context and correct the approved HR-only rule rather than allowing every remote user.

Explanation

Correct Answer

A:

Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The intervention considered for Evergreen Distribution Security is: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. It follows this underlying rule: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table. Confirm the actual result: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

Incorrect Answers

B:

Another suggested intervention is: Apply a documented alternative-member and health-aware strategy while preserving payment segmentation and return-path requirements. It is not sufficient evidence of resolving the Evergreen Distribution Security condition: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The measurable outcome still required is: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

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 single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Its independent recovery check must establish: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

D:

Another option proposes: Validate the actual SASE-to-hub source and identity context and correct the approved HR-only rule rather than allowing every remote user. At Evergreen Distribution Security, the decisive evidence is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. That step alone does not demonstrate correction of the specified problem: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules.

Question 342

At Evergreen Distribution Security, the team administers business application SD-WAN steering and routing and must preserve least-privilege access and predictable return paths. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The team must verify the root cause before changing production settings. Which specific observation should determine the next investigation step?

  1. Session captures correlate affected application flows with a load-balancing strategy that does not preserve the partner's required source and routing context.
  2. The rule uses lowest-cost link preference without applying the verified real-time service SLA requirement that would reject the degraded link.
  3. The hub's route and SD-WAN rule selects the public underlay for the SASE client pool, not the intended encrypted overlay member.
  4. Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection.

Explanation

Correct Answer

D:

For Evergreen Distribution Security, the decisive evidence is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. It connects the reported failure to the actual operating dependency: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The relevant rule is: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

Incorrect Answers

A:

Session captures correlate affected application flows with a load-balancing strategy that does not preserve the partner's required source and routing context. It is not the discriminating clue in this record; that clue is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The Evergreen Distribution Security issue is: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules.

B:

The rule uses lowest-cost link preference without applying the verified real-time service SLA requirement that would reject the degraded link. The trace for Evergreen Distribution Security instead establishes: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. This is the clue to the issue actually described.

C:

The hub's route and SD-WAN rule selects the public underlay for the SASE client pool, not the intended encrypted overlay member. The reported Evergreen Distribution Security fault is: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The signal that actually distinguishes it is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection.

Question 343

For Evergreen Distribution Security, operators support business application SD-WAN steering and routing and are expected to preserve least-privilege access and predictable return paths. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Confirmed observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Proposed controlled action: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. What separate result verifies the change without hiding a second failure?

  1. ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.
  2. When jitter exceeds the threshold, the tested transaction selects the qualified backup while policy-denied traffic stays denied.
  3. An authorized bidirectional private session returns through the overlay without changing unrelated tenant routes.
  4. Normal authorized batch traffic stays on a suitable member and a sustained synthetic loss condition triggers the expected fallback.

Explanation

Correct Answer

A:

For Evergreen Distribution Security, an accepted fix must show: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. The initial diagnostic clue was: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The result therefore tests the stated failure rather than a separate control.

Incorrect Answers

B:

An alternative finding would be: When jitter exceeds the threshold, the tested transaction selects the qualified backup while policy-denied traffic stays denied. The applicable acceptance criterion at Evergreen Distribution Security is: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. That result is related to the original issue.

C:

An authorized bidirectional private session returns through the overlay without changing unrelated tenant routes. The recorded clue at Evergreen Distribution Security is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Closure has to validate the corresponding result: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

D:

Normal authorized batch traffic stays on a suitable member and a sustained synthetic loss condition triggers the expected fallback. That alone would not confirm correction of the Evergreen Distribution Security problem: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The necessary proof is: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

Question 344

At Evergreen Distribution Security, the team administers business application SD-WAN steering and routing and must preserve least-privilege access and predictable return paths. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Recorded observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Which operational principle governs the documented incident?

  1. The cheapest available link is not necessarily the path meeting an application's latency, jitter and loss objectives.
  2. Application-based SD-WAN steering requires a match between observed traffic classification and rule conditions.
  3. Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.
  4. Installed security software does not necessarily mean endpoint security state satisfies a current compliance requirement.

Explanation

Correct Answer

C:

The governing principle is: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table. The Evergreen Distribution Security record contains the corresponding signal: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. This accounts for the stated issue.

Incorrect Answers

A:

Another principle is: The cheapest available link is not necessarily the path meeting an application's latency, jitter and loss objectives. It is not enough to account for the recorded Evergreen Distribution Security evidence: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The applicable rule is: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

B:

Application-based SD-WAN steering requires a match between observed traffic classification and rule conditions. The documented Evergreen Distribution Security failure is: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The case is instead explained by: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

D:

Installed security software does not necessarily mean endpoint security state satisfies a current compliance requirement. At Evergreen Distribution Security, the reported issue is: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The stated observations instead follow from: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

Question 345

For Evergreen Distribution Security, operators support business application SD-WAN steering and routing and are expected to preserve least-privilege access and predictable return paths. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Confirmed observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Which approved change and separate test together resolve the issue?

  1. Action: Select the supported strategy that honors qualified SLA constraints while retaining agreed cost priorities among acceptable members. Proof: Degraded cheap transport is bypassed for real-time trials while acceptable normal links follow intended cost preference.
  2. Action: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. Proof: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.
  3. Action: Use current observed classification to correct the approved application or internet-service match and preserve overlay rules for private traffic. Proof: A synthetic approved SaaS session exits locally and a private ERP control remains on its authorized overlay.
  4. Action: Attach the approved intrusion prevention profile to the appropriate allowed policy and confirm required traffic visibility and signatures. Proof: A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful.

Explanation

Correct Answer

B:

Action: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. Proof: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. The Evergreen Distribution Security finding is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Independent completion must establish: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

Incorrect Answers

A:

Action: Select the supported strategy that honors qualified SLA constraints while retaining agreed cost priorities among acceptable members. Proof: Degraded cheap transport is bypassed for real-time trials while acceptable normal links follow intended cost preference. They do not directly establish recovery of the reported Evergreen Distribution Security problem: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Verification requires: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

C:

An alternative option suggests: Action: Use current observed classification to correct the approved application or internet-service match and preserve overlay rules for private traffic. Proof: A synthetic approved SaaS session exits locally and a private ERP control remains on its authorized overlay. The documented Evergreen Distribution Security problem calls for a check against: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. The original clue is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection.

D:

Action: Attach the approved intrusion prevention profile to the appropriate allowed policy and confirm required traffic visibility and signatures. Proof: A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful. At Evergreen Distribution Security, the actual distinguishing clue is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The related test must establish: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

Question 346

At Silverpeak Cloud Services, the team administers enterprise edge transport policy and route governance and must verify rule hits, correct route decisions and application availability. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Confirmed observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Which approved correction best addresses the documented root cause?

  1. Remove or reconcile the stale route within the approved routing plan and test traffic lookup for the affected destination.
  2. Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change.
  3. Review routing, NAT identity and upstream return-path design to restore an approved symmetric flow across eligible links.
  4. Add the verified secondary interface as an eligible SD-WAN member and test controlled failover without weakening firewall segmentation.

Explanation

Correct Answer

B:

The issue at Silverpeak Cloud Services is: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. A valid post-change result is: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

Incorrect Answers

A:

Although that step is: Remove or reconcile the stale route within the approved routing plan and test traffic lookup for the affected destination, the decisive observation here is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. That choice alone does not establish the needed correction at Silverpeak Cloud Services.

C:

The suggested alternative is: Review routing, NAT identity and upstream return-path design to restore an approved symmetric flow across eligible links. The case identifies the cause at Silverpeak Cloud Services using: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Implementing that step alone would not verify: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

D:

Another proposed action is: Add the verified secondary interface as an eligible SD-WAN member and test controlled failover without weakening firewall segmentation. In Silverpeak Cloud Services, the relevant evidence is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The focused correction should address the root condition shown by that clue.

Question 347

For Silverpeak Cloud Services, operators support enterprise edge transport policy and route governance and are expected to verify rule hits, correct route decisions and application availability. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The team must verify the root cause before changing production settings. What measured finding directly supports the recorded issue?

  1. Policy route tracing shows traffic leaves toward a newly named SD-WAN zone not referenced in the authorized security policy.
  2. Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection.
  3. The applicable SD-WAN service rule references the performance SLA but its allowed-member list contains only the impaired primary WAN.
  4. The report filter includes employee groups but omits a newly onboarded approved contractor group with active SASE sessions.

Explanation

Correct Answer

B:

Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. In Silverpeak Cloud Services, the problem described is: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules.

Incorrect Answers

A:

Another possibility is: Policy route tracing shows traffic leaves toward a newly named SD-WAN zone not referenced in the authorized security policy. The current case at Silverpeak Cloud Services contains a different identifying observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The relevant mechanism is: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

C:

The applicable SD-WAN service rule references the performance SLA but its allowed-member list contains only the impaired primary WAN. It does not directly identify the problem reported at Silverpeak Cloud Services. The determining evidence is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection.

D:

The report filter includes employee groups but omits a newly onboarded approved contractor group with active SASE sessions. It does not substantiate the particular Silverpeak Cloud Services condition: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The documented finding is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection.

Question 348

At Silverpeak Cloud Services, the team administers enterprise edge transport policy and route governance and must verify rule hits, correct route decisions and application availability. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Confirmed observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Proposed controlled action: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. Which independent test would establish that the original problem is resolved?

  1. A permitted SaaS test follows the intended eligible member and protected private prefixes preserve their separate routes.
  2. ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.
  3. An authorized bidirectional private session returns through the overlay without changing unrelated tenant routes.
  4. The prohibited test resource is blocked while the approved collaboration hostname remains accessible.

Explanation

Correct Answer

B:

The strongest acceptance check is: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. At Silverpeak Cloud Services, this confirms a result related to the recorded issue: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. It is consistent with: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

Incorrect Answers

A:

Another check would be: A permitted SaaS test follows the intended eligible member and protected private prefixes preserve their separate routes. The relevant Silverpeak Cloud Services problem requires a distinct success condition: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. The governing rule is: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

C:

An alternative test would show: An authorized bidirectional private session returns through the overlay without changing unrelated tenant routes. It does not show the required post-change result at Silverpeak Cloud Services: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. The original finding was: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection.

D:

The prohibited test resource is blocked while the approved collaboration hostname remains accessible. That is not sufficient to validate the stated Silverpeak Cloud Services failure, supported by: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The required check is: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

Question 349

For Silverpeak Cloud Services, operators support enterprise edge transport policy and route governance and are expected to verify rule hits, correct route decisions and application availability. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Recorded observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. What platform design concept best accounts for the symptoms?

  1. A manual fixed-member steering choice can override resilience expectations if fallback is not designed.
  2. Stateful applications and their remote peers may depend on stable path and source identity even when links individually work.
  3. Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.
  4. Per-member performance measurement requires the intended link to participate in the relevant SLA check.

Explanation

Correct Answer

C:

The technical relationship governing Silverpeak Cloud Services is: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table. The record shows: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. That observation is a direct consequence of the stated failure.

Incorrect Answers

A:

Another relationship would be: A manual fixed-member steering choice can override resilience expectations if fallback is not designed. It does not account for the issue reported by Silverpeak Cloud Services: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The applicable principle is: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

B:

Stateful applications and their remote peers may depend on stable path and source identity even when links individually work. The key evidence is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. That observation is explained by a different rule: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

D:

Per-member performance measurement requires the intended link to participate in the relevant SLA check. In Silverpeak Cloud Services, the actual observation is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The rule connected to that evidence is: Policy routing is a separate forwarding decision that can supersede assumptions from the conventional routing table.

Question 350

At Silverpeak Cloud Services, the team administers enterprise edge transport policy and route governance and must verify rule hits, correct route decisions and application availability. Operational incident: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Confirmed observation: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Which scoped action plus measurable success result should the team choose?

  1. Action: Advertise or install the approved branch prefix through the supported routing design and validate hub and spoke route symmetry. Proof: An authorized bidirectional private session returns through the overlay without changing unrelated tenant routes.
  2. Action: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. Proof: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.
  3. 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.
  4. Action: Attach the approved intrusion prevention profile to the appropriate allowed policy and confirm required traffic visibility and signatures. Proof: A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful.

Explanation

Correct Answer

B:

This pair is the bounded choice for Silverpeak Cloud Services: Action: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. Proof: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. The underlying issue is: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. Confirm the recorded outcome: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

Incorrect Answers

A:

Action: Advertise or install the approved branch prefix through the supported routing design and validate hub and spoke route symmetry. Proof: An authorized bidirectional private session returns through the overlay without changing unrelated tenant routes. The actual issue at Silverpeak Cloud Services is: A single ERP subnet takes an old next hop while all neighboring branch subnets correctly follow the new SD-WAN rules. The proposed verification does not establish that the required result is: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

C:

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 recorded evidence at Silverpeak Cloud Services is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. The correct outcome to measure is: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

D:

Action: Attach the approved intrusion prevention profile to the appropriate allowed policy and confirm required traffic visibility and signatures. Proof: A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful. The relevant Silverpeak Cloud Services observation is: Diagnostics identify a legacy policy-route match on the ERP source that forces a distinct egress path ahead of ordinary route selection. Any successful correction still needs to verify: ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

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