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

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?

  1. SUM(Destination Domain)
  2. AVG(Destination Domain)
  3. COUNT(DISTINCT Destination Domain)
  4. 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.

Question 141

An analyst at North Finance determines a permission failure event is more urgent than its assigned severity suggests. Which incident action updates prioritization without changing the original matching rule logic?

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

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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

C:

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

D:

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

Question 142

A saved Logistics Automation Policy for sign-in is not sending messages. Its rule, severity, and action criteria are correct. Which setting should be checked before changing detection rules?

  1. Whether the rule’s test window has been shortened to one second
  2. Whether the event parser was renamed after policy creation
  3. Edit the detection search but omit an Automation Policy matching criterion and action
  4. Whether the Automation Policy is enabled

Explanation

Correct Answer

D:

FortiSIEM creates and stores policies independently of activation. An unchecked Enabled control prevents the policy from sending the expected sign-in alerts.

Incorrect Answers

A:

Changing rule testing scope will not activate a disabled action policy for Logistics.

B:

For Automation Policy workflow at Logistics: Parser naming is not a substitute for enabling an otherwise correctly scoped automation policy.

C:

Considering Automation Policy workflow at Logistics: Searches return matching records; the automation engine requires a policy with explicit incident criteria and a delivery or remediation action.

Question 143

After a failed sign-in detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic rule. What must the first rule’s generated incident provide?

  1. Modify the case label without reviewing rule state or exceptions
  2. A typed Host incident attribute compatible with the IP watchlist
  3. Only the literal words suspected host in the incident title
  4. A notification threshold without an incident definition

Explanation

Correct Answer

B:

For After a failed sign-in detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic rule.: For rule deployment or exception at Corporate HQ: The watchlist update uses a field from the generated incident. A correctly typed Host value lets downstream rules match the same address reliably.

Incorrect Answers

A:

For After a failed sign-in detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic rule.: In rule deployment or exception at Corporate HQ: Case metadata does not activate an inactive rule or correctly scope a rule exception for future event matches.

C:

For After a failed sign-in detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic rule.: Considering rule deployment or exception at Corporate HQ: An informal title string does not provide a typed IP field that the watchlist can store and another rule can match.

D:

For After a failed sign-in detection, Corporate HQ needs a watchlist of Host IP addresses for use in a second analytic rule.: Under rule deployment or exception at Corporate HQ: Alerts require a defined incident, and the watchlist needs its typed attribute; frequency alone supplies neither.

Question 144

Corporate HQ has confirmed that an inner quarantine report from email security events returns the expected Sender IP values, yet the outer search unexpectedly omits older eligible records. Both types match. Which time-related check is most useful?

  1. Change the notification action from email to SNMP
  2. Replace the matched event filter with an unrelated device property
  3. Review the independent outer and nested report time ranges
  4. Delete the saved inner report and rely on a display-only value

Explanation

Correct Answer

C:

Even compatible Sender IP comparisons fail to include older evidence when either dataset is queried over an overly narrow interval. Check both temporal scopes.

Incorrect Answers

A:

In nested search comparison at Corporate HQ using email security events: Notification channel selection does not govern whether older event rows qualify for a nested Analytics query.

B:

Changing the identity test abandons the intended quarantine correlation rather than addressing an interval omission.

D:

Under nested search comparison at Corporate HQ using email security events: The inner report is the query’s value source. Removing it prevents the nested condition from examining the relevant previous data.

Question 145

Research searches web application alerts and sees the right event count but needs the URI Path value beside each Source IP in unaggregated rows. Which change addresses the output without excluding matches?

  1. Add URI Path to the displayed event fields
  2. Shorten the historical time range until one row remains
  3. Group the results only by Source IP
  4. Filter to events where URI Path equals a single value

Explanation

Correct Answer

A:

Display Fields controls the attributes shown for matching events. Including URI Path preserves the filter and makes the requested evidence visible alongside Source IP.

Incorrect Answers

B:

For historical or real-time event analysis at Research using web application alerts: Changing time arbitrarily alters the count and risks removing relevant events; the problem is display columns, not volume.

C:

A group summary collapses event rows and can hide each individual URI Path relationship sought by the investigator.

D:

A new equality filter would discard legitimate web application alerts records with other URI Path values, changing the evidence set rather than its columns.

Question 146

After opening one failed authentication event from VPN authentication records, an investigator wants other events having the same User on host-202, not merely lines containing its spelling. How should the query be narrowed?

  1. Group all events by their ingestion minute
  2. Query CMDB for every inventoried asset instead of events
  3. Filter on the parsed User event attribute with the exact value
  4. Use only a free-text keyword extracted from the raw event

Explanation

Correct Answer

C:

A structured Event Attribute condition compares the normalized User field, avoiding accidental text matches in unrelated portions of VPN authentication records.

Incorrect Answers

A:

In historical or real-time event analysis at the SOC for host-202 using VPN authentication records: Grouping by minute changes output granularity but does not enforce equality on User for the related-event investigation.

B:

CMDB can enrich host identity, yet it is not the normalized VPN authentication records search that finds events sharing User.

D:

Keyword matching can find the same characters in messages that have a different parsed User, weakening entity identity for host-202.

Question 147

A Cloud Services analyst needs to maintain a small, manually governed set of AssetOwners identifiers used to enrich future permission failure events. The values are not necessarily discoverable assets. Which repository best fits?

  1. The CMDB device inventory only, with fabricated devices for each identifier
  2. An email notification list with one recipient per identifier
  3. A Resources lookup table with a defined key and value schema
  4. A real-time search result window as the sole durable repository

Explanation

Correct Answer

C:

Lookup tables store user-managed tabular keys and columns. AssetOwners can then be referenced by compatible searches and rules to enrich incoming permission failure evidence.

Incorrect Answers

A:

CMDB objects represent discoverable entities. Inventing assets for arbitrary AssetOwners values corrupts inventory semantics and is not needed.

B:

Notification recipients route alert messages and do not implement a queryable enrichment dataset for permission failure events.

D:

Streaming results describe transient events; they are not a controlled persistent table of approved AssetOwners identifiers.

Question 148

For a policy violation incident in Corporate HQ, the analyst wants to record findings that a responder can read without falsely treating the alert as resolved. Which incident operation is suitable?

  1. Set False Positive and clear every incident sharing the category
  2. Delete the device from CMDB so the incident loses context
  3. Add an incident comment or remediation advice while preserving current status
  4. Raise the global rule count threshold as a substitute for notes

Explanation

Correct Answer

C:

FortiSIEM supports comments on incident records and remediation notes in rules. Documentation helps responders act on host-142 without prematurely clearing the live alert.

Incorrect Answers

A:

This asserts a benign verdict and changes lifecycle state for alerts that may still represent genuine policy violation activity.

B:

For incident-management case at Corporate HQ: Removing an inventory object discards relevant asset information and does not constitute safe analyst documentation.

D:

Under incident-management case at Corporate HQ: Changing detection conditions alters future alerts, not the investigation narrative that a responder needs now.

Question 149

The Manufacturing search has 8 matching Windows security logs events for host-70 and 9 for a second host. The analyst groups by Host. What determines the count of result rows?

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

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

17 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-70 using Windows security logs: Display columns determine attributes and measures shown; merely adding a column does not establish the number of distinct Host groups.

C:

Considering aggregate-query calculation at Manufacturing for host-70 using Windows security logs: Rule availability affects incident correlation, while this historical search’s row cardinality comes from distinct grouping-key values.

Question 150

A policy violation policy at Corporate HQ has the correct severity, time, and organization but triggers for unrelated detection rules. What policy criterion can narrow the action to its intended detections?

  1. The alphabetical order of incident titles
  2. The selected Rules list in the Automation Policy
  3. The number of data collectors in the organization
  4. A blanket increase of every rule’s aggregation threshold

Explanation

Correct Answer

B:

For Automation Policy workflow at Corporate HQ: Automation Policies can select specific generating rules. Limiting the set to the policy violation detection prevents actions caused by unrelated incident types.

Incorrect Answers

A:

In Automation Policy workflow at Corporate HQ: Alert-title sorting does not determine which source rule satisfies an Automation Policy.

C:

Considering Automation Policy workflow at Corporate HQ: Distributed collection architecture does not replace selecting which correlation rules should invoke the automation.

D:

Under Automation Policy workflow at Corporate HQ: This weakens detections across the tenant and does not correctly configure the notification scope.

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