NSE5_FSM-6.3 無料問題集「Fortinet NSE 5 - FortiSIEM 6.3」

（A）FortiSIEM uses global and per device thresholds tor all performance metrics.

（B）FortiSIEM uses global thresholds for all security metrics.

（C）FortiSIEM uses fixed hardcoded thresholds for all performance metrics.

（D）FortiSIEM uses global thresholds for all performance metrics.

（A）Notification policy

（B）Remediation engine

（C）Notification engine

（D）Remediation policy

（A）Run an analytic search.

（B）Run a baseline report.

（C）Run a query using the Inventory tab.

（D）Run a CMDB report

（A）A clear condition set on a rule was satisfied.

（B）The incident was cleared by an operator.

（C）A security rule issue has been resolved.

（D）Two hours have passed since the incident occurred and the incident has not reoccurred.

（A）FortiSIEM will apply system monitor jobs to collect resources data.

（B）FortiSIEM will apply a Job to collect security event logs

（C）FortiSIEM will apply a job to collect system event logs.

（D）FortiSIEM will apply a job to collect application event logs.

（A）The connection ID is not in the raw message.

（B）408228

（C）134

（D）33909

（A）A yellow star indicates that a metric was applied during discovery, and data has been collected successfully

（B）A yellow star indicates that a metric was applied during discovery, but data collection has not started

（C）A yellow star indicates that a metric was applied during discovery, but FortiSIEM is unable to collect data.

（D）A yellow star indicates that a metric was not applied during discovery and, therefore, FortiSEIM was unable to collect data.