Question 750
An analyst wants separate incidents when the same connection burst arises from different Source IP values in Manufacturing. Which subpattern component separates the candidate event populations?
- Configure an outbound email recipient for each log entry
- Set a higher incident title priority
- Use no Group By and count all events globally
- Group By the Source IP event attribute
Explanation
Correct Answer
D:Under correlation-rule investigation at Manufacturing: Grouping partitions matching records by their Source IP value before applying the rule threshold. This preserves per-actor detection rather than merging every network flow records event.
Incorrect Answers
A:In correlation-rule investigation at Manufacturing: Alert recipients do not control the correlation grouping key or the incident identity.
B:For correlation-rule investigation at Manufacturing: Title wording cannot partition events from different Source IP entities during subpattern evaluation.
C:Considering correlation-rule investigation at Manufacturing: A global count allows small bursts from unrelated sources to accumulate into a single trigger, losing the per-Source IP boundary.
Question 751
West Operations is building a scheduled analytics rule for stopped service. A designer tries adding two distinct subpatterns to its condition. Which FortiSIEM 7.2 restriction explains the rejection?
- All rules are limited to one event attribute globally
- Scheduled rules support only one subpattern
- Scheduled rules must use only raw-text keywords as filters
- Scheduled rules cannot use any event filters
Explanation
Correct Answer
B:For correlation-rule investigation at West Operations with the specified 7.2 value: FortiSIEM explicitly restricts scheduled rule conditions to a single subpattern. Multi-subpattern temporal correlation belongs to applicable real-time rule designs.
Incorrect Answers
A:In correlation-rule investigation at West Operations with the specified 7.2 value: A subpattern may use multiple filter attributes. The documented scheduled restriction is a structural subpattern count.
C:Considering correlation-rule investigation at West Operations with the specified 7.2 value: Normalized Event Attribute conditions are supported in rule filtering; the problem is the second subpattern rather than parser field use.
D:Under correlation-rule investigation at West Operations with the specified 7.2 value: Scheduled rules can specify the one subpattern’s filters; the limitation concerns the number of subpatterns, not whether stopped service can be selected.
Question 752
East Retail has confirmed that an inner blocked request report from web application alerts returns the expected Source IP values, yet the outer search unexpectedly omits older eligible records. Both types match. Which time-related check is most useful?
- Change the notification action from email to SNMP
- Delete the saved inner report and rely on a display-only value
- Review the independent outer and nested report time ranges
- Replace the matched event filter with an unrelated device property
Explanation
Correct Answer
C:Considering nested search comparison at East Retail using web application alerts: Even compatible Source IP comparisons fail to include older evidence when either dataset is queried over an overly narrow interval. Check both temporal scopes.
Incorrect Answers
A:In nested search comparison at East Retail using web application alerts: Notification channel selection does not govern whether older event rows qualify for a nested Analytics query.
B:For nested search comparison at East Retail using web application alerts: The inner report is the query’s value source. Removing it prevents the nested condition from examining the relevant previous data.
D:Changing the identity test abandons the intended blocked request correlation rather than addressing an interval omission.
Question 753
The Manufacturing search has 6 matching network flow records events for host-116 and 5 for a second host. The analyst groups by Source IP. What determines the count of result rows?
- The number of columns selected for display
- The number of rules enabled on the FortiSIEM Supervisor
- The number of distinct Source IP values among matched events
- The total number of events, 11
Explanation
Correct Answer
C:Group By emits a separate aggregate row for each distinct Source IP combination. Event counts of 6 and 5 affect group measures, not inherently the number of groups.
Incorrect Answers
A:In aggregate-query calculation at Manufacturing for host-116 using network flow records: Display columns determine attributes and measures shown; merely adding a column does not establish the number of distinct Source IP groups.
B:For aggregate-query calculation at Manufacturing for host-116 using network flow records: Rule availability affects incident correlation, while this historical search’s row cardinality comes from distinct grouping-key values.
D:Under aggregate-query calculation at Manufacturing for host-116 using network flow records: 11 is the combined raw event count. After Group By, several events can collapse into one Source IP-specific result row.
Question 754
City Branch imported a new maintenance state row into lookup table MaintenanceExclusions 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
- Delete every event from the historical database before retrying
- Assume a newly imported row permanently disables the correlation rule
- Allow for the documented lookup-data propagation interval before retesting
Explanation
Correct Answer
D:Under CMDB and lookup-table configuration at City Branch: 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 City Branch: An unrelated network address change does not accelerate lookup-table refresh on FortiSIEM analytics nodes.
B:Event deletion is not needed to refresh a lookup table and would destroy useful rejected request evidence for City Branch.
C:Considering CMDB and lookup-table configuration at City Branch: Lookup updates do not by themselves disable a rule. A delay while the new maintenance state entry reaches analytics is a more consistent explanation.
Question 755
Cloud Services is correlating roaming.p suspicious login activity with a high-value host-196 object. What additional data should remain available to improve prioritization?
- An inactive remediation script disconnected from the incident
- Only the number of characters in the hostname
- Group raw events by their collector name without retaining user or host identity
- Host criticality from CMDB together with relevant user-event context
Explanation
Correct Answer
D:Under entity-behavior risk evaluation at Cloud Services for host-196: Asset criticality increases the meaning of risky activity. Combining CMDB importance with user and host observations helps analysts prioritize the potentially impactful access.
Incorrect Answers
A:An unused script does not enrich risk signals or explain the actual impact of an access attempt against host-196.
B:Hostname length is an arbitrary string property and does not reflect the business importance of host-196.
C:Considering entity-behavior risk evaluation at Cloud Services for host-196: Collector grouping describes ingestion infrastructure rather than the identity whose behavior and risk must be evaluated.
Question 756
After opening one deny event from gateway denies, an investigator wants other events having the same Source IP on host-188, not merely lines containing its spelling. How should the query be narrowed?
- Filter on the parsed Source IP event attribute with the exact value
- Group all events by their ingestion minute
- Use only a free-text keyword extracted from the raw event
- Query CMDB for every inventoried asset instead of events
Explanation
Correct Answer
A:A structured Event Attribute condition compares the normalized Source IP field, avoiding accidental text matches in unrelated portions of gateway denies.
Incorrect Answers
B:For historical or real-time event analysis at the SOC for host-188 using gateway denies: Grouping by minute changes output granularity but does not enforce equality on Source IP for the related-event investigation.
C:Keyword matching can find the same characters in messages that have a different parsed Source IP, weakening entity identity for host-188.
D:CMDB can enrich host identity, yet it is not the normalized gateway denies search that finds events sharing Source IP.
Question 757
A rule in Manufacturing generates an incident when quarantine occurs; analysts need it categorized with the proper severity and impact. In which rule phase are these outputs assigned?
- Step 1: General only
- The data parser configuration exclusively
- Step 3: Define Actions
- A saved historical search display preference
Explanation
Correct Answer
C:Considering correlation-rule investigation at Manufacturing: Rule actions define incident severity, category, impact and related post-detection settings. These describe what the matched quarantine condition produces.
Incorrect Answers
A:In correlation-rule investigation at Manufacturing: General details name and organize the rule. They do not replace incident action fields such as severity and category.
B:For A rule in Manufacturing generates an incident when quarantine occurs; analysts need it categorized with the proper severity: For correlation-rule investigation at Manufacturing: Parsing determines incoming event fields; incident severity is a rule-output property rather than a raw-log parsing directive.
D:Under correlation-rule investigation at Manufacturing: Historical display columns shape query output, not the severity assigned to an incident when a rule fires.
Question 758
After West Operations deploys lookup table KnownScanners, the owner realizes that the schema needs another business owner key and wants to revise the original structure in place. What limitation controls the next step?
- Changing the data rows automatically changes key definitions
- A created lookup table schema cannot be modified in place
- A notification policy can append a key field to the schema
- Every analytic search rewrites the table schema on its next run
Explanation
Correct Answer
B:FortiSIEM documents the schema as immutable after table creation. The KnownScanners design must therefore be planned before deployment; the owner needs an appropriate replacement or rebuild strategy.
Incorrect Answers
A:Editing or importing records changes lookup contents, not the key/column schema of the existing KnownScanners.
C:Considering CMDB and lookup-table configuration at West Operations: Notification automation controls post-incident actions and has no role in changing existing table schema definitions.
D:Queries read lookup data but do not redeclare how business owner is typed or keyed in Resources.
Question 759
Partner Services / host-79: a FortiSIEM Collector should run a script that changes access controls on a managed firewall. Which role assignments are correct? Choose TWO.
- Set the managed firewall as the Enforce On device
- Set the Collector as the Run On device
- Treat the affected user identity as the Run On host
- Set the incident title as the Enforce On device
- Replace device roles with dashboard Group By settings
Explanation
Correct Answers
A:Enforce On identifies the actual endpoint receiving the remediation operation, and its CMDB definition must be resolvable.
B:Run On identifies where the script is launched; the Collector must have a supported route and required access to the target management interface.
Incorrect Answers
C:A user identifier is not the FortiSIEM execution node running the remote device script.
D:Titles do not identify a manageable device for executing a remote state change.
E:Analytic grouping cannot establish where a remediation script launches or where its changes are applied.
Question 760
A historical firewall session logs search for asset host-72 is grouped by both Source IP and Destination IP. The matched data contains 6 distinct (Source IP, Destination IP) pairs even though there are only 3 unique Source IP values. How many result rows should grouping produce?
- 9 grouped rows
- 18 grouped rows
- 6 grouped rows
- 3 grouped rows
Explanation
Correct Answer
C:Considering aggregate-query calculation at the SOC for host-72 using firewall session logs: Each distinct combination of Source IP and Destination IP creates one group, so 6 key pairs yield 6 aggregate rows.
Incorrect Answers
A:In aggregate-query calculation at the SOC for host-72 using firewall session logs: Adding the two distinct counts double-counts category dimensions. A composite group key is based on observed pairs, not the sum of marginal counts.
B:For aggregate-query calculation at the SOC for host-72 using firewall session logs: A Cartesian product assumes every source-destination combination occurred. The query returns only 6 observed combinations.
D:Under aggregate-query calculation at the SOC for host-72 using firewall session logs: 3 counts unique values of Source IP alone; adding Destination IP can split each source across multiple results.