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

Question 730

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: A branch performance report claims one provider exceeded latency targets, but current probes show that provider healthy. Confirmed observation: The saved analytics widget references an old SD-WAN member identifier reassigned during a migration. What remediation-and-validation combination most directly addresses this incident?

  1. Action: Correlate user, endpoint posture and actual threat categorization and initiate proportionate identity and endpoint investigation. Proof: The suspicious test identity is isolated for authorized review while other unaffected users continue normal browsing.
  2. Action: Separate allowed-session volume from threat-profile decisions and show correct denominators and explicit inspection enforcement outcomes. Proof: A control report distinguishes permitted business traffic from actual security enforcement and supports independent raw-log reconciliation.
  3. Action: Resolve member IDs and interface history for the reporting period, then update the saved report to current sources. Proof: The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs.
  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:

The option addresses the actual fault and includes measurable proof: Action: Resolve member IDs and interface history for the reporting period, then update the saved report to current sources. Proof: The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs. The case evidence at Silverpeak Cloud Services is: The saved analytics widget references an old SD-WAN member identifier reassigned during a migration. The acceptance target is: The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs.

Incorrect Answers

A:

Action: Correlate user, endpoint posture and actual threat categorization and initiate proportionate identity and endpoint investigation. Proof: The suspicious test identity is isolated for authorized review while other unaffected users continue normal browsing. The actual issue at Silverpeak Cloud Services is: A branch performance report claims one provider exceeded latency targets, but current probes show that provider healthy. The proposed verification does not establish that the required result is: The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs.

B:

Action: Separate allowed-session volume from threat-profile decisions and show correct denominators and explicit inspection enforcement outcomes. Proof: A control report distinguishes permitted business traffic from actual security enforcement and supports independent raw-log reconciliation. It is not sufficient proof of resolution for the stated Silverpeak Cloud Services incident: A branch performance report claims one provider exceeded latency targets, but current probes show that provider healthy.

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. The relevant Silverpeak Cloud Services observation is: The saved analytics widget references an old SD-WAN member identifier reassigned during a migration. Any successful correction still needs to verify: The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs.

Question 731

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Confirmed observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. What scoped change is justified by the observed evidence?

  1. Normalize the source time zone and explicit period boundaries before interpreting differences or opening duplicate incidents.
  2. Validate event context, source identity and change timeline before escalating or weakening the new security profile.
  3. Restore supported telemetry synchronization or re-evaluation and verify fresh posture data before altering the policy baseline.
  4. Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds.

Explanation

Correct Answer

D:

For Redwood Financial Applications, the recorded clue is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The bounded correction is: Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient. Confirm recovery using this outcome: A corrected test session uses the private route and its log confirms the intended policy and member selection.

Incorrect Answers

A:

Another proposed response centers on: Normalize the source time zone and explicit period boundaries before interpreting differences or opening duplicate incidents. The reported Redwood Financial Applications failure is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The decisive record shows: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.

B:

Another suggested intervention is: Validate event context, source identity and change timeline before escalating or weakening the new security profile. It is not sufficient evidence of resolving the Redwood Financial Applications condition: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The measurable outcome still required is: A corrected test session uses the private route and its log confirms the intended policy and member selection.

C:

Restore supported telemetry synchronization or re-evaluation and verify fresh posture data before altering the policy baseline. The reported failure at Redwood Financial Applications is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Its independent recovery check must establish: A corrected test session uses the private route and its log confirms the intended policy and member selection.

Question 732

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The team must verify the root cause before changing production settings. Which specific observation should determine the next investigation step?

  1. Security logs show a blocked web object and a user ID, but the device telemetry and action result are not joined for the same incident.
  2. SD-WAN event logs contain down/up changes but the report filter excludes the relevant event subtype and time window.
  3. SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.
  4. The SPA or connected SD-WAN overlay is established, but the FortiSASE routing view lacks the branch private application subnet.

Explanation

Correct Answer

C:

At Redwood Financial Applications, the reported condition is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The specifically relevant observation is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. That distinction is explained by: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

Incorrect Answers

A:

Security logs show a blocked web object and a user ID, but the device telemetry and action result are not joined for the same incident. It is not the discriminating clue in this record; that clue is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The Redwood Financial Applications issue is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics.

B:

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

D:

The SPA or connected SD-WAN overlay is established, but the FortiSASE routing view lacks the branch private application subnet. At Redwood Financial Applications, the recorded condition is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The particular evidence supporting it is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.

Question 733

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Confirmed observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Proposed controlled action: Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. 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 synthetic alert is correctly classified and real independent malicious-signature controls still trigger the expected response.
  3. During controlled added delay, voice moves to an acceptable member without unnecessary steering of unrelated bulk sessions.
  4. A corrected test session uses the private route and its log confirms the intended policy and member selection.

Explanation

Correct Answer

D:

The required post-change observation is: A corrected test session uses the private route and its log confirms the intended policy and member selection. It is tied to the original Redwood Financial Applications observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The operating rule is: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

Incorrect Answers

A:

A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing. The acceptance condition for the stated Redwood Financial Applications fault is: A corrected test session uses the private route and its log confirms the intended policy and member selection. The tests do not measure the same outcome.

B:

An alternative finding would be: The synthetic alert is correctly classified and real independent malicious-signature controls still trigger the expected response. The applicable acceptance criterion at Redwood Financial Applications is: A corrected test session uses the private route and its log confirms the intended policy and member selection. That result is related to the original issue.

C:

During controlled added delay, voice moves to an acceptable member without unnecessary steering of unrelated bulk sessions. The recorded clue at Redwood Financial Applications is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Closure has to validate the corresponding result: A corrected test session uses the private route and its log confirms the intended policy and member selection.

Question 734

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Recorded observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Which operational principle governs the documented incident?

  1. Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.
  2. A healthy path measurement cannot establish that a specific SD-WAN steering rule actually matched.
  3. Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.
  4. Security profile configuration does not enforce filtering unless the active policy attaches the intended profile.

Explanation

Correct Answer

A:

Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient. The Redwood Financial Applications incident is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The deciding clue is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.

Incorrect Answers

B:

A healthy path measurement cannot establish that a specific SD-WAN steering rule actually matched. The documented Redwood Financial Applications failure is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The case is instead explained by: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

C:

An alternative explanation is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response. It is not the reason established by the Redwood Financial Applications clue: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The relevant causal relationship is: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

D:

Security profile configuration does not enforce filtering unless the active policy attaches the intended profile. At Redwood Financial Applications, the reported issue is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The stated observations instead follow from: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

Question 735

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Confirmed observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Which approved change and separate test together resolve the issue?

  1. Action: Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. Proof: A corrected test session uses the private route and its log confirms the intended policy and member selection.
  2. Action: Separate allowed-session volume from threat-profile decisions and show correct denominators and explicit inspection enforcement outcomes. Proof: A control report distinguishes permitted business traffic from actual security enforcement and supports independent raw-log reconciliation.
  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: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. Proof: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss.

Explanation

Correct Answer

A:

The documented fault is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The selected change-plus-verification is: Action: Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. Proof: A corrected test session uses the private route and its log confirms the intended policy and member selection. That pair responds to the Redwood Financial Applications observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.

Incorrect Answers

B:

Action: Separate allowed-session volume from threat-profile decisions and show correct denominators and explicit inspection enforcement outcomes. Proof: A control report distinguishes permitted business traffic from actual security enforcement and supports independent raw-log reconciliation. It would not by itself demonstrate correction of the Redwood Financial Applications finding: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The required outcome is: A corrected test session uses the private route and its log confirms the intended policy and member selection.

C:

An alternative option suggests: 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 documented Redwood Financial Applications problem calls for a check against: A corrected test session uses the private route and its log confirms the intended policy and member selection. The original clue is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.

D:

Action: Remove or reconcile the obsolete route with approved routing design and validate route lookup for both ordinary and failover traffic. Proof: A controlled route inspection selects the intended SD-WAN route during normal operation and the approved fallback during link loss. At Redwood Financial Applications, the actual distinguishing clue is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The related test must establish: A corrected test session uses the private route and its log confirms the intended policy and member selection.

Question 736

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Confirmed observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Which approved correction best addresses the documented root cause?

  1. Resolve member IDs and interface history for the reporting period, then update the saved report to current sources.
  2. Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds.
  3. Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment.
  4. Tune supported fail/recovery behavior and select SLA criteria based on documented service stability requirements rather than suppressing health checks.

Explanation

Correct Answer

B:

The issue at Westport Managed Security is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. A valid post-change result is: A corrected test session uses the private route and its log confirms the intended policy and member selection.

Incorrect Answers

A:

Although that step is: Resolve member IDs and interface history for the reporting period, then update the saved report to current sources, the decisive observation here is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. That choice alone does not establish the needed correction at Westport Managed Security.

C:

The suggested alternative is: Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. The case identifies the cause at Westport Managed Security using: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Implementing that step alone would not verify: A corrected test session uses the private route and its log confirms the intended policy and member selection.

D:

Another proposed action is: Tune supported fail/recovery behavior and select SLA criteria based on documented service stability requirements rather than suppressing health checks. In Westport Managed Security, the relevant evidence is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The focused correction should address the root condition shown by that clue.

Question 737

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The team must verify the root cause before changing production settings. What measured finding directly supports the recorded issue?

  1. The report filter includes employee groups but omits a newly onboarded approved contractor group with active SASE sessions.
  2. The saved analytics widget references an old SD-WAN member identifier reassigned during a migration.
  3. SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.
  4. The effective FortiSASE compliance rule checks antivirus installed status but does not apply the organization-approved definition freshness criterion.

Explanation

Correct Answer

C:

The question asks for the distinguishing observation, which is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. It addresses the reported Westport Managed Security failure: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The causal relationship is: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

Incorrect Answers

A:

Another possibility is: The report filter includes employee groups but omits a newly onboarded approved contractor group with active SASE sessions. The current case at Westport Managed Security contains a different identifying observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The relevant mechanism is: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

B:

The saved analytics widget references an old SD-WAN member identifier reassigned during a migration. The original Westport Managed Security observation is instead: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. That is the evidence tied to the stated failure.

D:

The effective FortiSASE compliance rule checks antivirus installed status but does not apply the organization-approved definition freshness criterion. It does not substantiate the particular Westport Managed Security condition: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The documented finding is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.

Question 738

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Confirmed observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Proposed controlled action: Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. Which independent test would establish that the original problem is resolved?

  1. The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs.
  2. A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.
  3. A corrected test session uses the private route and its log confirms the intended policy and member selection.
  4. A controlled route impairment toward finance is detected before prolonged user loss, while other traffic retains its own policy.

Explanation

Correct Answer

C:

The measurable recovery condition for Westport Managed Security is: A corrected test session uses the private route and its log confirms the intended policy and member selection. This checks the actual failure revealed by: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

Incorrect Answers

A:

Another check would be: The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs. The relevant Westport Managed Security problem requires a distinct success condition: A corrected test session uses the private route and its log confirms the intended policy and member selection. The governing rule is: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

B:

A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing. It is not the evidence needed to close the reported issue. The proper Westport Managed Security success measure is: A corrected test session uses the private route and its log confirms the intended policy and member selection.

D:

A controlled route impairment toward finance is detected before prolonged user loss, while other traffic retains its own policy. That is not sufficient to validate the stated Westport Managed Security failure, supported by: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The required check is: A corrected test session uses the private route and its log confirms the intended policy and member selection.

Question 739

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Recorded observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. What platform design concept best accounts for the symptoms?

  1. Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry.
  2. A healthy path measurement cannot establish that a specific SD-WAN steering rule actually matched.
  3. Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.
  4. An interface migration must update higher-layer member references, not merely the physical port configuration.

Explanation

Correct Answer

C:

The technical relationship governing Westport Managed Security is: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient. The record shows: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. That observation is a direct consequence of the stated failure.

Incorrect Answers

A:

Another relationship would be: Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry. It does not account for the issue reported by Westport Managed Security: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The applicable principle is: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

B:

A healthy path measurement cannot establish that a specific SD-WAN steering rule actually matched. The key evidence is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. That observation is explained by a different rule: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

D:

An interface migration must update higher-layer member references, not merely the physical port configuration. In Westport Managed Security, the actual observation is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The rule connected to that evidence is: Investigating a steering anomaly requires session, routing and SLA data together; a healthy overlay alone is insufficient.

Question 740

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: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. Confirmed observation: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Which scoped action plus measurable success result should the team choose?

  1. Action: Normalize the source time zone and explicit period boundaries before interpreting differences or opening duplicate incidents. Proof: Both reports align on event count and timestamp after consistent conversion without losing boundary events.
  2. Action: Resolve member IDs and interface history for the reporting period, then update the saved report to current sources. Proof: The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs.
  3. Action: Create a narrowly scoped firewall policy referencing the appropriate source and SD-WAN destination zone with approved security profiles. Proof: A controlled sanctioned web transaction passes over local internet and an unauthorized source remains denied and logged.
  4. Action: Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. Proof: A corrected test session uses the private route and its log confirms the intended policy and member selection.

Explanation

Correct Answer

D:

The selection links action to a separately checked outcome: Action: Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. Proof: A corrected test session uses the private route and its log confirms the intended policy and member selection. It is grounded in the Westport Managed Security clue: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. Closure must show: A corrected test session uses the private route and its log confirms the intended policy and member selection.

Incorrect Answers

A:

Action: Normalize the source time zone and explicit period boundaries before interpreting differences or opening duplicate incidents. Proof: Both reports align on event count and timestamp after consistent conversion without losing boundary events. The actual issue at Westport Managed Security is: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics. The proposed verification does not establish that the required result is: A corrected test session uses the private route and its log confirms the intended policy and member selection.

B:

Action: Resolve member IDs and interface history for the reporting period, then update the saved report to current sources. Proof: The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs. It is not sufficient proof of resolution for the stated Westport Managed Security incident: The dashboard reports that a private database session used internet breakout despite normal tunnel-health metrics.

C:

Action: Create a narrowly scoped firewall policy referencing the appropriate source and SD-WAN destination zone with approved security profiles. Proof: A controlled sanctioned web transaction passes over local internet and an unauthorized source remains denied and logged. The recorded evidence at Westport Managed Security is: SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The correct outcome to measure is: A corrected test session uses the private route and its log confirms the intended policy and member selection.

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