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 55

Question 540

A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured. Which combined analytic action and validation test best solve this case?

  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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Validate using: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action. Validate using: Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement.

Answer & Explanations

Correct answer: A

A.

Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Check the result: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator. The technical reason is: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. The fictional case is: A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured.

B.

Choose this FortiAnalyzer analyst action: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Validate using: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. This action-and-test pairing concerns another situation: A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. The current case needs this action: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Test with: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

C.

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: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Test with: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

D.

Choose this FortiAnalyzer analyst action: Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action. Validate using: Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement. This action-and-test pairing concerns another situation: A bank firewall playbook blocks its payment processor after reading a destination IP as the malicious source indicator. The current case needs this action: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Test with: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

Question 541

A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Compare the playbook trigger's exact event or incident field filters against a real qualifying record and verify the playbook is enabled.
  2. Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.
  3. Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements.
  4. Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

Answer & Explanations

Correct answer: D

A.

Compare the playbook trigger's exact event or incident field filters against a real qualifying record and verify the playbook is enabled. That action is relevant to a different problem: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. Its technical basis is: Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting. The present case instead requires: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

B.

Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. That action is relevant to a different problem: A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. Its technical basis is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. The present case instead requires: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

C.

Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements. That action is relevant to a different problem: A retail chain wants its FortiGate Fabric automation stitch to react to a specific approved high-confidence FortiAnalyzer event. Its technical basis is: FortiAnalyzer events and Fabric automation mechanisms require a functioning matching trigger and authorized downstream action to produce a real response. The present case instead requires: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

D.

Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. The technical reason is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. Confirm by: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

Question 542

A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. The reviewed recommendation is: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages.
  2. Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting.
  3. Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results.
  4. Incidents can reference generated reports that summarize supporting evidence, allowing a reviewer to trace the same investigation data.

Answer & Explanations

Correct answer: A

A.

Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. It explains why the intervention—select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case—addresses the stated problem. Test the mechanism by: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

B.

Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting. That principle explains a different situation: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. Here the relevant cause is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. Apply it by: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

C.

Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. That principle explains a different situation: A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. Here the relevant cause is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. Apply it by: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

D.

Incidents can reference generated reports that summarize supporting evidence, allowing a reviewer to trace the same investigation data. That principle explains a different situation: A university SOC prepares a one-day firewall report for an active incident and wants the PDF linked to the analyst case. Here the relevant cause is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. Apply it by: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

Question 543

A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. The reviewed recommendation is: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Which observation best demonstrates that this corrective step worked?

  1. Open a harmless incident and verify that selected event records link back to their original device logs and correct time window.
  2. Create a benign event with known attributes and verify a matching filter starts one job while a nonmatching event does not.
  3. Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.
  4. Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

Answer & Explanations

Correct answer: C

A.

Open a harmless incident and verify that selected event records link back to their original device logs and correct time window. That test is for another requirement: A university security team sees several firewall detections from one suspicious workstation and needs a case with source evidence. It does not verify the stated outcome; the relevant check is: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

B.

Create a benign event with known attributes and verify a matching filter starts one job while a nonmatching event does not. That test is for another requirement: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. It does not verify the stated outcome; the relevant check is: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

C.

Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. This directly tests whether the chosen intervention works: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. The causal mechanism is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages.

D.

Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator. That test is for another requirement: A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. It does not verify the stated outcome; the relevant check is: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

Question 544

A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. Which unsafe investigation or automation shortcut must be rejected?

  1. Trigger destructive remediation at raw-event creation and assume an incident review always occurred first.
  2. Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements.
  3. Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged.
  4. Use the built-in local FortiAnalyzer connector and select supported incident and report actions within the playbook.

Answer & Explanations

Correct answer: A

A.

Trigger destructive remediation at raw-event creation and assume an incident review always occurred first. The risk is: Response automation may modify assets before the event is assessed and before required approvals or enrichment are available. The safer action is: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Confirm by: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

B.

Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements. That is an appropriate action for the separate case: A retail chain wants its FortiGate Fabric automation stitch to react to a specific approved high-confidence FortiAnalyzer event. It is not the unsafe shortcut asked about here. Reject: Trigger destructive remediation at raw-event creation and assume an incident review always occurred first. Its risk is: Response automation may modify assets before the event is assessed and before required approvals or enrichment are available.

C.

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: Trigger destructive remediation at raw-event creation and assume an incident review always occurred first. Its risk is: Response automation may modify assets before the event is assessed and before required approvals or enrichment are available.

D.

Use the built-in local FortiAnalyzer connector and select supported incident and report actions within the playbook. That is an appropriate action for the separate case: A bank automates incident evidence collection but has not recognized the FortiAnalyzer local connector's report action. It is not the unsafe shortcut asked about here. Reject: Trigger destructive remediation at raw-event creation and assume an incident review always occurred first. Its risk is: Response automation may modify assets before the event is assessed and before required approvals or enrichment are available.

Question 545

A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. 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: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Validate using: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.
  3. Choose this FortiAnalyzer analyst action: Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions. Validate using: Use a test FortiGate and permitted dummy indicator to verify the connector can perform only the authorized response action.
  4. Choose this FortiAnalyzer analyst action: Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged. Validate using: Trigger a non-destructive test event and verify it creates one correctly scoped incident with the expected source evidence.

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: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Test with: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

B.

Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Check the result: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. The technical reason is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages.

C.

Choose this FortiAnalyzer analyst action: Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions. Validate using: Use a test FortiGate and permitted dummy indicator to verify the connector can perform only the authorized response action. This action-and-test pairing concerns another situation: A hospital security team wants approved FortiAnalyzer playbook actions to update one branch firewall but not other clinics. The current case needs this action: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Test with: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

D.

Choose this FortiAnalyzer analyst action: Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged. Validate using: Trigger a non-destructive test event and verify it creates one correctly scoped incident with the expected source evidence. This action-and-test pairing concerns another situation: A bank SOC approves automatic case opening for confirmed malware quarantine events but its handler currently generates only events. The current case needs this action: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Test with: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

Question 546

A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events. What is the most defensible FortiAnalyzer action in this situation?

  1. Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.
  2. Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions.
  3. Verify connector account permissions and supported action authorization on the exact target device before changing the playbook definition.
  4. Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

Answer & Explanations

Correct answer: D

A.

Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. That action is relevant to a different problem: A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. Its technical basis is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. The present case instead requires: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

B.

Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions. That action is relevant to a different problem: A hospital security team wants approved FortiAnalyzer playbook actions to update one branch firewall but not other clinics. Its technical basis is: Remote automation needs both connector connectivity and authority on the target device; a local FortiAnalyzer event does not confer firewall permissions. The present case instead requires: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

C.

Verify connector account permissions and supported action authorization on the exact target device before changing the playbook definition. That action is relevant to a different problem: A regional bank can query one FortiGate through a connector but policy-block tasks are denied by its API permissions. Its technical basis is: Transport reachability confirms only a session path while remote API operations still require valid credentials and sufficient scope. The present case instead requires: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

D.

Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. The technical reason is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. Confirm by: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

Question 547

A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events. The reviewed recommendation is: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. What FortiAnalyzer mechanism supports the recommended analysis?

  1. FortiAnalyzer supports automatic incident generation from matching events when its incident-creation option is explicitly enabled.
  2. A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run.
  3. Incidents can reference generated reports that summarize supporting evidence, allowing a reviewer to trace the same investigation data.
  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: D

A.

FortiAnalyzer supports automatic incident generation from matching events when its incident-creation option is explicitly enabled. That principle explains a different situation: A bank SOC approves automatic case opening for confirmed malware quarantine events but its handler currently generates only events. Here the relevant cause is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. Apply it by: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

B.

A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. That principle explains a different situation: A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. Here the relevant cause is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. Apply it by: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.

C.

Incidents can reference generated reports that summarize supporting evidence, allowing a reviewer to trace the same investigation data. That principle explains a different situation: A university SOC prepares a one-day firewall report for an active incident and wants the PDF linked to the analyst case. Here the relevant cause is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. Apply it by: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

D.

Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. It explains why the intervention—select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case—addresses the stated problem. Test the mechanism by: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

Question 548

A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events. The reviewed recommendation is: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. What pilot verification directly establishes the intended result?

  1. Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event.
  2. Create a benign event with known attributes and verify a matching filter starts one job while a nonmatching event does not.
  3. Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.
  4. Open a harmless incident and verify that selected event records link back to their original device logs and correct time window.

Answer & Explanations

Correct answer: C

A.

Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event. That test is for another requirement: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. It does not verify the stated outcome; the relevant check is: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

B.

Create a benign event with known attributes and verify a matching filter starts one job while a nonmatching event does not. That test is for another requirement: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. It does not verify the stated outcome; the relevant check is: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

C.

Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. This directly tests whether the chosen intervention works: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. The causal mechanism is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

D.

Open a harmless incident and verify that selected event records link back to their original device logs and correct time window. That test is for another requirement: A university security team sees several firewall detections from one suspicious workstation and needs a case with source evidence. It does not verify the stated outcome; the relevant check is: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

Question 549

A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events. Which tempting SOC change would undermine the stated requirement?

  1. Trigger destructive remediation at raw-event creation and assume an incident review always occurred first.
  2. Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.
  3. Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events.
  4. Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged.

Answer & Explanations

Correct answer: A

A.

Trigger destructive remediation at raw-event creation and assume an incident review always occurred first. The risk is: Response automation may modify assets before the event is assessed and before required approvals or enrichment are available. The safer action is: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Confirm by: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

B.

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: Trigger destructive remediation at raw-event creation and assume an incident review always occurred first. Its risk is: Response automation may modify assets before the event is assessed and before required approvals or enrichment are available.

C.

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: Trigger destructive remediation at raw-event creation and assume an incident review always occurred first. Its risk is: Response automation may modify assets before the event is assessed and before required approvals or enrichment are available.

D.

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: Trigger destructive remediation at raw-event creation and assume an incident review always occurred first. Its risk is: Response automation may modify assets before the event is assessed and before required approvals or enrichment are available. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

Question 550

A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action. Validate using: Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement.
  2. Choose this FortiAnalyzer analyst action: Use the built-in local FortiAnalyzer connector and select supported incident and report actions within the playbook. Validate using: Run a harmless on-demand test that creates a sample incident and triggers a scoped report through authorized local connector tasks.
  3. Choose this FortiAnalyzer analyst action: Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format. Validate using: Attach a test PDF report to a synthetic incident and verify its selected device and time period reproduce the reported observations.
  4. Choose this FortiAnalyzer analyst action: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Validate using: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

Answer & Explanations

Correct answer: D

A.

Choose this FortiAnalyzer analyst action: Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action. Validate using: Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement. This action-and-test pairing concerns another situation: A bank firewall playbook blocks its payment processor after reading a destination IP as the malicious source indicator. The current case needs this action: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Test with: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

B.

Choose this FortiAnalyzer analyst action: Use the built-in local FortiAnalyzer connector and select supported incident and report actions within the playbook. Validate using: Run a harmless on-demand test that creates a sample incident and triggers a scoped report through authorized local connector tasks. This action-and-test pairing concerns another situation: A bank automates incident evidence collection but has not recognized the FortiAnalyzer local connector's report action. The current case needs this action: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Test with: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

C.

Choose this FortiAnalyzer analyst action: Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format. Validate using: Attach a test PDF report to a synthetic incident and verify its selected device and time period reproduce the reported observations. This action-and-test pairing concerns another situation: A university SOC prepares a one-day firewall report for an active incident and wants the PDF linked to the analyst case. The current case needs this action: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Test with: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.

D.

Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Check the result: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. The technical reason is: Incident triggers operate on incident creation conditions while event triggers operate on generated events and can represent different escalation stages. The fictional case is: A retail SOC automates triage for assigned incident cases but accidentally launches the workflow on all low-level events.

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