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 52

Question 510

A hospital laptop changes IP mid-investigation and the analyst needs asset context to relate its earlier and later security events. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  3. Choose this FortiAnalyzer analyst action: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Validate using: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.
  4. Choose this FortiAnalyzer analyst action: Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. Validate using: Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event.

Answer & Explanations

Correct answer: C

A.

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: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Test with: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

B.

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: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Test with: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

C.

Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Check the result: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity. The technical reason is: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. The fictional case is: A hospital laptop changes IP mid-investigation and the analyst needs asset context to relate its earlier and later security events.

D.

Choose this FortiAnalyzer analyst action: Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. Validate using: Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event. This action-and-test pairing concerns another situation: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. The current case needs this action: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Test with: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity. The fictional case is: A hospital laptop changes IP mid-investigation and the analyst needs asset context to relate its earlier and later security events.

Question 511

A retail bank sees a FortiGuard suspicious IP in an enrichment pane and needs to confirm a local flow to that address actually occurred. 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. Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.
  3. Use explicit incident owner, category, status, analyst notes, and evidence-based closure criteria with documented escalation boundaries.
  4. Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions.

Answer & Explanations

Correct answer: B

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: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

B.

Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. The technical reason is: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. Confirm by: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

C.

Use explicit incident owner, category, status, analyst notes, and evidence-based closure criteria with documented escalation boundaries. That action is relevant to a different problem: A hospital triage team has multiple open incidents with no analyst assignment and management cannot tell which are resolved. Its technical basis is: Incident lifecycle fields support accountable triage and review while an initial severity label does not establish final classification or response quality. The present case instead requires: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

D.

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: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

Question 512

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 reviewed recommendation is: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run.
  2. An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity.
  3. Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data.
  4. Correlation handlers can analyze specified patterns across observations whereas a simple one-record predicate does not represent multi-stage behavior.

Answer & Explanations

Correct answer: B

A.

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: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. Apply it by: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

B.

An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. It explains why the intervention—validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident—addresses the stated problem. Test the mechanism by: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

C.

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: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. Apply it by: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

D.

Correlation handlers can analyze specified patterns across observations whereas a simple one-record predicate does not represent multi-stage behavior. That principle explains a different situation: A bank SOC wants to detect suspicious logins followed by sensitive network access within a short investigation window. Here the relevant cause is: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. Apply it by: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

Question 513

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 reviewed recommendation is: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Which observation best demonstrates that this corrective step worked?

  1. Replay a harmless case with known source and destination values and inspect the resulting task argument log before enabling enforcement.
  2. Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain.
  3. Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.
  4. Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

Answer & Explanations

Correct answer: D

A.

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: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

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: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

C.

Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity. That test is for another requirement: A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. It does not verify the stated outcome; the relevant check is: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

D.

Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. This directly tests whether the chosen intervention works: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. The causal mechanism is: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity.

Question 514

A retail bank sees a FortiGuard suspicious IP in an enrichment pane and needs to confirm a local flow to that address actually occurred. Which unsafe investigation or automation shortcut must be rejected?

  1. Use the built-in local FortiAnalyzer connector and select supported incident and report actions within the playbook.
  2. Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.
  3. Automatically isolate every device whenever any global threat feed mentions an address absent from local logs.
  4. Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions.

Answer & Explanations

Correct answer: C

A.

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: Automatically isolate every device whenever any global threat feed mentions an address absent from local logs. Its risk is: Legitimate hosts are quarantined and analysts lose confidence in uncorroborated IOC-driven response.

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: Automatically isolate every device whenever any global threat feed mentions an address absent from local logs. Its risk is: Legitimate hosts are quarantined and analysts lose confidence in uncorroborated IOC-driven response.

C.

Automatically isolate every device whenever any global threat feed mentions an address absent from local logs. The risk is: Legitimate hosts are quarantined and analysts lose confidence in uncorroborated IOC-driven response. The safer action is: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Confirm by: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

D.

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: Automatically isolate every device whenever any global threat feed mentions an address absent from local logs. Its risk is: Legitimate hosts are quarantined and analysts lose confidence in uncorroborated IOC-driven response.

Question 515

A retail bank sees a FortiGuard suspicious IP in an enrichment pane and needs to confirm a local flow to that address actually occurred. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. Validate using: Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event.
  2. 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.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Validate using: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. Validate using: Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event. This action-and-test pairing concerns another situation: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. The current case needs this action: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Test with: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

B.

Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Check the result: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. The technical reason is: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity.

C.

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

D.

Choose this FortiAnalyzer analyst action: Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions. Validate using: Replay a safe ordered chain of related events inside and outside the configured window and compare whether the intended alert is generated. This action-and-test pairing concerns another situation: A bank SOC wants to detect suspicious logins followed by sensitive network access within a short investigation window. The current case needs this action: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Test with: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

Question 516

A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident. What is the most defensible FortiAnalyzer action in this situation?

  1. Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.
  2. Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy.
  3. Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.
  4. Use the built-in local FortiAnalyzer connector and select supported incident and report actions within the playbook.

Answer & Explanations

Correct answer: C

A.

Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. That action is relevant to a different problem: A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. Its technical basis is: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. The present case instead requires: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

B.

Choose an eligible EVENT_TRIGGER with explicit matching conditions or deliberately run an ON_DEMAND playbook as required by the response policy. That action is relevant to a different problem: A bank SOC creates a containment playbook but leaves it configured for on-demand runs when a high-confidence event should trigger it. Its technical basis is: A FortiAnalyzer playbook begins with one supported trigger and its start conditions govern when connected tasks can run. The present case instead requires: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

C.

Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. The technical reason is: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. Confirm by: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. The fictional case is: A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident.

D.

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: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

Question 517

A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident. The reviewed recommendation is: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Variable mapping translates alert context into remote action parameters and swapping endpoint roles can redirect a legitimate response.
  2. An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity.
  3. FortiAnalyzer supports automatic incident generation from matching events when its incident-creation option is explicitly enabled.
  4. Incident analysis can organize related detections while preserving the log evidence required to justify scope, cause, and disposition.

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: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. Apply it by: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

B.

An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. It explains why the intervention—validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident—addresses the stated problem. Test the mechanism by: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. The fictional case is: A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident.

C.

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: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. Apply it by: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

D.

Incident analysis can organize related detections while preserving the log evidence required to justify scope, cause, and disposition. That principle explains a different situation: A university security team sees several firewall detections from one suspicious workstation and needs a case with source evidence. Here the relevant cause is: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. Apply it by: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident.

Question 518

A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident. The reviewed recommendation is: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. What pilot verification directly establishes the intended result?

  1. Run a harmless on-demand test that creates a sample incident and triggers a scoped report through authorized local connector tasks.
  2. Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.
  3. Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.
  4. Review a synthetic incident from assignment through resolution and confirm each status change includes its supporting evidence.

Answer & Explanations

Correct answer: B

A.

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: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

B.

Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. This directly tests whether the chosen intervention works: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. The causal mechanism is: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. The fictional case is: A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident.

C.

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: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

D.

Review a synthetic incident from assignment through resolution and confirm each status change includes its supporting evidence. That test is for another requirement: A hospital triage team has multiple open incidents with no analyst assignment and management cannot tell which are resolved. It does not verify the stated outcome; the relevant check is: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.

Question 519

A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident. Which tempting SOC change would undermine the stated requirement?

  1. Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.
  2. Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case.
  3. Automatically isolate every device whenever any global threat feed mentions an address absent from local logs.
  4. Link the relevant events and raw log context to a single incident analysis case with a traceable time range.

Answer & Explanations

Correct answer: C

A.

Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. That is an appropriate action for the separate case: A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. It is not the unsafe shortcut asked about here. Reject: Automatically isolate every device whenever any global threat feed mentions an address absent from local logs. Its risk is: Legitimate hosts are quarantined and analysts lose confidence in uncorroborated IOC-driven response.

B.

Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. That is an appropriate action for the separate case: A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. It is not the unsafe shortcut asked about here. Reject: Automatically isolate every device whenever any global threat feed mentions an address absent from local logs. Its risk is: Legitimate hosts are quarantined and analysts lose confidence in uncorroborated IOC-driven response.

C.

Automatically isolate every device whenever any global threat feed mentions an address absent from local logs. The risk is: Legitimate hosts are quarantined and analysts lose confidence in uncorroborated IOC-driven response. The safer action is: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Confirm by: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. The fictional case is: A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident.

D.

Link the relevant events and raw log context to a single incident analysis case with a traceable time range. That is an appropriate action for the separate case: A university security team sees several firewall detections from one suspicious workstation and needs a case with source evidence. It is not the unsafe shortcut asked about here. Reject: Automatically isolate every device whenever any global threat feed mentions an address absent from local logs. Its risk is: Legitimate hosts are quarantined and analysts lose confidence in uncorroborated IOC-driven response.

Question 520

A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  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: 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.

Answer & Explanations

Correct answer: C

A.

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: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Test with: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. The fictional case is: A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident.

B.

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: Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Test with: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. The fictional case is: A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident.

C.

Validate indicator relevance with case time, observed source log, IOC type, and confidence before escalating the incident. Check the result: Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. The technical reason is: An indicator is contextual evidence only when observed in the investigated environment and an enrichment feed alone does not prove malicious activity. The fictional case is: A hospital analyst receives a malware hash alert but has no endpoint file observation to tie it to the incident.

D.

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

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