Practice Exams:

Fortinet FCP_FAZ_AN-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst
Verified By Experts
Premium Bundle
$49.99

FCP_FAZ_AN-7.6 Premium ETE File


  • Premium File 63 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FAZ_AN-7.6 Practice Test 43

Question 420

A hospital security team needs an alert only when related endpoint and firewall indicators form a defined sequence. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Validate using: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.
  2. Choose this FortiAnalyzer analyst action: Limit the handler to its intended logging devices or device groups and test its scope before production activation. Validate using: Send matching harmless test logs from a payment device and a guest device and confirm only the authorized target produces an alert.
  3. Choose this FortiAnalyzer analyst action: Link the relevant events and raw log context to a single incident analysis case with a traceable time range. Validate using: Open a harmless incident and verify that selected event records link back to their original device logs and correct time window.
  4. Choose this FortiAnalyzer analyst action: Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Validate using: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated.

Answer & Explanations

Correct answer: D

A.

Choose this FortiAnalyzer analyst action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Validate using: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. This action-and-test pairing concerns another situation: A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. The current case needs this action: Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Test with: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated.

B.

Choose this FortiAnalyzer analyst action: Limit the handler to its intended logging devices or device groups and test its scope before production activation. Validate using: Send matching harmless test logs from a payment device and a guest device and confirm only the authorized target produces an alert. This action-and-test pairing concerns another situation: A regional retailer adds a payment-card detection rule but its FortiAnalyzer domain includes public guest kiosks as well. The current case needs this action: Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Test with: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated.

C.

Choose this FortiAnalyzer analyst action: Link the relevant events and raw log context to a single incident analysis case with a traceable time range. Validate using: Open a harmless incident and verify that selected event records link back to their original device logs and correct time window. This action-and-test pairing concerns another situation: A university security team sees several firewall detections from one suspicious workstation and needs a case with source evidence. The current case needs this action: Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Test with: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated.

D.

Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Check the result: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated. The technical reason is: Correlation handlers can analyze specified patterns across observations whereas a simple one-record predicate does not represent multi-stage behavior. The fictional case is: A hospital security team needs an alert only when related endpoint and firewall indicators form a defined sequence.

Question 421

A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Link the relevant events and raw log context to a single incident analysis case with a traceable time range.
  2. Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged.
  3. Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.
  4. Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

Answer & Explanations

Correct answer: D

A.

Link the relevant events and raw log context to a single incident analysis case with a traceable time range. That action is relevant to a different problem: A university security team sees several firewall detections from one suspicious workstation and needs a case with source evidence. Its technical basis is: Incident analysis can organize related detections while preserving the log evidence required to justify scope, cause, and disposition. The present case instead requires: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

B.

Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged. That action is relevant to a different problem: A bank SOC approves automatic case opening for confirmed malware quarantine events but its handler currently generates only events. Its technical basis is: FortiAnalyzer supports automatic incident generation from matching events when its incident-creation option is explicitly enabled. The present case instead requires: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

C.

Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. That action is relevant to a different problem: A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. Its technical basis is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. The present case instead requires: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

D.

Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. The technical reason is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. Confirm by: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

Question 422

A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. The reviewed recommendation is: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. FortiAnalyzer events and Fabric automation mechanisms require a functioning matching trigger and authorized downstream action to produce a real response.
  2. Basic event handlers evaluate defined log predicates against eligible data and cannot trigger when the target source fields never match.
  3. Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense.
  4. Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages.

Answer & Explanations

Correct answer: C

A.

FortiAnalyzer events and Fabric automation mechanisms require a functioning matching trigger and authorized downstream action to produce a real response. That principle explains a different situation: A retail chain wants its FortiGate Fabric automation stitch to react to a specific approved high-confidence FortiAnalyzer event. Here the relevant cause is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. Apply it by: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

B.

Basic event handlers evaluate defined log predicates against eligible data and cannot trigger when the target source fields never match. That principle explains a different situation: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. Here the relevant cause is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. Apply it by: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

C.

Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. It explains why the intervention—configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts—addresses the stated problem. Test the mechanism by: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

D.

Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. That principle explains a different situation: A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. Here the relevant cause is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. Apply it by: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

Question 423

A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. The reviewed recommendation is: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Which observation best demonstrates that this corrective step worked?

  1. Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.
  2. Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.
  3. Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated.
  4. Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

Answer & Explanations

Correct answer: A

A.

Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. This directly tests whether the chosen intervention works: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. The causal mechanism is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense.

B.

Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. That test is for another requirement: A hospital turns off a noisy custom event handler and later assumes the branch firewalls have stopped logging entirely. It does not verify the stated outcome; the relevant check is: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

C.

Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated. That test is for another requirement: A bank SOC wants to detect suspicious logins followed by sensitive network access within a short investigation window. It does not verify the stated outcome; the relevant check is: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

D.

Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity. That test is for another requirement: A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. It does not verify the stated outcome; the relevant check is: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

Question 424

A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. Which unsafe investigation or automation shortcut must be rejected?

  1. Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events.
  2. Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged.
  3. Remove the threshold and open a critical incident for every single log line with the matching severity.
  4. Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

Answer & Explanations

Correct answer: C

A.

Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. That is an appropriate action for the separate case: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. It is not the unsafe shortcut asked about here. Reject: Remove the threshold and open a critical incident for every single log line with the matching severity. Its risk is: The SOC is flooded with routine repeated traffic while a meaningful burst pattern loses visibility.

B.

Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged. That is an appropriate action for the separate case: A bank SOC approves automatic case opening for confirmed malware quarantine events but its handler currently generates only events. It is not the unsafe shortcut asked about here. Reject: Remove the threshold and open a critical incident for every single log line with the matching severity. Its risk is: The SOC is flooded with routine repeated traffic while a meaningful burst pattern loses visibility.

C.

Remove the threshold and open a critical incident for every single log line with the matching severity. The risk is: The SOC is flooded with routine repeated traffic while a meaningful burst pattern loses visibility. The safer action is: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Confirm by: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

D.

Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. That is an appropriate action for the separate case: A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. It is not the unsafe shortcut asked about here. Reject: Remove the threshold and open a critical incident for every single log line with the matching severity. Its risk is: The SOC is flooded with routine repeated traffic while a meaningful burst pattern loses visibility.

Question 425

A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Validate using: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.
  2. Choose this FortiAnalyzer analyst action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Validate using: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.
  3. Choose this FortiAnalyzer analyst action: Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements. Validate using: Generate a benign test event and trace the stitch trigger, targeted action, and confirmation record in the respective products.
  4. Choose this FortiAnalyzer analyst action: Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Validate using: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Validate using: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator. This action-and-test pairing concerns another situation: A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. The current case needs this action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Test with: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

B.

Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Check the result: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. The technical reason is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense.

C.

Choose this FortiAnalyzer analyst action: Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements. Validate using: Generate a benign test event and trace the stitch trigger, targeted action, and confirmation record in the respective products. This action-and-test pairing concerns another situation: A retail chain wants its FortiGate Fabric automation stitch to react to a specific approved high-confidence FortiAnalyzer event. The current case needs this action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Test with: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

D.

Choose this FortiAnalyzer analyst action: Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Validate using: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated. This action-and-test pairing concerns another situation: A bank SOC wants to detect suspicious logins followed by sensitive network access within a short investigation window. The current case needs this action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Test with: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

Question 426

A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account. What is the most defensible FortiAnalyzer action in this situation?

  1. Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged.
  2. Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.
  3. Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events.
  4. Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

Answer & Explanations

Correct answer: D

A.

Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged. That action is relevant to a different problem: A bank SOC approves automatic case opening for confirmed malware quarantine events but its handler currently generates only events. Its technical basis is: FortiAnalyzer supports automatic incident generation from matching events when its incident-creation option is explicitly enabled. The present case instead requires: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

B.

Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. That action is relevant to a different problem: A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. Its technical basis is: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. The present case instead requires: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

C.

Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. That action is relevant to a different problem: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. Its technical basis is: Basic event handlers evaluate defined log predicates against eligible data and cannot trigger when the target source fields never match. The present case instead requires: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

D.

Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. The technical reason is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. Confirm by: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

Question 427

A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account. The reviewed recommendation is: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Predefined handlers may restrict editing of core logic whereas custom clones permit controlled tailoring without changing the original baseline.
  2. Basic event handlers evaluate defined log predicates against eligible data and cannot trigger when the target source fields never match.
  3. Event-handler configuration must match the eligible data source selection and one ADOM can contain several unrelated monitoring populations.
  4. Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense.

Answer & Explanations

Correct answer: D

A.

Predefined handlers may restrict editing of core logic whereas custom clones permit controlled tailoring without changing the original baseline. That principle explains a different situation: A university needs a narrower scan detector than the installed default handler and wants to preserve the vendor reference rule. Here the relevant cause is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. Apply it by: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

B.

Basic event handlers evaluate defined log predicates against eligible data and cannot trigger when the target source fields never match. That principle explains a different situation: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. Here the relevant cause is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. Apply it by: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

C.

Event-handler configuration must match the eligible data source selection and one ADOM can contain several unrelated monitoring populations. That principle explains a different situation: A regional retailer adds a payment-card detection rule but its FortiAnalyzer domain includes public guest kiosks as well. Here the relevant cause is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. Apply it by: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

D.

Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. It explains why the intervention—configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts—addresses the stated problem. Test the mechanism by: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

Question 428

A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account. The reviewed recommendation is: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. What pilot verification directly establishes the intended result?

  1. Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.
  2. Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.
  3. Send matching harmless test logs from a payment device and a guest device and confirm only the authorized target produces an alert.
  4. Generate a benign test event and trace the stitch trigger, targeted action, and confirmation record in the respective products.

Answer & Explanations

Correct answer: B

A.

Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity. That test is for another requirement: A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. It does not verify the stated outcome; the relevant check is: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

B.

Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. This directly tests whether the chosen intervention works: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. The causal mechanism is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

C.

Send matching harmless test logs from a payment device and a guest device and confirm only the authorized target produces an alert. That test is for another requirement: A regional retailer adds a payment-card detection rule but its FortiAnalyzer domain includes public guest kiosks as well. It does not verify the stated outcome; the relevant check is: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

D.

Generate a benign test event and trace the stitch trigger, targeted action, and confirmation record in the respective products. That test is for another requirement: A retail chain wants its FortiGate Fabric automation stitch to react to a specific approved high-confidence FortiAnalyzer event. It does not verify the stated outcome; the relevant check is: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

Question 429

A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account. Which tempting SOC change would undermine the stated requirement?

  1. Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events.
  2. Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.
  3. Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation.
  4. Remove the threshold and open a critical incident for every single log line with the matching severity.

Answer & Explanations

Correct answer: D

A.

Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. That is an appropriate action for the separate case: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. It is not the unsafe shortcut asked about here. Reject: Remove the threshold and open a critical incident for every single log line with the matching severity. Its risk is: The SOC is flooded with routine repeated traffic while a meaningful burst pattern loses visibility. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

B.

Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. That is an appropriate action for the separate case: A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. It is not the unsafe shortcut asked about here. Reject: Remove the threshold and open a critical incident for every single log line with the matching severity. Its risk is: The SOC is flooded with routine repeated traffic while a meaningful burst pattern loses visibility.

C.

Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. That is an appropriate action for the separate case: A university needs a narrower scan detector than the installed default handler and wants to preserve the vendor reference rule. It is not the unsafe shortcut asked about here. Reject: Remove the threshold and open a critical incident for every single log line with the matching severity. Its risk is: The SOC is flooded with routine repeated traffic while a meaningful burst pattern loses visibility.

D.

Remove the threshold and open a critical incident for every single log line with the matching severity. The risk is: The SOC is flooded with routine repeated traffic while a meaningful burst pattern loses visibility. The safer action is: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Confirm by: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

Question 430

A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Validate using: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.
  2. Choose this FortiAnalyzer analyst action: Compare the playbook trigger's exact event or incident field filters against a real qualifying record and verify the playbook is enabled. Validate using: Create a benign event with known attributes and verify a matching filter starts one job while a nonmatching event does not.
  3. Choose this FortiAnalyzer analyst action: Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. Validate using: Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences.
  4. Choose this FortiAnalyzer analyst action: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Validate using: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

Answer & Explanations

Correct answer: A

A.

Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Check the result: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. The technical reason is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. The fictional case is: A hospital has a possible brute-force event detector that should trigger only after several failures on the same affected account.

B.

Choose this FortiAnalyzer analyst action: Compare the playbook trigger's exact event or incident field filters against a real qualifying record and verify the playbook is enabled. Validate using: Create a benign event with known attributes and verify a matching filter starts one job while a nonmatching event does not. This action-and-test pairing concerns another situation: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. The current case needs this action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Test with: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

C.

Choose this FortiAnalyzer analyst action: Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. Validate using: Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences. This action-and-test pairing concerns another situation: A university needs a narrower scan detector than the installed default handler and wants to preserve the vendor reference rule. The current case needs this action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Test with: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

D.

Choose this FortiAnalyzer analyst action: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Validate using: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. This action-and-test pairing concerns another situation: A hospital turns off a noisy custom event handler and later assumes the branch firewalls have stopped logging entirely. The current case needs this action: Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. Test with: Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.

Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst (FCP_FAZ_AN-7.6) Practice Tests