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

Question 690

The City Branch performance report for host-60 and peer systems needs hosts whose average CPU is at least 30% AND whose average memory utilization is at least 35%. How should FortiSIEM limit the aggregate output?

  1. Use event keywords CPU and Memory with no aggregation
  2. Use AVG(CPU Util) >= 30 AND AVG(Memory Util) >= 35 as Display Conditions
  3. Use OR between the two aggregate thresholds
  4. Group only by event timestamp and discard host identity

Explanation

Correct Answer

B:

For aggregate-query calculation at City Branch for host-60: 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-60: Keywords do not compute per-host averages; individual messages do not prove that either mean crosses the specified limits.

C:

Considering aggregate-query calculation at City Branch for host-60: An OR permits a host with only high CPU or only high memory, contrary to the two simultaneous City Branch requirements.

D:

Under aggregate-query calculation at City Branch for host-60: Timestamp buckets cannot establish which host breached both mean-utilization thresholds, which is central to this performance report.

Question 691

FortiSIEM raises a new policy denial incident on host-19 for Research. No investigation has occurred. What are the initial status and resolution fields expected for that incident?

  1. Status Manually Cleared; Resolution True Positive
  2. Status Active; Resolution None
  3. Status System Cleared; Resolution False Positive
  4. Status Active; Resolution False Positive

Explanation

Correct Answer

B:

A newly triggered incident starts Active with no verdict. The Research analyst must investigate before classifying the policy denial finding as true or false positive.

Incorrect Answers

A:

That describes a verified, manually resolved real issue, not an untriaged alert that just fired on host-19.

C:

Considering incident-management case at Research for host-19: System clearing follows a configured recovery condition and does not represent the initial new-incident state.

D:

Under incident-management case at Research for host-19: Assigning a false-positive classification before investigation asserts a conclusion that the freshly generated policy denial alert has not earned.

Question 692

The Cloud Services SOC is designing a rotating team to handle assigned deny cases. Which FortiSIEM setup enables assignment to the right analysts and team leads?

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

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

In incident-management case at Cloud Services: Log facility values characterize messages, not human case-assignment permissions or team structure.

C:

Considering incident-management case at Cloud Services: Network address translation does not register eligible investigators or define case ownership.

D:

Grouping data does not define analyst membership, leads or work queues for cases in Cloud Services.

Question 693

Research needs blocked lookup events from DNS resolution records only when their device belongs to a CMDB list of critical host-39-class systems. Which nested search direction retains the event details?

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

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 blocked lookup rows.

Incorrect Answers

A:

That would produce devices as rows and cannot by itself display the full outer DNS resolution records event details requested.

B:

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

D:

Under nested search comparison at Research for host-39 using DNS resolution records: Notification emails do not establish a typed membership comparison between CMDB devices and event attributes.

Question 694

Corporate HQ wants to distinguish the busiest Source IP by events in a gateway denies query. A single source has 17 records spread across three Destination IP values with counts 6, 8, and 3. Which statistic will rank sources by traffic-event frequency?

  1. SUM(Source Port) across all sources
  2. COUNT(Matched Events) grouped by source
  3. AVG(CPU Util) grouped by source
  4. COUNT(DISTINCT Destination IP) grouped by source

Explanation

Correct Answer

B:

This measures 17 matching rows for the source, including repeats to the three destinations, which is the frequency metric requested.

Incorrect Answers

A:

In aggregate-query calculation at Corporate HQ using gateway denies with the specified 17 value: Source ports are labels rather than additive traffic quantities. Summing them across the full search would not produce a meaningful per-source frequency.

C:

CPU measures resource utilization rather than the frequency of gateway denies events; it cannot rank sources by event traffic.

D:

Only three destination values exist. Distinct destination count is a fan-out metric and ignores the 17 individual event occurrences.

Question 695

An analyst at Logistics is watching newly arriving cloud API audit events for rejected request on host-178; the requirement is to see records as they are ingested, with no grouping. Which FortiSIEM search approach fits?

  1. Use a real-time search with a normalized event-attribute filter
  2. Run only a historical search against an earlier time interval
  3. Run a CMDB device search for host-178 as the sole data source
  4. Use a real-time search with a Group By aggregation

Explanation

Correct Answer

A:

Real-time search evaluates incoming events in the streaming path. A condition on the normalized rejected request indicator can expose matching records on host-178 without retrieving stored history.

Incorrect Answers

B:

Historical searches read events already persisted in the database. This misses the requirement to observe newly arriving cloud API audit events as ingestion occurs.

C:

CMDB is inventory and configuration data, not the live stream of cloud API audit events needed to inspect rejected request evidence.

D:

Under historical or real-time event analysis at Logistics for host-178 using cloud API audit events: FortiSIEM real-time search does not support Group By. Here the desired output is raw incoming events, not aggregate group counts.

Question 696

City Branch updated the log parser so the fields carrying process executions per account are normalized differently. What should be checked before trusting ongoing FortiSIEM inference?

  1. Verify the new input schema matches training features; retrain if the feature distribution changed
  2. Publish every anomalous observation automatically to every tenant
  3. Swap incident severity labels without inspecting the model
  4. Assume model confidence cannot change after training

Explanation

Correct Answer

A:

Model quality depends on consistent feature meaning. Parser changes can introduce missing fields or shift the process executions per account distribution, invalidating earlier comparisons.

Incorrect Answers

B:

Indiscriminate distribution bypasses data scope and does not test whether process executions per account features remain valid.

C:

Considering historical or real-time event analysis at City Branch: Severity is downstream triage metadata and cannot restore a missing or changed numeric input feature.

D:

Under historical or real-time event analysis at City Branch: A trained learner is not immune to input drift or an altered parser, so unverified predictions may be misleading.

Question 697

A FortiSIEM correlation design at City Branch observes P1 (stopped service in service health records) and P2 (a related action on host-109). It must require P1 and then P2 in that order. Which relationship operator best expresses that precise condition?

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

Explanation

Correct Answer

E:

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

Incorrect Answers

A:

In subpattern correlation at City Branch for host-109 using service health records: 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.

B:

For subpattern correlation at City Branch for host-109 using service health records: 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 City Branch for host-109 using service health records: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the City Branch event sequence.

D:

Under subpattern correlation at City Branch for host-109 using service health records: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended City Branch test.

Question 698

The Partner Services investigation tracks two events in gateway denies: 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 Source IP identity attributes of P1 and P2
  2. Only a larger incident title text field
  3. Removal of all grouping keys and inter-subpattern constraints
  4. A greater-than test between the two event message lengths

Explanation

Correct Answer

A:

In subpattern correlation at Partner Services using gateway denies: Inter-subpattern comparisons link matching entity keys across both behaviors. Requiring the same Source IP prevents a different user’s P2 from completing this sequence.

Incorrect Answers

B:

For subpattern correlation at Partner Services using gateway denies: Title length affects labeling and cannot prevent a P2 from another Source IP being joined to the first event.

C:

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

D:

Under subpattern correlation at Partner Services using gateway denies: Message length does not establish user or entity identity for the P1–P2 correlation.

Question 699

The East Retail investigation tracks two events in cloud API audit events: 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. Only a larger incident title text field
  2. Equality between the relevant User identity attributes of P1 and P2
  3. Removal of all grouping keys and inter-subpattern constraints
  4. A greater-than test between the two event message lengths

Explanation

Correct Answer

B:

For subpattern correlation at East Retail using cloud API audit events: Inter-subpattern comparisons link matching entity keys across both behaviors. Requiring the same User prevents a different user’s P2 from completing this sequence.

Incorrect Answers

A:

In subpattern correlation at East Retail using cloud API audit events: Title length affects labeling and cannot prevent a P2 from another User being joined to the first event.

C:

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

D:

Under subpattern correlation at East Retail using cloud API audit events: Message length does not establish user or entity identity for the P1–P2 correlation.

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.

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