Free Practice Questions for Fortinet NSE6_FSM_AN-7.4 Exam

The best matching analytics search is Username CONTAIN smit. The FortiSIEM Analytics lesson explains keyword and attribute matching by using the CONTAIN operator for searching values inside raw logs or attributes. The Study Guide gives a direct example of FortiSIEM translating keyword logic into a condition such as “Raw Event Log CONTAIN TCP.” That shows the operator is designed for substring-style matching rather than full-value equality. For a user such as JSmith, the string fragment smit is contained inside the username value, so the condition can match events where the username appears as JSmith, jsmith, or possibly in a longer identity string such as a domain-qualified username. Option A is wrong because smith is not the complete username and uses an equality-style comparison. Option B is wrong because it excludes usernames ending in jsmith. Option C uses the wrong operator form for this context. Therefore, the practical FortiSIEM analytics condition that can match the target failed-login event is Username CONTAIN smit.

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.

When an associated rule triggers, FortiSIEM performs all selected actions in the automation policy. In this case, it will send an email/SMS/webhook, run the remediation script, invoke the integration policy (even if none is currently defined), and create a case. All checked actions are executed.

The correct answer is B because FortiSIEM automation policies are designed to execute the actions selected in the policy when the policy criteria match. The FortiSIEM Study Guide states that automation policy actions define what occurs when policy criteria match. It lists possible automation actions such as sending an alert, invoking an integration policy, sending SNMP or HTTPS XML notifications, opening a remedy ticket or creating a FortiSIEM case, sending email or SMS, and running a remediation script. The same Study Guide explains that users can configure “any combination of actions.” Therefore, there is no single-action precedence rule where remediation overrides all other selected actions or email runs only because it appears first. If multiple action checkboxes are selected, FortiSIEM executes the configured selected actions according to the automation policy. In the exhibit, multiple actions are selected, including email/SMS/webhook, remediation/script, integration policy, and case creation. Option C is incorrect because the absence of a defined integration policy does not make FortiSIEM ignore the other selected actions. The policy runs the selected configured actions.

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.

The correct answer is A. Design. In the FortiSIEM 7.4 User Guide’s anomaly detection workflow, the first configuration step is Step 1: Design. In that step, FortiSIEM requires the analyst to identify the fields that will be analyzed by the machine learning job. The guide states that under Design, the analyst must identify Fields to Analyze, and explains that these fields are considered for anomaly detection and must currently be numerical fields. The guide also identifies the time field requirement for statistical deviation algorithms and notes that a FortiSIEM report is used to provide the dataset. The Prepare Data step comes later and is used to load or prepare the data source for training. The Train step runs the algorithm against the prepared dataset. The Schedule step is used after training to run inference. Therefore, the selection of fields to analyze belongs to the Design phase, not Prepare Data, Train, or Schedule. This sequence matters because FortiSIEM must know which numerical fields are relevant before it can prepare, train, or run inference on the machine learning job.

FortiSIEM applies tags to FortiClient EMS-managed hosts through FortiEMS integration. The FortiSIEM 7.4 User Guide states that FortiSIEM supports discovery of FortiEMS servers using the FortiEMS Management Server API with username/password authentication. That supports option A: FortiEMS API credentials must be configured on FortiSIEM. The same guide explains that after FortiEMS discovery, “FortiSIEM can tag or untag a host, using classification tags on FortiEMS server.” It further explains the ZTNA workflow: in ZTNA, these tags are imported by Fortinet devices, especially FortiGate firewalls, and referenced in ZTNA firewall rules. That supports option C: the tag value used for ZTNA classification must be available/defined for the FortiEMS tagging workflow. Option B is not the best required configuration in the question because a remediation script is an execution method, not one of the two foundational settings being asked for. Option D reverses the API relationship; FortiSIEM connects to FortiEMS using FortiEMS credentials, not FortiSIEM API credentials stored on EMS.

The correct answer is A. FortiSIEM supports bulk rule operations for selected rules. The FortiSIEM 7.4 User Guide states that if you have permission to activate a rule, you can activate or deactivate multiple rules with a single click. The procedure instructs the user to go to Resources > Rules, click the edit icon, select Multiple Rules, choose the rules, and then use the Select Actions panel. In that panel, the guide states that you can select a Severity from the Severity drop-down list to change the selected rules, and you can also select or deselect active status options for new or existing organizations to make the selected rules active or inactive. This proves that both operations are available: severity changes and activation/deactivation changes. Option B is too restrictive because FortiSIEM allows multiple-rule selection. Option C is incomplete because activation/deactivation is also supported. Option D is incomplete because severity changes are also supported. Therefore, the correct answer is that you can change severity and activate or deactivate multiple selected rules.

The correct answers are A. Email and B. FortiSIEM Case. FortiSIEM automation policies can notify or route work to analysts when an incident is triggered. The Study Guide describes the incident notification email workflow and explains that when an incident triggers and an automation policy is defined, FortiSIEM can send a notification email using the default template. It also explains that notification frequency is configured per rule and that repeated incident notifications are controlled by the frequency timer. The FortiSIEM 7.4 User Guide also describes automated case creation through automation policy. It states that an automation policy can use the action Create Case when an incident is created, and that a case management policy can assign FortiSIEM Analyst Teams in an ordered handling sequence. Syslog is not listed as one of the analyst notification methods in the automation policy options shown in this question; FortiSIEM supports SNMP and webhook-style actions, but not “Syslog” as the listed answer. A pop-up window is not an automation policy notification method. Therefore, the two correct analyst-notification/routing methods are Email and FortiSIEM Case.

The best answer is A. Two . The exhibit shows an Analytics Search scatter plot with two visually distinct groups of data points: one isolated group around the lower-left area of the chart and another dense group near the upper-right area. For KMeans clustering, the analyst must provide the number of clusters based on the observed structure of the data. The FortiSIEM 7.4 User Guide describes KMeans as “an unsupervised clustering algorithm that groups data points into user specified K groups so that each data point belongs to one group.” It also states that KMeans “tries to iteratively minimize intra-cluster distance and maximize inter-cluster distance” and notes that the user must “specify the number of clusters based on user’s knowledge of data.”

The same FortiSIEM guide explains that during Clustering Local Mode training, the analyst chooses the algorithm and, “for KMeans choose the cluster size as a guess.” In this exhibit, the natural guess is 2, because the scatter plot separates into two obvious groups. Fifty or 100 clusters would overfit the small number of visible groups, while one cluster would merge two clearly separate behaviors into a single cluster.