NSE6_FSM_AN-7.4 Certification Exam Guide + Practice Questions Updated 2026

Explanation:
The time period must be defined under the Define Condition tab of the rule. The FortiSIEM Study Guide states that a rule has three components: General, Condition, and Action. The General section defines the overall purpose and scope of the rule, the Condition section specifies which conditions trigger the rule, and the Action section configures what happens after the rule is triggered. The Study Guide further explains that on the Define Condition page, FortiSIEM specifies “the conditions―event attributes and thresholds―that will trigger the rule and create an incident,” including “the time window” within which the subpatterns must match for the rule condition to be satisfied. It also states that when there is more than one subpattern, you must define the logic between subpatterns and their relationships or constraints.
For a 24-hour multiple-subpattern rule, the guide gives an example using an 86400-second time window, which equals 24 hours, and shows it under Resource > Rules > Define Condition.
Therefore, the time period is not configured inside each individual subpattern, not under General, and not under Define Action.

Explanation:
The rule is matching VPN logon failure events where the Source Country is outside the configured home country. In the exhibit, the filter section shows Event Type IN EventTypes: VPN Logon Failure and Source Country NOT IN GeoCountries: My Home. That means the source must be outside the home-country geo group. The aggregate condition shows COUNT(Matched Events) >= 3, so the rule is looking for at least three matching failed VPN logon events. The Group By section uses Source IP and User, so FortiSIEM evaluates the count per unique source IP and user combination, not by different countries.
The FortiSIEM Study Guide explains that a rule subpattern contains three components: Filter , Aggregate, and Group By. It states that the filter identifies the matching event group, the aggregate function specifies how many events must match, and Group By combines events with the same grouped attributes into one row while the count tracks those events.
Option A is wrong because the rule does not count different countries.
Options C and D are wrong because the source country is explicitly NOT IN My Home, not inside the home country.

Explanation:
The search fails because nested analytics queries require the outer query attribute type to match the inner query display-column data type. The FortiSIEM Study Guide explicitly explains this rule in the Nested Query section: “Another important aspect to understand is that the data value types must match.” It further explains that each inner query display column has a data value type, such as IP, string, or integer, and the outer query attribute must match that type. The FortiSIEM 7.4 User Guide states the same operational requirement: for a nested query to work correctly, “the data type of the filter attribute in the outer query must match up with the data type of one certain display column in the inner query.” Therefore, if the inner query returns a string attribute but the outer query compares it against an IP-type attribute, FortiSIEM cannot produce a valid match. The issue is not the time range, not the use of User and Event Type together, and not the Boolean operator. It is an attribute type mismatch between the query and subquery.

Explanation:
To detect three failed login attempts within three minutes, you must set the aggregate count to 3 in the subpattern and the time window to 180 seconds in the rule condition. This ensures the rule triggers only if three or more failed logins occur in that timeframe.
The correct answer is A because three minutes equals 180 seconds, and the aggregate threshold must be set to three matching events. The FortiSIEM Study Guide explains that rule conditions specify event attributes and thresholds that trigger the rule and create an incident. It further states that the time window defines the period within which the subpattern must match for the rule condition to be satisfied. The Study Guide’s single-subpattern rule example shows the same principle: the condition has a configured time window, and the Aggregate section uses a function such as COUNT(Matched Events) to require a minimum number of matching events. In this question, the analyst wants the rule to trigger when three failed login attempts happen within three minutes.
Therefore, the rule condition time window must be 180 seconds, and the aggregate count must be 3. A 90-second window would detect only events inside one and a half minutes, not the required three minutes. An aggregate count of 2 would trigger too early because the requirement is three failed attempts.

Explanation:
The correct answer is C because the rule’s Group By attributes determine how events are grouped before the aggregate condition is evaluated. The Study Guide explains that rule conditions are built from subpatterns consisting of event attribute filters and aggregation functions. It also explains that a subpattern combines filters, aggregate, and group by fields to form the rule logic. In this case, the filters may return matching events in Analytics, but the rule still may not trigger because the aggregate condition is calculated separately for each unique Group By combination. The exhibit groups by Destination IP and User while applying COUNT(Source IP) >= 2. This means FortiSIEM does not count all matching events together. Instead, it counts only events that share the same Destination IP and User combination. If no single grouped combination reaches the aggregate threshold, no incident is created. The issue is not the event lookup, not the Destination Host Name format, and not necessarily the aggregate expression itself. The grouping logic is what restricts the counted event set.