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 54

Question 530

A hospital analyst needs to attach a targeted FortiAnalyzer report to an incident so the next shift can verify the same host evidence. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  3. Choose this FortiAnalyzer analyst action: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Validate using: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.
  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: A

A.

Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format. Check the result: Attach a test PDF report to a synthetic incident and verify its selected device and time period reproduce the reported observations. The technical reason is: Incidents can reference generated reports that summarize supporting evidence, allowing a reviewer to trace the same investigation data. The fictional case is: A hospital analyst needs to attach a targeted FortiAnalyzer report to an incident so the next shift can verify the same host evidence.

B.

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: Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format. Test with: Attach a test PDF report to a synthetic incident and verify its selected device and time period reproduce the reported observations.

C.

Choose this FortiAnalyzer analyst action: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Validate using: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. This action-and-test pairing concerns another situation: A retail bank sees a FortiGuard suspicious IP in an enrichment pane and needs to confirm a local flow to that address actually occurred. The current case needs this action: Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format. Test with: Attach a test PDF report to a synthetic incident and verify its selected device and time period reproduce the reported observations.

D.

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. This action-and-test pairing concerns another situation: A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. The current case needs this action: Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format. Test with: Attach a test PDF report to a synthetic incident and verify its selected device and time period reproduce the reported observations.

Question 531

A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.
  2. Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions.
  3. Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements.
  4. Verify connector account permissions and supported action authorization on the exact target device before changing the playbook definition.

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. The technical reason is: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. Confirm by: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

B.

Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. That action is relevant to a different problem: A bank SOC wants to detect suspicious logins followed by sensitive network access within a short investigation window. Its technical basis is: Correlation handlers can analyze specified patterns across observations whereas a simple one-record predicate does not represent multi-stage behavior. The present case instead requires: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

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: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

D.

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: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

Question 532

A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. The reviewed recommendation is: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Variable mapping translates alert context into remote action parameters and swapping endpoint roles can redirect a legitimate response.
  2. A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run.
  3. FortiAnalyzer events and Fabric automation mechanisms require a functioning matching trigger and authorized downstream action to produce a real response.
  4. A timeout does not prove that an earlier API operation failed and blind retries can duplicate state changes or notifications.

Answer & Explanations

Correct answer: B

A.

Variable mapping translates alert context into remote action parameters and swapping endpoint roles can redirect a legitimate response. That principle explains a different situation: A bank firewall playbook blocks its payment processor after reading a destination IP as the malicious source indicator. Here the relevant cause is: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. Apply it by: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

B.

A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. It explains why the intervention—choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy—addresses the stated problem. Test the mechanism by: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

C.

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: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. Apply it by: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

D.

A timeout does not prove that an earlier API operation failed and blind retries can duplicate state changes or notifications. That principle explains a different situation: A hospital playbook times out after a firewall API call and must confirm whether the destination was already blocked before retrying. Here the relevant cause is: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. Apply it by: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

Question 533

A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. The reviewed recommendation is: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Which observation best demonstrates that this corrective step worked?

  1. Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event.
  2. Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.
  3. Run a harmless on-demand test that creates a sample incident and triggers a scoped report through authorized local connector tasks.
  4. Simulate a delayed successful test action and verify the retry path detects existing state instead of producing duplicate artifacts.

Answer & Explanations

Correct answer: B

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 harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

B.

Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator. This directly tests whether the chosen intervention works: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. The causal mechanism is: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run.

C.

Run a harmless on-demand test that creates a sample incident and triggers a scoped report through authorized local connector tasks. That test is for another requirement: A bank automates incident evidence collection but has not recognized the FortiAnalyzer local connector's report action. It does not verify the stated outcome; the relevant check is: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

D.

Simulate a delayed successful test action and verify the retry path detects existing state instead of producing duplicate artifacts. That test is for another requirement: A hospital playbook times out after a firewall API call and must confirm whether the destination was already blocked before retrying. It does not verify the stated outcome; the relevant check is: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

Question 534

A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. Which unsafe investigation or automation shortcut must be rejected?

  1. Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration.
  2. Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.
  3. Compare the playbook trigger's exact event or incident field filters against a real qualifying record and verify the playbook is enabled.
  4. Add explicit pre-action state verification and outcome logging before retrying actions that must be safe and repeatable.

Answer & Explanations

Correct answer: A

A.

Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration. The risk is: Authorized response tasks do not run and the incident remains untriaged despite apparently complete automation diagrams. The safer action is: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Confirm by: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

B.

Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. That is an appropriate action for the separate case: A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. It is not the unsafe shortcut asked about here. Reject: Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration. Its risk is: Authorized response tasks do not run and the incident remains untriaged despite apparently complete automation diagrams.

C.

Compare the playbook trigger's exact event or incident field filters against a real qualifying record and verify the playbook is enabled. That is an appropriate action for the separate case: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. It is not the unsafe shortcut asked about here. Reject: Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration. Its risk is: Authorized response tasks do not run and the incident remains untriaged despite apparently complete automation diagrams.

D.

Add explicit pre-action state verification and outcome logging before retrying actions that must be safe and repeatable. That is an appropriate action for the separate case: A hospital playbook times out after a firewall API call and must confirm whether the destination was already blocked before retrying. It is not the unsafe shortcut asked about here. Reject: Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration. Its risk is: Authorized response tasks do not run and the incident remains untriaged despite apparently complete automation diagrams.

Question 535

A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. 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: 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: Add explicit pre-action state verification and outcome logging before retrying actions that must be safe and repeatable. Validate using: Simulate a delayed successful test action and verify the retry path detects existing state instead of producing duplicate artifacts.
  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: 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.

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: 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: Add explicit pre-action state verification and outcome logging before retrying actions that must be safe and repeatable. Validate using: Simulate a delayed successful test action and verify the retry path detects existing state instead of producing duplicate artifacts. This action-and-test pairing concerns another situation: A hospital playbook times out after a firewall API call and must confirm whether the destination was already blocked before retrying. 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: 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. This action-and-test pairing concerns another situation: A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. 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 536

A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured. What is the most defensible FortiAnalyzer action in this situation?

  1. Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.
  2. Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action.
  3. Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions.
  4. Add explicit pre-action state verification and outcome logging before retrying actions that must be safe and repeatable.

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. The technical reason is: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. Confirm by: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator. The fictional case is: A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured.

B.

Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action. That action is relevant to a different problem: A bank firewall playbook blocks its payment processor after reading a destination IP as the malicious source indicator. Its technical basis is: Variable mapping translates alert context into remote action parameters and swapping endpoint roles can redirect a legitimate response. The present case instead requires: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

C.

Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. That action is relevant to a different problem: A bank SOC wants to detect suspicious logins followed by sensitive network access within a short investigation window. Its technical basis is: Correlation handlers can analyze specified patterns across observations whereas a simple one-record predicate does not represent multi-stage behavior. The present case instead requires: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. The fictional case is: A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured.

D.

Add explicit pre-action state verification and outcome logging before retrying actions that must be safe and repeatable. That action is relevant to a different problem: A hospital playbook times out after a firewall API call and must confirm whether the destination was already blocked before retrying. Its technical basis is: A timeout does not prove that an earlier API operation failed and blind retries can duplicate state changes or notifications. The present case instead requires: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

Question 537

A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured. The reviewed recommendation is: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results.
  2. A timeout does not prove that an earlier API operation failed and blind retries can duplicate state changes or notifications.
  3. Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting.
  4. A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run.

Answer & Explanations

Correct answer: D

A.

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: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. Apply it by: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

B.

A timeout does not prove that an earlier API operation failed and blind retries can duplicate state changes or notifications. That principle explains a different situation: A hospital playbook times out after a firewall API call and must confirm whether the destination was already blocked before retrying. Here the relevant cause is: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. Apply it by: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. The fictional case is: A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured.

C.

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: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. Apply it by: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.

D.

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

Question 538

A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured. The reviewed recommendation is: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. What pilot verification directly establishes the intended result?

  1. Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.
  2. Use a test FortiGate and permitted dummy indicator to verify the connector can perform only the authorized response action.
  3. Generate a benign test event and trace the stitch trigger, targeted action, and confirmation record in the respective products.
  4. 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: A

A.

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

Use a test FortiGate and permitted dummy indicator to verify the connector can perform only the authorized response action. That test is for another requirement: A hospital security team wants approved FortiAnalyzer playbook actions to update one branch firewall but not other clinics. It does not verify the stated outcome; the relevant check is: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

C.

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 harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

D.

Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. That test is for another requirement: A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. It does not verify the stated outcome; the relevant check is: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator.

Question 539

A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured. Which tempting SOC change would undermine the stated requirement?

  1. Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions.
  2. Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions.
  3. Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements.
  4. Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration.

Answer & Explanations

Correct answer: D

A.

Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. That is an appropriate action for the separate case: A bank SOC wants to detect suspicious logins followed by sensitive network access within a short investigation window. It is not the unsafe shortcut asked about here. Reject: Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration. Its risk is: Authorized response tasks do not run and the incident remains untriaged despite apparently complete automation diagrams.

B.

Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions. That is an appropriate action for the separate case: A hospital security team wants approved FortiAnalyzer playbook actions to update one branch firewall but not other clinics. It is not the unsafe shortcut asked about here. Reject: Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration. Its risk is: Authorized response tasks do not run and the incident remains untriaged despite apparently complete automation diagrams.

C.

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: Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration. Its risk is: Authorized response tasks do not run and the incident remains untriaged despite apparently complete automation diagrams.

D.

Assume any playbook saved to the library executes whenever any raw log arrives regardless of trigger configuration. The risk is: Authorized response tasks do not run and the incident remains untriaged despite apparently complete automation diagrams. The safer action is: Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. Confirm by: Generate a harmless qualifying event and confirm the event-triggered playbook creates a job while the manual version waits for an operator. The fictional case is: A university analyst expects a saved playbook to act on suspicious DNS events although no event trigger was configured.

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.

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