Question 770
FortiSIEM returns individual web application alerts rows for East Retail; the analyst now wants a per-Source IP summary with aggregate values while retaining the same blocked request filter. Which portion of search configuration changes?
- Group By and Display Fields with the required aggregate expressions
- Replace the event search with a pure CMDB search
- Change the notification target of the associated rule
- Only switch raw logs to a different parser
Explanation
Correct Answer
A:Grouping creates one result per Source IP value and aggregated displays compute measures over matching blocked request events, without needing a new ingestion configuration.
Incorrect Answers
B:CMDB focuses on inventory attributes and cannot compute the requested event aggregates over the selected blocked request rows.
C:Considering historical or real-time event analysis at East Retail using web application alerts: Notification routing acts after incident detection and does not transform a search result into grouped aggregate output.
D:Parser configuration affects field normalization; it is not the way to summarize an already-correct web application alerts result set by Source IP.
Question 771
A West Operations report groups sign-in events by User and uses COUNT(Matched Events). The analyst wants only groups exceeding 7 events to remain in the result, not to remove the underlying records before aggregation. What should be configured?
- Group By COUNT(Matched Events) instead of User
- An event filter that rejects all records until their count exceeds 7
- A Display Condition of COUNT(Matched Events) > 7
- A time range of exactly 7 seconds
Explanation
Correct Answer
C:For A West Operations report groups sign-in events by User and uses COUNT(Matched Events). The analyst wants only groups: Considering aggregate-query calculation at West Operations with the specified 7 value: FortiSIEM display conditions filter aggregates after grouping, analogous to HAVING. Groups must first be counted, then those above 7 remain visible.
Incorrect Answers
A:For A West Operations report groups sign-in events by User and uses COUNT(Matched Events). The analyst wants only groups: In aggregate-query calculation at West Operations with the specified 7 value: COUNT is the measure to test, while User defines the groups whose counts are compared; swapping these loses the per-source view.
B:For aggregate-query calculation at West Operations with the specified 7 value: An event filter evaluates record attributes before aggregation. Individual identity provider events events do not carry the completed group count to filter on.
D:Under aggregate-query calculation at West Operations with the specified 7 value: The literal threshold is a count of records, not a query time window. Shortening time would alter which sign-in events are included.
Question 772
West Operations / host-56: a historical group-by report must reveal each User event volume, distinct Application target breadth and organization-limited scope. Which THREE elements should be present? Choose THREE.
- Group only by high-resolution raw timestamps
- Replace all source identities with a fixed constant
- Group By User
- COUNT(DISTINCT Application) together with an West Operations scope filter
- Use an ungrouped real-time stream as the final grouped report
- COUNT of matching events
Explanation
Correct Answers
C:Grouping by the normalized source forms one row per entity rather than a row per raw identity provider events event.
D:Unique target count captures breadth while the organization predicate keeps cross-tenant source records out of the aggregation.
F:Total count captures the request volume, including duplicate attempts and repeated requests by the same source.
Incorrect Answers
A:Grouping each record by a unique time stamp fragments the intended per-source event and target counts.
B:A constant key merges separate actors and defeats the requested source-level comparisons.
E:The desired stored-event summary and multiple aggregates require the historical grouped query path.
Question 773
At Partner Services, the analyst wants to correlate privileged.e behavior across VPN and identity-provider logs. Which prerequisite makes this a meaningful UEBA investigation?
- Group solely by log source filename without user fields
- Block all identity-provider collection while preserving only CMDB
- Normalize identity attributes and map events to a consistent user entity
- Replace every user name with an unrelated constant
Explanation
Correct Answer
C:Considering entity-behavior risk evaluation at Partner Services: UEBA analysis relies on linking actions by the same identity. Consistent user fields across the VPN and identity providers support a consolidated behavior trail.
Incorrect Answers
A:Grouping files can count ingestion but does not join actions to privileged.e across the distinct platforms.
B:CMDB inventory cannot reconstruct privileged.e cross-source activity after the relevant authentication events are omitted.
D:Under entity-behavior risk evaluation at Partner Services: Overwriting identities destroys the ability to identify the distinct user whose behavior diverges from baseline.
Question 774
Corporate HQ knows a legitimate scheduled scanner will produce failed sign-in events on host-63 during a maintenance window. The detection should remain active for all other assets and times. Which rule feature targets the exception?
- A rule exception constrained by relevant attributes and an effective period
- Disable the entire rule permanently
- Change the incident severity to low with no exception
- Delete the parser for the log source
Explanation
Correct Answer
A:Rule exceptions suppress incidents for matching host-63 conditions during a defined single or recurring interval, preserving detection elsewhere.
Incorrect Answers
B:Global disablement discards all failed sign-in detections beyond the approved host-63 maintenance exception.
C:Considering correlation-rule investigation at Corporate HQ for host-63: Lowering priority still creates incidents for the expected scan and does not delimit the approved maintenance period.
D:Under correlation-rule investigation at Corporate HQ for host-63: Removing event parsing would harm all observations from Windows security logs and is not a precise, time-bound exception.
Question 775
An incident rule at West Operations was built with a reasonable blocked lookup filter but produces no alerts after the test passed. The rule exists and evidence is arriving. Which lifecycle setting should the analyst verify?
- That every event has an unusually long message string
- 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
Explanation
Correct Answer
D:Passing a test does not activate a rule. An inactive saved definition cannot generate live incidents from the incoming DNS resolution records stream.
Incorrect Answers
A:Message length is not a general prerequisite for triggering a valid blocked lookup correlation rule.
B:For rule deployment or exception at West Operations: Result-table size affects Analytics output, not whether an otherwise valid rule has been activated.
C:For An incident rule at West Operations was built with a reasonable blocked lookup filter but produces no alerts after the test: Considering rule deployment or exception at West Operations: Historical export jobs do not determine the active/inactive state of the live rule evaluator.
Question 776
Lookup table ProtectedSystems in City Branch has a numeric key, while the event field supplied by proxy access records is normalized as a string. Searches find no matching rows. What should be checked first?
- That the incident has a high severity label
- That a remediation script already ran for each event
- That the lookup key type and event expression use compatible data types
- That the analyst enabled a real-time Group By
Explanation
Correct Answer
C:The table schema requires typed keys. A numeric ProtectedSystems key cannot be reliably matched against a string-form proxy access records field without compatible typing or an appropriate conversion.
Incorrect Answers
A:Severity does not coerce a string event attribute into the numeric key type expected by ProtectedSystems.
B:For CMDB and lookup-table configuration at City Branch using proxy access records: Remediation occurs after incident logic and cannot repair the input data-type mismatch causing the lookup misses.
D:Under CMDB and lookup-table configuration at City Branch using proxy access records: Grouping changes how query results are summarized and is not a fix for a mismatched lookup key type.
Question 777
An analyst at East Retail wants incidents from a failed login rule to show the corresponding Source IP from the matching events so they can be grouped later in incident analytics. Which configuration maps that value?
- Select Source IP from the subpattern as an incident attribute
- Set the rule severity to high regardless of source identity
- Add a local text note without mapping the event field
- Enable the response workflow before validating the underlying rule match
Explanation
Correct Answer
A:In rule deployment or exception at East Retail: Incident definitions can inherit relevant Group By and filter fields from the triggering subpatterns. This makes Source IP available for later incident investigation and grouping.
Incorrect Answers
B:For An analyst at East Retail wants incidents from a failed login rule to show the corresponding Source IP from the matching: For rule deployment or exception at East Retail: Severity represents urgency, not the Source IP entity whose value needs to be stored for each incident.
C:For An analyst at East Retail wants incidents from a failed login rule to show the corresponding Source IP from the matching: Considering rule deployment or exception at East Retail: Notes may explain triage intent but do not populate the structured incident Source IP column from each matched event.
D:Under rule deployment or exception at East Retail: An Automation Policy cannot compensate for inaccurate event correlation; an untested rule may flood or miss production incidents.
Question 778
A Manufacturing rule for policy violation uses two subpatterns and should fire only if subpattern P1 occurs before P2 for the same Source IP. Which rule relationship expresses the order?
- AND
- OR
- AND-NOT
- FOLLOWED-BY
Explanation
Correct Answer
D:Under correlation-rule investigation at Manufacturing: FOLLOWED-BY requires P1 first and P2 later. Correlating the matching Source IP attributes further keeps the ordered events tied to one actor.
Incorrect Answers
A:In correlation-rule investigation at Manufacturing: AND requires both patterns but does not enforce their order; P2 could precede P1 for this policy violation activity.
B:OR triggers when either pattern appears, so the complete two-stage sequence for Manufacturing is not required.
C:Considering correlation-rule investigation at Manufacturing: AND-NOT expresses presence of P1 and absence of P2, the opposite of requiring a later P2 stage.
Question 779
A Partner Services rule should identify a single Host that reaches 6 DIFFERENT Process Name values, even if it sends many repeated events to one target. Which aggregate avoids that false positive?
- COUNT(Matched Events) >= 6 grouped by Host
- SUM(Destination Port) >= 6 without grouping
- COUNT(DISTINCT Process Name) >= 6 grouped by Host
- COUNT(DISTINCT Host) >= 6 grouped by Process Name
Explanation
Correct Answer
C:DISTINCT removes repeated target identities; the rule needs 6 independent Process Name values for one Host, not merely repeated attempts.
Incorrect Answers
A:6 raw events might all target one Process Name; repeated retries would meet this alternative without the required breadth.
B:Adding numerical port labels has no meaningful relationship to how many distinct Process Name values the actor contacted.
D:Under subpattern correlation at Partner Services with the specified 6 value: This reverses direction and measures many sources contacting one destination, not the specified source’s unique targets.
Question 780
For Manufacturing, a correlation rule must select deny events from gateway denies before testing frequency on host-85. Which rule component limits which events contribute to the calculation?
- The incident clear condition
- The subpattern event filter
- Configure an Automation Policy action without a rule-generated incident
- The email destination of the automation policy
Explanation
Correct Answer
B:For correlation-rule investigation at Manufacturing for host-85 using gateway denies: Event filters select matching attributes and values within each subpattern. Only eligible deny records from gateway denies enter later aggregation and threshold evaluation.
Incorrect Answers
A:In correlation-rule investigation at Manufacturing for host-85 using gateway denies: Clear conditions affect active incidents after triggering; they are not the first-stage selector of deny events.
C:Considering correlation-rule investigation at Manufacturing for host-85 using gateway denies: An action policy operates on qualifying incidents; it does not independently implement the matching event rule and incident definition.
D:Under correlation-rule investigation at Manufacturing for host-85 using gateway denies: This determines who is notified after an incident, not which source events pass subpattern filters.