Fortinet NSE5_SSE_AD-7.6 Practice Test 69
Question 680
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A branch experiences afternoon congestion and needs to identify which user/application pairs account for most outbound traffic. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Instead configure: Inspect FortiSASE inline-CASB or application-security events for the recorded SaaS action and rule verdict.
- Use the shortcut: Disable all SD-WAN performance SLAs to determine which app consumed bandwidth.
- Test the diagnosis with: Inspect per-application and per-user bytes, time window and relevant egress member in the analytics view.
- Instead collect: Inspect signature/category, action, matched user/policy and corresponding session/time fields in security events.
- Correct the fault by: Use the applicable FortiView/application traffic dashboard and filtered report for top users and applications in the incident window.
Explanation
Correct Answer
C:This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
E:This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence. Aggregate link volume does not attribute utilization to specific applications or users.
Incorrect Answers
A:This concerns a different operational control (Cloud-app control event) and can be sensible in its own incident, but the reported fortiview top-app analysis problem requires a more direct response.
B:The direct remedial step is: Use the applicable FortiView/application traffic dashboard and filtered report for top users and applications in the incident window.
D:This concerns a different operational control (Traffic log versus threat event) and can be sensible in its own incident, but the reported fortiview top-app analysis problem requires a more direct response.
Question 681
A company enabled external security monitoring but the SIEM receives no FortiSASE security events after a collector change. An initial suggestion was to assume visibility in the SASE local portal proves the SIEM received every event. Which engineering change fixes the specific control gap rather than a neighboring symptom? Select ONE best answer.
- Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
- Assume visibility in the SASE local portal proves the SIEM received every event.
- Inspect FortiSASE inline-CASB or application-security events for the recorded SaaS action and rule verdict.
- Query the web-filter logs for the precise URL, user, policy, category and resulting enforcement action.
Explanation
Correct Answer
A:Local event generation and successful forwarding to an external collector are separate operational stages.
Incorrect Answers
B:That option would assume visibility in the SASE local portal proves the SIEM received every event, but it addresses a different concern. Local event generation and successful forwarding to an external collector are separate operational stages.
C:This concerns a different operational control (Cloud-app control event) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
D:This concerns a different operational control (Web-filter event diagnosis) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
Question 682
Consider this FortiSASE/SD-WAN 7.6 operational report: A company enabled external security monitoring but the SIEM receives no FortiSASE security events after a collector change. The engineering proposal is: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end. What concept makes the proposed correction technically appropriate in this situation? Select ONE best answer.
- Traffic logging explains sessions, while threat or security events provide inspection verdict and detection context.
- Aggregation can hide short service-impacting loss spikes that drive steering or application failures.
- Local event generation and successful forwarding to an external collector are separate operational stages.
- Raw latency or jitter has no isolated pass/fail meaning without the corresponding objective and chosen rule.
Explanation
Correct Answer
C:A satisfactory result would be: The external monitoring system receives the corresponding test event with usable time and source details.
Incorrect Answers
A:This concerns a different operational control (Traffic log versus threat event) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
B:This concerns a different operational control (Packet-loss trend review) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
D:This concerns a different operational control (SLA target versus performance plots) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
Question 683
The on-call engineer is evaluating the following behavior before changing production configuration: A company enabled external security monitoring but the SIEM receives no FortiSASE security events after a collector change. What diagnostic comparison best establishes the reported control mismatch? Select ONE best answer.
- Inspect signature/category, action, matched user/policy and corresponding session/time fields in security events.
- Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
- Match user, authentication request time, identity method and response or trust error across systems.
- Compare event timestamps, member ID, affected SLA and client incident intervals.
Explanation
Correct Answer
B:This observation directly distinguishes the reported external log forwarding assurance problem from unrelated network or SASE symptoms.
Incorrect Answers
A:Applied to the observed case: A security manager opens a traffic volume report and concludes that no malware block occurred because the volume panel lacks signature detail. That addresses an alternative control; the reported Fortinet requirement instead calls for: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
C:This concerns a different operational control (Identity sign-in failure analytics) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
D:A present healthy status does not reconstruct transient failures; historical events and SLA changes are needed to explain failover. That addresses an alternative control; the reported Fortinet requirement instead calls for: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
Question 684
After the authorized response to this incident, the operator must validate the effect: A company enabled external security monitoring but the SIEM receives no FortiSASE security events after a collector change. Which observable outcome most convincingly confirms a successful remediation? Select ONE best answer.
- The external monitoring system receives the corresponding test event with usable time and source details.
- The team identifies the exact category or policy decision responsible for the block.
- The root authentication cause is identified without altering unrelated network steering.
- The investigation can name the exact steering rule and member used by the cited application flow.
Explanation
Correct Answer
A:The required mechanism is: Local event generation and successful forwarding to an external collector are separate operational stages.
Incorrect Answers
B:The required mechanism is: A URL deny may be an intended category verdict; the decision must be traced to its matching inspection policy. That addresses an alternative control; the reported Fortinet requirement instead calls for: The external monitoring system receives the corresponding test event with usable time and source details.
C:The required mechanism is: User authentication can fail independently of internet forwarding and SD-WAN quality. That addresses an alternative control; the reported Fortinet requirement instead calls for: The external monitoring system receives the corresponding test event with usable time and source details.
D:This concerns a different operational control (SD-WAN rule-match evidence) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
Question 685
An operations ticket describes this condition: A company enabled external security monitoring but the SIEM receives no FortiSASE security events after a collector change. The team needs to address the underlying fault and gather conclusive evidence. What change-and-validation pairing is most directly justified by the incident? Select ONE best answer.
- Correct: Query identity/authentication logs and the upstream identity provider's corresponding events to isolate login failures. Verify: Match user, authentication request time, identity method and response or trust error across systems.
- Correct: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end. Verify: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
- Correct: Correlate relevant FortiSASE threat/security event logs with traffic sessions, policy and signature details. Verify: Inspect signature/category, action, matched user/policy and corresponding session/time fields in security events.
- Correct: Examine fine-grained loss and SLA measurement data over the incident window, rather than only broad averages. Verify: Graph member-level loss samples and threshold changes at the specific outage timestamps.
Explanation
Correct Answer
B:The change should demonstrate: The external monitoring system receives the corresponding test event with usable time and source details.
Incorrect Answers
A:This concerns a different operational control (Identity sign-in failure analytics) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response. Correct: Query identity/authentication logs and the upstream identity provider's corresponding events to isolate login failures.
C:Traffic logging explains sessions, while threat or security events provide inspection verdict and detection context. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correct: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end. Verify: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
D:Aggregation can hide short service-impacting loss spikes that drive steering or application failures. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correct: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end. Verify: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
Question 686
A branch's local SASE dashboard contains recent threat detections, yet the central logging service has a two-hour ingestion gap. An initial suggestion was to assume visibility in the SASE local portal proves the SIEM received every event. Which implementation or configuration decision most directly corrects the stated problem? Select ONE best answer.
- Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
- Use SD-WAN rule and session logs to identify the actual matching rule and selected member for the affected flow.
- Inspect FortiSASE inline-CASB or application-security events for the recorded SaaS action and rule verdict.
- Assume visibility in the SASE local portal proves the SIEM received every event.
Explanation
Correct Answer
A:Local event generation and successful forwarding to an external collector are separate operational stages. Accept the remediation only when: The external monitoring system receives the corresponding test event with usable time and source details.
Incorrect Answers
B:Link utilization summaries cannot by themselves establish why a particular session matched a steering rule. That addresses an alternative control; the reported Fortinet requirement instead calls for: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
C:Accept the remediation only when: The investigation distinguishes an enforced SaaS activity restriction from a reachability problem. That addresses an alternative control; the reported Fortinet requirement instead calls for: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
D:That option would assume visibility in the SASE local portal proves the SIEM received every event, but it addresses a different concern. Local event generation and successful forwarding to an external collector are separate operational stages. The direct remedial step is: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
Question 687
Consider this FortiSASE/SD-WAN 7.6 operational report: A branch's local SASE dashboard contains recent threat detections, yet the central logging service has a two-hour ingestion gap. The engineering proposal is: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end. Which technical principle best explains the expected behavior and why the direct correction is necessary? Select ONE best answer.
- Local event generation and successful forwarding to an external collector are separate operational stages.
- Aggregation can hide short service-impacting loss spikes that drive steering or application failures.
- Identity success and tunnel availability are distinct from device-compliance authorization.
- Application-level SaaS control decisions require application/action telemetry, not merely name-resolution success.
Explanation
Correct Answer
A:A satisfactory result would be: The external monitoring system receives the corresponding test event with usable time and source details. The principle explains why the proposed direct fix is necessary: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
Incorrect Answers
B:Evidence that tests the explanation: Graph member-level loss samples and threshold changes at the specific outage timestamps. That addresses an alternative control; the reported Fortinet requirement instead calls for: Local event generation and successful forwarding to an external collector are separate operational stages.
C:Applied to the observed case: A managed laptop is denied SASE access and network engineers assume a tunnel fault without inspecting the endpoint's compliance state. That addresses an alternative control; the reported Fortinet requirement instead calls for: Local event generation and successful forwarding to an external collector are separate operational stages.
D:Applied to the observed case: A risk team asks why an SaaS file upload was blocked while the help desk reviews only ordinary DNS lookup results. That addresses an alternative control; the reported Fortinet requirement instead calls for: Local event generation and successful forwarding to an external collector are separate operational stages.
Question 688
The on-call engineer is evaluating the following behavior before changing production configuration: A branch's local SASE dashboard contains recent threat detections, yet the central logging service has a two-hour ingestion gap. What evidence should the engineer gather FIRST to distinguish the suspected fault from unrelated issues? Select ONE best answer.
- Match user, authentication request time, identity method and response or trust error across systems.
- Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
- Read current SLA thresholds, metric values and rule membership at the same point in time.
- Inspect signature/category, action, matched user/policy and corresponding session/time fields in security events.
Explanation
Correct Answer
B:This observation directly distinguishes the reported external log forwarding assurance problem from unrelated network or SASE symptoms.
Incorrect Answers
A:If confirmed, the targeted intervention is: Query identity/authentication logs and the upstream identity provider's corresponding events to isolate login failures. That addresses an alternative control; the reported Fortinet requirement instead calls for: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
C:Applied to the observed case: An operations analyst sees a 90-ms latency graph but calls the link unhealthy without knowing the service's configured latency target. That addresses an alternative control; the reported Fortinet requirement instead calls for: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
D:Applied to the observed case: A security manager opens a traffic volume report and concludes that no malware block occurred because the volume panel lacks signature detail. That addresses an alternative control; the reported Fortinet requirement instead calls for: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
Question 689
After the authorized response to this incident, the operator must validate the effect: A branch's local SASE dashboard contains recent threat detections, yet the central logging service has a two-hour ingestion gap. Which result would most directly demonstrate that the change achieved its intended outcome? Select ONE best answer.
- Fresh sessions demonstrably follow the new design while older session behavior is accounted for.
- The external monitoring system receives the corresponding test event with usable time and source details.
- The report states whether each candidate met the configured service requirements for the incident.
- The review can tie a specific threat verdict to the session without conflating it with aggregate traffic.
Explanation
Correct Answer
B:The required mechanism is: Local event generation and successful forwarding to an external collector are separate operational stages. This is an outcome-level acceptance check rather than a proxy such as link light or portal sign-in.
Incorrect Answers
A:The required mechanism is: Session persistence can differ from new connection selection; timing matters to interpreting steering logs. That addresses an alternative control; the reported Fortinet requirement instead calls for: The external monitoring system receives the corresponding test event with usable time and source details.
C:The required mechanism is: Raw latency or jitter has no isolated pass/fail meaning without the corresponding objective and chosen rule. That addresses an alternative control; the reported Fortinet requirement instead calls for: The external monitoring system receives the corresponding test event with usable time and source details.
D:The required mechanism is: Traffic logging explains sessions, while threat or security events provide inspection verdict and detection context. That addresses an alternative control; the reported Fortinet requirement instead calls for: The external monitoring system receives the corresponding test event with usable time and source details.
Question 690
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A branch's local SASE dashboard contains recent threat detections, yet the central logging service has a two-hour ingestion gap. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Instead configure: Inspect FortiSASE inline-CASB or application-security events for the recorded SaaS action and rule verdict.
- Use the shortcut: Assume visibility in the SASE local portal proves the SIEM received every event.
- Test the diagnosis with: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
- Correct the fault by: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
- Instead collect: Graph member-level loss samples and threshold changes at the specific outage timestamps.
Explanation
Correct Answer
C:This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
D:This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence. Local event generation and successful forwarding to an external collector are separate operational stages.
Incorrect Answers
A:This concerns a different operational control (Cloud-app control event) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
B:The direct remedial step is: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
E:This concerns a different operational control (Packet-loss trend review) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response. Check the relevant evidence instead: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.