Question 1
A historical endpoint process alerts search for asset host-26 is grouped by both Host and Process Name. The matched data contains 6 distinct (Host, Process Name) pairs even though there are only 3 unique Host values. How many result rows should grouping produce?
- 6 grouped rows
- 18 grouped rows
- 9 grouped rows
- 3 grouped rows
Explanation
Correct Answer
A:Each distinct combination of Host and Process Name creates one group, so 6 key pairs yield 6 aggregate rows.
Incorrect Answers
B:For aggregate-query calculation at the SOC for host-26 using endpoint process alerts: A Cartesian product assumes every source-destination combination occurred. The query returns only 6 observed combinations.
C:Considering aggregate-query calculation at the SOC for host-26 using endpoint process alerts: Adding the two distinct counts double-counts category dimensions. A composite group key is based on observed pairs, not the sum of marginal counts.
D:3 counts unique values of Host alone; adding Process Name can split each source across multiple results.
Question 2
A security engineer is designing table OutboundExceptions at East Retail. The asset class field stores names and text. Which available lookup-table field type should be chosen?
- STRING
- LONG
- DOUBLE
- BOOLEAN
Explanation
Correct Answer
A:In CMDB and lookup-table configuration at East Retail: STRING holds character data. It is suitable for textual asset class labels and avoids inappropriate numeric operations on identity values.
Incorrect Answers
B:For CMDB and lookup-table configuration at East Retail: LONG represents integer values. It fits whole-number asset class identifiers but not free text or decimal fractions.
C:Considering CMDB and lookup-table configuration at East Retail: DOUBLE represents real-valued numbers, such as fractional asset class scores; it is unsuitable for arbitrary text or exact integer-only identifiers when LONG is intended.
D:Under CMDB and lookup-table configuration at East Retail: BOOLEAN is not one of the schema field types offered in the FortiSIEM 7.2 lookup table editor, which provides STRING, LONG, and DOUBLE.
Question 3
For City Branch, expected policy denial volume differs significantly among host-127-class devices. A fixed threshold of 20 events creates noise. Which rule concept better accounts for each device’s established normal behavior?
- Use an appropriate statistical baseline to derive an anomaly threshold
- Use the rule title as a numeric threshold
- Increase the one global threshold equally for all devices
- Disable the rule and stop collecting the event source
Explanation
Correct Answer
A:FortiSIEM can compute baseline statistics for dynamic rule thresholds. Comparing the observed 37 events against local normal activity is more meaningful than one global constant.
Incorrect Answers
B:For subpattern correlation at City Branch for host-127: The title is metadata, not a computed mean, variance or other baseline statistic for anomaly evaluation.
C:A universal increase might suppress false alerts on host-127 yet miss genuinely unusual activity on quieter systems.
D:This removes both false positives and valuable detections instead of adapting policy denial criteria to an observed baseline.
Question 4
FortiSIEM raises a new blocked request incident on host-88 for Research. No investigation has occurred. What are the initial status and resolution fields expected for that incident?
- Status Active; Resolution False Positive
- Status Manually Cleared; Resolution True Positive
- Status Active; Resolution None
- Status System Cleared; Resolution False Positive
Explanation
Correct Answer
C:A newly triggered incident starts Active with no verdict. The Research analyst must investigate before classifying the blocked request finding as true or false positive.
Incorrect Answers
A:In incident-management case at Research for host-88: Assigning a false-positive classification before investigation asserts a conclusion that the freshly generated blocked request alert has not earned.
B:That describes a verified, manually resolved real issue, not an untriaged alert that just fired on host-88.
D:Under incident-management case at Research for host-88: System clearing follows a configured recovery condition and does not represent the initial new-incident state.
Question 5
A West Operations report groups failed authentication events by User and uses COUNT(Matched Events). The analyst wants only groups exceeding 9 events to remain in the result, not to remove the underlying records before aggregation. What should be configured?
- A Display Condition of COUNT(Matched Events) > 9
- Group By COUNT(Matched Events) instead of User
- A time range of exactly 9 seconds
- An event filter that rejects all records until their count exceeds 9
Explanation
Correct Answer
A:For A West Operations report groups failed authentication events by User and uses COUNT(Matched Events). The analyst wants only: In aggregate-query calculation at West Operations with the specified 9 value: FortiSIEM display conditions filter aggregates after grouping, analogous to HAVING. Groups must first be counted, then those above 9 remain visible.
Incorrect Answers
B:For aggregate-query calculation at West Operations with the specified 9 value: COUNT is the measure to test, while User defines the groups whose counts are compared; swapping these loses the per-source view.
C:Considering aggregate-query calculation at West Operations with the specified 9 value: The literal threshold is a count of records, not a query time window. Shortening time would alter which failed authentication events are included.
D:Under aggregate-query calculation at West Operations with the specified 9 value: An event filter evaluates record attributes before aggregation. Individual VPN authentication records events do not carry the completed group count to filter on.
Question 6
North Finance / host-78: the SOC must enforce a risky-IP feed against administrative connections to the FortiGate itself. Which choices address the correct traffic path? Choose TWO.
- Disable connector refresh after creating the initial policy
- Apply the appropriate FortiGate local-in restrictions referencing that indicator set
- Use only a forwarding policy for application servers behind the firewall
- Publish supported source IP indicators through FortiSIEM’s external feed
- Store source usernames where FortiGate expects IPv4 indicator values
Explanation
Correct Answers
B:Administrative sessions terminate on FortiGate, so local-in rather than only forwarding policy logic must cover the restriction.
D:FortiGate needs a parseable address list to match source IPs; user names alone are not sufficient for an IP connector.
Incorrect Answers
A:Without updates the firewall can miss newly risky addresses or retain removed ones, undermining timely enforcement.
C:Forwarded server traffic is a different path and need not filter connections to FortiGate’s own administrative interface.
E:An IP external connector cannot reliably enforce username-only entries as source addresses.
Question 7
A West Operations report groups stopped service events by Host and uses COUNT(Matched Events). The analyst wants only groups exceeding 9 events to remain in the result, not to remove the underlying records before aggregation. What should be configured?
- Group By COUNT(Matched Events) instead of Host
- An event filter that rejects all records until their count exceeds 9
- A time range of exactly 9 seconds
- A Display Condition of COUNT(Matched Events) > 9
Explanation
Correct Answer
D:Under aggregate-query calculation at West Operations with the specified 9 value: FortiSIEM display conditions filter aggregates after grouping, analogous to HAVING. Groups must first be counted, then those above 9 remain visible.
Incorrect Answers
A:In aggregate-query calculation at West Operations with the specified 9 value: COUNT is the measure to test, while Host defines the groups whose counts are compared; swapping these loses the per-source view.
B:For aggregate-query calculation at West Operations with the specified 9 value: An event filter evaluates record attributes before aggregation. Individual service health records events do not carry the completed group count to filter on.
C:Considering aggregate-query calculation at West Operations with the specified 9 value: The literal threshold is a count of records, not a query time window. Shortening time would alter which stopped service events are included.
Question 8
The Partner Services SOC is designing a rotating team to handle assigned unauthorized change cases. Which FortiSIEM setup enables assignment to the right analysts and team leads?
- Use only an event-data Group By over destination ports
- Replace case owners with raw syslog facility codes
- Configure a firewall NAT rule as the case roster
- Organize eligible FortiSIEM Analysts into Analyst Teams under CMDB > Users
Explanation
Correct Answer
D:Under incident-management case at Partner Services: Case assignments use defined analyst teams, whose members and leads can participate in the management policy. This supports coordinated ownership across shifts.
Incorrect Answers
A:Grouping data does not define analyst membership, leads or work queues for cases in Partner Services.
B:For incident-management case at Partner Services: Log facility values characterize messages, not human case-assignment permissions or team structure.
C:Considering incident-management case at Partner Services: Network address translation does not register eligible investigators or define case ownership.
Question 9
West Operations needs all CMDB devices whose IDs occur in a report of blocked request web application alerts events from the past 10 minutes. Which nested-search arrangement is suited to that goal?
- Outer event query with an inner CMDB query returning owners only
- Real-time Group By over all incoming events
- Outer CMDB query with an inner event query returning matching device identifiers
- Two unrelated CMDB queries combined only by report titles
Explanation
Correct Answer
C:The desired result is a device inventory list, so CMDB forms the outer set. The inner event report supplies qualifying IDs from the 10-minute event window.
Incorrect Answers
A:This direction produces event results, not a complete CMDB device list selected by observed blocked request activity.
B:For nested search comparison at West Operations using web application alerts with the specified 10 value: The request selects inventory objects based on prior stored events. Streaming Group By is unsupported and does not implement the needed outer CMDB set.
D:Without the inner event condition, inventory queries cannot establish which devices actually generated web application alerts in the specified interval.
Question 10
North Finance / host-48: a correlation rule creates a matching subpattern but no usable incident. Which two configuration elements should the rule owner inspect? Choose TWO.
- The incident-generation definition attached to the rule
- Use a search-result column as if it were a rule subpattern with conditions
- The rule activation state
- Change the incident severity but leave the event-selection and trigger components unset
- Configure an Automation Policy action without a rule-generated incident
Explanation
Correct Answers
A:Incident metadata and creation configuration are required for a match to become the alert artifact that analysts can manage.
C:A newly created or inactive rule does not evaluate production events until it is enabled; a valid pattern alone is not sufficient.
Incorrect Answers
B:For correlation-rule investigation at North Finance for host-48: Report display fields do not express the event class, grouping and thresholds that a rule must evaluate.
D:Under correlation-rule investigation at North Finance for host-48: Severity classifies an incident after a rule match; it cannot replace event filters and the actual correlation trigger.
E:In correlation-rule investigation at North Finance for host-48: An action policy operates on qualifying incidents; it does not independently implement the matching event rule and incident definition.