Question 740
An incident analyst must calculate total outbound byte volume for a User group in database audit records. The three matched records carry 480, 650, and 360 sent bytes. Which aggregator belongs in the query?
- MIN(Sent Bytes)
- COUNT(DISTINCT Sent Bytes)
- SUM(Sent Bytes)
- AVG(Sent Bytes)
Explanation
Correct Answer
C:SUM adds event-measured byte quantities, producing 1490 bytes for the selected User. This measures total transferred volume rather than the number of rows.
Incorrect Answers
A:In aggregate-query calculation at the SOC using database audit records with the specified 480 value: MIN yields only 360 bytes, the smallest observed transfer; it excludes the other two contributions.
B:For the measured records containing 480, 650, and 360 sent bytes: For aggregate-query calculation at the SOC using database audit records with the specified 480 value: Counting unique numeric byte values asks how many different sizes appeared, not how much traffic crossed the link for North Finance.
D:Under aggregate-query calculation at the SOC using database audit records with the specified 480 value: AVG yields 496.7 bytes per record; it is useful for average transfer size but understates the requested combined volume.
Question 741
A query in Manufacturing correctly selects CMDB devices with service group=production, but the output must also show owner and location fields for triage. What should be added to the CMDB search?
- A manual-clear action on every displayed device
- A subpattern FOLLOWED-BY relationship between owner and location
- An event-count threshold to suppress all devices with no recent logs
- Relevant CMDB attributes as display fields
Explanation
Correct Answer
D:Display selections expose owner and location for the already-matched inventory objects without changing the service group=production predicate.
Incorrect Answers
A:Manually clearing incidents is an independent workflow and does not add the requested inventory columns to Manufacturing output.
B:For CMDB and lookup-table configuration at Manufacturing: Temporal rule operators relate event patterns, not static owner and location columns in a device inventory query.
C:Considering CMDB and lookup-table configuration at Manufacturing: Filtering by event count changes the population and may remove quiet production assets that still belong in the requested CMDB list.
Question 742
A West Operations report groups policy denial events by User and uses COUNT(Matched Events). The analyst wants only groups exceeding 7 events to remain in the result, not to remove the underlying records before aggregation. What should be configured?
- A Display Condition of COUNT(Matched Events) > 7
- A time range of exactly 7 seconds
- Group By COUNT(Matched Events) instead of User
- An event filter that rejects all records until their count exceeds 7
Explanation
Correct Answer
A:In aggregate-query calculation at West Operations with the specified 7 value: FortiSIEM display conditions filter aggregates after grouping, analogous to HAVING. Groups must first be counted, then those above 7 remain visible.
Incorrect Answers
B:For aggregate-query calculation at West Operations with the specified 7 value: The literal threshold is a count of records, not a query time window. Shortening time would alter which policy denial events are included.
C:Considering aggregate-query calculation at West Operations with the specified 7 value: COUNT is the measure to test, while User defines the groups whose counts are compared; swapping these loses the per-source view.
D:Under aggregate-query calculation at West Operations with the specified 7 value: An event filter evaluates record attributes before aggregation. Individual proxy access records events do not carry the completed group count to filter on.
Question 743
The Manufacturing team tests a new failed sign-in rule. It triggers on a documented false positive generated by host-194 at normal business hours. Which correction preserves coverage while reducing repeat noise?
- Remove the event data source from FortiSIEM for every device
- Always mark every later incident from the rule false positive
- Change the case-assignment queue without modifying event logic
- Narrow the event filters, group logic, or applicable exception based on the false-positive evidence
Explanation
Correct Answer
D:Rule tuning should target the characteristic that distinguished this benign host-194 event from malicious failed sign-in behavior rather than discarding the entire detector.
Incorrect Answers
A:In rule deployment or exception at Manufacturing for host-194: Loss of visibility would suppress valid detections across Manufacturing, not only the verified benign event pattern.
B:For rule deployment or exception at Manufacturing for host-194: Future matches may represent a true attack. Automatic blanket false-positive classification is not a precise correlation correction.
C:Considering rule deployment or exception at Manufacturing for host-194: Reassigning incidents affects workflow ownership but leaves the original high-noise rule conditions intact.
Question 744
An MSSP analyst is authorized to inspect Logistics only. A query for failed login events from SSH audit logs unexpectedly includes tenant peers. Which search setting should be restricted?
- Group the mixed result by Source IP
- Increase the maximum rows returned by the search
- Select the intended organization in the service-provider search scope
- Add a display column showing the event time
Explanation
Correct Answer
C:FortiSIEM service-provider searches support organization selection. Constraining scope to Logistics prevents the query from including the other tenants’ event sets.
Incorrect Answers
A:Grouping by Source IP reorganizes the already selected records and does not enforce the organizational boundary for Logistics.
B:Row limits affect truncation, not data tenancy; a higher limit would reveal more mixed-tenant events instead of isolating Logistics.
D:Under historical or real-time event analysis at Logistics using SSH audit logs: Event timestamps assist investigation but do not replace the search’s organization selection when isolating one customer.
Question 745
Cloud Services wants an active unauthorized change incident on host-63 to clear after the original rule has not triggered for 10 minutes. The rule is a real-time rule. Which clear-condition option fits?
- Increase notification frequency to one message per minute
- Original Rule Does Not Trigger with a 10-minute clear period
- Change the incident title to Resolved but leave status Active
- Exception effective for 10 minutes starting now
Explanation
Correct Answer
B:For rule deployment or exception at Cloud Services for host-63: The clear timer waits for the specified duration without another rule match, then changes the incident state when the condition is satisfied.
Incorrect Answers
A:In rule deployment or exception at Cloud Services for host-63: Notification cadence affects delivery only; it cannot use quiet time to clear the incident.
C:Renaming an incident is not a status transition and provides no test of whether unauthorized change stopped.
D:An exception suppresses future matching incidents; it is not equivalent to clearing an already-active host-63 alert after inactivity.
Question 746
The Research SOC should receive failed authentication alerts only during its shift beginning at 21:00. Other conditions are correct. Which policy dimension controls when notifications are sent?
- The CMDB display-column ordering
- The Automation Policy Time Range
- The report Trend Interval
- The incident’s raw message length
Explanation
Correct Answer
B:FortiSIEM evaluates the policy’s effective notification window, so matching failed authentication incidents outside the configured Research shift need not trigger this action.
Incorrect Answers
A:In Automation Policy workflow at Research with the specified 21 value: Changing inventory columns does not define an Automation Policy time schedule for notifications.
C:Considering Automation Policy workflow at Research with the specified 21 value: A query trend interval changes how historical events are bucketed and cannot schedule when incident notifications should be delivered.
D:Under Automation Policy workflow at Research with the specified 21 value: Number of bytes in a raw VPN authentication records record does not encode the analyst team’s effective working hours.
Question 747
For the response to an incident affecting host-98, north Finance wants to customize a validated remediation script for quarantine a suspicious connection on a Linux server. Where are built-in and user-created remediation resources maintained?
- The Incident Resolution dropdown
- Resources > Remediations
- The CMDB user alias table
- Only the Analytics Group By editor
Explanation
Correct Answer
B:For remediation operation at the SOC for host-98: FortiSIEM includes remediation scripts in its Resources area and supports creating new remediation definitions there. A vetted script can be selected for later incident execution.
Incorrect Answers
A:In remediation operation at the SOC for host-98: Resolution captures true/false positive verdicts rather than the script body and execution parameters for Linux server.
C:Considering remediation operation at the SOC for host-98: User aliases help identity/risk relationships and are not the library where management-device remediation scripts are defined.
D:Under remediation operation at the SOC for host-98: The search editor aggregates event data, not the stored script resource used to enforce quarantine a suspicious connection.
Question 748
Cloud Services added 198.51.100.19 to a FortiSIEM watchlist used for corporate VPN 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
- Assign an unrelated UEBA user alias
- Remove all IP addresses from the watchlist
- Verify the external feed URL, authentication/reachability and watchlist API response
Explanation
Correct Answer
D:Under IP feed and FortiGate enforcement at Cloud Services 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 Cloud Services with the specified 198.51 value: A rule without the feed-backed source object may not match the newly risky IPs learned by FortiSIEM.
B:For IP feed and FortiGate enforcement at Cloud Services with the specified 198.51 value: Identity alias changes do not test whether FortiGate successfully retrieves an external IPv4 feed.
C:Deleting 198.51.100.19 ensures there will be no feed content and does not repair the connector URL or access path.
Question 749
For the response to an incident affecting host-144, north Finance wants to customize a validated remediation script for quarantine a suspicious connection on a Linux server. Where are built-in and user-created remediation resources maintained?
- The Incident Resolution dropdown
- Only the Analytics Group By editor
- The CMDB user alias table
- Resources > Remediations
Explanation
Correct Answer
D:Under remediation operation at the SOC for host-144: FortiSIEM includes remediation scripts in its Resources area and supports creating new remediation definitions there. A vetted script can be selected for later incident execution.
Incorrect Answers
A:In remediation operation at the SOC for host-144: Resolution captures true/false positive verdicts rather than the script body and execution parameters for Linux server.
B:For remediation operation at the SOC for host-144: The search editor aggregates event data, not the stored script resource used to enforce quarantine a suspicious connection.
C:Considering remediation operation at the SOC for host-144: User aliases help identity/risk relationships and are not the library where management-device remediation scripts are defined.
Question 750
An analyst wants separate incidents when the same connection burst arises from different Source IP values in Manufacturing. Which subpattern component separates the candidate event populations?
- Configure an outbound email recipient for each log entry
- Set a higher incident title priority
- Use no Group By and count all events globally
- Group By the Source IP event attribute
Explanation
Correct Answer
D:Under correlation-rule investigation at Manufacturing: Grouping partitions matching records by their Source IP value before applying the rule threshold. This preserves per-actor detection rather than merging every network flow records event.
Incorrect Answers
A:In correlation-rule investigation at Manufacturing: Alert recipients do not control the correlation grouping key or the incident identity.
B:For correlation-rule investigation at Manufacturing: Title wording cannot partition events from different Source IP entities during subpattern evaluation.
C:Considering correlation-rule investigation at Manufacturing: A global count allows small bursts from unrelated sources to accumulate into a single trigger, losing the per-Source IP boundary.