Question 760
A historical firewall session logs search for asset host-72 is grouped by both Source IP and Destination IP. The matched data contains 6 distinct (Source IP, Destination IP) pairs even though there are only 3 unique Source IP values. How many result rows should grouping produce?
- 9 grouped rows
- 18 grouped rows
- 6 grouped rows
- 3 grouped rows
Explanation
Correct Answer
C:Considering aggregate-query calculation at the SOC for host-72 using firewall session logs: Each distinct combination of Source IP and Destination IP creates one group, so 6 key pairs yield 6 aggregate rows.
Incorrect Answers
A:In aggregate-query calculation at the SOC for host-72 using firewall session logs: Adding the two distinct counts double-counts category dimensions. A composite group key is based on observed pairs, not the sum of marginal counts.
B:For aggregate-query calculation at the SOC for host-72 using firewall session logs: A Cartesian product assumes every source-destination combination occurred. The query returns only 6 observed combinations.
D:Under aggregate-query calculation at the SOC for host-72 using firewall session logs: 3 counts unique values of Source IP alone; adding Destination IP can split each source across multiple results.
Question 761
Partner Services is correlating privileged.e suspicious login activity with a high-value host-64 object. What additional data should remain available to improve prioritization?
- Host criticality from CMDB together with relevant user-event context
- Replace the entity score with incident-list display ordering
- Only the number of characters in the hostname
- An inactive remediation script disconnected from the incident
Explanation
Correct Answer
A:In entity-behavior risk evaluation at Partner Services for host-64: Asset criticality increases the meaning of risky activity. Combining CMDB importance with user and host observations helps analysts prioritize the potentially impactful access.
Incorrect Answers
B:For entity-behavior risk evaluation at Partner Services for host-64: Sorting incidents can prioritize a screen view but cannot rebuild the normalized entity mapping or actual risk contributors.
C:Hostname length is an arbitrary string property and does not reflect the business importance of host-64.
D:An unused script does not enrich risk signals or explain the actual impact of an access attempt against host-64.
Question 762
Lookup table AssetOwners in Manufacturing has a numeric key, while the event field supplied by file integrity alerts is normalized as a string. Searches find no matching rows. What should be checked first?
- That a remediation script already ran for each event
- That the lookup key type and event expression use compatible data types
- That the incident has a high severity label
- That the analyst enabled a real-time Group By
Explanation
Correct Answer
B:The table schema requires typed keys. A numeric AssetOwners key cannot be reliably matched against a string-form file integrity alerts field without compatible typing or an appropriate conversion.
Incorrect Answers
A:In CMDB and lookup-table configuration at Manufacturing using file integrity alerts: Remediation occurs after incident logic and cannot repair the input data-type mismatch causing the lookup misses.
C:Severity does not coerce a string event attribute into the numeric key type expected by AssetOwners.
D:Under CMDB and lookup-table configuration at Manufacturing using file integrity alerts: Grouping changes how query results are summarized and is not a fix for a mismatched lookup key type.
Question 763
An incident rule at West Operations was built with a reasonable stopped service filter but produces no alerts after the test passed. The rule exists and evidence is arriving. Which lifecycle setting should the analyst verify?
- That the search result limit is at least one million
- That the incident PDF export completed yesterday
- That the tested rule is actually enabled for production processing
- That every event has an unusually long message string
Explanation
Correct Answer
C:Passing a test does not activate a rule. An inactive saved definition cannot generate live incidents from the incoming service health records stream.
Incorrect Answers
A:For An incident rule at West Operations was built with a reasonable stopped service filter but produces no alerts after the test: In rule deployment or exception at West Operations: Result-table size affects Analytics output, not whether an otherwise valid rule has been activated.
B:For An incident rule at West Operations was built with a reasonable stopped service filter but produces no alerts after the test: For rule deployment or exception at West Operations: Historical export jobs do not determine the active/inactive state of the live rule evaluator.
D:Message length is not a general prerequisite for triggering a valid stopped service correlation rule.
Question 764
A Research ML job repeatedly misses new daily unique destination counts samples because it has no recurring inference schedule. Which operational change addresses the gap?
- Keep rerunning an exported PDF manually as the schedule
- Disable every related incident rule permanently
- Change the Collector hostname to the affected user name
- Configure and enable an inference schedule for the supported job and input source
Explanation
Correct Answer
D:Scheduled inference processes new report-derived data on the selected cadence. The analyst should ensure report windows and prerequisites align with incoming daily unique destination counts telemetry.
Incorrect Answers
A:In machine-learning analysis at Research: A PDF is a presentation document, not a supported recurring inference input or scheduler for the model.
B:Disabling incident rules hides downstream symptoms but does not make the ML model process the new daily unique destination counts batches.
C:Considering machine-learning analysis at Research: Collector naming does not define when the trained model scores new feature values.
Question 765
For the response to an incident affecting host-21, an Logistics analyst confirms a sign-in incident and wants to execute a one-time approved remediation on a FortiGate firewall while supervising its effect. Which FortiSIEM workflow fits?
- Select the incident and initiate an ad hoc remediation action from Incidents
- Delete the original {kind} raw event records
- Attach a global automatic script to every rule without approval
- Only change the incident category to Remediated
Explanation
Correct Answer
A:In remediation operation at Logistics for host-21: FortiSIEM supports incident-specific manual/scripted remediation. The analyst can select the affected FortiGate firewall and validate the effect before repeating the action.
Incorrect Answers
B:For remediation operation at Logistics for host-21: Evidence deletion does not contain or recover the affected FortiGate firewall; it also weakens investigation and auditability.
C:Considering remediation operation at Logistics for host-21: Unrestricted automation would apply the action to unrelated incidents, conflicting with the explicitly supervised one-time Logistics response.
D:Under remediation operation at Logistics for host-21: Labels do not execute a device action; the FortiGate firewall would remain in its original state despite the category change.
Question 766
Lookup table CriticalServiceInventory in Corporate HQ has a numeric key, while the event field supplied by Windows security logs is normalized as a string. Searches find no matching rows. What should be checked first?
- That a remediation script already ran for each event
- That the incident has a high severity label
- That the analyst enabled a real-time Group By
- That the lookup key type and event expression use compatible data types
Explanation
Correct Answer
D:The table schema requires typed keys. A numeric CriticalServiceInventory key cannot be reliably matched against a string-form Windows security logs field without compatible typing or an appropriate conversion.
Incorrect Answers
A:In CMDB and lookup-table configuration at Corporate HQ using Windows security logs: Remediation occurs after incident logic and cannot repair the input data-type mismatch causing the lookup misses.
B:Severity does not coerce a string event attribute into the numeric key type expected by CriticalServiceInventory.
C:Considering CMDB and lookup-table configuration at Corporate HQ using Windows security logs: Grouping changes how query results are summarized and is not a fix for a mismatched lookup key type.
Question 767
A Corporate HQ correlation rule must operate per (Source IP, Destination Port) pair instead of per Source IP alone, because the same actor contacts several unrelated target systems. What change prevents cross-target aggregation?
- Group By both Source IP and Destination Port
- Remove all aggregate constraints
- Group By only Destination Port
- Group By only Source IP
Explanation
Correct Answer
A:A composite key partitions the evidence by actor-and-target combination, so separate Destination Port systems do not contribute to the same rule threshold.
Incorrect Answers
B:Without thresholds the rule cannot evaluate the intended per-pair connection frequency, regardless of the chosen grouping keys.
C:Considering subpattern correlation at Corporate HQ: This combines different attacking sources against one target and loses the required actor-specific relationship.
D:This still merges all Destination Port targets reached by that actor and can create a combined count unsupported by any single pair.
Question 768
For an audit of failed sign-in events in Windows security logs, North Finance must investigate activity from exactly 35 minutes ago and compute counts by Host. Which search design preserves that requirement?
- Real-time streaming search with Group By
- CMDB search with no event criteria
- Historical event search, time window, then Group By on the specified field
- Search only the raw event keyword without selecting a time range
Explanation
Correct Answer
C:Stored events can be bounded to the requested 35-minute historical interval, and grouping by Host summarizes the matching records for this audit.
Incorrect Answers
A:Streaming search is designed for arriving data and does not allow Group By; it cannot reliably reconstruct the 35-minute stored period.
B:Inventory records may identify devices but have no event-count dataset for Windows security logs and the requested Host grouping.
D:A keyword alone does not specify the 35-minute historical boundary or the grouped output that the audit requires.
Question 769
Logistics has correlated several blocked request incidents and related events into one investigation that should have an owner, workflow status, and associated evidence. Which FortiSIEM object is most appropriate?
- A case associated with the relevant incidents/events
- A free-text event keyword saved as a report
- An unrelated CMDB lookup key
- A notification severity threshold alone
Explanation
Correct Answer
A:Case management groups related incidents into an assigned work item with investigation ownership and progression, rather than treating every host-109 alert independently.
Incorrect Answers
B:A saved search can surface evidence but is not the managed case workflow with assignment and status for Logistics.
C:Considering incident-management case at Logistics: A lookup key helps enrichment but does not provide an investigator owner and lifecycle for the related incident cluster.
D:Under incident-management case at Logistics: A threshold may control alert delivery but cannot connect multiple findings into one assigned investigation.
Question 770
FortiSIEM returns individual web application alerts rows for East Retail; the analyst now wants a per-Source IP summary with aggregate values while retaining the same blocked request filter. Which portion of search configuration changes?
- Group By and Display Fields with the required aggregate expressions
- Replace the event search with a pure CMDB search
- Change the notification target of the associated rule
- Only switch raw logs to a different parser
Explanation
Correct Answer
A:Grouping creates one result per Source IP value and aggregated displays compute measures over matching blocked request events, without needing a new ingestion configuration.
Incorrect Answers
B:CMDB focuses on inventory attributes and cannot compute the requested event aggregates over the selected blocked request rows.
C:Considering historical or real-time event analysis at East Retail using web application alerts: Notification routing acts after incident detection and does not transform a search result into grouped aggregate output.
D:Parser configuration affects field normalization; it is not the way to summarize an already-correct web application alerts result set by Source IP.