Question 130
A Research analyst wants the event’s URI Path and Source IP values visible in a generated incident but notices only the incident category appears. Which editor area should be reviewed?
- Define Action and the incident’s Triggered Attributes mapping
- The lookup-table schema editor for unrelated enrichment
- Modify the case label without reviewing rule state or exceptions
- The FortiGate DHCP lease duration
Explanation
Correct Answer
A:Triggered Attributes controls which details from matching events are carried into the incident for dashboards and analysis, including Source IP and URI Path.
Incorrect Answers
B:For A Research analyst wants the event’s URI Path and Source IP values visible in a generated incident but notices only the: For rule deployment or exception at Research: Lookup tables can supply context, but the missing direct event fields are selected in the incident definition.
C:Considering rule deployment or exception at Research: Case metadata does not activate an inactive rule or correctly scope a rule exception for future event matches.
D:For A Research analyst wants the event’s URI Path and Source IP values visible in a generated incident but notices only the: Under rule deployment or exception at Research: DHCP duration does not determine which parsed attributes are copied into the FortiSIEM incident.
Question 131
A Logistics analyst needs an event-to-event nested search that finds stopped service records on host-83 only when the same Host appeared in a previously saved anomaly report. What establishes the relationship?
- Group by incident severity with no identity comparison
- Use the inner report name as a literal event keyword
- Compare the outer event Host field against the corresponding inner report Host column
- Compare outer event timestamp against inner Host as text
Explanation
Correct Answer
C:Matching the same typed entity attribute across the two event datasets performs the intended membership lookup for host-83.
Incorrect Answers
A:Grouping by severity changes how matches are summarized and fails to correlate host-83 events with the prior actor set.
B:For nested search comparison at Logistics for host-83: A report title is not the data returned by that report. Keyword matching cannot establish membership among suspicious Host entities.
D:Under nested search comparison at Logistics for host-83: Time and entity identity are different attribute types; the comparison would not indicate whether the same Host was observed.
Question 132
Manufacturing wants notifications for LOW suspicious launch incidents, but not for incidents of other severities from the same rule. Which automation-policy criterion should be set?
- A larger Analytics result-row limit
- Severity selection matching LOW
- Changing the reporting device hostname
- An unqualified selection of all incident categories
Explanation
Correct Answer
B:For Automation Policy workflow at Manufacturing: The policy can select one or more incident severities. Restricting it to LOW controls delivery without altering the rule’s triggering conditions.
Incorrect Answers
A:For Manufacturing wants notifications for LOW suspicious launch incidents, but not for incidents of other severities from the: In Automation Policy workflow at Manufacturing: Query row limits affect display, not whether the Automation Policy sends an alert based on severity.
C:Considering Automation Policy workflow at Manufacturing: Device identity changes are unrelated to choosing which severity values qualify for notification.
D:Under Automation Policy workflow at Manufacturing: Categories alone do not enforce the required LOW boundary; other-severity alerts may still notify.
Question 133
After Partner Services deploys lookup table ApprovedPrivilegedUsers, the owner realizes that the schema needs another criticality key and wants to revise the original structure in place. What limitation controls the next step?
- Changing the data rows automatically changes key definitions
- A created lookup table schema cannot be modified in place
- Every analytic search rewrites the table schema on its next run
- A notification policy can append a key field to the schema
Explanation
Correct Answer
B:FortiSIEM documents the schema as immutable after table creation. The ApprovedPrivilegedUsers design must therefore be planned before deployment; the owner needs an appropriate replacement or rebuild strategy.
Incorrect Answers
A:Editing or importing records changes lookup contents, not the key/column schema of the existing ApprovedPrivilegedUsers.
C:Queries read lookup data but do not redeclare how criticality is typed or keyed in Resources.
D:Under CMDB and lookup-table configuration at Partner Services: Notification automation controls post-incident actions and has no role in changing existing table schema definitions.
Question 134
FortiSIEM has three CPU utilization samples for host-17 in Research: 30%, 40%, and 30%. The rule should compare mean utilization across samples. Which search expression evaluates the required statistic?
- SUM(CPU Util)
- MAX(CPU Util)
- COUNT(Matched Events)
- AVG(CPU Util)
Explanation
Correct Answer
D:AVG calculates the arithmetic mean: (30 + 40 + 30) / 3 = 33.3%. This matches the average-utilization objective for host-17.
Incorrect Answers
A:In aggregate-query calculation at Research for host-17: SUM adds the sample percentages to 100; the total is not mean utilization and would distort a percentage threshold.
B:For aggregate-query calculation at Research for host-17: MAX returns 40%, the single highest observation. A transient spike can exceed the mean, so it does not characterize all three samples.
C:Considering aggregate-query calculation at Research for host-17: COUNT reports the three matching samples, not their CPU utilization values. It would test frequency rather than the requested load measure.
Question 135
A West Operations ML job repeatedly misses new nightly database write rate samples because it has no recurring inference schedule. Which operational change addresses the gap?
- Change the Collector hostname to the affected user name
- Configure and enable an inference schedule for the supported job and input source
- Keep rerunning an exported PDF manually as the schedule
- Disable every related incident rule permanently
Explanation
Correct Answer
B:Scheduled inference processes new report-derived data on the selected cadence. The analyst should ensure report windows and prerequisites align with incoming nightly database write rate telemetry.
Incorrect Answers
A:In machine-learning analysis at West Operations: Collector naming does not define when the trained model scores new feature values.
C:Considering machine-learning analysis at West Operations: A PDF is a presentation document, not a supported recurring inference input or scheduler for the model.
D:Disabling incident rules hides downstream symptoms but does not make the ML model process the new nightly database write rate batches.
Question 136
East Retail tests a rule on blocked lookup records and finds its COUNT threshold reached by separate sources combined together. The goal is one threshold per Source IP. Where in the rule is the fix made?
- Rename the subpattern with a unique suffix only
- Add the Source IP event attribute to that subpattern’s Group By
- Export the last incident report as PDF
- Set the incident notification recipient to the security team
Explanation
Correct Answer
B:The per-source group key splits the matched DNS resolution records stream before COUNT evaluation, preventing unrelated sources from jointly meeting the threshold.
Incorrect Answers
A:In subpattern correlation at East Retail: A name adjustment does not introduce the missing per-Source IP aggregation boundary that caused the false trigger.
C:Reporting preserves evidence but leaves the correlation rule’s global aggregate unchanged for future blocked lookup matches.
D:Under subpattern correlation at East Retail: Routing the alert is useful operationally but cannot change how matched Source IP values are counted.
Question 137
Corporate HQ is correlating contractor.r suspicious login activity with a high-value host-131 object. What additional data should remain available to improve prioritization?
- Use only event timestamp as the user/entity correlation key
- Host criticality from CMDB together with relevant user-event context
- Only the number of characters in the hostname
- An inactive remediation script disconnected from the incident
Explanation
Correct Answer
B:For entity-behavior risk evaluation at Corporate HQ for host-131: 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
A:In entity-behavior risk evaluation at Corporate HQ for host-131: Timestamps cannot establish stable identity across VPN, identity-provider and other event sources for a UEBA investigation.
C:Hostname length is an arbitrary string property and does not reflect the business importance of host-131.
D:An unused script does not enrich risk signals or explain the actual impact of an access attempt against host-131.
Question 138
In City Branch, an investigator wants to repeat the same blocked request filter over web application alerts next week without reconstructing the search. Which operation captures the query as a reusable analytic artifact?
- Save the working search definition as a report
- Export one row without saving any definition
- Clear the open incident generated by a different rule
- Modify the data collector polling interval
Explanation
Correct Answer
A:Saving the query definition preserves its selected filter and display logic for reuse on future web application alerts investigations; time can be adjusted when run.
Incorrect Answers
B:For historical or real-time event analysis at City Branch using web application alerts: A row export is evidence from one run; it does not retain reusable filters and aggregation choices for the next week.
C:Clearing changes incident lifecycle state; it does not persist the analysis query for future blocked request searches.
D:Under historical or real-time event analysis at City Branch using web application alerts: Collection rate controls incoming monitoring data rather than the stored search definition the investigator wants to reuse.
Question 139
For the response to an incident affecting host-197, the Research remediation framework has a target Windows server in CMDB and valid credentials, but the chosen Collector cannot reach the management interface. Which dependency explains the failure?
- Use a report-generated value as the Enforce On endpoint without a CMDB device definition
- Every event must contain an email address before remediation
- Run On must have the required access-protocol connectivity to Enforce On
- Only the incident export format affects remote script execution
Explanation
Correct Answer
C:Considering inventory or lookup query at Research for host-197: FortiSIEM transfers the action to the execution node, which then connects to the target Windows server using the specified management protocol. Routing and reachability matter.
Incorrect Answers
A:In inventory or lookup query at Research for host-197: An event attribute does not replace the managed device identity used by FortiSIEM remediation to select a target.
B:For inventory or lookup query at Research for host-197: Email contacts are for notification and do not establish the network path required for the Windows server protocol.
D:Under inventory or lookup query at Research for host-197: PDF versus CSV selection cannot establish the missing management route from the Collector to the device.
Question 140
In East Retail, a stored search matches 9 policy denial records from proxy access records, including only 5 unique Destination Domain values for host-41. To measure unique targets rather than raw volume, which aggregate is required?
- SUM(Destination Domain)
- AVG(Destination Domain)
- COUNT(DISTINCT Destination Domain)
- COUNT(Matched Events)
Explanation
Correct Answer
C:This removes repeated Destination Domain values before counting. For host-41, the expected unique-target measure is 5 rather than the 9 event rows.
Incorrect Answers
A:In aggregate-query calculation at East Retail for host-41 using proxy access records: SUM is intended for numeric measures and is not a meaningful distinct-count function for the Destination Domain identity field in these proxy access records records.
B:For aggregate-query calculation at East Retail for host-41 using proxy access records: An average of an identifier would not quantify unique Destination Domain values, even if the attribute happened to be encoded numerically.
D:Under aggregate-query calculation at East Retail for host-41 using proxy access records: This produces 9 because each qualifying event contributes one row. It cannot distinguish repeat connections to a target from a new Destination Domain.