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

Question 490

At Silverpeak Cloud Services, the team administers hybrid remote-user and FortiGate private access integration and must preserve correct cloud security service onboarding and private-route scope. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Confirmed observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. What remediation-and-validation combination most directly addresses this incident?

  1. Action: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. Proof: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.
  2. Action: Issue a fresh supported tenant-scoped onboarding invitation and verify enrollment using an approved test endpoint. Proof: The authorized managed client registers to the intended tenant and receives its permitted connection configuration.
  3. Action: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Proof: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.
  4. Action: Add the verified overlay member to an appropriate service-specific performance SLA and establish a valid reachable probe target. Proof: Its own latency and loss observations appear and a controlled impairment updates its status without changing unrelated paths.

Explanation

Correct Answer

C:

The option addresses the actual fault and includes measurable proof: Action: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Proof: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. The case evidence at Silverpeak Cloud Services is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The acceptance target is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Incorrect Answers

A:

Action: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. Proof: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. The actual issue at Silverpeak Cloud Services is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The proposed verification does not establish that the required result is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

B:

Action: Issue a fresh supported tenant-scoped onboarding invitation and verify enrollment using an approved test endpoint. Proof: The authorized managed client registers to the intended tenant and receives its permitted connection configuration. It is not sufficient proof of resolution for the stated Silverpeak Cloud Services incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall.

D:

Action: Add the verified overlay member to an appropriate service-specific performance SLA and establish a valid reachable probe target. Proof: Its own latency and loss observations appear and a controlled impairment updates its status without changing unrelated paths. The relevant Silverpeak Cloud Services observation is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Any successful correction still needs to verify: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Question 491

For Redwood Financial Applications, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Confirmed observation: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. What scoped change is justified by the observed evidence?

  1. Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection.
  2. Issue a fresh supported tenant-scoped onboarding invitation and verify enrollment using an approved test endpoint.
  3. Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks.
  4. Apply the licensed supported OS posture condition to the narrowly authorized privileged access group and retest endpoints.

Explanation

Correct Answer

C:

At Redwood Financial Applications, the evidence establishes the immediate concern: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The appropriate response is: Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks. The causal rule is: Transport establishment alone does not guarantee BGP route exchange between private-access peers. The required outcome is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

Incorrect Answers

A:

Another proposed response centers on: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. The reported Redwood Financial Applications failure is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The decisive record shows: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability.

B:

Another suggested intervention is: Issue a fresh supported tenant-scoped onboarding invitation and verify enrollment using an approved test endpoint. It is not sufficient evidence of resolving the Redwood Financial Applications condition: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The measurable outcome still required is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

D:

Another option proposes: Apply the licensed supported OS posture condition to the narrowly authorized privileged access group and retest endpoints. At Redwood Financial Applications, the decisive evidence is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. That step alone does not demonstrate correction of the specified problem: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer.

Question 492

At Redwood Financial Applications, the team administers FortiSASE tenant administration and user enrollment and must enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The team must verify the root cause before changing production settings. Which specific observation should determine the next investigation step?

  1. The installed client's preconfigured invitation or bootstrap identifiers are bound to a different tenant than the approved employer.
  2. BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability.
  3. The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.
  4. One export uses UTC and the other uses tenant-local time, moving the same sessions across a day boundary.

Explanation

Correct Answer

B:

The most relevant recorded signal is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. That finding belongs to the observed problem at Redwood Financial Applications: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The underlying relationship is: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

Incorrect Answers

A:

The installed client's preconfigured invitation or bootstrap identifiers are bound to a different tenant than the approved employer. It is not the discriminating clue in this record; that clue is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The Redwood Financial Applications issue is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer.

C:

The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The reported Redwood Financial Applications fault is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The signal that actually distinguishes it is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability.

D:

One export uses UTC and the other uses tenant-local time, moving the same sessions across a day boundary. At Redwood Financial Applications, the recorded condition is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The particular evidence supporting it is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability.

Question 493

For Redwood Financial Applications, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Confirmed observation: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Proposed controlled action: Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks. What separate result verifies the change without hiding a second failure?

  1. A controlled contractor device registers only in its authorized organization and receives correct scoped access.
  2. The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.
  3. A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.
  4. A controlled full login succeeds across failover tests while other independent internet flows retain eligible balancing.

Explanation

Correct Answer

B:

The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent. In Redwood Financial Applications, the evidence requiring that check is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability.

Incorrect Answers

A:

A controlled contractor device registers only in its authorized organization and receives correct scoped access. The acceptance condition for the stated Redwood Financial Applications fault is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent. The tests do not measure the same outcome.

C:

A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. The recorded clue at Redwood Financial Applications is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Closure has to validate the corresponding result: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

D:

A controlled full login succeeds across failover tests while other independent internet flows retain eligible balancing. That alone would not confirm correction of the Redwood Financial Applications problem: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The necessary proof is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

Question 494

At Redwood Financial Applications, the team administers FortiSASE tenant administration and user enrollment and must enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Recorded observation: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Which operational principle governs the documented incident?

  1. Client connection profiles and authorization groups must reflect the intended access class rather than simply successful sign-in.
  2. Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.
  3. Transport establishment alone does not guarantee BGP route exchange between private-access peers.
  4. Health checks must measure a path relevant to the protected application; unrelated reachable services can hide partial failures.

Explanation

Correct Answer

C:

The governing principle is: Transport establishment alone does not guarantee BGP route exchange between private-access peers. The Redwood Financial Applications record contains the corresponding signal: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. This accounts for the stated issue.

Incorrect Answers

A:

Another principle is: Client connection profiles and authorization groups must reflect the intended access class rather than simply successful sign-in. It is not enough to account for the recorded Redwood Financial Applications evidence: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The applicable rule is: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

B:

Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub. The documented Redwood Financial Applications failure is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The case is instead explained by: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

D:

Health checks must measure a path relevant to the protected application; unrelated reachable services can hide partial failures. At Redwood Financial Applications, the reported issue is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The stated observations instead follow from: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

Question 495

For Redwood Financial Applications, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Confirmed observation: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Which approved change and separate test together resolve the issue?

  1. Action: Review supported FortiSASE access location and connection selection settings and validate region and policy requirements. Proof: Test users connect through the approved suitable service region and latency improves without loss of security inspection.
  2. Action: Configure approved split DNS or internal resolver forwarding for that specific namespace and validate private service reachability. Proof: The corporate name resolves to the approved private target and a permitted SASE client completes its secured private session.
  3. Action: Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks. Proof: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.
  4. Action: Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope. Proof: The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results.

Explanation

Correct Answer

C:

Action: Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks. Proof: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent. The Redwood Financial Applications incident is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The required result is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

Incorrect Answers

A:

Action: Review supported FortiSASE access location and connection selection settings and validate region and policy requirements. Proof: Test users connect through the approved suitable service region and latency improves without loss of security inspection. They do not directly establish recovery of the reported Redwood Financial Applications problem: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Verification requires: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

B:

Action: Configure approved split DNS or internal resolver forwarding for that specific namespace and validate private service reachability. Proof: The corporate name resolves to the approved private target and a permitted SASE client completes its secured private session. It would not by itself demonstrate correction of the Redwood Financial Applications finding: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The required outcome is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

D:

Action: Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope. Proof: The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results. At Redwood Financial Applications, the actual distinguishing clue is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The related test must establish: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

Question 496

At Westport Managed Security, the team administers hybrid remote-user and FortiGate private access integration and must preserve correct cloud security service onboarding and private-route scope. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Confirmed observation: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Which approved correction best addresses the documented root cause?

  1. Restrict supported FortiSASE client profile and user-group mapping to the approved contractor role and retest enrollment.
  2. Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks.
  3. Restore the baseline and implement a supported narrower exception assigned to only the permitted user group.
  4. Review routing, NAT identity and upstream return-path design to restore an approved symmetric flow across eligible links.

Explanation

Correct Answer

B:

The issue at Westport Managed Security is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks. A valid post-change result is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

Incorrect Answers

A:

Although that step is: Restrict supported FortiSASE client profile and user-group mapping to the approved contractor role and retest enrollment, the decisive observation here is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. That choice alone does not establish the needed correction at Westport Managed Security.

C:

The suggested alternative is: Restore the baseline and implement a supported narrower exception assigned to only the permitted user group. The case identifies the cause at Westport Managed Security using: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Implementing that step alone would not verify: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

D:

Another proposed action is: Review routing, NAT identity and upstream return-path design to restore an approved symmetric flow across eligible links. In Westport Managed Security, the relevant evidence is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The focused correction should address the root condition shown by that clue.

Question 497

For Westport Managed Security, operators support hybrid remote-user and FortiGate private access integration and are expected to preserve correct cloud security service onboarding and private-route scope. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The team must verify the root cause before changing production settings. What measured finding directly supports the recorded issue?

  1. BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability.
  2. Client DNS diagnostics show internal domain rules are not applied for the application namespace while the private route exists.
  3. Audit records show a shared baseline security profile was edited instead of creating a department-specific approved policy scope.
  4. The policy includes the correct SaaS service definition but the active SD-WAN service rule still references a different application category.

Explanation

Correct Answer

A:

BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. It supports investigation of the Westport Managed Security issue: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The governing technical reason is: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

Incorrect Answers

B:

Client DNS diagnostics show internal domain rules are not applied for the application namespace while the private route exists. The original Westport Managed Security observation is instead: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. That is the evidence tied to the stated failure.

C:

Audit records show a shared baseline security profile was edited instead of creating a department-specific approved policy scope. It does not directly identify the problem reported at Westport Managed Security. The determining evidence is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability.

D:

The policy includes the correct SaaS service definition but the active SD-WAN service rule still references a different application category. It does not substantiate the particular Westport Managed Security condition: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The documented finding is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability.

Question 498

At Westport Managed Security, the team administers hybrid remote-user and FortiGate private access integration and must preserve correct cloud security service onboarding and private-route scope. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Confirmed observation: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Proposed controlled action: Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks. Which independent test would establish that the original problem is resolved?

  1. Test users connect through the approved suitable service region and latency improves without loss of security inspection.
  2. The authorized managed client registers to the intended tenant and receives its permitted connection configuration.
  3. The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.
  4. ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths.

Explanation

Correct Answer

C:

The measurable recovery condition for Westport Managed Security is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent. This checks the actual failure revealed by: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Transport establishment alone does not guarantee BGP route exchange between private-access peers.

Incorrect Answers

A:

Another check would be: Test users connect through the approved suitable service region and latency improves without loss of security inspection. The relevant Westport Managed Security problem requires a distinct success condition: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent. The governing rule is: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

B:

The authorized managed client registers to the intended tenant and receives its permitted connection configuration. It is not the evidence needed to close the reported issue. The proper Westport Managed Security success measure is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

D:

ERP flows use the intended SD-WAN strategy and other services retain their existing selected paths. That is not sufficient to validate the stated Westport Managed Security failure, supported by: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The required check is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

Question 499

For Westport Managed Security, operators support hybrid remote-user and FortiGate private access integration and are expected to preserve correct cloud security service onboarding and private-route scope. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Recorded observation: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. What platform design concept best accounts for the symptoms?

  1. Tenant-wide policy defaults affect more identities than a narrowly bound user-group exception.
  2. Application-specific DNS resolution must align with private routes for split-access designs to work.
  3. Transport establishment alone does not guarantee BGP route exchange between private-access peers.
  4. Health checks must measure a path relevant to the protected application; unrelated reachable services can hide partial failures.

Explanation

Correct Answer

C:

The technical relationship governing Westport Managed Security is: Transport establishment alone does not guarantee BGP route exchange between private-access peers. The record shows: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. That observation is a direct consequence of the stated failure.

Incorrect Answers

A:

Another relationship would be: Tenant-wide policy defaults affect more identities than a narrowly bound user-group exception. It does not account for the issue reported by Westport Managed Security: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The applicable principle is: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

B:

Application-specific DNS resolution must align with private routes for split-access designs to work. The key evidence is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. That observation is explained by a different rule: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

D:

Health checks must measure a path relevant to the protected application; unrelated reachable services can hide partial failures. In Westport Managed Security, the actual observation is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The rule connected to that evidence is: Transport establishment alone does not guarantee BGP route exchange between private-access peers.

Question 500

At Westport Managed Security, the team administers hybrid remote-user and FortiGate private access integration and must preserve correct cloud security service onboarding and private-route scope. Operational incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. Confirmed observation: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Which scoped action plus measurable success result should the team choose?

  1. Action: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. Proof: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.
  2. Action: Confirm the licensed feature and approved entitlement before configuring a supported design or obtaining authorized upgrade. Proof: A sanctioned test user gains only subscribed access after an approved license change, while unsupported options remain unavailable.
  3. Action: Trace the application and source selectors against the rule definition and correct the scoped match if authorized. Proof: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.
  4. Action: Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks. Proof: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

Explanation

Correct Answer

D:

The selection links action to a separately checked outcome: Action: Correct the supported BGP neighbor and approved routing settings on both SASE and FortiGate sides without advertising unauthorized networks. Proof: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent. It is grounded in the Westport Managed Security clue: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. Closure must show: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

Incorrect Answers

A:

Action: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. Proof: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. The actual issue at Westport Managed Security is: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer. The proposed verification does not establish that the required result is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

B:

Action: Confirm the licensed feature and approved entitlement before configuring a supported design or obtaining authorized upgrade. Proof: A sanctioned test user gains only subscribed access after an approved license change, while unsupported options remain unavailable. It is not sufficient proof of resolution for the stated Westport Managed Security incident: A new secure private access connection establishes its transport but does not exchange routes with the FortiGate peer.

C:

Action: Trace the application and source selectors against the rule definition and correct the scoped match if authorized. Proof: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing. The recorded evidence at Westport Managed Security is: BGP session logs show a peer address or autonomous system mismatch despite established encrypted reachability. The correct outcome to measure is: The peer becomes established and approved private prefixes appear in both routing tables while blocked prefixes remain absent.

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