Question 390
A Logistics rule must add a User address from a rejected request incident to a watchlist whose declared element type is IP. The incident attribute is a string label instead. What should be verified?
- The historical search uses a 30-day default range
- The watchlist type matches the type of the incident attribute written to it
- The rule has at least three different email recipients
- The rule incident title includes the word IP
Explanation
Correct Answer
B:For correlation-rule investigation at Logistics: FortiSIEM rejects incompatible watchlist/incident attribute types. An IP watchlist expects a compatible IP-type incident value, not an unrelated string label.
Incorrect Answers
A:In correlation-rule investigation at Logistics: Search time horizon does not convert a string incident attribute to an IP-type watchlist entry.
C:Considering correlation-rule investigation at Logistics: Email fan-out has no effect on the type compatibility of a User entry stored in the IP watchlist.
D:Under correlation-rule investigation at Logistics: Free-text title labels cannot change the underlying attribute type used for watchlist updates.
Question 391
After a unauthorized change detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic rule. What must the first rule’s generated incident provide?
- Only the literal words suspected host in the incident title
- A typed Host incident attribute compatible with the IP watchlist
- A notification threshold without an incident definition
- Enable the response workflow before validating the underlying rule match
Explanation
Correct Answer
B:For After a unauthorized change detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic: For rule deployment or exception at Corporate HQ: The watchlist update uses a field from the generated incident. A correctly typed Host value lets downstream rules match the same address reliably.
Incorrect Answers
A:For After a unauthorized change detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic: In rule deployment or exception at Corporate HQ: An informal title string does not provide a typed IP field that the watchlist can store and another rule can match.
C:For After a unauthorized change detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic: Considering rule deployment or exception at Corporate HQ: Alerts require a defined incident, and the watchlist needs its typed attribute; frequency alone supplies neither.
D:Under rule deployment or exception at Corporate HQ: An Automation Policy cannot compensate for inaccurate event correlation; an untested rule may flood or miss production incidents.
Question 392
For the response to an incident affecting host-153, a FortiSIEM remediation for a Linux server fails at City Branch. The target appliance exists physically but does not appear in CMDB. What prerequisite is missing?
- A real-time Group By on raw event size
- The Enforce On device must be defined in FortiSIEM CMDB
- A customer-wide increase of the risk score
- An exported CSV of every unrelated past incident
Explanation
Correct Answer
B:For inventory or lookup query at City Branch for host-153: Remediation requires the target device to be represented as the Enforce On device in inventory. Physical reachability alone does not give FortiSIEM the required identity and context.
Incorrect Answers
A:In inventory or lookup query at City Branch for host-153: Grouping search results cannot replace the target device inventory prerequisite for the remediation framework.
C:Considering inventory or lookup query at City Branch for host-153: Changing priority does not create the missing CMDB object required to enforce the script action.
D:Under inventory or lookup query at City Branch for host-153: Export files do not register the affected Linux server as a manageable remediation target.
Question 393
Partner Services wants to use the same hourly failed sign-ins training job for host-111 but discovers that the training dataset contains almost no valid records. What is the priority before production inference?
- Increase the notification recipient count
- Change the ZTNA enforcement port for unrelated traffic
- Repair the event/report source and confirm adequate representative training samples
- Mark all nonexistent model findings as resolved
Explanation
Correct Answer
C:Insufficient or malformed hourly failed sign-ins data prevents reliable learning. Verify the report filters, time span, field types and job inputs before interpreting model output.
Incorrect Answers
A:Alert recipients affect message delivery after a finding, not whether enough valid hourly failed sign-ins samples exist for training.
B:For historical or real-time event analysis at Partner Services for host-111: External access-policy ports do not address missing training observations in the ML pipeline.
D:Under historical or real-time event analysis at Partner Services for host-111: Incident statuses cannot compensate for an empty or nonrepresentative training dataset.
Question 394
Research has correlated several failed authentication incidents and related events into one investigation that should have an owner, workflow status, and associated evidence. Which FortiSIEM object is most appropriate?
- A notification severity threshold alone
- An unrelated CMDB lookup key
- A free-text event keyword saved as a report
- A case associated with the relevant incidents/events
Explanation
Correct Answer
D:Case management groups related incidents into an assigned work item with investigation ownership and progression, rather than treating every host-42 alert independently.
Incorrect Answers
A:In incident-management case at Research: A threshold may control alert delivery but cannot connect multiple findings into one assigned investigation.
B:For incident-management case at Research: A lookup key helps enrichment but does not provide an investigator owner and lifecycle for the related incident cluster.
C:A saved search can surface evidence but is not the managed case workflow with assignment and status for Research.
Question 395
After completing an East Retail outer event search with an inner CMDB list, the analyst wants to rerun the combined definition during later stopped service investigations. What should be saved?
- Save the complete nested search definition as a report
- Only archive the last rendered table as an image
- Add a new lookup-table key without changing the report
- Clear an unrelated incident and discard the search
Explanation
Correct Answer
A:Persisting the outer definition records its nested membership criterion and display configuration, allowing it to be rerun for later service health records evidence.
Incorrect Answers
B:For nested search comparison at East Retail: A static image preserves one output but not the outer query, CMDB comparison and future event interval.
C:Considering nested search comparison at East Retail: Editing a table schema is not required to preserve the existing event/CMDB nested search logic.
D:Incident clearing affects workflow state and does not retain the nested query used to find qualifying stopped service records.
Question 396
Research needs all CMDB devices whose IDs occur in a report of rejected request cloud API audit events events from the past 20 minutes. Which nested-search arrangement is suited to that goal?
- Real-time Group By over all incoming events
- Outer CMDB query with an inner event query returning matching device identifiers
- Outer event query with an inner CMDB query returning owners only
- Two unrelated CMDB queries combined only by report titles
Explanation
Correct Answer
B:The desired result is a device inventory list, so CMDB forms the outer set. The inner event report supplies qualifying IDs from the 20-minute event window.
Incorrect Answers
A:In nested search comparison at Research using cloud API audit events with the specified 20 value: The request selects inventory objects based on prior stored events. Streaming Group By is unsupported and does not implement the needed outer CMDB set.
C:This direction produces event results, not a complete CMDB device list selected by observed rejected request activity.
D:Without the inner event condition, inventory queries cannot establish which devices actually generated cloud API audit events in the specified interval.
Question 397
A Research analyst wants the event’s Application and User values visible in a generated incident but notices only the incident category appears. Which editor area should be reviewed?
- Change only a dashboard filter while leaving the production rule unchanged
- The FortiGate DHCP lease duration
- Define Action and the incident’s Triggered Attributes mapping
- The lookup-table schema editor for unrelated enrichment
Explanation
Correct Answer
C:Triggered Attributes controls which details from matching events are carried into the incident for dashboards and analysis, including User and Application.
Incorrect Answers
A:In rule deployment or exception at Research: Dashboard filtering modifies analyst display data, not the enabled rule conditions used by FortiSIEM to generate incidents.
B:For rule deployment or exception at Research: DHCP duration does not determine which parsed attributes are copied into the FortiSIEM incident.
D:For A Research analyst wants the event’s Application and User values visible in a generated incident but notices only the: Under rule deployment or exception at Research: Lookup tables can supply context, but the missing direct event fields are selected in the incident definition.
Question 398
North Finance wants to tag incidents produced by a deny correlation rule so that analysts can filter the Incident dashboard by this classification. Which step is appropriate?
- Change every incident’s resolution to false positive
- Rename the event parser so the rule inherits the parser’s name as a tag
- Select an existing rule tag in Step 3: Define Actions
- Create a search result column named tag but leave the rule unchanged
Explanation
Correct Answer
C:For North Finance wants to tag incidents produced by a deny correlation rule so that analysts can filter the Incident dashboard: Considering rule deployment or exception at North Finance: FortiSIEM lets an analyst attach defined tags to a rule; those tags can appear for incidents in applicable views and support focused triage.
Incorrect Answers
A:Resolution records investigation outcome, not the shared deny classification used to filter incidents.
B:For North Finance wants to tag incidents produced by a deny correlation rule so that analysts can filter the Incident dashboard: For rule deployment or exception at North Finance: Parser names describe event normalization and are not the same resource as configurable tags attached to rules.
D:For North Finance wants to tag incidents produced by a deny correlation rule so that analysts can filter the Incident dashboard: Under rule deployment or exception at North Finance: A temporary display column does not assign the intended tag to future incidents generated by the rule.
Question 399
A West Operations policy is configured to create cases automatically for blocked lookup incidents. Case creation remains unavailable in the policy editor. What prerequisite should be checked?
- Every host has an arbitrary text tag named case
- A real-time Group By was enabled for the incident search
- The rule has zero incident definitions
- Analyst Team and Case Management Policy are configured, and the action is at a supported scope
Explanation
Correct Answer
D:Under Automation Policy workflow at West Operations: FortiSIEM 7.2 automated case creation requires analyst teams and case policy configuration and is not available at the organization level. Those prerequisites govern this option.
Incorrect Answers
A:Host tags do not establish the required analyst team/assignment policy objects for case creation in West Operations.
B:For Automation Policy workflow at West Operations: Real-time Group By is unsupported and cannot register case management teams or resolve the policy editor prerequisite.
C:Considering Automation Policy workflow at West Operations: A valid incident-generating rule needs a defined incident; an empty definition would block rule save but does not establish case team configuration.
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.