The correct answer is C. SSL . FortiSIEM receives raw logs, processes them through parsers, normalizes the extracted fields, classifies the event, and stores the structured data. The Study Guide explains the FortiSIEM process flow: data is collected, processed by the parsing engine, normalized, classified, and then stored. It further states that normalization extracts individual fields from raw events and maps those fields to a common schema. The FortiSIEM 7.4 User Guide describes a parser as a file containing instructions for the parser module to convert a raw log into event attributes. In the exhibit, the raw FortiGate log includes values such as profiletype= " applist " , appcat= " Network.Service " , and app= " SSL " . The field that directly represents the application value is app= " SSL " . Therefore, the parser would use SSL to populate the normalized Application Name field. applist describes the profile type, Network.Service is the application category, and wan1 is the interface, not the application name.

The correct answer is A. FortiSIEM agent. The FortiSIEM Study Guide identifies FortiSIEM agents as the component responsible for “file, log monitoring, and UEBA.” It also explains that FortiSIEM agents can be installed on endpoints or servers to provide data collection functions that native syslog may not provide. For Windows systems specifically, the guide states that Windows servers do not natively send syslog messages and that a FortiSIEM Windows agent can be installed to perform that function. The FortiSIEM 7.4 User Guide also confirms that FortiInsight UEBA functionality runs as an integrated module within the FortiSIEM Windows Agent in newer releases. SSH and SNMP are access or monitoring protocols; they can support discovery or performance monitoring, but they are not the UEBA data-sending component. A FortiSIEM worker performs analysis and search functions inside the FortiSIEM architecture; it is not installed on endpoints to collect UEBA telemetry. Therefore, the FortiSIEM agent is the correct mechanism for sending UEBA-relevant endpoint data to FortiSIEM.

The correct answer is C. Regression. Regression is the machine learning task used when a model predicts a target value based on other fields in a dataset. In FortiSIEM’s machine learning workflow, regression configuration includes selecting Fields to use for Prediction and a Field to Predict. The User Guide explains that during regression training, the analyst chooses the fields used for prediction and the field being predicted, then trains the model with a Train factor. This matches the question exactly: the model predicts a target based on other fields, and the inference phase can identify anomalies when observed values differ significantly from predicted values. Classification is used to assign records to discrete classes or categories, not to predict a continuous target metric from other variables. Clustering groups similar observations without a predefined target field. Forecasting predicts future values over time, normally based on time-series behavior. Because the question specifically describes predicting a target field from other dataset fields and detecting mismatch from the prediction, the correct machine learning method is Regression.

The correct answer is A. Filters, Aggregate, Group By definitions. FortiSIEM rule subpatterns are built from three main configuration areas. The Study Guide states that rule conditions are built from subpatterns of event attribute filters and aggregation functions. It also explains that the single-subpattern rule example in the FortiSIEM GUI demonstrates how “filters, aggregate, and group by” come together to form a subpattern rule. Filters define which events are eligible for matching, such as Event Type, Source IP, Destination IP, or other event attributes. Aggregate defines the threshold or statistical calculation, such as COUNT(Matched Events) > = 3 or an average metric threshold. Group By defines how FortiSIEM partitions matching events into separate evaluation groups, such as by User, Source IP, Destination IP, Host Name, or Reporting Device. Time Window is part of the higher-level rule condition, not one of the three subpattern definition sections. Therefore, the exact components used to define a subpattern are Filters, Aggregate, and Group By.

The exhibit shows a machine learning Regression configuration. In FortiSIEM regression, selected numerical fields are used as predictors, and another field is selected as the value to predict. The FortiSIEM 7.4 User Guide’s Machine Learning section lists Regression separately and describes the training workflow, including selecting fields used by the algorithm. The exhibit shows Memory Utilization, Sent Bytes, and Received Bytes selected under Fields to use for Prediction, while CPU Utilization is selected under Field to Predict. This means Memory Utilization is an input variable used by the model. If memory utilization is consistently high during training or retraining, that higher value becomes part of the learned model pattern. FortiSIEM does not automatically trigger a high-memory incident merely because a regression input value is high; an incident would require inference behavior and an anomaly action or rule configuration. Option C is also wrong because FortiSIEM does not dynamically lower a CPU trigger threshold just because memory is high. The correct behavior is model update based on the higher observed input value.

FortiSIEM grouping works by combining events that have the same values for all selected Group By attributes. The Study Guide’s rule and subpattern example states that when multiple events have the same Group By values, “they are grouped together in one row, and the count column tracks the number of events for each of those rows.” In the exhibit, the selected grouping fields are Reporting Device, Reporting IP, and Application Category. The table contains six raw rows, but two rows share the same grouped combination: FW01 / 10.1.1.1 / DB . Those two rows are collapsed into one grouped result. The other combinations are unique: FW02 / 10.1.1.2 / WebApp, FW01 / 10.1.1.1 / SSH, FW03 / 10.1.1.3 / DB, and FW04 / 10.1.1.4 / SSH. That creates five grouped rows in total. FortiSIEM does not display six because grouping removes duplicate combinations, and it does not display four because only one duplicate combination exists.

The correct answer is D. ZTNA tags. FortiSIEM 7.4 includes FortiEMS endpoint tagging integration. The FortiSIEM 7.4 User Guide states that FortiSIEM supports discovery of FortiEMS servers by using the FortiEMS Management Server API with basic username/password authentication. It also explains that after FortiEMS discovery, FortiSIEM can tag or untag a host by using classification tags on the FortiEMS server. In a ZTNA deployment, those tags are imported by member Fortinet devices, especially FortiGate firewalls, and are referenced in ZTNA firewall rules. The guide gives a common use case in which a host is tagged as suspicious or potentially compromised so firewall rules can isolate it or allow only minimal traffic. Host software versions, FortiSIEM license information, and host login credentials are not the FortiEMS API information relevant to this ZTNA tagging workflow. The API integration supports retrieving FortiEMS-managed host context and using classification/ZTNA tags for automated response and policy enforcement.

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.

The correct answer is B because the analyst is searching for events to either of two destination IP addresses, but the filter uses the wrong Boolean relationship. The FortiSIEM Study Guide explains structured searches with multiple conditions and states that “when you use multiple conditions, you must specify the next logical operator between conditions.” It gives a direct example: when searching for events from two specific devices, the first condition is one IP address, the second condition is another IP address, and “the next logical operator between the two conditions is an OR operator, because the search is for events from condition 1 OR condition 2.” The same logic applies here. A single event cannot usually have Destination IP equal to 10.10.1.1 and Destination IP equal to 192.168.1.1 at the same time. Using AND requires both conditions to be true simultaneously, so no results are returned. The correct operator between the two Destination IP conditions is OR.