Question 570
A Research rule should identify a single User that reaches 18 DIFFERENT Application values, even if it sends many repeated events to one target. Which aggregate avoids that false positive?
- COUNT(Matched Events) >= 18 grouped by User
- COUNT(DISTINCT User) >= 18 grouped by Application
- SUM(Destination Port) >= 18 without grouping
- COUNT(DISTINCT Application) >= 18 grouped by User
Explanation
Correct Answer
D:DISTINCT removes repeated target identities; the rule needs 18 independent Application values for one User, not merely repeated attempts.
Incorrect Answers
A:18 raw events might all target one Application; repeated retries would meet this alternative without the required breadth.
B:For subpattern correlation at Research with the specified 18 value: This reverses direction and measures many sources contacting one destination, not the specified source’s unique targets.
C:Adding numerical port labels has no meaningful relationship to how many distinct Application values the actor contacted.
Question 571
East Retail wants to correlate events about host-29 with its business owner and ownership stored in CMDB, without requiring the property to be present in every incoming proxy access records record. Which conceptual join is needed?
- Convert the incident category into a free-form CMDB schema
- Match an event device identifier to the corresponding CMDB record
- Count all events from all organizations as one global measure
- Use only the latest raw-message text and disregard device identity
Explanation
Correct Answer
B:For CMDB and lookup-table configuration at East Retail for host-29 using proxy access records: Combining event identifiers with CMDB inventory supplies the business owner and ownership information even when the original log only describes an observed action.
Incorrect Answers
A:In CMDB and lookup-table configuration at East Retail for host-29 using proxy access records: Incident classification is not a join key and does not turn an alert into a device record with reliable ownership context.
C:Global event totals erase the specific host relationship required to retrieve the correct business owner from East Retail inventory.
D:Text alone does not guarantee that a record identifies the same host-29 as the inventory entry; the relationship requires a stable matching attribute.
Question 572
East Retail / host-196: an outer analytics query must find users who appear in an inner suspicious-authentication report. Which configuration choices are essential? Choose TWO.
- Use the inner report as a compatible nested-query input
- Delete the inner report after choosing it
- Treat the outer query’s incident severity as an automatic identity mapping
- Align the inner output key type with the outer user comparison field
- Use a text-only report title as the user join key
Explanation
Correct Answers
A:The nested result supplies the candidate identity set that the outer service health records search needs to match.
D:Nested membership checks require compatible fields. A type mismatch can silently exclude the intended stopped service accounts.
Incorrect Answers
B:Removing the source query would eliminate the nested membership set needed by the outer condition.
C:Severity measures priority and cannot substitute for the identity field required for the nested comparison.
E:A report title is not a normalized account identifier and cannot reliably match the user IDs in the outer query.
Question 573
An analyst at City Branch is watching newly arriving VPN authentication records for failed authentication on host-26; the requirement is to see records as they are ingested, with no grouping. Which FortiSIEM search approach fits?
- Use a real-time search with a Group By aggregation
- Run only a historical search against an earlier time interval
- Run a CMDB device search for host-26 as the sole data source
- Use a real-time search with a normalized event-attribute filter
Explanation
Correct Answer
D:Real-time search evaluates incoming events in the streaming path. A condition on the normalized failed authentication indicator can expose matching records on host-26 without retrieving stored history.
Incorrect Answers
A:In historical or real-time event analysis at City Branch for host-26 using VPN authentication records: FortiSIEM real-time search does not support Group By. Here the desired output is raw incoming events, not aggregate group counts.
B:Historical searches read events already persisted in the database. This misses the requirement to observe newly arriving VPN authentication records as ingestion occurs.
C:CMDB is inventory and configuration data, not the live stream of VPN authentication records needed to inspect failed authentication evidence.
Question 574
An investigator at Logistics wants to inspect the failed authentication incidents affecting host-63, change one alert severity, and add a triage comment. Which interface is intended for those analyst actions?
- The FortiSIEM software update installer
- Only the Resources lookup-table schema screen
- A raw log parser rule with no incident reference
- Incidents List View and its Actions menu
Explanation
Correct Answer
D:List View supports filtering incident records, changing severity, editing information, and incident lifecycle actions; it keeps host-63 triage attached to the alert.
Incorrect Answers
A:Upgrading the platform does not provide the incident-specific severity and comment operations for an active host-63 case.
B:For incident-management case at Logistics for host-63: Lookup tables hold enrichment data, not the incident workflow operations required to review and comment on the failed authentication alert.
C:Considering incident-management case at Logistics for host-63: Parsers normalize event data but cannot substitute for the analyst’s incident-level review and annotation controls.
Question 575
A Corporate HQ analyst needs an event-to-event nested search that finds failed sign-in records on host-180 only when the same Host appeared in a previously saved anomaly report. What establishes the relationship?
- Compare outer event timestamp against inner Host as text
- Use the inner report name as a literal event keyword
- Group by incident severity with no identity comparison
- Compare the outer event Host field against the corresponding inner report Host column
Explanation
Correct Answer
D:Matching the same typed entity attribute across the two event datasets performs the intended membership lookup for host-180.
Incorrect Answers
A:In nested search comparison at Corporate HQ for host-180: Time and entity identity are different attribute types; the comparison would not indicate whether the same Host was observed.
B:For nested search comparison at Corporate HQ for host-180: A report title is not the data returned by that report. Keyword matching cannot establish membership among suspicious Host entities.
C:Grouping by severity changes how matches are summarized and fails to correlate host-180 events with the prior actor set.
Question 576
Cloud Services wants notifications for LOW failed sign-in incidents, but not for incidents of other severities from the same rule. Which automation-policy criterion should be set?
- A larger Analytics result-row limit
- Changing the reporting device hostname
- An unqualified selection of all incident categories
- Severity selection matching LOW
Explanation
Correct Answer
D:Under Automation Policy workflow at Cloud Services: 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 Cloud Services: Query row limits affect display, not whether the Automation Policy sends an alert based on severity.
B:For Automation Policy workflow at Cloud Services: Device identity changes are unrelated to choosing which severity values qualify for notification.
C:Considering Automation Policy workflow at Cloud Services: Categories alone do not enforce the required LOW boundary; other-severity alerts may still notify.
Question 577
An analyst drills from a sign-in event on host-92 into Analytics and wants the query to follow the event’s existing normalized Application value. Which starting technique minimizes transcription errors?
- Change the incident severity before running any search
- Switch from Analytics to an empty CMDB inventory view
- Build or refine a search directly from the selected event attributes
- Use a random keyword unrelated to the opened event
Explanation
Correct Answer
C:Starting from an event helps carry the concrete parsed Application context into the new search, avoiding manual retyping of the value for host-92.
Incorrect Answers
A:In historical or real-time event analysis at the SOC for host-92: Severity influences priority but not the initial search predicate or its connection to the selected event attributes.
B:For historical or real-time event analysis at the SOC for host-92: Inventory can supplement the investigation but does not inherit the event’s normalized field-value combination into a search.
D:An unrelated raw-text keyword cannot reliably reproduce the selected Application context and is likely to change which records match.
Question 578
A FortiSIEM correlation design at North Finance observes P1 (quarantine in email security events) and P2 (a related action on host-182). It must require P1 and then P2 in that order. Which relationship operator best expresses that precise condition?
- FOLLOWED-BY
- AND
- AND-NOT
- NOT-FOLLOWED-BY
- OR
Explanation
Correct Answer
A:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-182 rather than unordered coincidence.
Incorrect Answers
B:For subpattern correlation at North Finance for host-182 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-182 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.
D:Under subpattern correlation at North Finance for host-182 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.
E:In subpattern correlation at North Finance for host-182 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.
Question 579
West Operations must estimate the expected number of nightly database write rate occurrences on host-13 tomorrow, expressed as a numeric value instead of a category. Which FortiSIEM ML objective is most aligned?
- A ZTNA IP watchlist connector
- A regression or forecasting task for the numeric target
- A rule exception that always suppresses this host
- A binary category classifier without a numeric target
Explanation
Correct Answer
B:Predicting the numerical level of nightly database write rate is a continuous-value objective. If successive time intervals and trends matter, forecasting is especially relevant.
Incorrect Answers
A:A watchlist connector distributes enforcement indicators rather than predicting numeric behavior of host-13.
C:An exception removes matches from a rule and offers no estimate of tomorrow’s nightly database write rate count.
D:A classifier assigns category probabilities or labels and would not directly yield the requested numeric volume estimate for host-13.
Question 580
For the response to an incident affecting host-32, cloud Services wants the same vetted action, isolate an infected endpoint, to execute when its verified failed sign-in incident rule fires, with no per-incident analyst click. Which configuration automates response?
- An enabled Automation Policy with Run Remediation/Script
- A dashboard Group By on incident time
- A historical event export scheduled daily
- An incident comment template without an action
Explanation
Correct Answer
A:In correlation-rule investigation at the SOC for host-32: The policy can invoke an approved remediation script as the rule generates a matching incident. Preconditions and device scope must be validated before unattended action.
Incorrect Answers
B:For correlation-rule investigation at the SOC for host-32: Dashboard aggregation shows incident patterns but is not the action engine for the Cloud Services response.
C:Considering correlation-rule investigation at the SOC for host-32: Export creates copies of evidence, not a near-real-time response on incident generation.
D:Under correlation-rule investigation at the SOC for host-32: Comments convey instructions but do not execute isolate an infected endpoint automatically on the selected systems.