Question 80
An incident analyst must calculate total outbound byte volume for a Sender IP group in email security events. The three matched records carry 480, 650, and 720 sent bytes. Which aggregator belongs in the query?
- SUM(Sent Bytes)
- MIN(Sent Bytes)
- COUNT(DISTINCT Sent Bytes)
- AVG(Sent Bytes)
Explanation
Correct Answer
A:SUM adds event-measured byte quantities, producing 1850 bytes for the selected Sender IP. This measures total transferred volume rather than the number of rows.
Incorrect Answers
B:For aggregate-query calculation at the SOC using email security events with the specified 480 value: MIN yields only 480 bytes, the smallest observed transfer; it excludes the other two contributions.
C:Considering aggregate-query calculation at the SOC using email security events 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 email security events with the specified 480 value: AVG yields 616.7 bytes per record; it is useful for average transfer size but understates the requested combined volume.
Question 81
The City Branch performance report for host-14 and peer systems needs hosts whose average CPU is at least 30% AND whose average memory utilization is at least 35%. How should FortiSIEM limit the aggregate output?
- Use AVG(CPU Util) >= 30 AND AVG(Memory Util) >= 35 as Display Conditions
- Use event keywords CPU and Memory with no aggregation
- Use OR between the two aggregate thresholds
- Group only by event timestamp and discard host identity
Explanation
Correct Answer
A:In aggregate-query calculation at City Branch for host-14: Both threshold tests run against aggregate values for each host after grouping. The conjunction excludes hosts that exceed only one of the two measures.
Incorrect Answers
B:For aggregate-query calculation at City Branch for host-14: Keywords do not compute per-host averages; individual messages do not prove that either mean crosses the specified limits.
C:Considering aggregate-query calculation at City Branch for host-14: An OR permits a host with only high CPU or only high memory, contrary to the two simultaneous City Branch requirements.
D:Under aggregate-query calculation at City Branch for host-14: Timestamp buckets cannot establish which host breached both mean-utilization thresholds, which is central to this performance report.
Question 82
A FortiSIEM correlation design at Manufacturing observes P1 (unauthorized change in file integrity alerts) and P2 (a related action on host-96). It must require P1 present and no subsequent P2 in the rule window. Which relationship operator best expresses that precise condition?
- OR
- FOLLOWED-BY
- AND
- AND-NOT
- NOT-FOLLOWED-BY
Explanation
Correct Answer
E:In subpattern correlation at Manufacturing for host-96 using file integrity alerts: NOT-FOLLOWED-BY requires P1 and no P2 afterward in the evaluated rule period. It tests lack of follow-up, distinct from unordered AND-NOT.
Incorrect Answers
A:In subpattern correlation at Manufacturing for host-96 using file integrity alerts: OR permits either P1 or P2 to satisfy the rule. It is suited to alternative signals, not a requirement that both occur or that a later stage be missing.
B:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-96 rather than unordered coincidence.
C:Considering subpattern correlation at Manufacturing for host-96 using file integrity alerts: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended Manufacturing test.
D:Under subpattern correlation at Manufacturing for host-96 using file integrity alerts: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the Manufacturing event sequence.
Question 83
While reviewing identity provider events at Research, the analyst wants to remove results for a known maintenance account but keep the remaining sign-in events in the same time window. What is the most direct query adjustment?
- Add an exclusion condition to the event filter for the maintenance identity
- Change Group By to the reporting host alone
- Increase the trend interval
- Hide the identity column in Display Fields
Explanation
Correct Answer
A:The event filter determines which records qualify. An explicit NOT/equivalent exclusion removes the maintenance identity while retaining the original period for identity provider events.
Incorrect Answers
B:For historical or real-time event analysis at Research using identity provider events: Grouping on the reporting host can conceal who generated an event but will not eliminate maintenance-account data from matching records.
C:Trend granularity influences time-based summaries; it does not exclude the known account’s sign-in events.
D:Under historical or real-time event analysis at Research using identity provider events: Removing a column changes visibility only; matching maintenance-account events still contribute to the result set and any aggregates.
Question 84
For the response to an incident affecting host-198, a script for blocked request in East Retail is dispatched from one FortiSIEM node to change state on a FortiEDR appliance. Which term identifies the node that LAUNCHES the script?
- Group By Key
- Run On Device
- Enforce On Device
- Incident Resolution
Explanation
Correct Answer
B:For incident-management case at East Retail for host-198: The Run On device is the FortiSIEM node, such as a Collector, from which the script is launched. It must have management-protocol reachability to the target.
Incorrect Answers
A:In incident-management case at East Retail for host-198: A grouping attribute partitions event data and is not a runtime location for the script that performs apply a temporary deny rule.
C:Considering incident-management case at East Retail for host-198: Enforce On identifies the target where the remediation takes effect, such as the FortiEDR appliance, not necessarily the FortiSIEM node executing the script.
D:Under incident-management case at East Retail for host-198: Resolution is the analyst verdict about a finding; it does not identify the script-execution host in the remediation architecture.
Question 85
For a failed sign-in incident in Manufacturing, the analyst wants to record findings that a responder can read without falsely treating the alert as resolved. Which incident operation is suitable?
- Add an incident comment or remediation advice while preserving current status
- Set False Positive and clear every incident sharing the category
- Raise the global rule count threshold as a substitute for notes
- Delete the device from CMDB so the incident loses context
Explanation
Correct Answer
A:FortiSIEM supports comments on incident records and remediation notes in rules. Documentation helps responders act on host-77 without prematurely clearing the live alert.
Incorrect Answers
B:For incident-management case at Manufacturing: This asserts a benign verdict and changes lifecycle state for alerts that may still represent genuine failed sign-in activity.
C:Considering incident-management case at Manufacturing: Changing detection conditions alters future alerts, not the investigation narrative that a responder needs now.
D:Under incident-management case at Manufacturing: Removing an inventory object discards relevant asset information and does not constitute safe analyst documentation.
Question 86
City Branch wants an agentless FortiSIEM-to-FortiGate risk exchange for 198.51.100.20, and someone claims endpoint software must always be installed before any such IP-based connector can work. What is the accurate response?
- Agentless means traffic must bypass all security inspection
- An IP-feed exchange can operate agentlessly, subject to FortiGate policy and the integration’s own prerequisites
- Agentless means FortiGate needs no configured enforcement policy
- Every IP watchlist item must be delivered by a client agent
Explanation
Correct Answer
B:The documented approach uses FortiSIEM analytics/watchlists and a FortiGate feed connector. It does not inherently require deploying an endpoint agent solely to transfer 198.51.100.20.
Incorrect Answers
A:In IP feed and FortiGate enforcement at City Branch with the specified 198.51 value: The term describes how risk intelligence is exchanged; it does not remove the requirement for normal traffic inspection and access control.
C:Considering IP feed and FortiGate enforcement at City Branch with the specified 198.51 value: Even with agentless indicator sharing, the firewall still needs policies that act on the imported address object.
D:Under IP feed and FortiGate enforcement at City Branch with the specified 198.51 value: FortiGate can retrieve a network-accessible IP indicator feed, so client-agent delivery is not the only mechanism.
Question 87
Partner Services creates lookup table CriticalServiceInventory to enrich failed sign-in events. The schema currently needs 4 key field(s), and all fields are valid scalar lookup types. Which design constraint must be kept in mind?
- Treat all lookup columns as keys with no limit
- Create a separate incident for every schema column before saving
- Select a real-time Group By to declare lookup keys
- Use no more than five key fields in the lookup table schema
Explanation
Correct Answer
D:Under CMDB and lookup-table configuration at Partner Services with the specified 4 value: FortiSIEM 7.2 permits up to five lookup-table key values. The proposed 4 keys fit, but a sixth key would exceed that limit.
Incorrect Answers
A:FortiSIEM explicitly limits key count; indiscriminately converting the columns in CriticalServiceInventory to keys can violate the schema design.
B:For CMDB and lookup-table configuration at Partner Services with the specified 4 value: Lookup schema creation is independent of incident generation; columns are metadata used for event lookups, not incident definitions.
C:Group By describes aggregation output, whereas lookup keys are defined when the CriticalServiceInventory schema is created in Resources.
Question 88
After investigating a permission failure alert from database audit records at Partner Services, the analyst confirms a harmless authorized action and manually closes the alert with a reason. What resolution should be recorded?
- None with Active status indefinitely
- True Positive with Active status after marking it harmless
- True Positive with System Cleared status
- False Positive with Manually Cleared status
Explanation
Correct Answer
D:Under historical or real-time event analysis at Partner Services using database audit records: The event matched detection logic but did not represent the targeted threat. Recording False Positive and manually clearing documents the verified benign permission failure cause.
Incorrect Answers
A:In historical or real-time event analysis at Partner Services using database audit records: Leaving the incident unresolved obscures the completed triage decision and keeps the reviewed permission failure alert open.
B:For historical or real-time event analysis at Partner Services using database audit records: A true-positive verdict contradicts the documented authorized behavior; active state also fails to reflect closure.
C:Considering historical or real-time event analysis at Partner Services using database audit records: This claims both a real security issue and automatic recovery, while the Partner Services investigation found benign activity and a person cleared it.
Question 89
For the response to an incident affecting host-89, 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 customer-wide increase of the risk score
- The Enforce On device must be defined in FortiSIEM CMDB
- An exported CSV of every unrelated past incident
- A real-time Group By on raw event size
Explanation
Correct Answer
B:For inventory or lookup query at City Branch for host-89: 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-89: Changing priority does not create the missing CMDB object required to enforce the script action.
C:Considering inventory or lookup query at City Branch for host-89: Export files do not register the affected Linux server as a manageable remediation target.
D:Under inventory or lookup query at City Branch for host-89: Grouping search results cannot replace the target device inventory prerequisite for the remediation framework.
Question 90
The City Branch performance report for host-147 and peer systems needs hosts whose average CPU is at least 20% AND whose average memory utilization is at least 25%. How should FortiSIEM limit the aggregate output?
- Group only by event timestamp and discard host identity
- Use OR between the two aggregate thresholds
- Use event keywords CPU and Memory with no aggregation
- Use AVG(CPU Util) >= 20 AND AVG(Memory Util) >= 25 as Display Conditions
Explanation
Correct Answer
D:Under aggregate-query calculation at City Branch for host-147: Both threshold tests run against aggregate values for each host after grouping. The conjunction excludes hosts that exceed only one of the two measures.
Incorrect Answers
A:In aggregate-query calculation at City Branch for host-147: Timestamp buckets cannot establish which host breached both mean-utilization thresholds, which is central to this performance report.
B:For aggregate-query calculation at City Branch for host-147: An OR permits a host with only high CPU or only high memory, contrary to the two simultaneous City Branch requirements.
C:Considering aggregate-query calculation at City Branch for host-147: Keywords do not compute per-host averages; individual messages do not prove that either mean crosses the specified limits.