Question 290
North Finance wants notifications for LOW connection incidents, but not for incidents of other severities from the same rule. Which automation-policy criterion should be set?
- An unqualified selection of all incident categories
- Severity selection matching LOW
- A larger Analytics result-row limit
- Changing the reporting device hostname
Explanation
Correct Answer
B:For Automation Policy workflow at North Finance: The policy can select one or more incident severities. Restricting it to LOW controls delivery without altering the rule’s triggering conditions.
Incorrect Answers
A:In Automation Policy workflow at North Finance: Categories alone do not enforce the required LOW boundary; other-severity alerts may still notify.
C:Considering Automation Policy workflow at North Finance: Query row limits affect display, not whether the Automation Policy sends an alert based on severity.
D:Under Automation Policy workflow at North Finance: Device identity changes are unrelated to choosing which severity values qualify for notification.
Question 291
For a suspicious launch incident in Partner Services, the analyst wants to record findings that a responder can read without falsely treating the alert as resolved. Which incident operation is suitable?
- Add an incident comment or remediation advice while preserving current status
- Delete the device from CMDB so the incident loses context
- Raise the global rule count threshold as a substitute for notes
- Set False Positive and clear every incident sharing the category
Explanation
Correct Answer
A:FortiSIEM supports comments on incident records and remediation notes in rules. Documentation helps responders act on host-75 without prematurely clearing the live alert.
Incorrect Answers
B:For incident-management case at Partner Services: Removing an inventory object discards relevant asset information and does not constitute safe analyst documentation.
C:Considering incident-management case at Partner Services: Changing detection conditions alters future alerts, not the investigation narrative that a responder needs now.
D:Under incident-management case at Partner Services: This asserts a benign verdict and changes lifecycle state for alerts that may still represent genuine suspicious launch activity.
Question 292
In a FortiSIEM anomaly task for hourly failed sign-ins, East Retail wants the model to tolerate routine variation rather than treat every unusual point as a certain attack. What should the analyst examine?
- Treat a normalized event query as a completed ML training model
- The anomaly threshold/contamination settings and observed false-positive rate
- Changing every benign record to a firewall deny
- Whether every source host is deleted from CMDB
Explanation
Correct Answer
B:Anomaly scoring uses statistical decisions about unusual behavior. Threshold and contamination tuning affect sensitivity; analysts should compare flagged hourly failed sign-ins cases with actual operations.
Incorrect Answers
A:In machine-learning analysis at East Retail: An event search selects records, while a model must be trained on the intended dataset and then applied to compatible new features.
C:Blanket blocking is not model threshold calibration and could disrupt legitimate business flows at East Retail.
D:Deleting assets suppresses useful context and does not provide a principled threshold for recognizing abnormal hourly failed sign-ins values.
Question 293
A FortiSIEM correlation design at City Branch observes P1 (failed authentication in VPN authentication records) and P2 (a related action on host-150). It must require P1 present and no subsequent P2 in the rule window. Which relationship operator best expresses that precise condition?
- AND-NOT
- OR
- AND
- NOT-FOLLOWED-BY
- FOLLOWED-BY
Explanation
Correct Answer
D:Under subpattern correlation at City Branch for host-150 using VPN authentication records: 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
A:In subpattern correlation at City Branch for host-150 using VPN authentication records: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the City Branch event sequence.
B:For subpattern correlation at City Branch for host-150 using VPN authentication records: 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.
C:Considering subpattern correlation at City Branch for host-150 using VPN authentication records: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended City Branch test.
E:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-150 rather than unordered coincidence.
Question 294
The West Operations UEBA dashboard mixes contractor.r events from last month with yesterday’s incidents. An analyst needs a fair short-term comparison. What should be aligned?
- Only the order of email recipients
- The query time windows, entity filters and aggregation definitions
- Replace the entity score with incident-list display ordering
- Only the export filename extension
Explanation
Correct Answer
B:Comparable UEBA panels use consistent source populations and metrics. Aligning those elements avoids mistaking different observation windows for changes in contractor.r behavior.
Incorrect Answers
A:Notification routing does not control time-series grouping or the comparability of contractor.r statistics.
C:Considering entity-behavior risk evaluation at West Operations: Sorting incidents can prioritize a screen view but cannot rebuild the normalized entity mapping or actual risk contributors.
D:Under entity-behavior risk evaluation at West Operations: File format labels do not enforce a consistent sampling window for UEBA analysis.
Question 295
Research sees roaming.p with multiple high-severity suspicious sign-ins and access to a critical host. Why is entity risk more informative than raw alert count alone?
- Entity risk is only a cosmetic dashboard color
- Risk can incorporate event severity, rarity and affected asset criticality
- A high alert count automatically proves every event is malicious
- Risk must equal the exact number of normalized source IP values
Explanation
Correct Answer
B:For entity-behavior risk evaluation at Research: An entity’s risk assessment combines context beyond volume. A few unusual, severe events involving a critical asset may merit more attention than many routine benign records.
Incorrect Answers
A:In entity-behavior risk evaluation at Research: Risk information supports investigation and prioritization, not merely display choices in a widget.
C:Considering entity-behavior risk evaluation at Research: False positives, benign bursts and asset context require triage; volume alone does not provide that certainty.
D:Unique IP cardinality can be an input to a rule, but it is not the complete definition of UEBA risk for roaming.p.
Question 296
East Retail creates lookup table KnownScanners to enrich failed authentication events. The schema currently needs 4 key field(s), and all fields are valid scalar lookup types. Which design constraint must be kept in mind?
- Select a real-time Group By to declare lookup keys
- Create a separate incident for every schema column before saving
- Treat all lookup columns as keys with no limit
- Use no more than five key fields in the lookup table schema
Explanation
Correct Answer
D:Under CMDB and lookup-table configuration at East Retail with the specified 4 value: FortiSIEM 7.2 permits up to five lookup-table key values. The proposed 4 keys fit, but a sixth key would exceed that limit.
Incorrect Answers
A:Group By describes aggregation output, whereas lookup keys are defined when the KnownScanners schema is created in Resources.
B:For CMDB and lookup-table configuration at East Retail with the specified 4 value: Lookup schema creation is independent of incident generation; columns are metadata used for event lookups, not incident definitions.
C:FortiSIEM explicitly limits key count; indiscriminately converting the columns in KnownScanners to keys can violate the schema design.
Question 297
A FortiSIEM ML model for bytes transferred per remote session at Manufacturing has finished training. The analyst next wants to score newly observed values on host-44. Which operation is needed?
- An unrelated case export
- Inference using the trained model and incoming feature values
- Training the same model without presenting new data for scoring
- Deleting all stored training examples first
Explanation
Correct Answer
B:Inference applies the existing learned model to new bytes transferred per remote session observations for host-44. It is distinct from retraining and should use compatible feature definitions.
Incorrect Answers
A:Exporting cases facilitates handoff, not applying the learned bytes transferred per remote session pattern to fresh input.
C:Retraining refreshes or rebuilds model parameters but does not by itself describe scoring the newly observed host-44 values.
D:Under machine-learning analysis at Manufacturing for host-44: Removing relevant history can undermine the ability to retrain or diagnose model quality and does not perform inference.
Question 298
North Finance has a CMDB property named criticality for host-149. The investigator must list inventory devices having that property, regardless of whether they emitted database audit records recently. Which FortiSIEM search source is appropriate?
- Notification automation policy with the inventory term as severity
- Pure CMDB search using the device property condition
- Real-time search for the inventory object itself
- Event-only historical search filtering on a recent log type
Explanation
Correct Answer
B:A CMDB query reads inventory attributes such as criticality directly. It can list host-149 even during periods when no database audit records events arrive.
Incorrect Answers
A:Automation policies act on incidents; they are not a device property search engine for North Finance.
C:Considering CMDB and lookup-table configuration at North Finance for host-149 using database audit records: Real-time Analytics evaluates new events, not static device records; it cannot guarantee all devices with the criticality property appear.
D:Event search returns recorded telemetry and might omit host-149 if it has not emitted database audit records; it does not inherently enumerate all inventory objects.
Question 299
A Corporate HQ analyst is already searching connection events in network flow records, but only wants records whose reporting devices have CMDB criticality=critical. How can event selection incorporate inventory context?
- Group the events by ingestion timestamp alone
- Reference CMDB device properties through the supported event/CMDB query mechanism
- Compare the raw event keyword against the word criticality only
- Set incident severity to critical before running the query
Explanation
Correct Answer
B:For CMDB and lookup-table configuration at Corporate HQ using network flow records: FortiSIEM combined Event/CMDB searches and DeviceToCMDBAttr-style access can apply inventory properties such as criticality to event evidence.
Incorrect Answers
A:In CMDB and lookup-table configuration at Corporate HQ using network flow records: Changing time granularity does not test whether the reporting device has the required CMDB criticality value.
C:Unless that property is present in every raw network flow records message, keyword text cannot reliably enforce the CMDB-derived criticality constraint.
D:Under CMDB and lookup-table configuration at Corporate HQ using network flow records: Incident severity is an alert attribute; it does not add the criticality predicate to existing event-search matches.
Question 300
West Operations wants the correlated incident for blocked request to include the original Source IP, URI Path, and other event context for investigation. Which rule configuration maps the evidence into the generated alert?
- Only the incident email template without event mapping
- Only the rules folder name
- Incident Attributes and Triggered Attributes from rule subpatterns
- Only the global source data retention setting
Explanation
Correct Answer
C:The incident definition maps selected filter, group and aggregate attributes into incident fields. Including Source IP and URI Path preserves actionable context for analysts.
Incorrect Answers
A:An email template cannot recover omitted triggered values unless the incident definition first includes the relevant Source IP and URI Path context.
B:For correlation-rule investigation at West Operations: The folder identifies where the rule is stored, not which event attributes the resulting incident retains.
D:Under correlation-rule investigation at West Operations: Retention controls availability of evidence but does not decide the fields copied into each generated incident.