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 58

Question 570

A bank SOC configures a FortiOS automation connector for indicator blocking and needs scoped authority before activating it. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. Choose this FortiAnalyzer analyst action: Verify connector account permissions and supported action authorization on the exact target device before changing the playbook definition. Validate using: Run one harmless authorized read or test action and compare its permission result with the failed write operation.
  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: 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.

Answer & Explanations

Correct answer: A

A.

Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions. Check the result: Use a test FortiGate and permitted dummy indicator to verify the connector can perform only the authorized response action. The technical reason is: Remote automation needs both connector connectivity and authority on the target device; a local FortiAnalyzer event does not confer firewall permissions. The fictional case is: A bank SOC configures a FortiOS automation connector for indicator blocking and needs scoped authority before activating it.

B.

Choose this FortiAnalyzer analyst action: Verify connector account permissions and supported action authorization on the exact target device before changing the playbook definition. Validate using: Run one harmless authorized read or test action and compare its permission result with the failed write operation. This action-and-test pairing concerns another situation: A regional bank can query one FortiGate through a connector but policy-block tasks are denied by its API permissions. The current case needs this action: Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions. Test with: Use a test FortiGate and permitted dummy indicator to verify the connector can perform only the authorized response action.

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: Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions. Test with: Use a test FortiGate and permitted dummy indicator to verify the connector can perform only the authorized response action. The fictional case is: A bank SOC configures a FortiOS automation connector for indicator blocking and needs scoped authority before activating it.

D.

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: Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions. Test with: Use a test FortiGate and permitted dummy indicator to verify the connector can perform only the authorized response action.

Question 571

A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Add the supported indicator and perform authorized enrichment against its correct type and original observed value.
  2. Use the built-in local FortiAnalyzer connector and select supported incident and report actions within the playbook.
  3. Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.
  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: C

A.

Add the supported indicator and perform authorized enrichment against its correct type and original observed value. That action is relevant to a different problem: A hospital detects contact with a new domain and wants the exact DNS value attached to its incident's indicator panel. Its technical basis is: Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data. The present case instead requires: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

B.

Use the built-in local FortiAnalyzer connector and select supported incident and report actions within the playbook. That action is relevant to a different problem: A bank automates incident evidence collection but has not recognized the FortiAnalyzer local connector's report action. Its technical basis is: Local connector actions can operate on FortiAnalyzer incidents and reports without requiring a remote FortiGate enforcement connector. The present case instead requires: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

C.

Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. The technical reason is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. Confirm by: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

D.

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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

Question 572

A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. The reviewed recommendation is: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results.
  2. An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality.
  3. A downstream task may be marked upstream_failed when its prerequisite could not complete, so the earliest failing step is the useful root cause.
  4. Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data.

Answer & Explanations

Correct answer: A

A.

Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. It explains why the intervention—connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them—addresses the stated problem. Test the mechanism by: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

B.

An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. That principle explains a different situation: A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. Here the relevant cause is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. Apply it by: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

C.

A downstream task may be marked upstream_failed when its prerequisite could not complete, so the earliest failing step is the useful root cause. That principle explains a different situation: A university's incident playbook shows an evidence task as upstream_failed after its threat-intelligence connector lost connectivity. Here the relevant cause is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. Apply it by: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

D.

Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data. That principle explains a different situation: A hospital detects contact with a new domain and wants the exact DNS value attached to its incident's indicator panel. Here the relevant cause is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. Apply it by: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

Question 573

A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. The reviewed recommendation is: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Which observation best demonstrates that this corrective step worked?

  1. Simulate a delayed successful test action and verify the retry path detects existing state instead of producing duplicate artifacts.
  2. Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain.
  3. Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.
  4. Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement.

Answer & Explanations

Correct answer: C

A.

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: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

B.

Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain. That test is for another requirement: A hospital detects contact with a new domain and wants the exact DNS value attached to its incident's indicator panel. It does not verify the stated outcome; the relevant check is: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

C.

Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. This directly tests whether the chosen intervention works: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. The causal mechanism is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results.

D.

Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement. That test is for another requirement: A bank firewall playbook blocks its payment processor after reading a destination IP as the malicious source indicator. It does not verify the stated outcome; the relevant check is: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

Question 574

A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. Which unsafe investigation or automation shortcut must be rejected?

  1. Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.
  2. Verify connector account permissions and supported action authorization on the exact target device before changing the playbook definition.
  3. Configure the supported FortiOS connector with a controlled authentication relationship and narrowly authorized device actions.
  4. Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions.

Answer & Explanations

Correct answer: D

A.

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: Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions. Its risk is: The response sends empty or stale indicators to connectors and automated actions fail or affect the wrong target.

B.

Verify connector account permissions and supported action authorization on the exact target device before changing the playbook definition. That is an appropriate action for the separate case: A regional bank can query one FortiGate through a connector but policy-block tasks are denied by its API permissions. It is not the unsafe shortcut asked about here. Reject: Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions. Its risk is: The response sends empty or stale indicators to connectors and automated actions fail or affect the wrong target.

C.

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: Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions. Its risk is: The response sends empty or stale indicators to connectors and automated actions fail or affect the wrong target.

D.

Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions. The risk is: The response sends empty or stale indicators to connectors and automated actions fail or affect the wrong target. The safer action is: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Confirm by: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

Question 575

A university builds a FortiAnalyzer playbook that queries an incident IP and then enriches it before notifying the analyst. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Test with: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

B.

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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Test with: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

C.

Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Check the result: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. The technical reason is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results.

D.

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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Test with: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

Question 576

A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes. What is the most defensible FortiAnalyzer action in this situation?

  1. Use Playbook Monitor to inspect the job timeline, task status, and upstream connector error before retrying a dependent action.
  2. Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action.
  3. Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.
  4. Add explicit pre-action state verification and outcome logging before retrying actions that must be safe and repeatable.

Answer & Explanations

Correct answer: C

A.

Use Playbook Monitor to inspect the job timeline, task status, and upstream connector error before retrying a dependent action. That action is relevant to a different problem: A university's incident playbook shows an evidence task as upstream_failed after its threat-intelligence connector lost connectivity. Its technical basis is: A downstream task may be marked upstream_failed when its prerequisite could not complete, so the earliest failing step is the useful root cause. The present case instead requires: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

C.

Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. The technical reason is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. Confirm by: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. The fictional case is: A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes.

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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

Question 577

A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes. The reviewed recommendation is: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. 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. Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data.
  3. A timeout does not prove that an earlier API operation failed and blind retries can duplicate state changes or notifications.
  4. Transport reachability confirms only a session path while remote API operations still require valid credentials and sufficient scope.

Answer & Explanations

Correct answer: A

A.

Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. It explains why the intervention—connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them—addresses the stated problem. Test the mechanism by: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. The fictional case is: A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes.

B.

Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data. That principle explains a different situation: A hospital detects contact with a new domain and wants the exact DNS value attached to its incident's indicator panel. Here the relevant cause is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. Apply it by: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. The fictional case is: A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes.

C.

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: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. Apply it by: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

D.

Transport reachability confirms only a session path while remote API operations still require valid credentials and sufficient scope. That principle explains a different situation: A regional bank can query one FortiGate through a connector but policy-block tasks are denied by its API permissions. Here the relevant cause is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. Apply it by: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them.

Question 578

A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes. The reviewed recommendation is: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. What pilot verification directly establishes the intended result?

  1. Generate a benign test event and trace the stitch trigger, targeted action, and confirmation record in the respective products.
  2. Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.
  3. Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement.
  4. Run a harmless workflow with a deliberately unavailable test connector and identify the first failed task before its dependents.

Answer & Explanations

Correct answer: B

A.

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: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

B.

Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. This directly tests whether the chosen intervention works: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. The causal mechanism is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. The fictional case is: A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes.

C.

Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement. That test is for another requirement: A bank firewall playbook blocks its payment processor after reading a destination IP as the malicious source indicator. It does not verify the stated outcome; the relevant check is: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. The fictional case is: A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes.

D.

Run a harmless workflow with a deliberately unavailable test connector and identify the first failed task before its dependents. That test is for another requirement: A university's incident playbook shows an evidence task as upstream_failed after its threat-intelligence connector lost connectivity. It does not verify the stated outcome; the relevant check is: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

Question 579

A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes. Which tempting SOC change would undermine the stated requirement?

  1. Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions.
  2. Add the supported indicator and perform authorized enrichment against its correct type and original observed value.
  3. Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action.
  4. Use Playbook Monitor to inspect the job timeline, task status, and upstream connector error before retrying a dependent action.

Answer & Explanations

Correct answer: A

A.

Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions. The risk is: The response sends empty or stale indicators to connectors and automated actions fail or affect the wrong target. The safer action is: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Confirm by: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. The fictional case is: A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes.

B.

Add the supported indicator and perform authorized enrichment against its correct type and original observed value. That is an appropriate action for the separate case: A hospital detects contact with a new domain and wants the exact DNS value attached to its incident's indicator panel. It is not the unsafe shortcut asked about here. Reject: Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions. Its risk is: The response sends empty or stale indicators to connectors and automated actions fail or affect the wrong target.

C.

Inspect task input mappings and verify that each source, destination, hostname, and indicator variable is passed to the intended connector action. That is an appropriate action for the separate case: A bank firewall playbook blocks its payment processor after reading a destination IP as the malicious source indicator. It is not the unsafe shortcut asked about here. Reject: Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions. Its risk is: The response sends empty or stale indicators to connectors and automated actions fail or affect the wrong target.

D.

Use Playbook Monitor to inspect the job timeline, task status, and upstream connector error before retrying a dependent action. That is an appropriate action for the separate case: A university's incident playbook shows an evidence task as upstream_failed after its threat-intelligence connector lost connectivity. It is not the unsafe shortcut asked about here. Reject: Start all tasks in parallel and assume the result from a slower upstream lookup is already available to downstream actions. Its risk is: The response sends empty or stale indicators to connectors and automated actions fail or affect the wrong target.

Question 580

A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes. 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: 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: 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: Add the supported indicator and perform authorized enrichment against its correct type and original observed value. Validate using: Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain.

Answer & Explanations

Correct answer: B

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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Test with: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

B.

Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Check the result: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output. The technical reason is: Connected playbook tasks execute according to configured predecessor completion and downstream actions depend on correctly named upstream results. The fictional case is: A hospital SOC chains reputation lookup, evidence attachment, and an approved report action but the report starts before enrichment completes.

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: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Test with: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

D.

Choose this FortiAnalyzer analyst action: Add the supported indicator and perform authorized enrichment against its correct type and original observed value. Validate using: Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain. This action-and-test pairing concerns another situation: A hospital detects contact with a new domain and wants the exact DNS value attached to its incident's indicator panel. The current case needs this action: Connect playbook tasks according to their dependencies and map output variables only after upstream tasks successfully produce them. Test with: Run a harmless incident lookup in staging and confirm the enrichment task completes before a report or response task consumes its output.

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