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 51

Question 500

A bank analyst sees a suspicious source IP but its incident contains no structured indicator for FortiGuard enrichment. 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: 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.
  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 explicit incident owner, category, status, analyst notes, and evidence-based closure criteria with documented escalation boundaries. Validate using: Review a synthetic incident from assignment through resolution and confirm each status change includes its supporting evidence.

Answer & Explanations

Correct answer: B

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: Add the supported indicator and perform authorized enrichment against its correct type and original observed value. Test with: Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain.

B.

Add the supported indicator and perform authorized enrichment against its correct type and original observed value. Check the result: Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain. The technical reason is: Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data. The fictional case is: A bank analyst sees a suspicious source IP but its incident contains no structured indicator for FortiGuard enrichment.

C.

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: Add the supported indicator and perform authorized enrichment against its correct type and original observed value. Test with: Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain.

D.

Choose this FortiAnalyzer analyst action: Use explicit incident owner, category, status, analyst notes, and evidence-based closure criteria with documented escalation boundaries. Validate using: Review a synthetic incident from assignment through resolution and confirm each status change includes its supporting evidence. This action-and-test pairing concerns another situation: A hospital triage team has multiple open incidents with no analyst assignment and management cannot tell which are resolved. The current case needs this action: Add the supported indicator and perform authorized enrichment against its correct type and original observed value. Test with: Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain. The fictional case is: A bank analyst sees a suspicious source IP but its incident contains no structured indicator for FortiGuard enrichment.

Question 501

A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.
  2. Link the relevant events and raw log context to a single incident analysis case with a traceable time range.
  3. Create an appropriate correlation handler with an explicit relationship, bounded time window, and tested event conditions.
  4. Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

Answer & Explanations

Correct answer: D

A.

Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. That action is relevant to a different problem: A hospital turns off a noisy custom event handler and later assumes the branch firewalls have stopped logging entirely. Its technical basis is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. The present case instead requires: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

B.

Link the relevant events and raw log context to a single incident analysis case with a traceable time range. That action is relevant to a different problem: A university security team sees several firewall detections from one suspicious workstation and needs a case with source evidence. Its technical basis is: Incident analysis can organize related detections while preserving the log evidence required to justify scope, cause, and disposition. The present case instead requires: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

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: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

D.

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

Question 502

A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. The reviewed recommendation is: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Event-handler configuration must match the eligible data source selection and one ADOM can contain several unrelated monitoring populations.
  2. Correlation handlers can analyze specified patterns across observations whereas a simple one-record predicate does not represent multi-stage behavior.
  3. An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality.
  4. Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data.

Answer & Explanations

Correct answer: C

A.

Event-handler configuration must match the eligible data source selection and one ADOM can contain several unrelated monitoring populations. That principle explains a different situation: A regional retailer adds a payment-card detection rule but its FortiAnalyzer domain includes public guest kiosks as well. Here the relevant cause is: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. Apply it by: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

B.

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 endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. Apply it by: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

C.

An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. It explains why the intervention—use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents—addresses the stated problem. Test the mechanism by: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

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: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. Apply it by: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

Question 503

A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. The reviewed recommendation is: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Which observation best demonstrates that this corrective step worked?

  1. Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.
  2. Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain.
  3. Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion.
  4. Open a harmless incident and verify that selected event records link back to their original device logs and correct time window.

Answer & Explanations

Correct answer: A

A.

Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity. This directly tests whether the chosen intervention works: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. The causal mechanism is: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality.

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: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

C.

Compare one indicator present in a harmless test case with one unrelated value and document which original event supports each conclusion. That test is for another requirement: A retail bank sees a FortiGuard suspicious IP in an enrichment pane and needs to confirm a local flow to that address actually occurred. It does not verify the stated outcome; the relevant check is: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

D.

Open a harmless incident and verify that selected event records link back to their original device logs and correct time window. That test is for another requirement: A university security team sees several firewall detections from one suspicious workstation and needs a case with source evidence. It does not verify the stated outcome; the relevant check is: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

Question 504

A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. Which unsafe investigation or automation shortcut must be rejected?

  1. Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping.
  2. Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format.
  3. Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged.
  4. Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events.

Answer & Explanations

Correct answer: A

A.

Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping. The risk is: Investigators attribute several independent clients to the wrong asset or split one attack into false separate cases. The safer action is: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Confirm by: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

B.

Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format. That is an appropriate action for the separate case: A university SOC prepares a one-day firewall report for an active incident and wants the PDF linked to the analyst case. It is not the unsafe shortcut asked about here. Reject: Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping. Its risk is: Investigators attribute several independent clients to the wrong asset or split one attack into false separate cases.

C.

Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged. That is an appropriate action for the separate case: A bank SOC approves automatic case opening for confirmed malware quarantine events but its handler currently generates only events. It is not the unsafe shortcut asked about here. Reject: Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping. Its risk is: Investigators attribute several independent clients to the wrong asset or split one attack into false separate cases.

D.

Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. That is an appropriate action for the separate case: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. It is not the unsafe shortcut asked about here. Reject: Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping. Its risk is: Investigators attribute several independent clients to the wrong asset or split one attack into false separate cases.

Question 505

A university's wireless clients share one NAT address and FortiAnalyzer incident correlation must identify the individual affected machine. 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: Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. Validate using: Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences.
  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: 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: C

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: 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: Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. Validate using: Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences. This action-and-test pairing concerns another situation: A university needs a narrower scan detector than the installed default handler and wants to preserve the vendor reference rule. The current case needs this action: 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.

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

Question 506

A hospital laptop changes IP mid-investigation and the analyst needs asset context to relate its earlier and later security events. What is the most defensible FortiAnalyzer action in this situation?

  1. Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format.
  2. Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events.
  3. Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.
  4. Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

Answer & Explanations

Correct answer: D

A.

Generate an approved scoped FortiAnalyzer report and attach it to the related incident while preserving report time, device, and format. That action is relevant to a different problem: A university SOC prepares a one-day firewall report for an active incident and wants the PDF linked to the analyst case. Its technical basis is: Incidents can reference generated reports that summarize supporting evidence, allowing a reviewer to trace the same investigation data. The present case instead requires: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

B.

Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. That action is relevant to a different problem: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. Its technical basis is: Basic event handlers evaluate defined log predicates against eligible data and cannot trigger when the target source fields never match. The present case instead requires: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

C.

Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. That action is relevant to a different problem: A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. Its technical basis is: Grouping and threshold settings let a detection represent frequency for a specific source rather than every matching raw log as an independent offense. The present case instead requires: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

D.

Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. 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. Confirm by: 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 507

A hospital laptop changes IP mid-investigation and the analyst needs asset context to relate its earlier and later security events. The reviewed recommendation is: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Incident lifecycle fields support accountable triage and review while an initial severity label does not establish final classification or response quality.
  2. Threat indicators become useful to analysts when linked to observed logs and enriched with contextual reputation or source data.
  3. An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality.
  4. Incidents can reference generated reports that summarize supporting evidence, allowing a reviewer to trace the same investigation data.

Answer & Explanations

Correct answer: C

A.

Incident lifecycle fields support accountable triage and review while an initial severity label does not establish final classification or response quality. That principle explains a different situation: A hospital triage team has multiple open incidents with no analyst assignment and management cannot tell which are resolved. Here the relevant cause is: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. Apply it by: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

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: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. Apply it by: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. 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.

C.

An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. It explains why the intervention—use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents—addresses the stated problem. Test the mechanism by: 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.

D.

Incidents can reference generated reports that summarize supporting evidence, allowing a reviewer to trace the same investigation data. That principle explains a different situation: A university SOC prepares a one-day firewall report for an active incident and wants the PDF linked to the analyst case. Here the relevant cause is: An endpoint or identity may appear under changing IP addresses and cross-source correlations need grounded asset attribution rather than blind string equality. Apply it by: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents.

Question 508

A hospital laptop changes IP mid-investigation and the analyst needs asset context to relate its earlier and later security events. The reviewed recommendation is: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. What pilot verification directly establishes the intended result?

  1. Attach a harmless sample domain indicator to a test incident and verify its enriched details refer to the same domain.
  2. Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.
  3. Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.
  4. Review a synthetic incident from assignment through resolution and confirm each status change includes its supporting evidence.

Answer & Explanations

Correct answer: B

A.

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

B.

Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity. This directly tests whether the chosen intervention works: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. The causal mechanism 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.

C.

Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers. That test is for another requirement: A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. It does not verify the stated outcome; the relevant check is: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

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: Observe a lab workstation before and after a controlled DHCP lease change and verify its case context retains the correct asset identity.

Question 509

A hospital laptop changes IP mid-investigation and the analyst needs asset context to relate its earlier and later security events. Which tempting SOC change would undermine the stated requirement?

  1. Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged.
  2. Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping.
  3. Link the relevant events and raw log context to a single incident analysis case with a traceable time range.
  4. Use explicit incident owner, category, status, analyst notes, and evidence-based closure criteria with documented escalation boundaries.

Answer & Explanations

Correct answer: B

A.

Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged. That is an appropriate action for the separate case: A bank SOC approves automatic case opening for confirmed malware quarantine events but its handler currently generates only events. It is not the unsafe shortcut asked about here. Reject: Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping. Its risk is: Investigators attribute several independent clients to the wrong asset or split one attack into false separate cases. 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.

B.

Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping. The risk is: Investigators attribute several independent clients to the wrong asset or split one attack into false separate cases. The safer action is: Use available asset and identity context to reconcile supported device and user mappings before combining or separating incidents. Confirm by: 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.

C.

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: Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping. Its risk is: Investigators attribute several independent clients to the wrong asset or split one attack into false separate cases.

D.

Use explicit incident owner, category, status, analyst notes, and evidence-based closure criteria with documented escalation boundaries. That is an appropriate action for the separate case: A hospital triage team has multiple open incidents with no analyst assignment and management cannot tell which are resolved. It is not the unsafe shortcut asked about here. Reject: Merge all alerts with the same public NAT IP into one compromised host without checking internal endpoint mapping. Its risk is: Investigators attribute several independent clients to the wrong asset or split one attack into false separate cases.

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.

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