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

Question 760

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 weekly threat dashboard shows only a small increase in risky category hits, but one managed user has repeated blocked destinations. Confirmed observation: Per-user FortiSASE security logs show repeated high-risk destination attempts by one identity while aggregate counts remain modest. What remediation-and-validation combination most directly addresses this incident?

  1. 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.
  2. 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.
  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: Adjust the approved application route and service-specific health strategy to reflect the real destination reachability. Proof: When the remote application prefix is withdrawn, traffic stops blackholing and uses only an approved viable path or fails explicitly.

Explanation

Correct Answer

B:

This pair is the bounded choice for Westport Managed Security: 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 underlying issue is: The weekly threat dashboard shows only a small increase in risky category hits, but one managed user has repeated blocked destinations. Confirm the recorded outcome: The suspicious test identity is isolated for authorized review while other unaffected users continue normal browsing.

Incorrect Answers

A:

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 actual issue at Westport Managed Security is: The weekly threat dashboard shows only a small increase in risky category hits, but one managed user has repeated blocked destinations. The proposed verification does not establish that the required result is: The suspicious test identity is isolated for authorized review while other unaffected users continue normal browsing.

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: Per-user FortiSASE security logs show repeated high-risk destination attempts by one identity while aggregate counts remain modest. The correct outcome to measure is: The suspicious test identity is isolated for authorized review while other unaffected users continue normal browsing.

D:

Action: Adjust the approved application route and service-specific health strategy to reflect the real destination reachability. Proof: When the remote application prefix is withdrawn, traffic stops blackholing and uses only an approved viable path or fails explicitly. The relevant Westport Managed Security observation is: Per-user FortiSASE security logs show repeated high-risk destination attempts by one identity while aggregate counts remain modest. Any successful correction still needs to verify: The suspicious test identity is isolated for authorized review while other unaffected users continue normal browsing.

Question 761

For Evergreen Distribution Security, 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 FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Confirmed observation: 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. What scoped change is justified by the observed evidence?

  1. Expand the authorized analytics group scope for the stated reporting purpose and rerun without exposing unrelated personal data.
  2. Correlate user, endpoint posture and actual threat categorization and initiate proportionate identity and endpoint investigation.
  3. Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment.
  4. Validate the actual application signature or permitted internet-service selector and revise only the scoped steering match.

Explanation

Correct Answer

C:

At Evergreen Distribution Security, the evidence establishes the immediate concern: 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. The appropriate response is: Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. The causal rule is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response. The required outcome is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

Incorrect Answers

A:

Another proposed response centers on: Expand the authorized analytics group scope for the stated reporting purpose and rerun without exposing unrelated personal data. The reported Evergreen Distribution Security failure is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The decisive record shows: 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.

B:

Another suggested intervention is: Correlate user, endpoint posture and actual threat categorization and initiate proportionate identity and endpoint investigation. It is not sufficient evidence of resolving the Evergreen Distribution Security condition: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The measurable outcome still required is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

D:

Another option proposes: Validate the actual application signature or permitted internet-service selector and revise only the scoped steering match. At Evergreen Distribution Security, the decisive evidence is: 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. That step alone does not demonstrate correction of the specified problem: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file.

Question 762

At Evergreen Distribution Security, the team administers SD-WAN telemetry and FortiSASE incident analysis and must correlate trusted event evidence, time windows and source identities. Operational incident: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. 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. One export uses UTC and the other uses tenant-local time, moving the same sessions across a day boundary.
  3. FortiSASE security logs show the alerts cluster around a known policy rollout and one approved synthetic validation source rather than diverse attackers.
  4. SLA criteria assess only latency and do not apply the documented jitter threshold required by the media service.

Explanation

Correct Answer

A:

The observation directly identifies the cause at Evergreen Distribution Security: 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. The reported problem is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

Incorrect Answers

B:

One export uses UTC and the other uses tenant-local time, moving the same sessions across a day boundary. The trace for Evergreen Distribution Security instead establishes: 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. This is the clue to the issue actually described.

C:

FortiSASE security logs show the alerts cluster around a known policy rollout and one approved synthetic validation source rather than diverse attackers. The reported Evergreen Distribution Security fault is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The signal that actually distinguishes it is: 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.

D:

SLA criteria assess only latency and do not apply the documented jitter threshold required by the media service. At Evergreen Distribution Security, the recorded condition is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The particular evidence supporting it is: 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.

Question 763

For Evergreen Distribution Security, 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 FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Confirmed observation: 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. Proposed controlled action: Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. What separate result verifies the change without hiding a second failure?

  1. The synthetic alert is correctly classified and real independent malicious-signature controls still trigger the expected response.
  2. A corrected test session uses the private route and its log confirms the intended policy and member selection.
  3. The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.
  4. Public controls use direct breakout, private test sessions use encrypted transport, and the route logs match the defined segmentation.

Explanation

Correct Answer

C:

The reported failure at Evergreen Distribution Security is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The necessary independent result is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. It tests recovery against the original evidence: 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.

Incorrect Answers

A:

The synthetic alert is correctly classified and real independent malicious-signature controls still trigger the expected response. The acceptance condition for the stated Evergreen Distribution Security fault is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. 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 Evergreen Distribution Security is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. That result is related to the original issue.

D:

Public controls use direct breakout, private test sessions use encrypted transport, and the route logs match the defined segmentation. That alone would not confirm correction of the Evergreen Distribution Security problem: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The necessary proof is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

Question 764

At Evergreen Distribution Security, the team administers SD-WAN telemetry and FortiSASE incident analysis and must correlate trusted event evidence, time windows and source identities. Operational incident: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Recorded observation: 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. Which operational principle governs the documented incident?

  1. Security threat interpretation must distinguish authorized validation from hostile activity using time-aligned context.
  2. Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry.
  3. A performance SLA can compare only the eligible members it actually measures and the service rule permits.
  4. Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

Explanation

Correct Answer

D:

Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response. For Evergreen Distribution Security, the supporting evidence is: 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. The reported condition is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file.

Incorrect Answers

A:

Another principle is: Security threat interpretation must distinguish authorized validation from hostile activity using time-aligned context. It is not enough to account for the recorded Evergreen Distribution Security evidence: 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. The applicable rule is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

B:

Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry. The documented Evergreen Distribution Security failure is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The case is instead explained by: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

C:

An alternative explanation is: A performance SLA can compare only the eligible members it actually measures and the service rule permits. It is not the reason established by the Evergreen Distribution Security clue: 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. The relevant causal relationship is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

Question 765

For Evergreen Distribution Security, 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 FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Confirmed observation: 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. 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: 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.
  3. Action: Separate supported user and device management groups and apply the documented access restrictions per class. Proof: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.
  4. 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.

Explanation

Correct Answer

D:

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. The relevant finding at Evergreen Distribution Security is: 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.

Incorrect Answers

A:

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. They do not directly establish recovery of the reported Evergreen Distribution Security problem: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Verification requires: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

B:

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. It would not by itself demonstrate correction of the Evergreen Distribution Security finding: 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. The required outcome is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

C:

An alternative option suggests: Action: Separate supported user and device management groups and apply the documented access restrictions per class. Proof: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. The documented Evergreen Distribution Security problem calls for a check against: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. The original clue is: 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.

Question 766

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 FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Confirmed observation: 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. Which approved correction best addresses the documented root cause?

  1. Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact.
  2. Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment.
  3. Normalize the source time zone and explicit period boundaries before interpreting differences or opening duplicate incidents.
  4. Include the supported eligible backup in the scoped rule and verify the member has accurate health telemetry and firewall permission.

Explanation

Correct Answer

B:

The issue at Silverpeak Cloud Services is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. 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. Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. A valid post-change result is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

Incorrect Answers

A:

Although that step is: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact, the decisive observation here is: 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. That choice alone does not establish the needed correction at Silverpeak Cloud Services.

C:

The suggested alternative is: Normalize the source time zone and explicit period boundaries before interpreting differences or opening duplicate incidents. The case identifies the cause at Silverpeak Cloud Services using: 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. Implementing that step alone would not verify: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

D:

Another proposed action is: Include the supported eligible backup in the scoped rule and verify the member has accurate health telemetry and firewall permission. In Silverpeak Cloud Services, the relevant evidence is: 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. The focused correction should address the root condition shown by that clue.

Question 767

For Silverpeak Cloud Services, 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 FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The team must verify the root cause before changing production settings. What measured finding directly supports the recorded issue?

  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. 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.
  4. Application-specific traces show the resolver is reachable on the primary member while the actual finance destination is experiencing upstream path loss.

Explanation

Correct Answer

C:

The question asks for the distinguishing observation, which is: 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 addresses the reported Silverpeak Cloud Services failure: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The causal relationship is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

Incorrect Answers

A:

Another possibility is: Per-user FortiSASE security logs show repeated high-risk destination attempts by one identity while aggregate counts remain modest. The current case at Silverpeak Cloud Services contains a different identifying observation: 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. The relevant mechanism is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

B:

SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. The original Silverpeak Cloud Services observation is instead: 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. That is the evidence tied to the stated failure.

D:

Application-specific traces show the resolver is reachable on the primary member while the actual finance destination is experiencing upstream path loss. It does not substantiate the particular Silverpeak Cloud Services condition: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The documented finding is: 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.

Question 768

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 FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Confirmed observation: 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. Proposed controlled action: Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. Which independent test would establish that the original problem is resolved?

  1. The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.
  2. The corrected widget aligns historical quality metrics to the intended physical circuit and raw health logs.
  3. A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.
  4. HR test users reach the application while a non-HR remote user remains blocked in correlated hub logs.

Explanation

Correct Answer

A:

The listed result is the right measure for Silverpeak Cloud Services: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. It verifies the intended effect, whereas the case originally showed: 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. The relevant principle is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

Incorrect Answers

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 Silverpeak Cloud Services success measure is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

C:

An alternative test would show: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing. It does not show the required post-change result at Silverpeak Cloud Services: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. The original finding was: 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.

D:

HR test users reach the application while a non-HR remote user remains blocked in correlated hub logs. That is not sufficient to validate the stated Silverpeak Cloud Services failure, supported by: 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. The required check is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

Question 769

For Silverpeak Cloud Services, 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 FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Recorded observation: 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. What platform design concept best accounts for the symptoms?

  1. A healthy path measurement cannot establish that a specific SD-WAN steering rule actually matched.
  2. Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.
  3. Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry.
  4. Authentication establishes identity; authorization relies on accurate policy groups and assignment.

Explanation

Correct Answer

B:

At Silverpeak Cloud Services, the evidence is: 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. The principle that explains it is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response. It connects that clue to the specified failure.

Incorrect Answers

A:

Another relationship would be: A healthy path measurement cannot establish that a specific SD-WAN steering rule actually matched. It does not account for the issue reported by Silverpeak Cloud Services: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The applicable principle is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

C:

Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry. The failure at Silverpeak Cloud Services is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The operating rule directly related to that failure is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

D:

Authentication establishes identity; authorization relies on accurate policy groups and assignment. In Silverpeak Cloud Services, the actual observation is: 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. The rule connected to that evidence is: Threat detection logs and endpoint delivery outcomes are different facts that must be reconciled before response.

Question 770

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 FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. Confirmed observation: 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. Which scoped action plus measurable success result should the team choose?

  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: 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: 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.
  4. 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.

Explanation

Correct Answer

D:

The selection links action to a separately checked outcome: 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 grounded in the Silverpeak Cloud Services clue: 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. Closure must show: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

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 Silverpeak Cloud Services is: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file. The proposed verification does not establish that the required result is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

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 Silverpeak Cloud Services incident: A FortiSASE antivirus event identifies a suspicious download, but investigators cannot tell whether the managed laptop actually received the file.

C:

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. The recorded evidence at Silverpeak Cloud Services is: 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. The correct outcome to measure is: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

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