Question 200
A North Finance analyst defines subpattern conditions for quarantine events but cannot save the rule because no incident action exists. What rule component is mandatory before saving?
- A manually cleared older incident of the same category
- A completed export of every historical event from the past year
- At least one incident definition with its triggered attributes
- A custom lookup table regardless of the conditions
Explanation
Correct Answer
C:Considering correlation-rule investigation at North Finance: FortiSIEM requires at least one generated-incident definition. The quarantine subpattern must map relevant event attributes into the incident output before the rule can be saved.
Incorrect Answers
A:In correlation-rule investigation at North Finance: Existing incident lifecycle state does not substitute for defining the incident produced by the new rule.
B:Event export is not a prerequisite for rule definition; the missing component is how North Finance will represent the triggered incident.
D:Under correlation-rule investigation at North Finance: Lookup tables are optional enrichment sources. They are not a universal requirement for saving a quarantine analytics rule.
Question 201
Cloud Services wants an active suspicious launch incident on host-150 to clear after the original rule has not triggered for 45 minutes. The rule is a real-time rule. Which clear-condition option fits?
- Change the incident title to Resolved but leave status Active
- Increase notification frequency to one message per minute
- Exception effective for 45 minutes starting now
- Original Rule Does Not Trigger with a 45-minute clear period
Explanation
Correct Answer
D:Under rule deployment or exception at Cloud Services for host-150: The clear timer waits for the specified duration without another rule match, then changes the incident state when the condition is satisfied.
Incorrect Answers
A:Renaming an incident is not a status transition and provides no test of whether suspicious launch stopped.
B:For rule deployment or exception at Cloud Services for host-150: Notification cadence affects delivery only; it cannot use quiet time to clear the incident.
C:An exception suppresses future matching incidents; it is not equivalent to clearing an already-active host-150 alert after inactivity.
Question 202
FortiSIEM has three CPU utilization samples for host-150 in Research: 50%, 40%, and 50%. The rule should compare mean utilization across samples. Which search expression evaluates the required statistic?
- COUNT(Matched Events)
- AVG(CPU Util)
- MAX(CPU Util)
- SUM(CPU Util)
Explanation
Correct Answer
B:AVG calculates the arithmetic mean: (50 + 40 + 50) / 3 = 46.7%. This matches the average-utilization objective for host-150.
Incorrect Answers
A:In aggregate-query calculation at Research for host-150: COUNT reports the three matching samples, not their CPU utilization values. It would test frequency rather than the requested load measure.
C:Considering aggregate-query calculation at Research for host-150: MAX returns 50%, the single highest observation. A transient spike can exceed the mean, so it does not characterize all three samples.
D:SUM adds the sample percentages to 140; the total is not mean utilization and would distort a percentage threshold.
Question 203
City Branch is trying to restrict risky 198.51.100.40 from connecting to FortiGate’s own administrative interface, rather than a server behind the firewall. Which policy context is relevant?
- FortiGate local-in policy for traffic terminating on the firewall itself
- Only a FortiSIEM incident comment
- Only a server-side policy for forwarded database traffic
- Only a machine-learning training schedule
Explanation
Correct Answer
A:In IP feed and FortiGate enforcement at City Branch with the specified 198.51 value: Administrative connections to the FortiGate are local-in rather than forwarded sessions. To enforce a risky-source feed for this case, the control must apply to that traffic class.
Incorrect Answers
B:Comments do not provide the local-in filtering needed to limit administrative sessions from 198.51.100.40.
C:Considering IP feed and FortiGate enforcement at City Branch with the specified 198.51 value: A forwarded traffic policy is not the same path as a request terminating on the firewall management interface.
D:Under IP feed and FortiGate enforcement at City Branch with the specified 198.51 value: Learner scheduling has no direct effect on FortiGate local-in access policy evaluation.
Question 204
A saved City Branch Automation Policy for stopped service is not sending messages. Its rule, severity, and action criteria are correct. Which setting should be checked before changing detection rules?
- Whether the Automation Policy is enabled
- Whether the rule’s test window has been shortened to one second
- Whether the event parser was renamed after policy creation
- Configure incident severity with no message or integration action
Explanation
Correct Answer
A:In Automation Policy workflow at City Branch: FortiSIEM creates and stores policies independently of activation. An unchecked Enabled control prevents the policy from sending the expected stopped service alerts.
Incorrect Answers
B:Changing rule testing scope will not activate a disabled action policy for City Branch.
C:Considering Automation Policy workflow at City Branch: Parser naming is not a substitute for enabling an otherwise correctly scoped automation policy.
D:Under Automation Policy workflow at City Branch: Severity is a selection attribute. Notification does not occur until an Automation Policy connects matching incidents to an action.
Question 205
North Finance imported a new service group row into lookup table ApprovedPrivilegedUsers and immediately tested a rule, but the result still resembles the old table. No schema problem is present. What timing effect should be considered?
- Change the FortiGate interface IP to force a CMDB rescan
- Allow for the documented lookup-data propagation interval before retesting
- Delete every event from the historical database before retrying
- Assume a newly imported row permanently disables the correlation rule
Explanation
Correct Answer
B:For CMDB and lookup-table configuration at North Finance: Changes propagate through Supervisor/Worker Redis and are periodically reread by analytics. In FortiSIEM 7.2 this can take about 5–10 minutes, so an immediate rule result may be stale.
Incorrect Answers
A:In CMDB and lookup-table configuration at North Finance: An unrelated network address change does not accelerate lookup-table refresh on FortiSIEM analytics nodes.
C:Event deletion is not needed to refresh a lookup table and would destroy useful suspicious launch evidence for North Finance.
D:Lookup updates do not by themselves disable a rule. A delay while the new service group entry reaches analytics is a more consistent explanation.
Question 206
FortiSIEM raises a new policy denial incident on host-153 for East Retail. No investigation has occurred. What are the initial status and resolution fields expected for that incident?
- Status Active; Resolution None
- Status Active; Resolution False Positive
- Status System Cleared; Resolution False Positive
- Status Manually Cleared; Resolution True Positive
Explanation
Correct Answer
A:A newly triggered incident starts Active with no verdict. The East Retail analyst must investigate before classifying the policy denial finding as true or false positive.
Incorrect Answers
B:For incident-management case at East Retail for host-153: Assigning a false-positive classification before investigation asserts a conclusion that the freshly generated policy denial alert has not earned.
C:Considering incident-management case at East Retail for host-153: System clearing follows a configured recovery condition and does not represent the initial new-incident state.
D:That describes a verified, manually resolved real issue, not an untriaged alert that just fired on host-153.
Question 207
For Partner Services the two Host groups contain 3 and 3 suspicious launch events. The analyst needs total event count per Host, without mixing the sources. Which pair of settings is necessary?
- Group By Process Name and show AVG(Sent Bytes)
- Filter to one Host before counting and treat it as the whole result
- Show only COUNT(Matched Events) without a Group By attribute
- Group By Host and show COUNT(Matched Events)
Explanation
Correct Answer
D:For For Partner Services the two Host groups contain 3 and 3 suspicious launch events. The analyst needs total event count per: Under aggregate-query calculation at Partner Services with the specified 3 value: Host partitions the matching events into independent groups while COUNT tallies their individual 3 and 3 records.
Incorrect Answers
A:In aggregate-query calculation at Partner Services with the specified 3 value: This would summarize a different dimension and average traffic volume rather than count suspicious launch events per Host.
B:For aggregate-query calculation at Partner Services with the specified 3 value: Excluding the other source can produce one count but cannot satisfy the simultaneous side-by-side Host comparison.
C:For For Partner Services the two Host groups contain 3 and 3 suspicious launch events. The analyst needs total event count per: Considering aggregate-query calculation at Partner Services with the specified 3 value: A global COUNT collapses the 6 events together and loses the separate per-Host quantities.
Question 208
Research is prioritizing two hosts: one has a rare high-severity stopped service event and high asset criticality, while the other has routine low-impact alerts. Which FortiSIEM concept better combines those signals?
- Host or user risk score using severity, rarity, resolution, and criticality
- Number of characters in each raw syslog message
- Alphabetical order of the hostnames
- Change only the dashboard grouping and assume it updates the incident case history
Explanation
Correct Answer
A:In historical or real-time event analysis at Research: FortiSIEM 7.2 enhanced risk scoring incorporates incident rarity and asset criticality alongside severity/resolution, helping identify materially different investigation priority.
Incorrect Answers
B:For Research is prioritizing two hosts: one has a rare high-severity stopped service event and high asset criticality, while the: For historical or real-time event analysis at Research: Message length does not capture rarity, consequence, or asset importance for the two Research hosts.
C:Considering historical or real-time event analysis at Research: Lexical ordering is not a meaningful threat or business-impact prioritization measure for stopped service incidents.
D:For Research is prioritizing two hosts: one has a rare high-severity stopped service event and high asset criticality, while the: Under historical or real-time event analysis at Research: Grouping changes a view of the data, not the underlying incident dispositions, investigator notes or case associations.
Question 209
Partner Services has created a rule to detect quarantine and populated its conditions, but wants to minimize false alerts before production. What is the appropriate immediate next workflow?
- Test the saved inactive rule against relevant events, then activate it
- Replace the rule with a notification policy that has no conditions
- Activate the rule without testing because Save guarantees accuracy
- Delete all prior log events so test output is empty
Explanation
Correct Answer
A:FortiSIEM saves new rules inactive. Testing the proposed quarantine conditions against observed events exposes overly broad filters or incorrect thresholds before live incidents appear.
Incorrect Answers
B:For Partner Services has created a rule to detect quarantine and populated its conditions, but wants to minimize false alerts: For rule deployment or exception at Partner Services: Automation policies act after incidents; they cannot independently perform the rule’s required event correlation.
C:For Partner Services has created a rule to detect quarantine and populated its conditions, but wants to minimize false alerts: Considering rule deployment or exception at Partner Services: Saving validates configuration structure, not the operational meaning of the detection for Partner Services event traffic.
D:Erasing evidence prevents meaningful verification of the detection’s ability to match legitimate quarantine activity.
Question 210
After a connection detection, Corporate HQ needs a watchlist of Source IP IP addresses for use in a second analytic rule. What must the first rule’s generated incident provide?
- Enable the response workflow before validating the underlying rule match
- A typed Source IP incident attribute compatible with the IP watchlist
- Only the literal words suspected host in the incident title
- A notification threshold without an incident definition
Explanation
Correct Answer
B:For rule deployment or exception at Corporate HQ: The watchlist update uses a field from the generated incident. A correctly typed Source IP value lets downstream rules match the same address reliably.
Incorrect Answers
A:In rule deployment or exception at Corporate HQ: An Automation Policy cannot compensate for inaccurate event correlation; an untested rule may flood or miss production incidents.
C:For After a connection detection, Corporate HQ needs a watchlist of Source IP IP addresses for use in a second analytic rule.: Considering rule deployment or exception at Corporate HQ: An informal title string does not provide a typed IP field that the watchlist can store and another rule can match.
D:For After a connection detection, Corporate HQ needs a watchlist of Source IP IP addresses for use in a second analytic rule.: Under rule deployment or exception at Corporate HQ: Alerts require a defined incident, and the watchlist needs its typed attribute; frequency alone supplies neither.