Question 280
An incident rule at West Operations was built with a reasonable failed login filter but produces no alerts after the test passed. The rule exists and evidence is arriving. Which lifecycle setting should the analyst verify?
- That the search result limit is at least one million
- That the incident PDF export completed yesterday
- That the tested rule is actually enabled for production processing
- That every event has an unusually long message string
Explanation
Correct Answer
C:Passing a test does not activate a rule. An inactive saved definition cannot generate live incidents from the incoming SSH audit logs stream.
Incorrect Answers
A:For An incident rule at West Operations was built with a reasonable failed login filter but produces no alerts after the test: In rule deployment or exception at West Operations: Result-table size affects Analytics output, not whether an otherwise valid rule has been activated.
B:For An incident rule at West Operations was built with a reasonable failed login filter but produces no alerts after the test: For rule deployment or exception at West Operations: Historical export jobs do not determine the active/inactive state of the live rule evaluator.
D:Message length is not a general prerequisite for triggering a valid failed login correlation rule.
Question 281
The Manufacturing external connector contains 198.51.100.13 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?
- Disable logging on the FortiGate before testing
- 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
Explanation
Correct Answer
C: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.13.
Incorrect Answers
A:In IP feed and FortiGate enforcement at Manufacturing with the specified 198.51 value: Suppressing logs removes the policy-hit evidence useful for distinguishing the feed decision from unrelated denies.
B:For IP feed and FortiGate enforcement at Manufacturing with the specified 198.51 value: The source IP is fundamental to an IP-based watchlist restriction; unrelated addresses must not be assumed equivalent.
D:Other policies may deny the session; evidence is needed to attribute the decision specifically to the imported 198.51.100.13 object.
Question 282
An analyst at East Retail wants incidents from a failed authentication rule to show the corresponding User from the matching events so they can be grouped later in incident analytics. Which configuration maps that value?
- Modify the case label without reviewing rule state or exceptions
- Set the rule severity to high regardless of source identity
- Add a local text note without mapping the event field
- Select User from the subpattern as an incident attribute
Explanation
Correct Answer
D:For An analyst at East Retail wants incidents from a failed authentication rule to show the corresponding User from the matching: Under rule deployment or exception at East Retail: Incident definitions can inherit relevant Group By and filter fields from the triggering subpatterns. This makes User available for later incident investigation and grouping.
Incorrect Answers
A:For An analyst at East Retail wants incidents from a failed authentication rule to show the corresponding User from the matching: In rule deployment or exception at East Retail: Case metadata does not activate an inactive rule or correctly scope a rule exception for future event matches.
B:For rule deployment or exception at East Retail: Severity represents urgency, not the User entity whose value needs to be stored for each incident.
C:Considering rule deployment or exception at East Retail: Notes may explain triage intent but do not populate the structured incident User column from each matched event.
Question 283
In West Operations, a rule must fire when a single Host produces at least 20 stopped service events in service health records. What Group By and aggregation correctly define the rule?
- Group By Host; COUNT(Matched Events) >= 20
- Group By Service; COUNT(DISTINCT Host) >= 20
- No grouping; COUNT(Matched Events) >= 20
- Group By Host; AVG(CPU Util) >= 20
Explanation
Correct Answer
A:The grouping isolates each Host and the raw-event count checks whether its stopped service volume reaches 20 within the rule window.
Incorrect Answers
B:For subpattern correlation at West Operations using service health records with the specified 20 value: This asks for many source entities per destination. It is not a burst count for each individual Host.
C:Considering subpattern correlation at West Operations using service health records with the specified 20 value: The global count can be met by aggregating unrelated Host values, creating false correlations across distinct actors.
D:Average CPU describes resource load, not the frequency of stopped service service health records records from the source.
Question 284
The MSSP has a lookup table named TrustedNetworks owned by Manufacturing; another tenant runs a similarly named enrichment. Which property should be verified before sharing result assumptions across the tenants?
- Join on a display-only attribute that is not the defined lookup key
- The organization associated with the lookup-table definition and data
- The last incident severity used by another customer
- Compare a string identity value with a numeric lookup key without conversion or type alignment
Explanation
Correct Answer
B:FortiSIEM lookup-table creation selects an Organization. Even if names appear similar, Manufacturing data and another tenant’s scoped lookup must not be assumed interchangeable.
Incorrect Answers
A:In CMDB and lookup-table configuration at Manufacturing: Lookup enrichment depends on the table’s actual key schema; a plausible label in the UI may not identify the record to return.
C:Alert priority is not an ownership or lookup-data scoping control for the TrustedNetworks repository.
D:Under CMDB and lookup-table configuration at Manufacturing: The comparison must respect the configured lookup data types. A type mismatch prevents a reliable exact key match.
Question 285
A FortiSIEM correlation design at Partner Services observes P1 (suspicious launch in endpoint process alerts) and P2 (a related action on host-204). It must require P1 present and no subsequent P2 in the rule window. Which relationship operator best expresses that precise condition?
- AND-NOT
- NOT-FOLLOWED-BY
- OR
- AND
- FOLLOWED-BY
Explanation
Correct Answer
B:For subpattern correlation at Partner Services for host-204 using endpoint process alerts: 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 Partner Services for host-204 using endpoint process alerts: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the Partner Services event sequence.
C:Considering subpattern correlation at Partner Services for host-204 using endpoint process alerts: 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:Under subpattern correlation at Partner Services for host-204 using endpoint process alerts: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended Partner Services test.
E:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-204 rather than unordered coincidence.
Question 286
A FortiSIEM correlation design at Manufacturing observes P1 (failed sign-in in Windows security logs) and P2 (a related action on host-206). It must require at least one of P1 or P2. Which relationship operator best expresses that precise condition?
- FOLLOWED-BY
- NOT-FOLLOWED-BY
- AND-NOT
- OR
- AND
Explanation
Correct Answer
D:Under subpattern correlation at Manufacturing for host-206 using Windows security logs: 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.
Incorrect Answers
A:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-206 rather than unordered coincidence.
B:For subpattern correlation at Manufacturing for host-206 using Windows security logs: 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.
C:Considering subpattern correlation at Manufacturing for host-206 using Windows security logs: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the Manufacturing event sequence.
E:In subpattern correlation at Manufacturing for host-206 using Windows security logs: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended Manufacturing test.
Question 287
City Branch wants to correlate events about host-181 with its asset class and ownership stored in CMDB, without requiring the property to be present in every incoming identity provider events record. Which conceptual join is needed?
- Use only the latest raw-message text and disregard device identity
- Match an event device identifier to the corresponding CMDB record
- Convert the incident category into a free-form CMDB schema
- Count all events from all organizations as one global measure
Explanation
Correct Answer
B:Combining event identifiers with CMDB inventory supplies the asset class and ownership information even when the original log only describes an observed action.
Incorrect Answers
A:Text alone does not guarantee that a record identifies the same host-181 as the inventory entry; the relationship requires a stable matching attribute.
C:Considering CMDB and lookup-table configuration at City Branch for host-181 using identity provider events: Incident classification is not a join key and does not turn an alert into a device record with reliable ownership context.
D:Global event totals erase the specific host relationship required to retrieve the correct asset class from City Branch inventory.
Question 288
A Research investigator wants historical failed login events from SSH audit logs where Source IP appears in an earlier event report of suspicious actors. Which nested query data-source pairing is natural?
- Use a rule clear condition as the inner dataset
- Outer event search using an inner event report as a membership source
- Outer lookup schema editor with an inner alert notification
- Outer pure CMDB search regardless of the event evidence
Explanation
Correct Answer
B:Both the displayed evidence and the prior actor list derive from events. Event-to-event nesting filters historical SSH audit logs rows using values from the inner report.
Incorrect Answers
A:In nested search comparison at Research using SSH audit logs: Clear conditions manage incident status, not the result set supplied to the outer event search for Source IP.
C:Considering nested search comparison at Research using SSH audit logs: Neither schema editing nor notification delivery evaluates event membership from an existing suspicious-actor report.
D:An inventory outer query would return CMDB objects rather than the historical failed login event rows the investigator needs.
Question 289
In Research, an investigator wants to repeat the same failed login filter over SSH audit logs next week without reconstructing the search. Which operation captures the query as a reusable analytic artifact?
- Modify the data collector polling interval
- Export one row without saving any definition
- Save the working search definition as a report
- Clear the open incident generated by a different rule
Explanation
Correct Answer
C:Saving the query definition preserves its selected filter and display logic for reuse on future SSH audit logs investigations; time can be adjusted when run.
Incorrect Answers
A:In historical or real-time event analysis at Research using SSH audit logs: Collection rate controls incoming monitoring data rather than the stored search definition the investigator wants to reuse.
B:For historical or real-time event analysis at Research using SSH audit logs: A row export is evidence from one run; it does not retain reusable filters and aggregation choices for the next week.
D:Clearing changes incident lifecycle state; it does not persist the analysis query for future failed login searches.
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.