Fortinet FCP_FSM_AN-7.2 (FCP - FortiSIEM 7.2 Analyst) Practice Test 68

Question 670

An analyst at Cloud Services determines a unauthorized change event is more urgent than its assigned severity suggests. Which incident action updates prioritization without changing the original matching rule logic?

  1. Delete the {kind} event parser from its source
  2. Change the historical report time range
  3. Change Severity for the selected incident
  4. Remove every active rule in the tenant

Explanation

Correct Answer

C:

Incident List View includes a severity-change action. Raising urgency on this host-143 finding affects the current triage priority without rewriting the correlation filter.

Incorrect Answers

A:

In correlation-rule investigation at Cloud Services: Deleting normalization would affect future telemetry broadly and is unrelated to correcting urgency of one reviewed incident.

B:

For correlation-rule investigation at Cloud Services: Search interval changes which evidence is displayed but does not change the selected incident’s severity classification.

D:

Under correlation-rule investigation at Cloud Services: Global rule removal is disproportionate and would destroy alerting coverage unrelated to the current severity adjustment.

Question 671

Partner Services needs suspicious launch events from endpoint process alerts only when their device belongs to a CMDB list of critical host-136-class systems. Which nested search direction retains the event details?

  1. Two incident notifications whose messages have the same subject
  2. A real-time stream with Group By turned on
  3. Outer event query referencing an inner CMDB query
  4. Outer CMDB query using an inner event query exclusively

Explanation

Correct Answer

C:

The outer dataset remains the event evidence. The inner CMDB report contributes the list of critical devices used to include or exclude suspicious launch rows.

Incorrect Answers

A:

In nested search comparison at Partner Services for host-136 using endpoint process alerts: Notification emails do not establish a typed membership comparison between CMDB devices and event attributes.

B:

Real-time grouping is not supported and would not preserve the historical suspicious launch records selected by CMDB membership.

D:

That would produce devices as rows and cannot by itself display the full outer endpoint process alerts event details requested.

Question 672

After a FortiSIEM rule enriches svc.backup with a UEBA tag at Logistics, which analyst workflow helps verify whether the tag is justified?

  1. Clear all incidents involving other user accounts
  2. Reduce the historical data retention to zero
  3. Trust the tag without examining event data or thresholds
  4. Pivot from the tagged entity to underlying matching events and rule criteria

Explanation

Correct Answer

D:

The analyst can inspect how svc.backup met the rule, whether grouping and filters were correct, and whether the assigned tag represents meaningful behavior.

Incorrect Answers

A:

Changing unrelated incident dispositions does not validate the evidence attached to the tag for svc.backup.

B:

Removing historical context makes it harder to understand whether svc.backup activity is normal or unusual.

C:

Considering entity-behavior risk evaluation at Logistics: A tag is an analytic outcome and can reflect benign activity, mis-parsed events or an overbroad correlation condition.

Question 673

A recurring suspicious launch incident in Cloud Services is a known maintenance false positive at host-33, but other devices might legitimately trigger. What is the most targeted longer-term action?

  1. Manually mark all future matches as False Positive without examination
  2. Permanently disable the entire class of incident for every tenant
  3. Remove the raw event source for the organization
  4. Tune the triggering rule or create a scoped exception for the known benign condition

Explanation

Correct Answer

D:

Filtering the precise host-33 signature or its maintenance time reduces repeat noise while preserving visibility for genuine suspicious launch events elsewhere.

Incorrect Answers

A:

In incident-management case at Cloud Services for host-33: The meaning of a later suspicious launch event can change; bulk preclassification bypasses necessary evidence review.

B:

Global suppression would hide true incidents unrelated to the verified host-33 maintenance exception.

C:

Considering incident-management case at Cloud Services for host-33: Loss of endpoint process alerts telemetry destroys valuable investigation evidence and prevents other related detections.

Question 674

During an approved 45-minute window, host-98 at Logistics is deliberately generating failed login events. The existing rule must continue to detect the same behavior on other hosts. What should the analyst configure?

  1. Clear all previously recorded incidents as the only action
  2. Disable the rule for every organization until next week
  3. Raise the count threshold for all hosts permanently
  4. A scoped, time-bounded exception for the rule

Explanation

Correct Answer

D:

The exception can match host-98 and the 45-minute approval window, suppressing only the anticipated incident without silencing other devices.

Incorrect Answers

A:

In rule deployment or exception at Logistics for host-98: Clearing historical incidents does not prevent newly matching maintenance events from producing fresh alerts during the window.

B:

Global disablement creates an avoidable monitoring gap well beyond host-98 and the approved interval.

C:

Considering rule deployment or exception at Logistics for host-98: A threshold increase changes the detector everywhere and may miss attacks on otherwise quiet devices after the maintenance period.

Question 675

The Manufacturing search has 8 matching endpoint process alerts events for host-139 and 10 for a second host. The analyst groups by Host. What determines the count of result rows?

  1. The total number of events, 18
  2. The number of columns selected for display
  3. The number of distinct Host values among matched events
  4. The number of rules enabled on the FortiSIEM Supervisor

Explanation

Correct Answer

C:

Group By emits a separate aggregate row for each distinct Host combination. Event counts of 8 and 10 affect group measures, not inherently the number of groups.

Incorrect Answers

A:

18 is the combined raw event count. After Group By, several events can collapse into one Host-specific result row.

B:

For aggregate-query calculation at Manufacturing for host-139 using endpoint process alerts: Display columns determine attributes and measures shown; merely adding a column does not establish the number of distinct Host groups.

D:

Under aggregate-query calculation at Manufacturing for host-139 using endpoint process alerts: Rule availability affects incident correlation, while this historical search’s row cardinality comes from distinct grouping-key values.

Question 676

Cloud Services wants to correlate events about host-60 with its service group and ownership stored in CMDB, without requiring the property to be present in every incoming firewall session logs record. Which conceptual join is needed?

  1. Count all events from all organizations as one global measure
  2. Use only the latest raw-message text and disregard device identity
  3. Convert the incident category into a free-form CMDB schema
  4. Match an event device identifier to the corresponding CMDB record

Explanation

Correct Answer

D:

Combining event identifiers with CMDB inventory supplies the service group and ownership information even when the original log only describes an observed action.

Incorrect Answers

A:

Global event totals erase the specific host relationship required to retrieve the correct service group from Cloud Services inventory.

B:

Text alone does not guarantee that a record identifies the same host-60 as the inventory entry; the relationship requires a stable matching attribute.

C:

Considering CMDB and lookup-table configuration at Cloud Services for host-60 using firewall session logs: Incident classification is not a join key and does not turn an alert into a device record with reliable ownership context.

Question 677

East Retail has correlated several failed login incidents and related events into one investigation that should have an owner, workflow status, and associated evidence. Which FortiSIEM object is most appropriate?

  1. An unrelated CMDB lookup key
  2. A case associated with the relevant incidents/events
  3. A notification severity threshold alone
  4. A free-text event keyword saved as a report

Explanation

Correct Answer

B:

Case management groups related incidents into an assigned work item with investigation ownership and progression, rather than treating every host-107 alert independently.

Incorrect Answers

A:

In incident-management case at East Retail: A lookup key helps enrichment but does not provide an investigator owner and lifecycle for the related incident cluster.

C:

Considering incident-management case at East Retail: A threshold may control alert delivery but cannot connect multiple findings into one assigned investigation.

D:

For East Retail has correlated several failed login incidents and related events into one investigation that should have an: Under incident-management case at East Retail: A saved search can surface evidence but is not the managed case workflow with assignment and status for East Retail.

Question 678

Cloud Services wants a FortiSIEM dashboard listing the users associated with the most suspicious email security events events, rather than a separate row for each raw event. Which approach best fits?

  1. Convert every alert into a remediation script
  2. Group by the raw event timestamp at maximum precision only
  3. Use a device-only CMDB table without event joins
  4. Group a search or dashboard dataset by user and aggregate a relevant metric

Explanation

Correct Answer

D:

Grouping normalized email security events data by user produces entity-level summaries. Metrics such as count, distinct destinations or risk can make a dashboard useful for user behavior review.

Incorrect Answers

A:

In entity-behavior risk evaluation at Cloud Services using email security events: Remediation definitions are device actions, not a dashboard data aggregation for user analytics.

B:

For entity-behavior risk evaluation at Cloud Services using email security events: Each event may have a different timestamp, so this grouping defeats the requested user-centered rollup.

C:

CMDB-only views do not show suspicious email security events behavior grouped by users across the timeframe.

Question 679

A security engineer is designing table CriticalServiceInventory at North Finance. The criticality field stores names and text. Which available lookup-table field type should be chosen?

  1. BOOLEAN
  2. STRING
  3. LONG
  4. DOUBLE

Explanation

Correct Answer

B:

STRING holds character data. It is suitable for textual criticality labels and avoids inappropriate numeric operations on identity values.

Incorrect Answers

A:

In CMDB and lookup-table configuration at North Finance: BOOLEAN is not one of the schema field types offered in the FortiSIEM 7.2 lookup table editor, which provides STRING, LONG, and DOUBLE.

C:

LONG represents integer values. It fits whole-number criticality identifiers but not free text or decimal fractions.

D:

DOUBLE represents real-valued numbers, such as fractional criticality scores; it is unsuitable for arbitrary text or exact integer-only identifiers when LONG is intended.

Question 680

A FortiSIEM correlation design at Research observes P1 (blocked request in web application alerts) and P2 (a related action on host-20). It must require P1 and then P2 in that order. Which relationship operator best expresses that precise condition?

  1. AND-NOT
  2. NOT-FOLLOWED-BY
  3. AND
  4. OR
  5. FOLLOWED-BY

Explanation

Correct Answer

E:

FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-20 rather than unordered coincidence.

Incorrect Answers

A:

In subpattern correlation at Research for host-20 using web application alerts: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the Research event sequence.

B:

For subpattern correlation at Research for host-20 using web application 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.

C:

Considering subpattern correlation at Research for host-20 using web application alerts: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended Research test.

D:

Under subpattern correlation at Research for host-20 using web application 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.

FCP - FortiSIEM 7.2 Analyst (FCP_FSM_AN-7.2) Practice Tests