Question 650
A Research analyst wants the event’s Source IP and User values visible in a generated incident but notices only the incident category appears. Which editor area should be reviewed?
- The FortiGate DHCP lease duration
- The lookup-table schema editor for unrelated enrichment
- Change only a dashboard filter while leaving the production rule unchanged
- Define Action and the incident’s Triggered Attributes mapping
Explanation
Correct Answer
D:Triggered Attributes controls which details from matching events are carried into the incident for dashboards and analysis, including User and Source IP.
Incorrect Answers
A:For A Research analyst wants the event’s Source IP and User values visible in a generated incident but notices only the incident: In rule deployment or exception at Research: DHCP duration does not determine which parsed attributes are copied into the FortiSIEM incident.
B:For A Research analyst wants the event’s Source IP and User values visible in a generated incident but notices only the incident: For rule deployment or exception at Research: Lookup tables can supply context, but the missing direct event fields are selected in the incident definition.
C:Considering rule deployment or exception at Research: Dashboard filtering modifies analyst display data, not the enabled rule conditions used by FortiSIEM to generate incidents.
Question 651
In Research, a rule must fire when a single Source IP produces at least 17 blocked lookup events in DNS resolution records. What Group By and aggregation correctly define the rule?
- No grouping; COUNT(Matched Events) >= 17
- Group By Source IP; COUNT(Matched Events) >= 17
- Group By Queried Domain; COUNT(DISTINCT Source IP) >= 17
- Group By Source IP; AVG(CPU Util) >= 17
Explanation
Correct Answer
B:The grouping isolates each Source IP and the raw-event count checks whether its blocked lookup volume reaches 17 within the rule window.
Incorrect Answers
A:In subpattern correlation at Research using DNS resolution records with the specified 17 value: The global count can be met by aggregating unrelated Source IP values, creating false correlations across distinct actors.
C:Considering subpattern correlation at Research using DNS resolution records with the specified 17 value: This asks for many source entities per destination. It is not a burst count for each individual Source IP.
D:Average CPU describes resource load, not the frequency of blocked lookup DNS resolution records records from the source.
Question 652
City Branch is being flooded by email when failed login incidents are automatically cleared by rule recovery conditions. Which policy setting specifically addresses clear-related notifications?
- Modify the CMDB device type for every alerting host
- The clear-notification suppression settings in Automation Policy
- Stop collecting all {log} events while the SOC is busy
- Delete the related correlation rule permanently
Explanation
Correct Answer
B:For Automation Policy workflow at City Branch: FortiSIEM supports excluding notifications for automatically, manually or system-cleared incidents. This can reduce recovery-message noise without suppressing new failed login detections.
Incorrect Answers
A:In Automation Policy workflow at City Branch: Inventory classification is not the direct clear-notification exception offered by the policy.
C:Considering Automation Policy workflow at City Branch: Discarding telemetry would create an evidence gap rather than controlling which incident status changes generate email.
D:Under Automation Policy workflow at City Branch: Rule deletion stops useful initial failed login detections as well as clears, a much broader change than the requested notification suppression.
Question 653
West Operations needs a portable record of several sign-in 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 sign-in alert records without changing their detection or resolution state.
Incorrect Answers
A:In incident-management case at West Operations: 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 sign-in alerts.
C:Disabling changes future detection; it is not necessary for exporting the investigation record from West Operations.
Question 654
The City Branch performance report for host-83 and peer systems needs hosts whose average CPU is at least 50% AND whose average memory utilization is at least 55%. How should FortiSIEM limit the aggregate output?
- Use event keywords CPU and Memory with no aggregation
- Use OR between the two aggregate thresholds
- Group only by event timestamp and discard host identity
- Use AVG(CPU Util) >= 50 AND AVG(Memory Util) >= 55 as Display Conditions
Explanation
Correct Answer
D:Under aggregate-query calculation at City Branch for host-83: Both threshold tests run against aggregate values for each host after grouping. The conjunction excludes hosts that exceed only one of the two measures.
Incorrect Answers
A:In aggregate-query calculation at City Branch for host-83: Keywords do not compute per-host averages; individual messages do not prove that either mean crosses the specified limits.
B:For aggregate-query calculation at City Branch for host-83: An OR permits a host with only high CPU or only high memory, contrary to the two simultaneous City Branch requirements.
C:Considering aggregate-query calculation at City Branch for host-83: Timestamp buckets cannot establish which host breached both mean-utilization thresholds, which is central to this performance report.
Question 655
After opening one permission failure event from database audit records, an investigator wants other events having the same User on host-81, not merely lines containing its spelling. How should the query be narrowed?
- Query CMDB for every inventoried asset instead of events
- Use only a free-text keyword extracted from the raw event
- Group all events by their ingestion minute
- Filter on the parsed User event attribute with the exact value
Explanation
Correct Answer
D:A structured Event Attribute condition compares the normalized User field, avoiding accidental text matches in unrelated portions of database audit records.
Incorrect Answers
A:CMDB can enrich host identity, yet it is not the normalized database audit records search that finds events sharing User.
B:Keyword matching can find the same characters in messages that have a different parsed User, weakening entity identity for host-81.
C:Considering historical or real-time event analysis at the SOC for host-81 using database audit records: Grouping by minute changes output granularity but does not enforce equality on User for the related-event investigation.
Question 656
Corporate HQ wants to distinguish the busiest Source IP by events in a firewall session logs query. A single source has 14 records spread across three Destination IP values with counts 6, 6, and 2. Which statistic will rank sources by traffic-event frequency?
- COUNT(Matched Events) grouped by source
- AVG(CPU Util) grouped by source
- SUM(Source Port) across all sources
- COUNT(DISTINCT Destination IP) grouped by source
Explanation
Correct Answer
A:In aggregate-query calculation at Corporate HQ using firewall session logs with the specified 14 value: This measures 14 matching rows for the source, including repeats to the three destinations, which is the frequency metric requested.
Incorrect Answers
B:For aggregate-query calculation at Corporate HQ using firewall session logs with the specified 14 value: CPU measures resource utilization rather than the frequency of firewall session logs events; it cannot rank sources by event traffic.
C:Considering aggregate-query calculation at Corporate HQ using firewall session logs with the specified 14 value: Source ports are labels rather than additive traffic quantities. Summing them across the full search would not produce a meaningful per-source frequency.
D:Under aggregate-query calculation at Corporate HQ using firewall session logs with the specified 14 value: Only three destination values exist. Distinct destination count is a fan-out metric and ignores the 14 individual event occurrences.
Question 657
An MSSP analyst is authorized to inspect West Operations only. A query for blocked lookup events from DNS resolution records unexpectedly includes tenant peers. Which search setting should be restricted?
- Group the mixed result by Source IP
- Add a display column showing the event time
- Increase the maximum rows returned by the search
- Select the intended organization in the service-provider search scope
Explanation
Correct Answer
D:FortiSIEM service-provider searches support organization selection. Constraining scope to West Operations prevents the query from including the other tenants’ event sets.
Incorrect Answers
A:Grouping by Source IP reorganizes the already selected records and does not enforce the organizational boundary for West Operations.
B:For historical or real-time event analysis at West Operations using DNS resolution records: Event timestamps assist investigation but do not replace the search’s organization selection when isolating one customer.
C:Row limits affect truncation, not data tenancy; a higher limit would reveal more mixed-tenant events instead of isolating West Operations.
Question 658
A FortiSIEM correlation design at West Operations observes P1 (stopped service in service health records) and P2 (a related action on host-193). It must require P1 present with P2 absent, without an ordering test. Which relationship operator best expresses that precise condition?
- AND
- FOLLOWED-BY
- NOT-FOLLOWED-BY
- OR
- AND-NOT
Explanation
Correct Answer
E:In subpattern correlation at West Operations for host-193 using service health records: 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.
Incorrect Answers
A:In subpattern correlation at West Operations for host-193 using service health records: 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.
B:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-193 rather than unordered coincidence.
C:Considering subpattern correlation at West Operations for host-193 using service health 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.
D:Under subpattern correlation at West Operations for host-193 using service health 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.
Question 659
A rule at Cloud Services should trigger when P1 (policy violation) occurs and a P2 recovery indicator does NOT arrive later in the configured evaluation window. Which operator distinguishes later absence from unordered exclusion?
- AND-NOT
- FOLLOWED-BY
- OR
- NOT-FOLLOWED-BY
Explanation
Correct Answer
D:This operator evaluates the existence of P1 and the absence of a subsequent P2. The temporal relationship is central to the missing-recovery use case on host-208.
Incorrect Answers
A:AND-NOT expresses P1 with P2 absent but lacks the same directional later-event condition for host-208.
B:For subpattern correlation at Cloud Services: FOLLOWED-BY requires the very P2 recovery event that the unresolved-fault detector says must be absent.
C:Considering subpattern correlation at Cloud Services: OR treats either P1 or P2 as enough, including a standalone recovery event that should not represent unresolved failure.
Question 660
The MSSP has a lookup table named ProtectedSystems owned by Research; another tenant runs a similarly named enrichment. Which property should be verified before sharing result assumptions across the tenants?
- Retrieve only the CMDB inventory view and assume it provides user-maintained lookup values
- The organization associated with the lookup-table definition and data
- Compare a string identity value with a numeric lookup key without conversion or type alignment
- The last incident severity used by another customer
Explanation
Correct Answer
B:FortiSIEM lookup-table creation selects an Organization. Even if names appear similar, Research data and another tenant’s scoped lookup must not be assumed interchangeable.
Incorrect Answers
A:In CMDB and lookup-table configuration at Research: Inventory data and user-managed lookup tables serve different purposes; reading CMDB alone need not return the requested mapping.
C:Considering CMDB and lookup-table configuration at Research: The comparison must respect the configured lookup data types. A type mismatch prevents a reliable exact key match.
D:Alert priority is not an ownership or lookup-data scoping control for the ProtectedSystems repository.