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

Question 700

The Manufacturing investigation tracks two events in endpoint process alerts: a denied login P1 followed by a successful login P2. The rule is incorrectly matching different users. Which inter-subpattern constraint should be added?

  1. Equality between the relevant Host identity attributes of P1 and P2
  2. Removal of all grouping keys and inter-subpattern constraints
  3. A greater-than test between the two event message lengths
  4. Only a larger incident title text field

Explanation

Correct Answer

A:

In subpattern correlation at Manufacturing using endpoint process alerts: Inter-subpattern comparisons link matching entity keys across both behaviors. Requiring the same Host prevents a different user’s P2 from completing this sequence.

Incorrect Answers

B:

Eliminating identity comparison makes cross-user false matches more likely in Manufacturing, not less.

C:

Considering subpattern correlation at Manufacturing using endpoint process alerts: Message length does not establish user or entity identity for the P1–P2 correlation.

D:

Under subpattern correlation at Manufacturing using endpoint process alerts: Title length affects labeling and cannot prevent a P2 from another Host being joined to the first event.

Question 701

A Cloud Services 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. A manually cleared older incident of the same category
  2. A custom lookup table regardless of the conditions
  3. A completed export of every historical event from the past year
  4. At least one incident definition with its triggered attributes

Explanation

Correct Answer

D:

Under correlation-rule investigation at Cloud Services: 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

A:

In correlation-rule investigation at Cloud Services: Existing incident lifecycle state does not substitute for defining the incident produced by the new rule.

B:

For correlation-rule investigation at Cloud Services: Lookup tables are optional enrichment sources. They are not a universal requirement for saving a deny analytics rule.

C:

Considering correlation-rule investigation at Cloud Services: Event export is not a prerequisite for rule definition; the missing component is how Cloud Services will represent the triggered incident.

Question 702

At East Retail, FortiSIEM exposes a watchlist intended for IP-based FortiGate access control, but its entries are usernames. Why will the integration not behave as intended?

  1. The FortiSIEM dashboard should sort users in reverse order
  2. FortiGate external connectors always parse usernames as IPv4 addresses
  3. The indicator type must match the FortiGate IP-address threat-feed expectations
  4. Configure a FortiGate deny rule that never references the imported dynamic address object

Explanation

Correct Answer

C:

An IP external connector consumes address indicators such as 198.51.100.22, not arbitrary account names. Source rule mapping and watchlist schema must align.

Incorrect Answers

A:

In IP feed and FortiGate enforcement at East Retail: Sorting display values cannot fix the underlying mismatch between source indicator type and firewall feed schema.

B:

For IP feed and FortiGate enforcement at East Retail: User identifiers are not generally valid IPv4 entries and cannot be automatically used as source-IP firewall matches.

D:

Under IP feed and FortiGate enforcement at East Retail: A rule without the feed-backed source object may not match the newly risky IPs learned by FortiSIEM.

Question 703

The Manufacturing SOC is designing a rotating team to handle assigned permission failure cases. Which FortiSIEM setup enables assignment to the right analysts and team leads?

  1. Organize eligible FortiSIEM Analysts into Analyst Teams under CMDB > Users
  2. Configure a firewall NAT rule as the case roster
  3. Use only an event-data Group By over destination ports
  4. Replace case owners with raw syslog facility codes

Explanation

Correct Answer

A:

In incident-management case at Manufacturing: Case assignments use defined analyst teams, whose members and leads can participate in the management policy. This supports coordinated ownership across shifts.

Incorrect Answers

B:

For incident-management case at Manufacturing: Network address translation does not register eligible investigators or define case ownership.

C:

Considering incident-management case at Manufacturing: Grouping data does not define analyst membership, leads or work queues for cases in Manufacturing.

D:

For The Manufacturing SOC is designing a rotating team to handle assigned permission failure cases. Which FortiSIEM setup: Under incident-management case at Manufacturing: Log facility values characterize messages, not human case-assignment permissions or team structure.

Question 704

An East Retail analyst is already searching rejected request events in cloud API audit events, but only wants records whose reporting devices have CMDB maintenance state=critical. How can event selection incorporate inventory context?

  1. Group the events by ingestion timestamp alone
  2. Reference CMDB device properties through the supported event/CMDB query mechanism
  3. Compare the raw event keyword against the word maintenance state only
  4. Set incident severity to critical before running the query

Explanation

Correct Answer

B:

FortiSIEM combined Event/CMDB searches and DeviceToCMDBAttr-style access can apply inventory properties such as maintenance state to event evidence.

Incorrect Answers

A:

Changing time granularity does not test whether the reporting device has the required CMDB maintenance state value.

C:

Unless that property is present in every raw cloud API audit events message, keyword text cannot reliably enforce the CMDB-derived criticality constraint.

D:

Incident severity is an alert attribute; it does not add the maintenance state predicate to existing event-search matches.

Question 705

A West Operations report groups policy denial events by User and uses COUNT(Matched Events). The analyst wants only groups exceeding 9 events to remain in the result, not to remove the underlying records before aggregation. What should be configured?

  1. A Display Condition of COUNT(Matched Events) > 9
  2. An event filter that rejects all records until their count exceeds 9
  3. A time range of exactly 9 seconds
  4. Group By COUNT(Matched Events) instead of User

Explanation

Correct Answer

A:

For A West Operations report groups policy denial events by User and uses COUNT(Matched Events). The analyst wants only groups: In aggregate-query calculation at West Operations with the specified 9 value: FortiSIEM display conditions filter aggregates after grouping, analogous to HAVING. Groups must first be counted, then those above 9 remain visible.

Incorrect Answers

B:

For aggregate-query calculation at West Operations with the specified 9 value: An event filter evaluates record attributes before aggregation. Individual proxy access records events do not carry the completed group count to filter on.

C:

Considering aggregate-query calculation at West Operations with the specified 9 value: The literal threshold is a count of records, not a query time window. Shortening time would alter which policy denial events are included.

D:

Under aggregate-query calculation at West Operations with the specified 9 value: COUNT is the measure to test, while User defines the groups whose counts are compared; swapping these loses the per-source view.

Question 706

During an approved 10-minute window, host-29 at Logistics is deliberately generating blocked request 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. A scoped, time-bounded exception for the rule
  3. Raise the count threshold for all hosts permanently
  4. Disable the rule for every organization until next week

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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

C:

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

D:

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

Question 707

North Finance already labeled prior permission failure events on host-66 as benign or suspicious. It wants a model to assign one of those known classes to new records. Which task is appropriate?

  1. Classification with training examples that include the outcome labels
  2. Clustering treated as if labels were available
  3. Regression without any category outcome
  4. CMDB asset-type filtering only

Explanation

Correct Answer

A:

Classification learns a mapping from database audit records input features to known categories, allowing inference of benign versus suspicious cases for host-66. Label quality must be evaluated.

Incorrect Answers

B:

Unsupervised clustering groups similar data but does not directly learn the predefined class names that North Finance has already annotated.

C:

Considering machine-learning analysis at North Finance for host-66: Regression estimates continuous numeric values rather than the requested named benign/suspicious class categories.

D:

Inventory filtering can select a population but cannot classify new permission failure records by learning from labeled historical examples.

Question 708

A rule in Corporate HQ generates an incident when permission failure occurs; analysts need it categorized with the proper severity and impact. In which rule phase are these outputs assigned?

  1. A saved historical search display preference
  2. Step 1: General only
  3. The data parser configuration exclusively
  4. Step 3: Define Actions

Explanation

Correct Answer

D:

Under correlation-rule investigation at Corporate HQ: Rule actions define incident severity, category, impact and related post-detection settings. These describe what the matched permission failure condition produces.

Incorrect Answers

A:

For A rule in Corporate HQ generates an incident when permission failure occurs; analysts need it categorized with the proper: In correlation-rule investigation at Corporate HQ: Historical display columns shape query output, not the severity assigned to an incident when a rule fires.

B:

For correlation-rule investigation at Corporate HQ: General details name and organize the rule. They do not replace incident action fields such as severity and category.

C:

Considering correlation-rule investigation at Corporate HQ: Parsing determines incoming event fields; incident severity is a rule-output property rather than a raw-log parsing directive.

Question 709

At West Operations, a security analyst needs to compare risk across contractor.r and nearby workstation entities in a dashboard. Which design makes the comparison meaningful?

  1. Summarize by entity type and stable entity identifier, with a comparable risk measure
  2. Hide all entity identifiers and show one grand total
  3. Group raw events by their collector name without retaining user or host identity
  4. Use only event timestamp as the user/entity correlation key

Explanation

Correct Answer

A:

In entity-behavior risk evaluation at West Operations: Entity-scoped dashboard data lets analysts compare user and host indicators while retaining identity. Stable identifiers avoid fragmented or duplicate risk rows.

Incorrect Answers

B:

A grand total cannot identify which contractor.r or host requires investigation after risk is aggregated.

C:

Considering entity-behavior risk evaluation at West Operations: Collector grouping describes ingestion infrastructure rather than the identity whose behavior and risk must be evaluated.

D:

Under entity-behavior risk evaluation at West Operations: Timestamps cannot establish stable identity across VPN, identity-provider and other event sources for a UEBA investigation.

Question 710

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

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

Explanation

Correct Answer

D:

Filtering the precise host-96 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 Corporate HQ for host-96: Loss of endpoint process alerts telemetry destroys valuable investigation evidence and prevents other related detections.

B:

For incident-management case at Corporate HQ for host-96: The meaning of a later suspicious launch event can change; bulk preclassification bypasses necessary evidence review.

C:

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

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