Question 400
North Finance wants a FortiSIEM dashboard listing the users associated with the most suspicious gateway denies events, rather than a separate row for each raw event. Which approach best fits?
- Group by the raw event timestamp at maximum precision only
- Use a device-only CMDB table without event joins
- Group a search or dashboard dataset by user and aggregate a relevant metric
- Convert every alert into a remediation script
Explanation
Correct Answer
C:Grouping normalized gateway denies data by user produces entity-level summaries. Metrics such as count, distinct destinations or risk can make a dashboard useful for user behavior review.
Incorrect Answers
A:In entity-behavior risk evaluation at North Finance using gateway denies: Each event may have a different timestamp, so this grouping defeats the requested user-centered rollup.
B:CMDB-only views do not show suspicious gateway denies behavior grouped by users across the timeframe.
D:Under entity-behavior risk evaluation at North Finance using gateway denies: Remediation definitions are device actions, not a dashboard data aggregation for user analytics.
Question 401
A rule at West Operations should trigger when P1 (blocked lookup) occurs and a P2 recovery indicator does NOT arrive later in the configured evaluation window. Which operator distinguishes later absence from unordered exclusion?
- NOT-FOLLOWED-BY
- FOLLOWED-BY
- OR
- AND-NOT
Explanation
Correct Answer
A: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-65.
Incorrect Answers
B:For subpattern correlation at West Operations: FOLLOWED-BY requires the very P2 recovery event that the unresolved-fault detector says must be absent.
C:Considering subpattern correlation at West Operations: OR treats either P1 or P2 as enough, including a standalone recovery event that should not represent unresolved failure.
D:AND-NOT expresses P1 with P2 absent but lacks the same directional later-event condition for host-65.
Question 402
For the response to an incident affecting host-165, cloud Services wants the same vetted action, isolate an infected endpoint, to execute when its verified permission failure incident rule fires, with no per-incident analyst click. Which configuration automates response?
- A historical event export scheduled daily
- A dashboard Group By on incident time
- An enabled Automation Policy with Run Remediation/Script
- An incident comment template without an action
Explanation
Correct Answer
C:Considering correlation-rule investigation at the SOC for host-165: 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
A:In correlation-rule investigation at the SOC for host-165: Export creates copies of evidence, not a near-real-time response on incident generation.
B:For correlation-rule investigation at the SOC for host-165: Dashboard aggregation shows incident patterns but is not the action engine for the Cloud Services response.
D:Under correlation-rule investigation at the SOC for host-165: Comments convey instructions but do not execute isolate an infected endpoint automatically on the selected systems.
Question 403
After connecting FortiSIEM UEBA risk intelligence to FortiGate for remote desktop service access at Corporate HQ, what provides a defensible end-to-end acceptance test?
- Configure a static IP list but never refresh changes from the FortiSIEM watchlist
- Confirm only that a training report was exported
- Verify source rule match, watchlist membership, successful connector import, applicable FortiGate policy hit, and observed test result
- Confirm only that one FortiSIEM incident exists
Explanation
Correct Answer
C:All stages matter: FortiSIEM must identify 198.51.100.41, publish the indicator, and FortiGate must retrieve and actually enforce it on the relevant remote desktop service path.
Incorrect Answers
A:In IP feed and FortiGate enforcement at Corporate HQ: Without feed synchronization, additions and removals in FortiSIEM need not propagate to the FortiGate enforcement data.
B:For IP feed and FortiGate enforcement at Corporate HQ: ML report export is not equivalent to validating a UEBA watchlist-to-policy enforcement chain.
D:Under IP feed and FortiGate enforcement at Corporate HQ: An incident proves detection but not indicator publication, connector synchronization or FortiGate enforcement.
Question 404
West Operations wants a rule on host-175 that triggers only when at least three matched performance samples have mean CPU utilization above 81%. Which subpattern condition expresses both requirements?
- COUNT(Matched Events) >= 3 OR AVG(CPU Util) > 81
- COUNT(DISTINCT Host) >= 3
- MAX(CPU Util) > 81 with no sample count
- COUNT(Matched Events) >= 3 AND AVG(CPU Util) > 81
Explanation
Correct Answer
D:The first aggregate protects against a one-sample spike; the second tests actual average load. Both are evaluated in the host-175 group.
Incorrect Answers
A:In subpattern correlation at West Operations for host-175: OR allows a three-sample low-CPU set or a single high-CPU sample to trigger, violating the combined requirements.
B:Three distinct hosts are not required. The question concerns at least three samples on the same host-175.
C:Considering subpattern correlation at West Operations for host-175: Only the maximum is tested, so one outlier can trigger even if the average and minimum sample count do not qualify.
Question 405
For the response to an incident affecting host-132, an analyst at West Operations has cleared a stopped service incident on host-132, but the malicious source is still allowed by the FortiEMS server. What does this show about incident clearing?
- Device reachability is unnecessary for any remediation script
- A cleared incident automatically changes every firewall policy
- The original {kind} events have been removed from the database
- Clearing incident status is not equivalent to executing network remediation
Explanation
Correct Answer
D:Under incident-management case at West Operations for host-132: A lifecycle transition documents closure or recovery, while the FortiEMS server needs a separate enforcement action to implement the desired containment.
Incorrect Answers
A:In incident-management case at West Operations for host-132: A management path and supported credentials are still needed when a script is intended to operate on the FortiEMS server.
B:For incident-management case at West Operations for host-132: No general rule links incident status changes to all network device configurations; remediation must be explicitly configured or executed.
C:Considering incident-management case at West Operations for host-132: Incident clear state does not imply deletion of the underlying evidence, and it would not explain unchanged firewall access.
Question 406
For Corporate HQ, expected failed sign-in volume differs significantly among host-143-class devices. A fixed threshold of 21 events creates noise. Which rule concept better accounts for each device’s established normal behavior?
- Increase the one global threshold equally for all devices
- Use the rule title as a numeric threshold
- Use an appropriate statistical baseline to derive an anomaly threshold
- Disable the rule and stop collecting the event source
Explanation
Correct Answer
C:FortiSIEM can compute baseline statistics for dynamic rule thresholds. Comparing the observed 39 events against local normal activity is more meaningful than one global constant.
Incorrect Answers
A:A universal increase might suppress false alerts on host-143 yet miss genuinely unusual activity on quieter systems.
B:For subpattern correlation at Corporate HQ for host-143: The title is metadata, not a computed mean, variance or other baseline statistic for anomaly evaluation.
D:This removes both false positives and valuable detections instead of adapting failed sign-in criteria to an observed baseline.
Question 407
East Retail / host-104: incident analytics must enrich service health records source addresses with a CMDB asset owner and a local lookup-listed business unit. Which design decisions enable these joins? Choose TWO.
- Create a lookup key whose type conflicts with the compared event field
- Assume search-result row numbers are stable device identities
- Match the event or CMDB value to an appropriately typed lookup-table key
- Delete the CMDB object after the search to improve accuracy
- Use the normalized source identifier compatible with the CMDB object key
Explanation
Correct Answers
C:Lookup enrichment requires a compatible key and field type so the business-unit value can be found for the correct source.
E:CMDB enrichment depends on matching the event Host identity to an inventory record, rather than grouping on unrelated text.
Incorrect Answers
A:An incompatible numeric/string key can prevent a correct equality lookup even when visually similar values appear.
B:Result ordering changes between searches and is not a reliable primary key for joining host-104 or the asset owner.
D:Removing the inventory record destroys the owner context that this enrichment depends upon.
Question 408
An MSSP analyst is authorized to inspect City Branch only. A query for rejected request events from cloud API audit events unexpectedly includes tenant peers. Which search setting should be restricted?
- Increase the maximum rows returned by the search
- Select the intended organization in the service-provider search scope
- Add a display column showing the event time
- Group the mixed result by User
Explanation
Correct Answer
B:FortiSIEM service-provider searches support organization selection. Constraining scope to City Branch prevents the query from including the other tenants’ event sets.
Incorrect Answers
A:Row limits affect truncation, not data tenancy; a higher limit would reveal more mixed-tenant events instead of isolating City Branch.
C:Considering historical or real-time event analysis at City Branch using cloud API audit events: Event timestamps assist investigation but do not replace the search’s organization selection when isolating one customer.
D:Grouping by User reorganizes the already selected records and does not enforce the organizational boundary for City Branch.
Question 409
After opening one rejected request event from cloud API audit events, an investigator wants other events having the same User on host-157, not merely lines containing its spelling. How should the query be narrowed?
- Filter on the parsed User event attribute with the exact value
- Use only a free-text keyword extracted from the raw event
- Group all events by their ingestion minute
- Query CMDB for every inventoried asset instead of events
Explanation
Correct Answer
A:A structured Event Attribute condition compares the normalized User field, avoiding accidental text matches in unrelated portions of cloud API audit events.
Incorrect Answers
B:Keyword matching can find the same characters in messages that have a different parsed User, weakening entity identity for host-157.
C:Considering historical or real-time event analysis at the SOC for host-157 using cloud API audit events: Grouping by minute changes output granularity but does not enforce equality on User for the related-event investigation.
D:CMDB can enrich host identity, yet it is not the normalized cloud API audit events search that finds events sharing User.
Question 410
For the response to an incident affecting host-77, corporate HQ has the FortiEMS server in CMDB, but a unauthorized change remediation cannot authenticate to the target. Which FortiSIEM configuration is the relevant prerequisite?
- A larger search result-row limit
- An unrelated notification subject line
- Use a report-generated value as the Enforce On endpoint without a CMDB device definition
- A supported Enforce On device access credential under Admin > Setup > Credentials
Explanation
Correct Answer
D:Under inventory or lookup query at the SOC for host-77: Remediation uses an approved access method and stored credential to connect to the target device. A CMDB entry alone cannot authorize the reset a controlled service operation.
Incorrect Answers
A:In inventory or lookup query at the SOC for host-77: Analytics limits affect displayed evidence and cannot provide credentials for the FortiEMS server action.
B:For inventory or lookup query at the SOC for host-77: Email content does not establish a supported management login for the remediation target.
C:Considering inventory or lookup query at the SOC for host-77: An event attribute does not replace the managed device identity used by FortiSIEM remediation to select a target.