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

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?

  1. Group only by event timestamp and discard host identity
  2. Use OR between the two aggregate thresholds
  3. Use event keywords CPU and Memory with no aggregation
  4. 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.

Question 91

In a managed-service FortiSIEM deployment, Corporate HQ should receive automation for its own deny incidents without alerting other customer organizations. Which selection is essential?

  1. Affected Orgs in the Automation Policy
  2. A global increase of the rule event threshold for every tenant
  3. Edit the detection search but omit an Automation Policy matching criterion and action
  4. Group By destination port in every search report

Explanation

Correct Answer

A:

MSSP policies have organization scope. Selecting Corporate HQ restricts incident actions to the intended tenant, subject to the other criteria in the policy.

Incorrect Answers

B:

For Automation Policy workflow at Corporate HQ: Changing the detection threshold is not a tenant notification boundary and may suppress valid findings across organizations.

C:

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

D:

Under Automation Policy workflow at Corporate HQ: Aggregation fields control analytic output rather than which customer is allowed to receive an action.

Question 92

At Logistics, an anomalous bytes transferred per remote session model was trained on a field imported as text, so numeric computations fail. Which correction most directly addresses the ML input?

  1. Mark all anomalous records as resolved before training
  2. Use a numeric report field for the measure being modeled
  3. Replace the field with the incident title
  4. Treat a normalized event query as a completed ML training model

Explanation

Correct Answer

B:

Numeric anomaly models rely on continuous or count-like features. Correctly typed bytes transferred per remote session data allows the learner to evaluate ranges and deviations.

Incorrect Answers

A:

Incident resolution is not a substitute for correcting the underlying bytes transferred per remote session feature type.

C:

Titles are labels for people and do not provide the numeric measurements needed to learn variation in bytes transferred per remote session.

D:

Under machine-learning analysis at Logistics: An event search selects records, while a model must be trained on the intended dataset and then applied to compatible new features.

Question 93

A North Finance automation must send an email for a failed sign-in incident and also invoke a remediation script when its conditions match. Which action configuration supports that design?

  1. Save a historical query and close the incident without actions
  2. Set only the rule severity and assume that sends the email and script
  3. Change the Lookup Table key count to two
  4. Enable matching policy actions for Email/SMS and Run Remediation/Script

Explanation

Correct Answer

D:

Automation Policies support both communications and scripted response. The North Finance team should independently verify recipients, script scope and safe execution before enabling the combination.

Incorrect Answers

A:

In Automation Policy workflow at North Finance: A report captures data, while the requested incident-triggered email and script require explicit automation actions.

B:

Severity classifies an incident; it does not itself configure message recipients or execute remediation for failed sign-in.

C:

Considering Automation Policy workflow at North Finance: Table schema does not route messages or run incident remediation commands.

Question 94

A City Branch rule must add a User address from a sign-in incident to a watchlist whose declared element type is IP. The incident attribute is a string label instead. What should be verified?

  1. The rule incident title includes the word IP
  2. The watchlist type matches the type of the incident attribute written to it
  3. The historical search uses a 30-day default range
  4. The rule has at least three different email recipients

Explanation

Correct Answer

B:

For correlation-rule investigation at City Branch: FortiSIEM rejects incompatible watchlist/incident attribute types. An IP watchlist expects a compatible IP-type incident value, not an unrelated string label.

Incorrect Answers

A:

In correlation-rule investigation at City Branch: Free-text title labels cannot change the underlying attribute type used for watchlist updates.

C:

Considering correlation-rule investigation at City Branch: Search time horizon does not convert a string incident attribute to an IP-type watchlist entry.

D:

Under correlation-rule investigation at City Branch: Email fan-out has no effect on the type compatibility of a User entry stored in the IP watchlist.

Question 95

After Cloud Services deploys lookup table TrustedNetworks, the owner realizes that the schema needs another service group key and wants to revise the original structure in place. What limitation controls the next step?

  1. A created lookup table schema cannot be modified in place
  2. Every analytic search rewrites the table schema on its next run
  3. Changing the data rows automatically changes key definitions
  4. A notification policy can append a key field to the schema

Explanation

Correct Answer

A:

FortiSIEM documents the schema as immutable after table creation. The TrustedNetworks design must therefore be planned before deployment; the owner needs an appropriate replacement or rebuild strategy.

Incorrect Answers

B:

For CMDB and lookup-table configuration at Cloud Services: Queries read lookup data but do not redeclare how service group is typed or keyed in Resources.

C:

Editing or importing records changes lookup contents, not the key/column schema of the existing TrustedNetworks.

D:

Under CMDB and lookup-table configuration at Cloud Services: Notification automation controls post-incident actions and has no role in changing existing table schema definitions.

Question 96

FortiSIEM has three CPU utilization samples for host-81 in Research: 10%, 40%, and 50%. The rule should compare mean utilization across samples. Which search expression evaluates the required statistic?

  1. AVG(CPU Util)
  2. MAX(CPU Util)
  3. SUM(CPU Util)
  4. COUNT(Matched Events)

Explanation

Correct Answer

A:

AVG calculates the arithmetic mean: (10 + 40 + 50) / 3 = 33.3%. This matches the average-utilization objective for host-81.

Incorrect Answers

B:

For aggregate-query calculation at Research for host-81: MAX returns 50%, 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-81: SUM adds the sample percentages to 100; the total is not mean utilization and would distort a percentage threshold.

D:

Under aggregate-query calculation at Research for host-81: COUNT reports the three matching samples, not their CPU utilization values. It would test frequency rather than the requested load measure.

Question 97

City Branch has a user-focused analytic rule for analyst.g. The analyst wants a recognizable UEBA tag on qualifying entity activity. Where should tag categories be managed?

  1. Replace the entity score with incident-list display ordering
  2. Analytics settings for UEBA Tags, with appropriate rule tagging configuration
  3. The event export file format selector
  4. Only the FortiGate IP address pool list

Explanation

Correct Answer

B:

For entity-behavior risk evaluation at City Branch: FortiSIEM’s Analytics settings contain UEBA tag management. Rules can use the configured tags to enrich entity context for investigation and reporting.

Incorrect Answers

A:

In entity-behavior risk evaluation at City Branch: Sorting incidents can prioritize a screen view but cannot rebuild the normalized entity mapping or actual risk contributors.

C:

Considering entity-behavior risk evaluation at City Branch: Export format affects downloaded evidence, not the reusable tag categories that analytics rules assign.

D:

Under entity-behavior risk evaluation at City Branch: FortiGate address objects support access control and are not the central FortiSIEM UEBA tag definition interface.

Question 98

City Branch wants the correlated incident for failed authentication to include the original User, Source IP, and other event context for investigation. Which rule configuration maps the evidence into the generated alert?

  1. Incident Attributes and Triggered Attributes from rule subpatterns
  2. Only the incident email template without event mapping
  3. Only the global source data retention setting
  4. Only the rules folder name

Explanation

Correct Answer

A:

In correlation-rule investigation at City Branch: The incident definition maps selected filter, group and aggregate attributes into incident fields. Including User and Source IP preserves actionable context for analysts.

Incorrect Answers

B:

For correlation-rule investigation at City Branch: An email template cannot recover omitted triggered values unless the incident definition first includes the relevant User and Source IP context.

C:

For City Branch wants the correlated incident for failed authentication to include the original User, Source IP, and other event: Considering correlation-rule investigation at City Branch: Retention controls availability of evidence but does not decide the fields copied into each generated incident.

D:

Under correlation-rule investigation at City Branch: The folder identifies where the rule is stored, not which event attributes the resulting incident retains.

Question 99

A Corporate HQ analyst defines subpattern conditions for deny events but cannot save the rule because no incident action exists. What rule component is mandatory before saving?

  1. At least one incident definition with its triggered attributes
  2. A manually cleared older incident of the same category
  3. A custom lookup table regardless of the conditions
  4. A completed export of every historical event from the past year

Explanation

Correct Answer

A:

In correlation-rule investigation at Corporate HQ: FortiSIEM requires at least one generated-incident definition. The deny subpattern must map relevant event attributes into the incident output before the rule can be saved.

Incorrect Answers

B:

For correlation-rule investigation at Corporate HQ: Existing incident lifecycle state does not substitute for defining the incident produced by the new rule.

C:

Considering correlation-rule investigation at Corporate HQ: Lookup tables are optional enrichment sources. They are not a universal requirement for saving a deny analytics rule.

D:

Event export is not a prerequisite for rule definition; the missing component is how Corporate HQ will represent the triggered incident.

Question 100

A Logistics ML job repeatedly misses new bytes transferred per remote session samples because it has no recurring inference schedule. Which operational change addresses the gap?

  1. Change the Collector hostname to the affected user name
  2. Keep rerunning an exported PDF manually as the schedule
  3. Disable every related incident rule permanently
  4. Configure and enable an inference schedule for the supported job and input source

Explanation

Correct Answer

D:

Scheduled inference processes new report-derived data on the selected cadence. The analyst should ensure report windows and prerequisites align with incoming bytes transferred per remote session telemetry.

Incorrect Answers

A:

In machine-learning analysis at Logistics: Collector naming does not define when the trained model scores new feature values.

B:

For machine-learning analysis at Logistics: A PDF is a presentation document, not a supported recurring inference input or scheduler for the model.

C:

Disabling incident rules hides downstream symptoms but does not make the ML model process the new bytes transferred per remote session batches.

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