Question 220
A FortiSIEM correlation design at West Operations observes P1 (rejected request in cloud API audit events) and P2 (a related action on host-42). It must require P1 present and no subsequent P2 in the rule window. Which relationship operator best expresses that precise condition?
- OR
- FOLLOWED-BY
- AND-NOT
- NOT-FOLLOWED-BY
- AND
Explanation
Correct Answer
D:Under subpattern correlation at West Operations for host-42 using cloud API audit 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
A:In subpattern correlation at West Operations for host-42 using cloud API audit 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.
B:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-42 rather than unordered coincidence.
C:Considering subpattern correlation at West Operations for host-42 using cloud API audit events: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the West Operations event sequence.
E:In subpattern correlation at West Operations for host-42 using cloud API audit events: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended West Operations test.
Question 221
An East Retail rule should identify a single Host that reaches 15 DIFFERENT Service values, even if it sends many repeated events to one target. Which aggregate avoids that false positive?
- COUNT(DISTINCT Service) >= 15 grouped by Host
- COUNT(DISTINCT Host) >= 15 grouped by Service
- COUNT(Matched Events) >= 15 grouped by Host
- SUM(Destination Port) >= 15 without grouping
Explanation
Correct Answer
A:DISTINCT removes repeated target identities; the rule needs 15 independent Service values for one Host, not merely repeated attempts.
Incorrect Answers
B:For subpattern correlation at East Retail with the specified 15 value: This reverses direction and measures many sources contacting one destination, not the specified source’s unique targets.
C:15 raw events might all target one Service; repeated retries would meet this alternative without the required breadth.
D:Adding numerical port labels has no meaningful relationship to how many distinct Service values the actor contacted.
Question 222
A nested search for Cloud Services produces no rows although the inner policy violation 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?
- Convert a historical search into unsupported real-time Group By
- Remove all inner report display columns
- Make the outer filter attribute compatible with the selected inner result-column type
- Increase the severity of the unrelated incident rule
Explanation
Correct Answer
C:Considering nested search comparison at Cloud Services: 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
A:In nested search comparison at Cloud Services: Changing search mode cannot make a numeric outer filter compare correctly with a string inner result column.
B:For nested search comparison at Cloud Services: The nested query needs an inner output column for its membership values. Hiding them all makes the comparison less defined, not more reliable.
D:Under nested search comparison at Cloud Services: Changing incident priority does not repair nested-query type compatibility for Source IP values.
Question 223
The Manufacturing team tests a new policy violation rule. It triggers on a documented false positive generated by host-20 at normal business hours. Which correction preserves coverage while reducing repeat noise?
- Change the case-assignment queue without modifying event logic
- Always mark every later incident from the rule false positive
- Remove the event data source from FortiSIEM for every device
- Narrow the event filters, group logic, or applicable exception based on the false-positive evidence
Explanation
Correct Answer
D:Rule tuning should target the characteristic that distinguished this benign host-20 event from malicious policy violation behavior rather than discarding the entire detector.
Incorrect Answers
A:In rule deployment or exception at Manufacturing for host-20: Reassigning incidents affects workflow ownership but leaves the original high-noise rule conditions intact.
B:For rule deployment or exception at Manufacturing for host-20: Future matches may represent a true attack. Automatic blanket false-positive classification is not a precise correlation correction.
C:Considering rule deployment or exception at Manufacturing for host-20: Loss of visibility would suppress valid detections across Manufacturing, not only the verified benign event pattern.
Question 224
A query in City Branch correctly selects CMDB devices with business owner=production, but the output must also show owner and location fields for triage. What should be added to the CMDB search?
- A manual-clear action on every displayed device
- Relevant CMDB attributes as display fields
- A subpattern FOLLOWED-BY relationship between owner and location
- An event-count threshold to suppress all devices with no recent logs
Explanation
Correct Answer
B:Display selections expose owner and location for the already-matched inventory objects without changing the business owner=production predicate.
Incorrect Answers
A:Manually clearing incidents is an independent workflow and does not add the requested inventory columns to City Branch output.
C:Considering CMDB and lookup-table configuration at City Branch: Temporal rule operators relate event patterns, not static owner and location columns in a device inventory query.
D:Under CMDB and lookup-table configuration at City Branch: Filtering by event count changes the population and may remove quiet production assets that still belong in the requested CMDB list.
Question 225
The Partner Services external connector contains 198.51.100.37 in FortiGate, but a test from a different source address is still blocked by a broader rule. How should the analyst isolate the ZTNA-feed behavior?
- Ignore source IP because all addresses match an imported feed
- Inspect policy order and matched source/destination/service details for the test session
- Assume any denial proves the FortiSIEM threat feed worked
- Disable logging on the FortiGate before testing
Explanation
Correct Answer
B:FortiGate decision tracing should confirm which rule applies and whether the connector address matches the tested source. A broader deny may be independent of 198.51.100.37.
Incorrect Answers
A:In IP feed and FortiGate enforcement at Partner Services with the specified 198.51 value: The source IP is fundamental to an IP-based watchlist restriction; unrelated addresses must not be assumed equivalent.
C:Other policies may deny the session; evidence is needed to attribute the decision specifically to the imported 198.51.100.37 object.
D:Under IP feed and FortiGate enforcement at Partner Services with the specified 198.51 value: Suppressing logs removes the policy-hit evidence useful for distinguishing the feed decision from unrelated denies.
Question 226
A West Operations report groups failed login events by Source IP and uses COUNT(Matched Events). The analyst wants only groups exceeding 5 events to remain in the result, not to remove the underlying records before aggregation. What should be configured?
- An event filter that rejects all records until their count exceeds 5
- A Display Condition of COUNT(Matched Events) > 5
- A time range of exactly 5 seconds
- Group By COUNT(Matched Events) instead of Source IP
Explanation
Correct Answer
B:For A West Operations report groups failed login events by Source IP and uses COUNT(Matched Events). The analyst wants only: For aggregate-query calculation at West Operations with the specified 5 value: FortiSIEM display conditions filter aggregates after grouping, analogous to HAVING. Groups must first be counted, then those above 5 remain visible.
Incorrect Answers
A:An event filter evaluates record attributes before aggregation. Individual SSH audit logs events do not carry the completed group count to filter on.
C:The literal threshold is a count of records, not a query time window. Shortening time would alter which failed login events are included.
D:Under aggregate-query calculation at West Operations with the specified 5 value: COUNT is the measure to test, while Source IP defines the groups whose counts are compared; swapping these loses the per-source view.
Question 227
Partner Services / host-21: the analyst must report each Source IP and the number of distinct Destination Port values observed in network flow records during a stored interval. Which settings belong in the analytic query? Choose TWO.
- Aggregate COUNT(DISTINCT Destination Port) within each source group
- Replace the target cardinality with a count of total events only
- Use a real-time grouped query despite the historical time requirement
- Group By the normalized Source IP field
- Group only by the exact raw event timestamp
Explanation
Correct Answers
A:Distinct counting removes duplicate Destination Port values, producing unique targets rather than counting repeated event rows.
D:This creates one row per Source IP so that a single source can be compared against other source identities in the report.
Incorrect Answers
B:Total event counts include repeats and do not equal the number of distinct Destination Port destinations.
C:The requested grouped analysis belongs to the historical search workflow rather than a real-time mode that does not provide Group By.
E:High-resolution event timestamps separate records rather than summarizing targets for each Source IP source.
Question 228
Logistics needs a portable record of several stopped service incidents, including the selected investigation information, for an offline review meeting. Which supported List View action is appropriate?
- Change the initial Active status to False Positive before exporting
- Force a new lookup-table schema for every incident
- Disable all rules that generated these incidents
- Export the selected incidents in PDF or CSV
Explanation
Correct Answer
D:FortiSIEM List View provides incident export formats. The output preserves the chosen stopped service alert records without changing their detection or resolution state.
Incorrect Answers
A:In incident-management case at Logistics: Export does not require falsifying incident resolution, which should continue to reflect the evidence and analyst conclusion.
B:Lookup schemas are unrelated to producing a portable PDF/CSV of reviewed stopped service alerts.
C:Disabling changes future detection; it is not necessary for exporting the investigation record from Logistics.
Question 229
A rejected request incident on host-173 at Logistics represented a real outage. After repair, the analyst manually clears it and records evidence. Which combination reflects that history?
- Resolution True Positive; Status System Cleared
- Resolution None; Status Active
- Resolution True Positive; Status Manually Cleared
- Resolution False Positive; Status Manually Cleared
Explanation
Correct Answer
C:Considering incident-management case at Logistics for host-173: An actual rejected request issue merits a true-positive verdict, and human closure after verified repair results in the manually cleared lifecycle state.
Incorrect Answers
A:In incident-management case at Logistics for host-173: System Cleared indicates an automated clear condition, not the manual verification and closure described here.
B:For incident-management case at Logistics for host-173: The incident has already been judged and closed; leaving it active with no verdict misrepresents the completed Logistics response.
D:False Positive would describe a benign or incorrect detection, contradicting the confirmed real incident on host-173.
Question 230
For the response to an incident affecting host-76, in Manufacturing, a remediation script runs from a Collector against the affected FortiGate firewall. Which component is the Enforce On Device in the FortiSIEM terminology?
- The target managed device where the change is applied
- The Collector that launches the script
- The user who clicked the incident row
- The historical Analytics search result table
Explanation
Correct Answer
A:In remediation operation at Manufacturing for host-76: The FortiGate firewall is the Enforce On endpoint that receives the security action; its CMDB entry, credentials and supported protocol are material.
Incorrect Answers
B:For remediation operation at Manufacturing for host-76: The Collector may be Run On, but it is not the affected target when the remediation actually modifies the FortiGate firewall.
C:Considering remediation operation at Manufacturing for host-76: The human operator initiates an ad hoc action but does not become the managed endpoint on which the change is enforced.
D:Under remediation operation at Manufacturing for host-76: Event results provide evidence, not the device address and management channel where the script applies block a malicious source address.