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 47

Question 460

A bank analyst must customize a built-in outbound anomaly rule without breaking its future content refresh. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. Choose this FortiAnalyzer analyst action: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Validate using: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook.
  3. Choose this FortiAnalyzer analyst action: 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.
  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: A

A.

Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. Check the result: Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences. The technical reason is: Predefined handlers may restrict editing of core logic whereas custom clones permit controlled tailoring without changing the original baseline. The fictional case is: A bank analyst must customize a built-in outbound anomaly rule without breaking its future content refresh.

B.

Choose this FortiAnalyzer analyst action: Select an INCIDENT_TRIGGER with suitable incident field filters rather than executing before an analyst or rule has created the required case. Validate using: Generate a test event without an incident and then a matching incident and verify only the incident starts the intended playbook. This action-and-test pairing concerns another situation: A hospital wants an evidence-gathering playbook to run only after a high-severity incident exists rather than on every IDS event. The current case needs this action: Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. Test with: Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences.

C.

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: Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. Test with: Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences. The fictional case is: A bank analyst must customize a built-in outbound anomaly rule without breaking its future content refresh.

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: Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. Test with: Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences.

Question 461

A hospital turns off a noisy custom event handler and later assumes the branch firewalls have stopped logging entirely. 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. Compare the playbook trigger's exact event or incident field filters against a real qualifying record and verify the playbook is enabled.
  3. Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.
  4. Use explicit incident owner, category, status, analyst notes, and evidence-based closure criteria with documented escalation boundaries.

Answer & Explanations

Correct answer: A

A.

Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. The technical reason is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. Confirm by: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

B.

Compare the playbook trigger's exact event or incident field filters against a real qualifying record and verify the playbook is enabled. That action is relevant to a different problem: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. Its technical basis is: Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting. The present case instead requires: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

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: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

D.

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: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

Question 462

A hospital turns off a noisy custom event handler and later assumes the branch firewalls have stopped logging entirely. The reviewed recommendation is: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. A downstream task may be marked upstream_failed when its prerequisite could not complete, so the earliest failing step is the useful root cause.
  2. A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable.
  3. Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting.
  4. Predefined handlers may restrict editing of core logic whereas custom clones permit controlled tailoring without changing the original baseline.

Answer & Explanations

Correct answer: B

A.

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: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. Apply it by: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

B.

A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. It explains why the intervention—check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic—addresses the stated problem. Test the mechanism by: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

C.

Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting. That principle explains a different situation: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. Here the relevant cause is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. Apply it by: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

D.

Predefined handlers may restrict editing of core logic whereas custom clones permit controlled tailoring without changing the original baseline. That principle explains a different situation: A university needs a narrower scan detector than the installed default handler and wants to preserve the vendor reference rule. Here the relevant cause is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. Apply it by: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

Question 463

A hospital turns off a noisy custom event handler and later assumes the branch firewalls have stopped logging entirely. The reviewed recommendation is: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Which observation best demonstrates that this corrective step worked?

  1. Generate a bounded count of test denials from one source and another unrelated source to verify only the thresholded group triggers.
  2. Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.
  3. Run a harmless workflow with a deliberately unavailable test connector and identify the first failed task before its dependents.
  4. Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event.

Answer & Explanations

Correct answer: B

A.

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: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

B.

Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. This directly tests whether the chosen intervention works: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. The causal mechanism is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable.

C.

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: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

D.

Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event. That test is for another requirement: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. It does not verify the stated outcome; the relevant check is: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

Question 464

A hospital turns off a noisy custom event handler and later assumes the branch firewalls have stopped logging entirely. Which unsafe investigation or automation shortcut must be rejected?

  1. Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation.
  2. Enable the event handler's supported automatic incident creation and define how the resulting incident will be triaged.
  3. Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle.
  4. Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

Answer & Explanations

Correct answer: C

A.

Clone the predefined handler into a custom rule and adjust supported filter and threshold fields with pilot validation. That is an appropriate action for the separate case: A university needs a narrower scan detector than the installed default handler and wants to preserve the vendor reference rule. It is not the unsafe shortcut asked about here. Reject: Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle. Its risk is: Analysts lose the alerting workflow and potentially discard healthy logs while trying to fix the wrong component.

B.

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: Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle. Its risk is: Analysts lose the alerting workflow and potentially discard healthy logs while trying to fix the wrong component.

C.

Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle. The risk is: Analysts lose the alerting workflow and potentially discard healthy logs while trying to fix the wrong component. The safer action is: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Confirm by: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

D.

Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. That is an appropriate action for the separate case: A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. It is not the unsafe shortcut asked about here. Reject: Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle. Its risk is: Analysts lose the alerting workflow and potentially discard healthy logs while trying to fix the wrong component.

Question 465

A hospital turns off a noisy custom event handler and later assumes the branch firewalls have stopped logging entirely. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Use Playbook Monitor to inspect the job timeline, task status, and upstream connector error before retrying a dependent action. Validate using: Run a harmless workflow with a deliberately unavailable test connector and identify the first failed task before its dependents.
  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: 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.
  4. Choose this FortiAnalyzer analyst action: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Validate using: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

Answer & Explanations

Correct answer: D

A.

Choose this FortiAnalyzer analyst action: Use Playbook Monitor to inspect the job timeline, task status, and upstream connector error before retrying a dependent action. Validate using: Run a harmless workflow with a deliberately unavailable test connector and identify the first failed task before its dependents. This action-and-test pairing concerns another situation: A university's incident playbook shows an evidence task as upstream_failed after its threat-intelligence connector lost connectivity. The current case needs this action: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Test with: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

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: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Test with: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

C.

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: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Test with: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

D.

Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Check the result: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. The technical reason is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable.

Question 466

A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler. 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. Link the relevant events and raw log context to a single incident analysis case with a traceable time range.
  3. Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.
  4. Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements.

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: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

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: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

C.

Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. The technical reason is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. Confirm by: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

D.

Configure the supported Fabric automation stitch and its paired event handler or rule with explicit trigger and safe action requirements. That action is relevant to a different problem: A retail chain wants its FortiGate Fabric automation stitch to react to a specific approved high-confidence FortiAnalyzer event. Its technical basis is: FortiAnalyzer events and Fabric automation mechanisms require a functioning matching trigger and authorized downstream action to produce a real response. The present case instead requires: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

Question 467

A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler. The reviewed recommendation is: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. What FortiAnalyzer mechanism supports the recommended analysis?

  1. A downstream task may be marked upstream_failed when its prerequisite could not complete, so the earliest failing step is the useful root cause.
  2. Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting.
  3. A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable.
  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: C

A.

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: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. Apply it by: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

B.

Trigger filters evaluate event or incident attributes and a syntactically correct but mismatched predicate prevents the job from starting. That principle explains a different situation: A university launches an event-triggered playbook but its filter expects a different event subtype from the incident handler. Here the relevant cause is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. Apply it by: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

C.

A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. It explains why the intervention—check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic—addresses the stated problem. Test the mechanism by: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

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: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. Apply it by: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic.

Question 468

A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler. The reviewed recommendation is: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. What pilot verification directly establishes the intended result?

  1. Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences.
  2. Open a harmless incident and verify that selected event records link back to their original device logs and correct time window.
  3. Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event.
  4. Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

Answer & Explanations

Correct answer: D

A.

Compare a benign test stream under the predefined rule and the cloned custom rule to confirm only intended threshold differences. That test is for another requirement: A university needs a narrower scan detector than the installed default handler and wants to preserve the vendor reference rule. It does not verify the stated outcome; the relevant check is: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

B.

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: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

C.

Generate a harmless test record containing the expected subtype and verify the enabled handler creates the intended event. That test is for another requirement: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. It does not verify the stated outcome; the relevant check is: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

D.

Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. This directly tests whether the chosen intervention works: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. The causal mechanism is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

Question 469

A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler. Which tempting SOC change would undermine the stated requirement?

  1. Link the relevant events and raw log context to a single incident analysis case with a traceable time range.
  2. Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle.
  3. Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events.
  4. Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts.

Answer & Explanations

Correct answer: B

A.

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: Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle. Its risk is: Analysts lose the alerting workflow and potentially discard healthy logs while trying to fix the wrong component.

B.

Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle. The risk is: Analysts lose the alerting workflow and potentially discard healthy logs while trying to fix the wrong component. The safer action is: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Confirm by: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

C.

Review the basic handler's log category, normalized field filters, selected device scope, and enabled state against representative source events. That is an appropriate action for the separate case: A hospital SOC writes a handler for repeated IPS blocks but the filter is attached to ordinary forward-traffic logs only. It is not the unsafe shortcut asked about here. Reject: Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle. Its risk is: Analysts lose the alerting workflow and potentially discard healthy logs while trying to fix the wrong component.

D.

Configure an event threshold and grouping key with appropriate time interval and device scope to control repeated-condition alerts. That is an appropriate action for the separate case: A university gets hundreds of individual network authentication alerts from a single misconfigured printer and needs controlled aggregation. It is not the unsafe shortcut asked about here. Reject: Rebuild the entire FortiAnalyzer log database when the only observed change is a handler status toggle. Its risk is: Analysts lose the alerting workflow and potentially discard healthy logs while trying to fix the wrong component. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

Question 470

A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  3. Choose this FortiAnalyzer analyst action: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Validate using: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.
  4. Choose this FortiAnalyzer analyst action: Use Playbook Monitor to inspect the job timeline, task status, and upstream connector error before retrying a dependent action. Validate using: Run a harmless workflow with a deliberately unavailable test connector and identify the first failed task before its dependents.

Answer & Explanations

Correct answer: C

A.

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: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Test with: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

B.

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: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Test with: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays.

C.

Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Check the result: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. The technical reason is: A disabled handler stops generating new events even when eligible underlying logs continue to arrive and remain searchable. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

D.

Choose this FortiAnalyzer analyst action: Use Playbook Monitor to inspect the job timeline, task status, and upstream connector error before retrying a dependent action. Validate using: Run a harmless workflow with a deliberately unavailable test connector and identify the first failed task before its dependents. This action-and-test pairing concerns another situation: A university's incident playbook shows an evidence task as upstream_failed after its threat-intelligence connector lost connectivity. The current case needs this action: Check handler enabled status, log source availability, and the Event Monitor independently before changing detection logic. Test with: Inspect a known raw log and re-enable a test handler to verify new matching activity appears as an event without implying older data automatically replays. The fictional case is: A regional insurer can search raw event logs but event-monitor alerts stopped after a policy administrator disabled a handler.

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