Question 800
Partner Services knows a legitimate scheduled scanner will produce connection events on host-193 during a maintenance window. The detection should remain active for all other assets and times. Which rule feature targets the exception?
- Disable the entire rule permanently
- Delete the parser for the log source
- Change the incident severity to low with no exception
- A rule exception constrained by relevant attributes and an effective period
Explanation
Correct Answer
D:Rule exceptions suppress incidents for matching host-193 conditions during a defined single or recurring interval, preserving detection elsewhere.
Incorrect Answers
A:Global disablement discards all connection detections beyond the approved host-193 maintenance exception.
B:For correlation-rule investigation at Partner Services for host-193: Removing event parsing would harm all observations from network flow records and is not a precise, time-bound exception.
C:Considering correlation-rule investigation at Partner Services for host-193: Lowering priority still creates incidents for the expected scan and does not delimit the approved maintenance period.
Question 801
A recurring connection incident in Manufacturing is a known maintenance false positive at host-31, but other devices might legitimately trigger. What is the most targeted longer-term action?
- Permanently disable the entire class of incident for every tenant
- Manually mark all future matches as False Positive without examination
- Remove the raw event source for the organization
- Tune the triggering rule or create a scoped exception for the known benign condition
Explanation
Correct Answer
D:Filtering the precise host-31 signature or its maintenance time reduces repeat noise while preserving visibility for genuine connection events elsewhere.
Incorrect Answers
A:Global suppression would hide true incidents unrelated to the verified host-31 maintenance exception.
B:For incident-management case at Manufacturing for host-31: The meaning of a later connection event can change; bulk preclassification bypasses necessary evidence review.
C:Considering incident-management case at Manufacturing for host-31: Loss of network flow records telemetry destroys valuable investigation evidence and prevents other related detections.
Question 802
City Branch sees analyst.g with multiple high-severity suspicious sign-ins and access to a critical host. Why is entity risk more informative than raw alert count alone?
- Risk can incorporate event severity, rarity and affected asset criticality
- A high alert count automatically proves every event is malicious
- Entity risk is only a cosmetic dashboard color
- Risk must equal the exact number of normalized source IP values
Explanation
Correct Answer
A:In entity-behavior risk evaluation at City Branch: 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
B:For entity-behavior risk evaluation at City Branch: False positives, benign bursts and asset context require triage; volume alone does not provide that certainty.
C:Considering entity-behavior risk evaluation at City Branch: Risk information supports investigation and prioritization, not merely display choices in a widget.
D:Unique IP cardinality can be an input to a rule, but it is not the complete definition of UEBA risk for analyst.g.
Question 803
A rejected request incident on host-110 at West Operations represented a real outage. After repair, the analyst manually clears it and records evidence. Which combination reflects that history?
- Resolution None; Status Active
- Resolution False Positive; Status Manually Cleared
- Resolution True Positive; Status System Cleared
- Resolution True Positive; Status Manually Cleared
Explanation
Correct Answer
D:Under incident-management case at West Operations for host-110: An actual rejected request issue merits a true-positive verdict, and human closure after verified repair results in the manually cleared lifecycle state.
Incorrect Answers
A:In incident-management case at West Operations for host-110: The incident has already been judged and closed; leaving it active with no verdict misrepresents the completed West Operations response.
B:False Positive would describe a benign or incorrect detection, contradicting the confirmed real incident on host-110.
C:Considering incident-management case at West Operations for host-110: System Cleared indicates an automated clear condition, not the manual verification and closure described here.
Question 804
Logistics needs rejected request events from cloud API audit events only when their device belongs to a CMDB list of critical host-37-class systems. Which nested search direction retains the event details?
- A real-time stream with Group By turned on
- Outer CMDB query using an inner event query exclusively
- Two incident notifications whose messages have the same subject
- Outer event query referencing an inner CMDB query
Explanation
Correct Answer
D:The outer dataset remains the event evidence. The inner CMDB report contributes the list of critical devices used to include or exclude rejected request rows.
Incorrect Answers
A:Real-time grouping is not supported and would not preserve the historical rejected request records selected by CMDB membership.
B:That would produce devices as rows and cannot by itself display the full outer cloud API audit events event details requested.
C:Considering nested search comparison at Logistics for host-37 using cloud API audit events: Notification emails do not establish a typed membership comparison between CMDB devices and event attributes.
Question 805
A Partner Services analyst needs an event-to-event nested search that finds policy violation records on host-182 only when the same Source IP appeared in a previously saved anomaly report. What establishes the relationship?
- Use the inner report name as a literal event keyword
- Compare the outer event Source IP field against the corresponding inner report Source IP column
- Group by incident severity with no identity comparison
- Compare outer event timestamp against inner Source IP as text
Explanation
Correct Answer
B:Matching the same typed entity attribute across the two event datasets performs the intended membership lookup for host-182.
Incorrect Answers
A:In nested search comparison at Partner Services for host-182: A report title is not the data returned by that report. Keyword matching cannot establish membership among suspicious Source IP entities.
C:Grouping by severity changes how matches are summarized and fails to correlate host-182 events with the prior actor set.
D:Under nested search comparison at Partner Services for host-182: Time and entity identity are different attribute types; the comparison would not indicate whether the same Source IP was observed.
Question 806
Corporate HQ added 198.51.100.31 to a FortiSIEM watchlist used for remote desktop service protection, but the FortiGate IP External Connector shows no items. What is the first integration check?
- Configure a FortiGate deny rule that never references the imported dynamic address object
- Verify the external feed URL, authentication/reachability and watchlist API response
- Assign an unrelated UEBA user alias
- Remove all IP addresses from the watchlist
Explanation
Correct Answer
B:For IP feed and FortiGate enforcement at Corporate HQ with the specified 198.51 value: FortiGate must retrieve the IP list exposed by FortiSIEM. Confirm the connector points to the correct watchlist and can reach and parse its feed before debugging firewall rules.
Incorrect Answers
A:In IP feed and FortiGate enforcement at Corporate HQ with the specified 198.51 value: A rule without the feed-backed source object may not match the newly risky IPs learned by FortiSIEM.
C:Considering IP feed and FortiGate enforcement at Corporate HQ with the specified 198.51 value: Identity alias changes do not test whether FortiGate successfully retrieves an external IPv4 feed.
D:Deleting 198.51.100.31 ensures there will be no feed content and does not repair the connector URL or access path.
Question 807
The outer search in Logistics examines DNS resolution records from the last 90 minutes, but the list of Source IP values must come from the preceding day. Where is the inner report interval controlled?
- Assume the outer Time Range automatically defines every inner report interval
- Set Nested Time Range for the selected inner report separately from the outer range
- Reduce the lookup-table schema key count to one
- Change the Group By field to elapsed time
Explanation
Correct Answer
B:Nested searches distinguish the outer query window from the inner report time window. This lets the actor list cover the preceding day while the visible DNS resolution records evidence covers 90 minutes.
Incorrect Answers
A:Using the outer 90-minute window for both datasets would omit actors observed earlier in the day.
C:Considering nested search comparison at Logistics using DNS resolution records with the specified 90 value: Lookup keys do not control how long an inner event report runs in this nested search.
D:Under nested search comparison at Logistics using DNS resolution records with the specified 90 value: Grouping alters result summaries and does not independently schedule the time horizon for the inner Source IP report.
Question 808
An investigator at East Retail wants to inspect the blocked request incidents affecting host-130, change one alert severity, and add a triage comment. Which interface is intended for those analyst actions?
- A raw log parser rule with no incident reference
- Only the Resources lookup-table schema screen
- Incidents List View and its Actions menu
- The FortiSIEM software update installer
Explanation
Correct Answer
C:List View supports filtering incident records, changing severity, editing information, and incident lifecycle actions; it keeps host-130 triage attached to the alert.
Incorrect Answers
A:In incident-management case at East Retail for host-130: Parsers normalize event data but cannot substitute for the analyst’s incident-level review and annotation controls.
B:Lookup tables hold enrichment data, not the incident workflow operations required to review and comment on the blocked request alert.
D:Upgrading the platform does not provide the incident-specific severity and comment operations for an active host-130 case.
Question 809
At Cloud Services, a built-in FortiSIEM ML job template is visible for daily unique destination counts. The team assumes the template alone will produce valid scores. What must occur first?
- Configure the relevant data source and train a usable model
- Delete the historical event database
- Create an unrelated ZTNA firewall policy
- Rename the template to the incident severity value
Explanation
Correct Answer
A:A job template provides a starting definition, not a trained statistical baseline. The Cloud Services dataset and training results must support subsequent inference.
Incorrect Answers
B:For machine-learning analysis at Cloud Services: Historical observations are normally necessary for establishing the behavior the ML job will learn.
C:External network enforcement does not build a trained model for the daily unique destination counts feature.
D:A cosmetic name change neither supplies daily unique destination counts samples nor fits model parameters.
Question 810
An analyst at West Operations is watching newly arriving SSH audit logs for failed login on host-133; the requirement is to see records as they are ingested, with no grouping. Which FortiSIEM search approach fits?
- Run only a historical search against an earlier time interval
- Run a CMDB device search for host-133 as the sole data source
- Use a real-time search with a Group By aggregation
- Use a real-time search with a normalized event-attribute filter
Explanation
Correct Answer
D:Real-time search evaluates incoming events in the streaming path. A condition on the normalized failed login indicator can expose matching records on host-133 without retrieving stored history.
Incorrect Answers
A:Historical searches read events already persisted in the database. This misses the requirement to observe newly arriving SSH audit logs as ingestion occurs.
B:CMDB is inventory and configuration data, not the live stream of SSH audit logs needed to inspect failed login evidence.
C:Considering historical or real-time event analysis at West Operations for host-133 using SSH audit logs: FortiSIEM real-time search does not support Group By. Here the desired output is raw incoming events, not aggregate group counts.