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 28

Question 270

A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Validate using: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.
  2. Choose this FortiAnalyzer analyst action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Validate using: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
  3. Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.
  4. Choose this FortiAnalyzer analyst action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Validate using: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Validate using: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. This action-and-test pairing concerns another situation: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. The current case needs this action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.

B.

Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Check the result: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. The technical reason is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.

C.

Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections. This action-and-test pairing concerns another situation: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. The current case needs this action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.

D.

Choose this FortiAnalyzer analyst action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Validate using: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. This action-and-test pairing concerns another situation: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. The current case needs this action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.

Question 271

A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance.
  2. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.
  3. Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.
  4. Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

Answer & Explanations

Correct answer: C

A.

Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. That action is relevant to a different problem: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. Its technical basis is: Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly. The present case instead requires: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

B.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. That action is relevant to a different problem: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. Its technical basis is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. The present case instead requires: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

C.

Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. The technical reason is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. Confirm by: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

D.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. That action is relevant to a different problem: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. Its technical basis is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. The present case instead requires: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

Question 272

A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. The reviewed recommendation is: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly.
  2. Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM.
  3. FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs.
  4. IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness.

Answer & Explanations

Correct answer: C

A.

Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly. That principle explains a different situation: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. Here the relevant cause is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. Apply it by: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

B.

Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM. That principle explains a different situation: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. Here the relevant cause is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. Apply it by: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

C.

FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. It explains why the intervention—verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range—addresses the stated problem. Test the mechanism by: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

D.

IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. That principle explains a different situation: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Here the relevant cause is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. Apply it by: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

Question 273

A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. The reviewed recommendation is: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Which observation best demonstrates that this corrective step worked?

  1. Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.
  2. Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  3. Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
  4. Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

Answer & Explanations

Correct answer: C

A.

Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. That test is for another requirement: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. It does not verify the stated outcome; the relevant check is: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

B.

Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality. That test is for another requirement: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. It does not verify the stated outcome; the relevant check is: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

C.

Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. This directly tests whether the chosen intervention works: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. The causal mechanism is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs.

D.

Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. That test is for another requirement: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. It does not verify the stated outcome; the relevant check is: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

Question 274

A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. Which unsafe investigation or automation shortcut must be rejected?

  1. Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.
  2. Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity.
  3. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.
  4. Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain.

Answer & Explanations

Correct answer: D

A.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. That is an appropriate action for the separate case: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. It is not the unsafe shortcut asked about here. Reject: Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain. Its risk is: Confidential tenant logs become exposed and cross-site findings are misattributed.

B.

Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. That is an appropriate action for the separate case: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. It is not the unsafe shortcut asked about here. Reject: Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain. Its risk is: Confidential tenant logs become exposed and cross-site findings are misattributed.

C.

Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. That is an appropriate action for the separate case: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. It is not the unsafe shortcut asked about here. Reject: Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain. Its risk is: Confidential tenant logs become exposed and cross-site findings are misattributed.

D.

Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain. The risk is: Confidential tenant logs become exposed and cross-site findings are misattributed. The safer action is: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Confirm by: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

Question 275

A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. Validate using: Generate a harmless supported security event and confirm the required log subtype and widget are then populated.
  2. Choose this FortiAnalyzer analyst action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Validate using: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.
  3. Choose this FortiAnalyzer analyst action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Validate using: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
  4. Choose this FortiAnalyzer analyst action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Validate using: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

Answer & Explanations

Correct answer: C

A.

Choose this FortiAnalyzer analyst action: Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. Validate using: Generate a harmless supported security event and confirm the required log subtype and widget are then populated. This action-and-test pairing concerns another situation: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. The current case needs this action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

B.

Choose this FortiAnalyzer analyst action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Validate using: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. This action-and-test pairing concerns another situation: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. The current case needs this action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

C.

Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Check the result: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. The technical reason is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs.

D.

Choose this FortiAnalyzer analyst action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Validate using: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. This action-and-test pairing concerns another situation: A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. The current case needs this action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

Question 276

A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View. What is the most defensible FortiAnalyzer action in this situation?

  1. Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity.
  2. Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
  3. Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance.
  4. Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

Answer & Explanations

Correct answer: D

A.

Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. That action is relevant to a different problem: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. Its technical basis is: Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM. The present case instead requires: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

B.

Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. That action is relevant to a different problem: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. Its technical basis is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. The present case instead requires: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

C.

Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. That action is relevant to a different problem: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. Its technical basis is: Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly. The present case instead requires: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.

D.

Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. The technical reason is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. Confirm by: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.

Question 277

A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View. The reviewed recommendation is: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. What FortiAnalyzer mechanism supports the recommended analysis?

  1. FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs.
  2. Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria.
  3. Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source.
  4. Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence.

Answer & Explanations

Correct answer: A

A.

FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. It explains why the intervention—verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range—addresses the stated problem. Test the mechanism by: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.

B.

Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. That principle explains a different situation: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. Here the relevant cause is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. Apply it by: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

C.

Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source. That principle explains a different situation: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. Here the relevant cause is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. Apply it by: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

D.

Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. That principle explains a different situation: A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. Here the relevant cause is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. Apply it by: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.

Question 278

A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View. The reviewed recommendation is: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. What pilot verification directly establishes the intended result?

  1. Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.
  2. Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.
  3. Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.
  4. Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

Answer & Explanations

Correct answer: D

A.

Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. That test is for another requirement: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. It does not verify the stated outcome; the relevant check is: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

B.

Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. That test is for another requirement: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. It does not verify the stated outcome; the relevant check is: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

C.

Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. That test is for another requirement: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. It does not verify the stated outcome; the relevant check is: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.

D.

Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. This directly tests whether the chosen intervention works: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. The causal mechanism is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.

Question 279

A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View. Which tempting SOC change would undermine the stated requirement?

  1. Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.
  2. Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer.
  3. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.
  4. Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain.

Answer & Explanations

Correct answer: D

A.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. That is an appropriate action for the separate case: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. It is not the unsafe shortcut asked about here. Reject: Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain. Its risk is: Confidential tenant logs become exposed and cross-site findings are misattributed.

B.

Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer. That is an appropriate action for the separate case: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. It is not the unsafe shortcut asked about here. Reject: Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain. Its risk is: Confidential tenant logs become exposed and cross-site findings are misattributed.

C.

Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. That is an appropriate action for the separate case: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. It is not the unsafe shortcut asked about here. Reject: Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain. Its risk is: Confidential tenant logs become exposed and cross-site findings are misattributed. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.

D.

Disable all administrative isolation and give every analyst superuser rights just to find an event in another team domain. The risk is: Confidential tenant logs become exposed and cross-site findings are misattributed. The safer action is: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Confirm by: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.

Question 280

A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Validate using: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
  2. Choose this FortiAnalyzer analyst action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Validate using: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.
  3. Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.
  4. Choose this FortiAnalyzer analyst action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Validate using: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.

Answer & Explanations

Correct answer: A

A.

Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Check the result: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. The technical reason is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.

B.

Choose this FortiAnalyzer analyst action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Validate using: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. This action-and-test pairing concerns another situation: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. The current case needs this action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

C.

Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections. This action-and-test pairing concerns another situation: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. The current case needs this action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

D.

Choose this FortiAnalyzer analyst action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Validate using: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. This action-and-test pairing concerns another situation: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. The current case needs this action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.

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