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

Question 590

An East Retail investigator wants historical sign-in events from identity provider events where User appears in an earlier event report of suspicious actors. Which nested query data-source pairing is natural?

  1. Use a rule clear condition as the inner dataset
  2. Outer pure CMDB search regardless of the event evidence
  3. Outer lookup schema editor with an inner alert notification
  4. Outer event search using an inner event report as a membership source

Explanation

Correct Answer

D:

Both the displayed evidence and the prior actor list derive from events. Event-to-event nesting filters historical identity provider events rows using values from the inner report.

Incorrect Answers

A:

Clear conditions manage incident status, not the result set supplied to the outer event search for User.

B:

An inventory outer query would return CMDB objects rather than the historical sign-in event rows the investigator needs.

C:

Considering nested search comparison at East Retail using identity provider events: Neither schema editing nor notification delivery evaluates event membership from an existing suspicious-actor report.

Question 591

City Branch is building a scheduled analytics rule for blocked lookup. A designer tries adding two distinct subpatterns to its condition. Which FortiSIEM 7.2 restriction explains the rejection?

  1. Scheduled rules cannot use any event filters
  2. All rules are limited to one event attribute globally
  3. Scheduled rules must use only raw-text keywords as filters
  4. Scheduled rules support only one subpattern

Explanation

Correct Answer

D:

For City Branch is building a scheduled analytics rule for blocked lookup. A designer tries adding two distinct subpatterns to: Under correlation-rule investigation at City Branch with the specified 7.2 value: FortiSIEM explicitly restricts scheduled rule conditions to a single subpattern. Multi-subpattern temporal correlation belongs to applicable real-time rule designs.

Incorrect Answers

A:

In correlation-rule investigation at City Branch with the specified 7.2 value: Scheduled rules can specify the one subpattern’s filters; the limitation concerns the number of subpatterns, not whether blocked lookup can be selected.

B:

For correlation-rule investigation at City Branch with the specified 7.2 value: A subpattern may use multiple filter attributes. The documented scheduled restriction is a structural subpattern count.

C:

For City Branch is building a scheduled analytics rule for blocked lookup. A designer tries adding two distinct subpatterns to: Considering correlation-rule investigation at City Branch with the specified 7.2 value: Normalized Event Attribute conditions are supported in rule filtering; the problem is the second subpattern rather than parser field use.

Question 592

For East Retail, incident automation should invoke a specified integration policy on every qualifying policy denial alert. Which policy action represents that design?

  1. Modify the CMDB asset owner without any alert action
  2. Clear the incident immediately and assume the connector runs
  3. Set a report to Group By application name
  4. Invoke Integration Policy with the intended integration selected

Explanation

Correct Answer

D:

Under Automation Policy workflow at East Retail: The action explicitly starts the configured integration on qualifying incidents, unlike changing a search or notification label without calling the integration.

Incorrect Answers

A:

In Automation Policy workflow at East Retail: Ownership metadata might help routing decisions, but it cannot invoke the requested integration without the policy action.

B:

For Automation Policy workflow at East Retail: Clearing updates incident state; it does not imply that an integration policy was invoked on the policy denial trigger.

C:

Report grouping does not execute an external incident integration for East Retail.

Question 593

Lookup table TrustedNetworks in Cloud Services has a numeric key, while the event field supplied by email security events is normalized as a string. Searches find no matching rows. What should be checked first?

  1. That the analyst enabled a real-time Group By
  2. That the lookup key type and event expression use compatible data types
  3. That a remediation script already ran for each event
  4. That the incident has a high severity label

Explanation

Correct Answer

B:

The table schema requires typed keys. A numeric TrustedNetworks key cannot be reliably matched against a string-form email security events field without compatible typing or an appropriate conversion.

Incorrect Answers

A:

In CMDB and lookup-table configuration at Cloud Services using email security events: Grouping changes how query results are summarized and is not a fix for a mismatched lookup key type.

C:

Considering CMDB and lookup-table configuration at Cloud Services using email security events: Remediation occurs after incident logic and cannot repair the input data-type mismatch causing the lookup misses.

D:

Severity does not coerce a string event attribute into the numeric key type expected by TrustedNetworks.

Question 594

After Manufacturing deploys lookup table CriticalServiceInventory, 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 notification policy can append a key field to the schema
  2. A created lookup table schema cannot be modified in place
  3. Every analytic search rewrites the table schema on its next run
  4. Changing the data rows automatically changes key definitions

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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

C:

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

D:

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

Question 595

A recurring failed sign-in incident in Partner Services is a known maintenance false positive at host-98, 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. Tune the triggering rule or create a scoped exception for the known benign condition
  3. Permanently disable the entire class of incident for every tenant
  4. Remove the raw event source for the organization

Explanation

Correct Answer

B:

Filtering the precise host-98 signature or its maintenance time reduces repeat noise while preserving visibility for genuine failed sign-in events elsewhere.

Incorrect Answers

A:

The meaning of a later failed sign-in event can change; bulk preclassification bypasses necessary evidence review.

C:

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

D:

Loss of Windows security logs telemetry destroys valuable investigation evidence and prevents other related detections.

Question 596

West Operations is prioritizing two hosts: one has a rare high-severity stopped service event and high asset criticality, while the other has routine low-impact alerts. Which FortiSIEM concept better combines those signals?

  1. Change only the dashboard grouping and assume it updates the incident case history
  2. Host or user risk score using severity, rarity, resolution, and criticality
  3. Alphabetical order of the hostnames
  4. Number of characters in each raw syslog message

Explanation

Correct Answer

B:

For historical or real-time event analysis at West Operations: FortiSIEM 7.2 enhanced risk scoring incorporates incident rarity and asset criticality alongside severity/resolution, helping identify materially different investigation priority.

Incorrect Answers

A:

In historical or real-time event analysis at West Operations: Grouping changes a view of the data, not the underlying incident dispositions, investigator notes or case associations.

C:

Considering historical or real-time event analysis at West Operations: Lexical ordering is not a meaningful threat or business-impact prioritization measure for stopped service incidents.

D:

Message length does not capture rarity, consequence, or asset importance for the two West Operations hosts.

Question 597

The outer search in City Branch examines proxy access records from the last 45 minutes, but the list of User values must come from the preceding day. Where is the inner report interval controlled?

  1. Set Nested Time Range for the selected inner report separately from the outer range
  2. Change the Group By field to elapsed time
  3. Reduce the lookup-table schema key count to one
  4. Assume the outer Time Range automatically defines every inner report interval

Explanation

Correct Answer

A:

Nested searches distinguish the outer query window from the inner report time window. This lets the actor list cover the preceding day while the visible proxy access records evidence covers 45 minutes.

Incorrect Answers

B:

For nested search comparison at City Branch using proxy access records with the specified 45 value: Grouping alters result summaries and does not independently schedule the time horizon for the inner User report.

C:

Considering nested search comparison at City Branch using proxy access records with the specified 45 value: Lookup keys do not control how long an inner event report runs in this nested search.

D:

Using the outer 45-minute window for both datasets would omit actors observed earlier in the day.

Question 598

The City Branch performance report for host-101 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. Use event keywords CPU and Memory with no aggregation
  2. Use OR between the two aggregate thresholds
  3. Group only by event timestamp and discard host identity
  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-101: 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-101: Keywords do not compute per-host averages; individual messages do not prove that either mean crosses the specified limits.

B:

For aggregate-query calculation at City Branch for host-101: 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-101: Timestamp buckets cannot establish which host breached both mean-utilization thresholds, which is central to this performance report.

Question 599

The Manufacturing team tests a new quarantine rule. It triggers on a documented false positive generated by host-107 at normal business hours. Which correction preserves coverage while reducing repeat noise?

  1. Narrow the event filters, group logic, or applicable exception based on the false-positive evidence
  2. Remove the event data source from FortiSIEM for every device
  3. Change the case-assignment queue without modifying event logic
  4. Always mark every later incident from the rule false positive

Explanation

Correct Answer

A:

Rule tuning should target the characteristic that distinguished this benign host-107 event from malicious quarantine behavior rather than discarding the entire detector.

Incorrect Answers

B:

For rule deployment or exception at Manufacturing for host-107: Loss of visibility would suppress valid detections across Manufacturing, not only the verified benign event pattern.

C:

Considering rule deployment or exception at Manufacturing for host-107: Reassigning incidents affects workflow ownership but leaves the original high-noise rule conditions intact.

D:

Under rule deployment or exception at Manufacturing for host-107: Future matches may represent a true attack. Automatic blanket false-positive classification is not a precise correlation correction.

Question 600

In East Retail, a stored search matches 13 failed authentication records from VPN authentication records, including only 9 unique Source IP values for host-169. To measure unique targets rather than raw volume, which aggregate is required?

  1. AVG(Source IP)
  2. COUNT(Matched Events)
  3. SUM(Source IP)
  4. COUNT(DISTINCT Source IP)

Explanation

Correct Answer

D:

This removes repeated Source IP values before counting. For host-169, the expected unique-target measure is 9 rather than the 13 event rows.

Incorrect Answers

A:

An average of an identifier would not quantify unique Source IP values, even if the attribute happened to be encoded numerically.

B:

This produces 13 because each qualifying event contributes one row. It cannot distinguish repeat connections to a target from a new Source IP.

C:

SUM is intended for numeric measures and is not a meaningful distinct-count function for the Source IP identity field in these VPN authentication records records.

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