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

Question 710

At Silverpeak Cloud Services, the team administers remote access reporting and network security operations and must avoid drawing false conclusions from aggregated or filtered metrics. Operational incident: Operations believes voice uses the low-latency rule but the weekly SD-WAN log export contains only implicit-rule sessions. Confirmed observation: The application session's recorded rule identifier is the implicit/default strategy rather than the expected explicit real-time service policy. Which scoped action plus measurable success result should the team choose?

  1. Action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Proof: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.
  2. 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.
  3. Action: Validate event context, source identity and change timeline before escalating or weakening the new security profile. Proof: The synthetic alert is correctly classified and real independent malicious-signature controls still trigger the expected response.
  4. Action: Update approved rule source scope to the actual team subnet and check rule matching and precedence without broadening it to all endpoints. Proof: New team sessions hit the explicit intended service rule and out-of-scope devices continue using the default route.

Explanation

Correct Answer

B:

This pair is the bounded choice for Silverpeak Cloud Services: 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 underlying issue is: Operations believes voice uses the low-latency rule but the weekly SD-WAN log export contains only implicit-rule sessions. Confirm the recorded outcome: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.

Incorrect Answers

A:

Action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Proof: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. The actual issue at Silverpeak Cloud Services is: Operations believes voice uses the low-latency rule but the weekly SD-WAN log export contains only implicit-rule sessions. The proposed verification does not establish that the required result is: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.

C:

Action: Validate event context, source identity and change timeline before escalating or weakening the new security profile. Proof: The synthetic alert is correctly classified and real independent malicious-signature controls still trigger the expected response. The recorded evidence at Silverpeak Cloud Services is: The application session's recorded rule identifier is the implicit/default strategy rather than the expected explicit real-time service policy. The correct outcome to measure is: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.

D:

Action: Update approved rule source scope to the actual team subnet and check rule matching and precedence without broadening it to all endpoints. Proof: New team sessions hit the explicit intended service rule and out-of-scope devices continue using the default route. The relevant Silverpeak Cloud Services observation is: The application session's recorded rule identifier is the implicit/default strategy rather than the expected explicit real-time service policy. Any successful correction still needs to verify: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.

Question 711

For Redwood Financial Applications, operators support SD-WAN telemetry and FortiSASE incident analysis and are expected to correlate trusted event evidence, time windows and source identities. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Confirmed observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Which supported administrator action should address this issue with the least unrelated impact?

  1. Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact.
  2. Resolve member IDs and interface history for the reporting period, then update the saved report to current sources.
  3. Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment.
  4. Check the FortiSASE managed endpoint posture record and corresponding compliance or access logs before granting an exception.

Explanation

Correct Answer

A:

SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The intervention considered for Redwood Financial Applications is: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. It follows this underlying rule: Log filtering can hide real link instability even when underlying events are recorded correctly. Confirm the actual result: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Incorrect Answers

B:

Another suggested intervention is: Resolve member IDs and interface history for the reporting period, then update the saved report to current sources. It is not sufficient evidence of resolving the Redwood Financial Applications condition: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The measurable outcome still required is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

C:

Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. The reported failure at Redwood Financial Applications is: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Its independent recovery check must establish: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

D:

Another option proposes: Check the FortiSASE managed endpoint posture record and corresponding compliance or access logs before granting an exception. At Redwood Financial Applications, the decisive evidence is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. That step alone does not demonstrate correction of the specified problem: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review.

Question 712

At Redwood Financial Applications, the team administers SD-WAN telemetry and FortiSASE incident analysis and must correlate trusted event evidence, time windows and source identities. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The team must verify the root cause before changing production settings. Which piece of evidence distinguishes this cause from unrelated symptoms?

  1. Per-user FortiSASE security logs show repeated high-risk destination attempts by one identity while aggregate counts remain modest.
  2. SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.
  3. Packet captures show health probes leave with a source address not routable via the provider segment associated with that member.
  4. SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window.

Explanation

Correct Answer

D:

For Redwood Financial Applications, the decisive evidence is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. It connects the reported failure to the actual operating dependency: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The relevant rule is: Log filtering can hide real link instability even when underlying events are recorded correctly.

Incorrect Answers

A:

Per-user FortiSASE security logs show repeated high-risk destination attempts by one identity while aggregate counts remain modest. It is not the discriminating clue in this record; that clue is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The Redwood Financial Applications issue is: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review.

B:

SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The trace for Redwood Financial Applications instead establishes: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. This is the clue to the issue actually described.

C:

Packet captures show health probes leave with a source address not routable via the provider segment associated with that member. The reported Redwood Financial Applications fault is: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The signal that actually distinguishes it is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window.

Question 713

For Redwood Financial Applications, operators support SD-WAN telemetry and FortiSASE incident analysis and are expected to correlate trusted event evidence, time windows and source identities. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Confirmed observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Proposed controlled action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Which accepted outcome confirms the intended behavior?

  1. The report includes contractor traffic for the correct period and individual access remains properly limited.
  2. A corrected test session uses the private route and its log confirms the intended policy and member selection.
  3. The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.
  4. The exact failed requirement is identified, remediated, and then access recovers without disabling broader posture enforcement.

Explanation

Correct Answer

C:

The reported failure at Redwood Financial Applications is: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The necessary independent result is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. It tests recovery against the original evidence: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window.

Incorrect Answers

A:

The report includes contractor traffic for the correct period and individual access remains properly limited. The acceptance condition for the stated Redwood Financial Applications fault is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. The tests do not measure the same outcome.

B:

An alternative finding would be: A corrected test session uses the private route and its log confirms the intended policy and member selection. The applicable acceptance criterion at Redwood Financial Applications is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. That result is related to the original issue.

D:

The exact failed requirement is identified, remediated, and then access recovers without disabling broader posture enforcement. That alone would not confirm correction of the Redwood Financial Applications problem: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The necessary proof is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Question 714

At Redwood Financial Applications, the team administers SD-WAN telemetry and FortiSASE incident analysis and must correlate trusted event evidence, time windows and source identities. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Recorded observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Which network security or traffic-steering principle explains this behavior?

  1. Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry.
  2. Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.
  3. Log filtering can hide real link instability even when underlying events are recorded correctly.
  4. Steering depends on the match actually installed for the application, not only on how the business names the service.

Explanation

Correct Answer

C:

The governing principle is: Log filtering can hide real link instability even when underlying events are recorded correctly. The Redwood Financial Applications record contains the corresponding signal: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. This accounts for the stated issue.

Incorrect Answers

A:

Another principle is: Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry. It is not enough to account for the recorded Redwood Financial Applications evidence: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The applicable rule is: Log filtering can hide real link instability even when underlying events are recorded correctly.

B:

Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient. The documented Redwood Financial Applications failure is: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The case is instead explained by: Log filtering can hide real link instability even when underlying events are recorded correctly.

D:

Steering depends on the match actually installed for the application, not only on how the business names the service. At Redwood Financial Applications, the reported issue is: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The stated observations instead follow from: Log filtering can hide real link instability even when underlying events are recorded correctly.

Question 715

For Redwood Financial Applications, operators support SD-WAN telemetry and FortiSASE incident analysis and are expected to correlate trusted event evidence, time windows and source identities. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Confirmed observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. What remediation-and-validation combination most directly addresses this incident?

  1. Action: Validate event context, source identity and change timeline before escalating or weakening the new security profile. Proof: The synthetic alert is correctly classified and real independent malicious-signature controls still trigger the expected response.
  2. Action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Proof: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.
  3. Action: Expand the authorized analytics group scope for the stated reporting purpose and rerun without exposing unrelated personal data. Proof: The report includes contractor traffic for the correct period and individual access remains properly limited.
  4. 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.

Explanation

Correct Answer

B:

Action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Proof: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. The Redwood Financial Applications finding is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Independent completion must establish: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Incorrect Answers

A:

Action: Validate event context, source identity and change timeline before escalating or weakening the new security profile. Proof: The synthetic alert is correctly classified and real independent malicious-signature controls still trigger the expected response. They do not directly establish recovery of the reported Redwood Financial Applications problem: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Verification requires: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

C:

An alternative option suggests: Action: Expand the authorized analytics group scope for the stated reporting purpose and rerun without exposing unrelated personal data. Proof: The report includes contractor traffic for the correct period and individual access remains properly limited. The documented Redwood Financial Applications problem calls for a check against: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. The original clue is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window.

D:

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. At Redwood Financial Applications, the actual distinguishing clue is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The related test must establish: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Question 716

At Westport Managed Security, the team administers remote access reporting and network security operations and must avoid drawing false conclusions from aggregated or filtered metrics. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Confirmed observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. What scoped change is justified by the observed evidence?

  1. Correlate user, endpoint posture and actual threat categorization and initiate proportionate identity and endpoint investigation.
  2. Trace the application and source selectors against the rule definition and correct the scoped match if authorized.
  3. Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact.
  4. Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change.

Explanation

Correct Answer

C:

At Westport Managed Security, the key finding is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The corresponding corrective action is: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Log filtering can hide real link instability even when underlying events are recorded correctly. The separate acceptance check is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Incorrect Answers

A:

Although that step is: Correlate user, endpoint posture and actual threat categorization and initiate proportionate identity and endpoint investigation, the decisive observation here is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. That choice alone does not establish the needed correction at Westport Managed Security.

B:

An alternative action is: Trace the application and source selectors against the rule definition and correct the scoped match if authorized. The observed evidence in Westport Managed Security instead establishes: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. A relevant response must address that observation and confirm: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

D:

Another proposed action is: Reconcile the explicit policy route with the approved SD-WAN service design and test the ERP-only change. In Westport Managed Security, the relevant evidence is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The focused correction should address the root condition shown by that clue.

Question 717

For Westport Managed Security, operators support remote access reporting and network security operations and are expected to avoid drawing false conclusions from aggregated or filtered metrics. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The team must verify the root cause before changing production settings. Which specific observation should determine the next investigation step?

  1. SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.
  2. One export uses UTC and the other uses tenant-local time, moving the same sessions across a day boundary.
  3. SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window.
  4. Packet captures show health probes leave with a source address not routable via the provider segment associated with that member.

Explanation

Correct Answer

C:

The question asks for the distinguishing observation, which is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. It addresses the reported Westport Managed Security failure: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The causal relationship is: Log filtering can hide real link instability even when underlying events are recorded correctly.

Incorrect Answers

A:

Another possibility is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The current case at Westport Managed Security contains a different identifying observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The relevant mechanism is: Log filtering can hide real link instability even when underlying events are recorded correctly.

B:

One export uses UTC and the other uses tenant-local time, moving the same sessions across a day boundary. The original Westport Managed Security observation is instead: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. That is the evidence tied to the stated failure.

D:

Packet captures show health probes leave with a source address not routable via the provider segment associated with that member. It does not substantiate the particular Westport Managed Security condition: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The documented finding is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window.

Question 718

At Westport Managed Security, the team administers remote access reporting and network security operations and must avoid drawing false conclusions from aggregated or filtered metrics. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Confirmed observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Proposed controlled action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. What separate result verifies the change without hiding a second failure?

  1. A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.
  2. The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs.
  3. The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.
  4. During controlled added delay, voice moves to an acceptable member without unnecessary steering of unrelated bulk sessions.

Explanation

Correct Answer

C:

The measurable recovery condition for Westport Managed Security is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. This checks the actual failure revealed by: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Log filtering can hide real link instability even when underlying events are recorded correctly.

Incorrect Answers

A:

Another check would be: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing. The relevant Westport Managed Security problem requires a distinct success condition: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. The governing rule is: Log filtering can hide real link instability even when underlying events are recorded correctly.

B:

The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs. It is not the evidence needed to close the reported issue. The proper Westport Managed Security success measure is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

D:

During controlled added delay, voice moves to an acceptable member without unnecessary steering of unrelated bulk sessions. That is not sufficient to validate the stated Westport Managed Security failure, supported by: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The required check is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Question 719

For Westport Managed Security, operators support remote access reporting and network security operations and are expected to avoid drawing false conclusions from aggregated or filtered metrics. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Recorded observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Which operational principle governs the documented incident?

  1. Reporting scope filters determine measured populations; missing users do not mean no traffic occurred.
  2. Aggregate security counts can conceal concentrated identity-specific abuse patterns.
  3. Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.
  4. Log filtering can hide real link instability even when underlying events are recorded correctly.

Explanation

Correct Answer

D:

Log filtering can hide real link instability even when underlying events are recorded correctly. At Westport Managed Security, the technical clue is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. That explains the reported condition: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review.

Incorrect Answers

A:

Another relationship would be: Reporting scope filters determine measured populations; missing users do not mean no traffic occurred. It does not account for the issue reported by Westport Managed Security: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The applicable principle is: Log filtering can hide real link instability even when underlying events are recorded correctly.

B:

Aggregate security counts can conceal concentrated identity-specific abuse patterns. The key evidence is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. That observation is explained by a different rule: Log filtering can hide real link instability even when underlying events are recorded correctly.

C:

Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub. The failure at Westport Managed Security is: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The operating rule directly related to that failure is: Log filtering can hide real link instability even when underlying events are recorded correctly.

Question 720

At Westport Managed Security, the team administers remote access reporting and network security operations and must avoid drawing false conclusions from aggregated or filtered metrics. Operational incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. Confirmed observation: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Which approved change and separate test together resolve the issue?

  1. 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.
  2. Action: Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. Proof: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.
  3. Action: Correct supported identity group synchronization and mapped SASE user/group authorization without a blanket accept rule. Proof: The approved employee obtains their specific access policy and a control identity outside the group remains restricted.
  4. Action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Proof: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Explanation

Correct Answer

D:

The selection links action to a separately checked outcome: Action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Proof: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. It is grounded in the Westport Managed Security clue: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. Closure must show: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Incorrect Answers

A:

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 actual issue at Westport Managed Security is: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review. The proposed verification does not establish that the required result is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

B:

Action: Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. Proof: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. It is not sufficient proof of resolution for the stated Westport Managed Security incident: A WAN circuit repeatedly changes state while the operational dashboard appears stable during incident review.

C:

Action: Correct supported identity group synchronization and mapped SASE user/group authorization without a blanket accept rule. Proof: The approved employee obtains their specific access policy and a control identity outside the group remains restricted. The recorded evidence at Westport Managed Security is: SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window. The correct outcome to measure is: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

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