Question 510
The Logistics team has written a new rule for blocked request in web application alerts, but it does not immediately generate incidents after saving. What is the expected initial lifecycle behavior?
- Rule creation automatically archives all matching events
- The rule will activate only when an analyst changes a CMDB device password
- Every new rule becomes active and irreversible as soon as Save is clicked
- The new rule is saved inactive and should be tested before activation
Explanation
Correct Answer
D:FortiSIEM rule creation saves a new rule in an inactive state. Testing against representative blocked request events before activation reduces avoidable noise.
Incorrect Answers
A:Saving a rule definition does not mean it archives or deletes web application alerts events; activation and execution are separate matters.
B:For correlation-rule investigation at Logistics using web application alerts: Credentials affect data acquisition, while enabling the saved correlation rule is a distinct step of the analytics workflow.
C:Considering correlation-rule investigation at Logistics using web application alerts: FortiSIEM does not automatically force a new resource rule active. Assuming this would obscure why Logistics sees no incident.
Question 511
A Manufacturing analyst is already searching permission failure events in database audit records, but only wants records whose reporting devices have CMDB service group=critical. How can event selection incorporate inventory context?
- Set incident severity to critical before running the query
- Reference CMDB device properties through the supported event/CMDB query mechanism
- Group the events by ingestion timestamp alone
- Compare the raw event keyword against the word service group only
Explanation
Correct Answer
B:FortiSIEM combined Event/CMDB searches and DeviceToCMDBAttr-style access can apply inventory properties such as service group to event evidence.
Incorrect Answers
A:Incident severity is an alert attribute; it does not add the service group predicate to existing event-search matches.
C:Changing time granularity does not test whether the reporting device has the required CMDB service group value.
D:Unless that property is present in every raw database audit records message, keyword text cannot reliably enforce the CMDB-derived criticality constraint.
Question 512
A blocked lookup incident on host-175 at Research represented a real outage. After repair, the analyst manually clears it and records evidence. Which combination reflects that history?
- Resolution None; Status Active
- Resolution True Positive; Status Manually Cleared
- Resolution True Positive; Status System Cleared
- Resolution False Positive; Status Manually Cleared
Explanation
Correct Answer
B:For incident-management case at Research for host-175: An actual blocked lookup issue merits a true-positive verdict, and human closure after verified repair results in the manually cleared lifecycle state.
Incorrect Answers
A:The incident has already been judged and closed; leaving it active with no verdict misrepresents the completed Research response.
C:Considering incident-management case at Research for host-175: System Cleared indicates an automated clear condition, not the manual verification and closure described here.
D:False Positive would describe a benign or incorrect detection, contradicting the confirmed real incident on host-175.
Question 513
Logistics is being flooded by email when blocked request incidents are automatically cleared by rule recovery conditions. Which policy setting specifically addresses clear-related notifications?
- The clear-notification suppression settings in Automation Policy
- Delete the related correlation rule permanently
- Modify the CMDB device type for every alerting host
- Stop collecting all {log} events while the SOC is busy
Explanation
Correct Answer
A:In Automation Policy workflow at Logistics: FortiSIEM supports excluding notifications for automatically, manually or system-cleared incidents. This can reduce recovery-message noise without suppressing new blocked request detections.
Incorrect Answers
B:For Automation Policy workflow at Logistics: Rule deletion stops useful initial blocked request detections as well as clears, a much broader change than the requested notification suppression.
C:For Logistics is being flooded by email when blocked request incidents are automatically cleared by rule recovery conditions.: Considering Automation Policy workflow at Logistics: Inventory classification is not the direct clear-notification exception offered by the policy.
D:For Logistics is being flooded by email when blocked request incidents are automatically cleared by rule recovery conditions.: Under Automation Policy workflow at Logistics: Discarding telemetry would create an evidence gap rather than controlling which incident status changes generate email.
Question 514
Research wants notifications only when sign-in affects the protected systems group, excluding its lab devices. How is this expressed in a FortiSIEM Automation Policy?
- Sorting the incident list by hostname
- Changing the rules folder name to Production
- A generic incident email sent to all tenants without item conditions
- Affected Items group selection with the lab group explicitly excluded
Explanation
Correct Answer
D:Under Automation Policy workflow at Research: Automation Policy affected items can include device/application groups and NOT selections, narrowing the sign-in action to protected production assets.
Incorrect Answers
A:In Automation Policy workflow at Research: Sort order helps viewing but cannot prevent lab-device alerts from meeting an action policy.
B:For Automation Policy workflow at Research: Folder naming does not restrict which devices are affected in the policy evaluation.
C:Considering Automation Policy workflow at Research: An unrestricted message action would still notify about lab devices and cannot implement the specified protected-systems scope.
Question 515
During an approved 60-minute window, host-75 at Logistics is deliberately generating failed authentication events. The existing rule must continue to detect the same behavior on other hosts. What should the analyst configure?
- Disable the rule for every organization until next week
- Clear all previously recorded incidents as the only action
- Raise the count threshold for all hosts permanently
- A scoped, time-bounded exception for the rule
Explanation
Correct Answer
D:The exception can match host-75 and the 60-minute approval window, suppressing only the anticipated incident without silencing other devices.
Incorrect Answers
A:Global disablement creates an avoidable monitoring gap well beyond host-75 and the approved interval.
B:For rule deployment or exception at Logistics for host-75: Clearing historical incidents does not prevent newly matching maintenance events from producing fresh alerts during the window.
C:Considering rule deployment or exception at Logistics for host-75: A threshold increase changes the detector everywhere and may miss attacks on otherwise quiet devices after the maintenance period.
Question 516
At City Branch, a security analyst needs to compare risk across analyst.g and nearby workstation entities in a dashboard. Which design makes the comparison meaningful?
- Hide all entity identifiers and show one grand total
- Summarize by entity type and stable entity identifier, with a comparable risk measure
- Group raw events by their collector name without retaining user or host identity
- Use only event timestamp as the user/entity correlation key
Explanation
Correct Answer
B:For entity-behavior risk evaluation at City Branch: Entity-scoped dashboard data lets analysts compare user and host indicators while retaining identity. Stable identifiers avoid fragmented or duplicate risk rows.
Incorrect Answers
A:A grand total cannot identify which analyst.g or host requires investigation after risk is aggregated.
C:Considering entity-behavior risk evaluation at City Branch: Collector grouping describes ingestion infrastructure rather than the identity whose behavior and risk must be evaluated.
D:Under entity-behavior risk evaluation at City Branch: Timestamps cannot establish stable identity across VPN, identity-provider and other event sources for a UEBA investigation.
Question 517
In a FortiSIEM anomaly task for nightly database write rate, West Operations wants the model to tolerate routine variation rather than treat every unusual point as a certain attack. What should the analyst examine?
- Changing every benign record to a firewall deny
- The anomaly threshold/contamination settings and observed false-positive rate
- Change the model’s display title without checking input data types and inference behavior
- Whether every source host is deleted from CMDB
Explanation
Correct Answer
B:Anomaly scoring uses statistical decisions about unusual behavior. Threshold and contamination tuning affect sensitivity; analysts should compare flagged nightly database write rate cases with actual operations.
Incorrect Answers
A:Blanket blocking is not model threshold calibration and could disrupt legitimate business flows at West Operations.
C:Considering machine-learning analysis at West Operations: Model labels are metadata; they do not repair malformed training values, missing features or drift in the input distribution.
D:Deleting assets suppresses useful context and does not provide a principled threshold for recognizing abnormal nightly database write rate values.
Question 518
For Partner Services, a correlation rule must select quarantine events from email security events before testing frequency on host-152. Which rule component limits which events contribute to the calculation?
- Change the incident severity but leave the event-selection and trigger components unset
- The email destination of the automation policy
- The incident clear condition
- The subpattern event filter
Explanation
Correct Answer
D:Under correlation-rule investigation at Partner Services for host-152 using email security events: Event filters select matching attributes and values within each subpattern. Only eligible quarantine records from email security events enter later aggregation and threshold evaluation.
Incorrect Answers
A:In correlation-rule investigation at Partner Services for host-152 using email security events: Severity classifies an incident after a rule match; it cannot replace event filters and the actual correlation trigger.
B:For correlation-rule investigation at Partner Services for host-152 using email security events: This determines who is notified after an incident, not which source events pass subpattern filters.
C:Considering correlation-rule investigation at Partner Services for host-152 using email security events: Clear conditions affect active incidents after triggering; they are not the first-stage selector of quarantine events.
Question 519
East Retail sees privileged.e with multiple high-severity suspicious sign-ins and access to a critical host. Why is entity risk more informative than raw alert count alone?
- Entity risk is only a cosmetic dashboard color
- Risk must equal the exact number of normalized source IP values
- Risk can incorporate event severity, rarity and affected asset criticality
- A high alert count automatically proves every event is malicious
Explanation
Correct Answer
C:Considering entity-behavior risk evaluation at East Retail: An entity’s risk assessment combines context beyond volume. A few unusual, severe events involving a critical asset may merit more attention than many routine benign records.
Incorrect Answers
A:In entity-behavior risk evaluation at East Retail: Risk information supports investigation and prioritization, not merely display choices in a widget.
B:Unique IP cardinality can be an input to a rule, but it is not the complete definition of UEBA risk for privileged.e.
D:Under entity-behavior risk evaluation at East Retail: False positives, benign bursts and asset context require triage; volume alone does not provide that certainty.
Question 520
In Manufacturing, an investigator wants to repeat the same deny filter over gateway denies next week without reconstructing the search. Which operation captures the query as a reusable analytic artifact?
- Clear the open incident generated by a different rule
- Export one row without saving any definition
- Save the working search definition as a report
- Modify the data collector polling interval
Explanation
Correct Answer
C:Saving the query definition preserves its selected filter and display logic for reuse on future gateway denies investigations; time can be adjusted when run.
Incorrect Answers
A:Clearing changes incident lifecycle state; it does not persist the analysis query for future deny searches.
B:For historical or real-time event analysis at Manufacturing using gateway denies: A row export is evidence from one run; it does not retain reusable filters and aggregation choices for the next week.
D:Under historical or real-time event analysis at Manufacturing using gateway denies: Collection rate controls incoming monitoring data rather than the stored search definition the investigator wants to reuse.