Question 260
At City Branch, an anomalous process executions per account model was trained on a field imported as text, so numeric computations fail. Which correction most directly addresses the ML input?
- Use a numeric report field for the measure being modeled
- Replace the field with the incident title
- Mark all anomalous records as resolved before training
- Change alert recipients without training or invoking the machine-learning model
Explanation
Correct Answer
A:Numeric anomaly models rely on continuous or count-like features. Correctly typed process executions per account data allows the learner to evaluate ranges and deviations.
Incorrect Answers
B:Titles are labels for people and do not provide the numeric measurements needed to learn variation in process executions per account.
C:Incident resolution is not a substitute for correcting the underlying process executions per account feature type.
D:Under machine-learning analysis at City Branch: Notification delivery is downstream of scoring and cannot supply training features, fitted parameters or inference output.
Question 261
A FortiSIEM correlation design at North Finance observes P1 (quarantine in email security events) and P2 (a related action on host-77). It must require P1 present and no subsequent P2 in the rule window. Which relationship operator best expresses that precise condition?
- NOT-FOLLOWED-BY
- AND
- OR
- FOLLOWED-BY
- AND-NOT
Explanation
Correct Answer
A:In subpattern correlation at North Finance for host-77 using email security events: NOT-FOLLOWED-BY requires P1 and no P2 afterward in the evaluated rule period. It tests lack of follow-up, distinct from unordered AND-NOT.
Incorrect Answers
B:For subpattern correlation at North Finance for host-77 using email security events: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended North Finance test.
C:Considering subpattern correlation at North Finance for host-77 using email security events: OR permits either P1 or P2 to satisfy the rule. It is suited to alternative signals, not a requirement that both occur or that a later stage be missing.
D:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-77 rather than unordered coincidence.
E:In subpattern correlation at North Finance for host-77 using email security events: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the North Finance event sequence.
Question 262
A North Finance rule tracks elevated risk for analyst.g, and the SOC wants a dashboard filter showing only the tagged subset. What should be preserved in the query?
- Only a report title that contains the word risk
- The UEBA tag/entity attribute and the filter that selects the intended population
- An unconditional count of all tenants’ unrelated events
- A notification recipient email as the aggregation key
Explanation
Correct Answer
B:A useful dashboard needs the same tag or entity identity carried through the rule/event model. Filtering by that attribute isolates the relevant analyst.g activity.
Incorrect Answers
A:In entity-behavior risk evaluation at North Finance: Human-readable text does not itself filter data by the underlying user tag or risk attribute.
C:Broad counts mix unrelated observations and obscure the selected North Finance tagged behavior.
D:Under entity-behavior risk evaluation at North Finance: Notification recipients identify delivery targets, not the entity attribute used to filter UEBA telemetry.
Question 263
The outer search in West Operations examines VPN authentication records from the last 10 minutes, but the list of User values must come from the preceding day. Where is the inner report interval controlled?
- Reduce the lookup-table schema key count to one
- Change the Group By field to elapsed time
- Set Nested Time Range for the selected inner report separately from the outer range
- Assume the outer Time Range automatically defines every inner report interval
Explanation
Correct Answer
C:Nested searches distinguish the outer query window from the inner report time window. This lets the actor list cover the preceding day while the visible VPN authentication records evidence covers 10 minutes.
Incorrect Answers
A:In nested search comparison at West Operations using VPN authentication records with the specified 10 value: Lookup keys do not control how long an inner event report runs in this nested search.
B:For nested search comparison at West Operations using VPN authentication records with the specified 10 value: Grouping alters result summaries and does not independently schedule the time horizon for the inner User report.
D:Using the outer 10-minute window for both datasets would omit actors observed earlier in the day.
Question 264
Manufacturing has a rule with a recovery condition. A real suspicious launch alert on host-54 stops firing and FortiSIEM clears the incident automatically. What incident status is appropriate?
- Manually Cleared with False Positive resolution
- Active with None forever
- Deleted from all event storage with no history
- System Cleared with True Positive resolution
Explanation
Correct Answer
D:Under correlation-rule investigation at Manufacturing for host-54: When the configured rule clear condition resolves a real incident, FortiSIEM can mark the status System Cleared and retain a true-positive classification.
Incorrect Answers
A:No person cleared this case, and the detected suspicious launch failure was genuine, not a false positive.
B:The configured recovery condition has completed, so leaving the incident unresolved ignores the observed host-54 recovery.
C:Incident clearing is a lifecycle status change, not evidence that all associated endpoint process alerts records are deleted.
Question 265
A nested search for North Finance produces no rows although the inner connection event report returns Source IP values. The outer filter uses numeric identifiers, but the chosen inner display field has a string type. Which issue must be resolved first?
- Make the outer filter attribute compatible with the selected inner result-column type
- Convert a historical search into unsupported real-time Group By
- Increase the severity of the unrelated incident rule
- Remove all inner report display columns
Explanation
Correct Answer
A:In nested search comparison at North Finance: FortiSIEM nested queries require the data type of the outer filter to match the selected inner report column. The numeric-versus-string mismatch can prevent the membership test from working.
Incorrect Answers
B:For nested search comparison at North Finance: Changing search mode cannot make a numeric outer filter compare correctly with a string inner result column.
C:Considering nested search comparison at North Finance: Changing incident priority does not repair nested-query type compatibility for Source IP values.
D:Under nested search comparison at North Finance: The nested query needs an inner output column for its membership values. Hiding them all makes the comparison less defined, not more reliable.
Question 266
East Retail needs a rule that detects at least 9 blocked lookup events by the same Source IP in DNS resolution records. Which part specifies the occurrence threshold?
- A category label with no condition
- A report export format selection
- The display name of the rule group
- An aggregate condition such as COUNT(Matched Events) >= 9
Explanation
Correct Answer
D:The aggregate threshold evaluates the number of matching events after subpattern filters and grouping. It distinguishes a burst of 9 records from an isolated occurrence.
Incorrect Answers
A:Category classifies the eventual incident but cannot enforce the requirement for 9 matching DNS resolution records events.
B:For correlation-rule investigation at East Retail using DNS resolution records with the specified 9 value: CSV or PDF export is an output workflow and does not determine when the blocked lookup detection fires.
C:Considering correlation-rule investigation at East Retail using DNS resolution records with the specified 9 value: Rule grouping organizes resource definitions and has no effect on count threshold comparisons for Source IP.
Question 267
In Manufacturing, a rule must fire when a single User produces at least 15 permission failure events in database audit records. What Group By and aggregation correctly define the rule?
- Group By User; AVG(CPU Util) >= 15
- Group By User; COUNT(Matched Events) >= 15
- No grouping; COUNT(Matched Events) >= 15
- Group By Database Host; COUNT(DISTINCT User) >= 15
Explanation
Correct Answer
B:The grouping isolates each User and the raw-event count checks whether its permission failure volume reaches 15 within the rule window.
Incorrect Answers
A:Average CPU describes resource load, not the frequency of permission failure database audit records records from the source.
C:The global count can be met by aggregating unrelated User values, creating false correlations across distinct actors.
D:This asks for many source entities per destination. It is not a burst count for each individual User.
Question 268
Manufacturing tests a rule on deny records and finds its COUNT threshold reached by separate sources combined together. The goal is one threshold per Source IP. Where in the rule is the fix made?
- Export the last incident report as PDF
- Set the incident notification recipient to the security team
- Rename the subpattern with a unique suffix only
- Add the Source IP event attribute to that subpattern’s Group By
Explanation
Correct Answer
D:The per-source group key splits the matched gateway denies stream before COUNT evaluation, preventing unrelated sources from jointly meeting the threshold.
Incorrect Answers
A:Reporting preserves evidence but leaves the correlation rule’s global aggregate unchanged for future deny matches.
B:For subpattern correlation at Manufacturing: Routing the alert is useful operationally but cannot change how matched Source IP values are counted.
C:Considering subpattern correlation at Manufacturing: A name adjustment does not introduce the missing per-Source IP aggregation boundary that caused the false trigger.
Question 269
In East Retail, a stored search matches 5 blocked lookup records from DNS resolution records, including only 3 unique Queried Domain values for host-13. To measure unique targets rather than raw volume, which aggregate is required?
- AVG(Queried Domain)
- SUM(Queried Domain)
- COUNT(Matched Events)
- COUNT(DISTINCT Queried Domain)
Explanation
Correct Answer
D:This removes repeated Queried Domain values before counting. For host-13, the expected unique-target measure is 3 rather than the 5 event rows.
Incorrect Answers
A:In aggregate-query calculation at East Retail for host-13 using DNS resolution records: An average of an identifier would not quantify unique Queried Domain values, even if the attribute happened to be encoded numerically.
B:For aggregate-query calculation at East Retail for host-13 using DNS resolution records: SUM is intended for numeric measures and is not a meaningful distinct-count function for the Queried Domain identity field in these DNS resolution records records.
C:Considering aggregate-query calculation at East Retail for host-13 using DNS resolution records: This produces 5 because each qualifying event contributes one row. It cannot distinguish repeat connections to a target from a new Queried Domain.
Question 270
An analyst wants separate incidents when the same policy violation burst arises from different Source IP values in Partner Services. Which subpattern component separates the candidate event populations?
- Group By the Source IP event attribute
- Set a higher incident title priority
- Configure an outbound email recipient for each log entry
- Use no Group By and count all events globally
Explanation
Correct Answer
A:In correlation-rule investigation at Partner Services: Grouping partitions matching records by their Source IP value before applying the rule threshold. This preserves per-actor detection rather than merging every firewall session logs event.
Incorrect Answers
B:For correlation-rule investigation at Partner Services: Title wording cannot partition events from different Source IP entities during subpattern evaluation.
C:Considering correlation-rule investigation at Partner Services: Alert recipients do not control the correlation grouping key or the incident identity.
D:Under correlation-rule investigation at Partner Services: A global count allows small bursts from unrelated sources to accumulate into a single trigger, losing the per-Source IP boundary.