NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
A support analyst is collecting data for this scenario. A network manager asks which applications consumed the backup carrier's data allowance, but the team filters only by source users without checking application classification. Which diagnostic check is most targeted?
Inspect period, source, application, interface/member and transfer-volume values. This inspection targets FortiView branch application bandwidth rather than a different configuration issue. The corrective action is: Use a supported FortiView or SD-WAN traffic view with application, user and member filters. Expected evidence: The report identifies the responsible application and source cohort on the backup link during the specified period.
Inspect local log settings, collector address, connectivity and received event count. This is useful when diagnosing FortiGate logging destination misconfiguration. Instead, inspect period, source, application, interface/member and transfer-volume values.
Inspect source group, report interval, traffic metrics and data availability. This is useful when diagnosing On-demand remote-user bandwidth report. Instead, inspect period, source, application, interface/member and transfer-volume values.
Inspect log source, user mode, report filter and raw matching events. This is useful when diagnosing Report coverage of remote agent and SWG users. Instead, inspect period, source, application, interface/member and transfer-volume values.
A Fortinet administrator must address this operational problem. A branch reports a five-minute interruption but IT cannot tell whether the outage came from physical ISP loss, SLA breach or a new policy push. Which response best resolves it?
Correlate SD-WAN health events, interface state, steering logs and configuration-change history for the exact incident window. Interface events, SLA results and policy updates are distinct telemetry sources that can explain a route change. Expected evidence: The event sequence separates a carrier failure from a policy-induced selection change. Key limit: One failed TCP request alone cannot identify the layer that caused the interruption.
Inspect FortiSASE web-filter event records for user identity, URL category, verdict and matched policy before approving any exception. This could apply to the separate issue FortiSASE malicious URL event investigation: An employee reports a browser block on a new website, and the help desk cannot tell whether the site is malicious or simply in a prohibited category. For SD-WAN failover event correlation, the directly relevant action is: Correlate SD-WAN health events, interface state, steering logs and configuration-change history for the exact incident window.
Correlate a specific FortiOS traffic log and SD-WAN service diagnostic for the ERP source, destination and time. This could apply to the separate issue SD-WAN service selection in traffic logs: A branch administrator claims that an ERP flow took the preferred ISP, but monitoring shows only aggregate interface throughput and no evidence of the particular session. For SD-WAN failover event correlation, the directly relevant action is: Correlate SD-WAN health events, interface state, steering logs and configuration-change history for the exact incident window.
Correlate endpoint detection and cloud traffic events using user, device, domain and aligned timestamps. This could apply to the separate issue Endpoint security malware event correlation: A managed FortiClient device reports an antivirus detection and FortiSASE simultaneously logs denied access to a suspicious domain. For SD-WAN failover event correlation, the directly relevant action is: Correlate SD-WAN health events, interface state, steering logs and configuration-change history for the exact incident window.
For this situation, a reviewer needs acceptance evidence. A branch reports a five-minute interruption but IT cannot tell whether the outage came from physical ISP loss, SLA breach or a new policy push. Which result most directly demonstrates success?
The event sequence separates a carrier failure from a policy-induced selection change. This is the directly relevant check for SD-WAN failover event correlation. It confirms the required step: Correlate SD-WAN health events, interface state, steering logs and configuration-change history for the exact incident window. The operating principle is: Interface events, SLA results and policy updates are distinct telemetry sources that can explain a route change.
The incident narrative links the relevant detections without mixing unrelated users or devices. This would validate a different scenario, Endpoint security malware event correlation, where A managed FortiClient device reports an antivirus detection and FortiSASE simultaneously logs denied access to a suspicious domain. The current case needs evidence for SD-WAN failover event correlation.
The session record identifies its matched rule and selected member while confirming the application transaction. This would validate a different scenario, SD-WAN service selection in traffic logs, where A branch administrator claims that an ERP flow took the preferred ISP, but monitoring shows only aggregate interface throughput and no evidence of the particular session. The current case needs evidence for SD-WAN failover event correlation.
The analyst identifies the precise classification and response and can document an appropriate allow or deny decision. This would validate a different scenario, FortiSASE malicious URL event investigation, where An employee reports a browser block on a new website, and the help desk cannot tell whether the site is malicious or simply in a prohibited category. The current case needs evidence for SD-WAN failover event correlation.
A network administrator must explain the underlying control. A branch reports a five-minute interruption but IT cannot tell whether the outage came from physical ISP loss, SLA breach or a new policy push. Which statement is correct?
Interface events, SLA results and policy updates are distinct telemetry sources that can explain a route change. This explains SD-WAN failover event correlation in the given environment. The implementation decision is: Correlate SD-WAN health events, interface state, steering logs and configuration-change history for the exact incident window. Confirm it with: The event sequence separates a carrier failure from a policy-induced selection change.
Web security logs record category verdict and rule action for eligible FortiSASE browsing sessions. That concept concerns FortiSASE malicious URL event investigation, not the mechanism needed for SD-WAN failover event correlation. The relevant principle is: Interface events, SLA results and policy updates are distinct telemetry sources that can explain a route change.
Endpoint posture telemetry and FortiSASE web or threat logs offer complementary evidence of a suspected compromise. That concept concerns Endpoint security malware event correlation, not the mechanism needed for SD-WAN failover event correlation. The relevant principle is: Interface events, SLA results and policy updates are distinct telemetry sources that can explain a route change.
FortiView can summarize observed session and application telemetry to support bandwidth analysis. That concept concerns FortiView branch application bandwidth, not the mechanism needed for SD-WAN failover event correlation. The relevant principle is: Interface events, SLA results and policy updates are distinct telemetry sources that can explain a route change.
An incident team needs to isolate the root cause. A branch reports a five-minute interruption but IT cannot tell whether the outage came from physical ISP loss, SLA breach or a new policy push. Which investigation should be prioritized?
Compare timestamps, health-check failure, route withdrawal, rule match and administrative changes. This inspection targets SD-WAN failover event correlation rather than a different configuration issue. The corrective action is: Correlate SD-WAN health events, interface state, steering logs and configuration-change history for the exact incident window. Expected evidence: The event sequence separates a carrier failure from a policy-induced selection change.
Inspect period, source, application, interface/member and transfer-volume values. This is useful when diagnosing FortiView branch application bandwidth, but not the best first investigation here. Instead, compare timestamps, health-check failure, route withdrawal, rule match and administrative changes.
Inspect endpoint ID, logged-in user, process alert, domain query and network verdict. This is useful when diagnosing Endpoint security malware event correlation, but not the best first investigation here. Instead, compare timestamps, health-check failure, route withdrawal, rule match and administrative changes.
Examine URL rating, identity, applied filter, timestamp and observed action. This is useful when diagnosing FortiSASE malicious URL event investigation, but not the best first investigation here. Instead, compare timestamps, health-check failure, route withdrawal, rule match and administrative changes.
A network engineer faces the following FortiSASE or SD-WAN condition. Local SD-WAN sessions work but the centralized security team sees no traffic records after FortiAnalyzer log forwarding was reconfigured. What should the engineer do?
Restore the approved logging destination, transport and policy/session log generation, then test delivery. Forwarded log availability depends on both event generation and a working remote logging path. Expected evidence: A controlled client flow is visible locally and arrives at the intended centralized collector with correct attribution. Key limit: A working internet application is not evidence that remote logging is configured correctly.
Compare FortiSASE decryption/exclusion policy and threat-log visibility before interpreting the lower count as an improvement. This could apply to the separate issue No threat logs after inspection bypass: An engineer adds a broad TLS inspection exception for a partner site, and security dashboards suddenly report fewer malware detections. For FortiGate logging destination misconfiguration, the directly relevant action is: Restore the approved logging destination, transport and policy/session log generation, then test delivery.
Check current service-rule hits, classified application, destination and traffic routes before retiring the old rule. This could apply to the separate issue Rule hit counters after application migration: A company moves an application from on-premises servers to SaaS, but an SD-WAN rules dashboard still shows hits on a deprecated private-datacenter service. For FortiGate logging destination misconfiguration, the directly relevant action is: Restore the approved logging destination, transport and policy/session log generation, then test delivery.
Include the appropriate FortiSASE ingress modes and user cohorts in the report query. This could apply to the separate issue Report coverage of remote agent and SWG users: A security analyst creates a remote-access usage report but filters only FortiClient tunnel sessions and omits browser-only SWG contractor traffic. For FortiGate logging destination misconfiguration, the directly relevant action is: Restore the approved logging destination, transport and policy/session log generation, then test delivery.
A pilot is validating the implementation. Local SD-WAN sessions work but the centralized security team sees no traffic records after FortiAnalyzer log forwarding was reconfigured. Which finding proves that the intended fix works?
A controlled client flow is visible locally and arrives at the intended centralized collector with correct attribution. This is the directly relevant check for FortiGate logging destination misconfiguration. It confirms the required step: Restore the approved logging destination, transport and policy/session log generation, then test delivery. The operating principle is: Forwarded log availability depends on both event generation and a working remote logging path.
The session record identifies its matched rule and selected member while confirming the application transaction. This would validate a different scenario, SD-WAN service selection in traffic logs, where A branch administrator claims that an ERP flow took the preferred ISP, but monitoring shows only aggregate interface throughput and no evidence of the particular session. The current case needs evidence for FortiGate logging destination misconfiguration.
Both authorized agent-based and agentless web sessions appear under correct groups without double counting. This would validate a different scenario, Report coverage of remote agent and SWG users, where A security analyst creates a remote-access usage report but filters only FortiClient tunnel sessions and omits browser-only SWG contractor traffic. The current case needs evidence for FortiGate logging destination misconfiguration.
Observed new SaaS sessions use the intended rule and old-rule hits are explained over a representative time window. This would validate a different scenario, Rule hit counters after application migration, where A company moves an application from on-premises servers to SaaS, but an SD-WAN rules dashboard still shows hits on a deprecated private-datacenter service. The current case needs evidence for FortiGate logging destination misconfiguration.
A technical lead asks why the recommended approach works. Local SD-WAN sessions work but the centralized security team sees no traffic records after FortiAnalyzer log forwarding was reconfigured. Which mechanism is most relevant?
Forwarded log availability depends on both event generation and a working remote logging path. This explains FortiGate logging destination misconfiguration in the given environment. The implementation decision is: Restore the approved logging destination, transport and policy/session log generation, then test delivery. Confirm it with: A controlled client flow is visible locally and arrives at the intended centralized collector with correct attribution.
Rule hit counters represent observed matches and must be interpreted against current application and address behavior. That concept concerns Rule hit counters after application migration, not the mechanism needed for FortiGate logging destination misconfiguration. The relevant principle is: Forwarded log availability depends on both event generation and a working remote logging path.
FortiView can summarize observed session and application telemetry to support bandwidth analysis. That concept concerns FortiView branch application bandwidth, not the mechanism needed for FortiGate logging destination misconfiguration. The relevant principle is: Forwarded log availability depends on both event generation and a working remote logging path.
Different SASE access modes can generate distinct connection and web logs that require deliberate report inclusion. That concept concerns Report coverage of remote agent and SWG users, not the mechanism needed for FortiGate logging destination misconfiguration. The relevant principle is: Forwarded log availability depends on both event generation and a working remote logging path.
Before changing production settings, an engineer reviews the symptoms. Local SD-WAN sessions work but the centralized security team sees no traffic records after FortiAnalyzer log forwarding was reconfigured. Which evidence is most useful?
Inspect local log settings, collector address, connectivity and received event count. This inspection targets FortiGate logging destination misconfiguration rather than a different configuration issue. The corrective action is: Restore the approved logging destination, transport and policy/session log generation, then test delivery. Expected evidence: A controlled client flow is visible locally and arrives at the intended centralized collector with correct attribution.
Inspect rule hit history, service IDs, source/destination scope and application owner confirmation. This is useful when diagnosing Rule hit counters after application migration. Instead, inspect local log settings, collector address, connectivity and received event count.
Inspect log source, user mode, report filter and raw matching events. This is useful when diagnosing Report coverage of remote agent and SWG users. Instead, inspect local log settings, collector address, connectivity and received event count.
Inspect period, source, application, interface/member and transfer-volume values. This is useful when diagnosing FortiView branch application bandwidth. Instead, inspect local log settings, collector address, connectivity and received event count.
A deployment review finds this gap. A company moves an application from on-premises servers to SaaS, but an SD-WAN rules dashboard still shows hits on a deprecated private-datacenter service. What is the most targeted next configuration step?
Check current service-rule hits, classified application, destination and traffic routes before retiring the old rule. Rule hit counters represent observed matches and must be interpreted against current application and address behavior. Expected evidence: Observed new SaaS sessions use the intended rule and old-rule hits are explained over a representative time window. Key limit: A zero hit count in one short interval cannot prove a rule is permanently unused.
Correlate SD-WAN health events, interface state, steering logs and configuration-change history for the exact incident window. This could apply to the separate issue SD-WAN failover event correlation: A branch reports a five-minute interruption but IT cannot tell whether the outage came from physical ISP loss, SLA breach or a new policy push. For Rule hit counters after application migration, the directly relevant action is: Check current service-rule hits, classified application, destination and traffic routes before retiring the old rule.
Correlate a specific FortiOS traffic log and SD-WAN service diagnostic for the ERP source, destination and time. This could apply to the separate issue SD-WAN service selection in traffic logs: A branch administrator claims that an ERP flow took the preferred ISP, but monitoring shows only aggregate interface throughput and no evidence of the particular session. For Rule hit counters after application migration, the directly relevant action is: Check current service-rule hits, classified application, destination and traffic routes before retiring the old rule.
Restore the approved logging destination, transport and policy/session log generation, then test delivery. This could apply to the separate issue FortiGate logging destination misconfiguration: Local SD-WAN sessions work but the centralized security team sees no traffic records after FortiAnalyzer log forwarding was reconfigured. For Rule hit counters after application migration, the directly relevant action is: Check current service-rule hits, classified application, destination and traffic routes before retiring the old rule.
The recommended change has been applied. A company moves an application from on-premises servers to SaaS, but an SD-WAN rules dashboard still shows hits on a deprecated private-datacenter service. Which observation best verifies the intended outcome?
Observed new SaaS sessions use the intended rule and old-rule hits are explained over a representative time window. This is the directly relevant check for Rule hit counters after application migration. It confirms the required step: Check current service-rule hits, classified application, destination and traffic routes before retiring the old rule. The operating principle is: Rule hit counters represent observed matches and must be interpreted against current application and address behavior.
The event sequence separates a carrier failure from a policy-induced selection change. This would validate a different scenario, SD-WAN failover event correlation, where A branch reports a five-minute interruption but IT cannot tell whether the outage came from physical ISP loss, SLA breach or a new policy push. The current case needs evidence for Rule hit counters after application migration.
The session record identifies its matched rule and selected member while confirming the application transaction. This would validate a different scenario, SD-WAN service selection in traffic logs, where A branch administrator claims that an ERP flow took the preferred ISP, but monitoring shows only aggregate interface throughput and no evidence of the particular session. The current case needs evidence for Rule hit counters after application migration.
The incident timeline shows whether jitter or loss exceeded thresholds when voice users reported degradation. This would validate a different scenario, Performance SLA jitter timeline review, where Operations receives reports that calls stuttered yesterday, but engineers inspect only today's green SLA dashboard. The current case needs evidence for Rule hit counters after application migration.
Please check your mailbox for a message from support@examlabs.com and follow the directions.