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 35

Question 340

A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

Answer & Explanations

Correct answer: D

A.

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: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

B.

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: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

C.

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: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

D.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Check the result: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The technical reason is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

Question 341

A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.
  2. Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.
  3. Verify the report definition's ADOM, selected devices, and time filter match the original logging sources.
  4. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.

Answer & Explanations

Correct answer: B

A.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. That action is relevant to a different problem: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Its technical basis is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. The present case instead requires: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

B.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. The technical reason is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. Confirm by: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

C.

Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. That action is relevant to a different problem: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. Its technical basis is: FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection. The present case instead requires: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

D.

Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. That action is relevant to a different problem: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. Its technical basis is: Multiple alerts can describe one traffic or security sequence and unambiguous event identity prevents duplicate investigations. The present case instead requires: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

Question 342

A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. The reviewed recommendation is: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window.
  2. Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria.
  3. A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope.
  4. Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM.

Answer & Explanations

Correct answer: B

A.

Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. That principle explains a different situation: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. Here the relevant cause is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. Apply it by: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

B.

Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. It explains why the intervention—create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints—addresses the stated problem. Test the mechanism by: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

C.

A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. That principle explains a different situation: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. Here the relevant cause is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. Apply it by: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

D.

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: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. Apply it by: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

Question 343

A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. The reviewed recommendation is: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Which observation best demonstrates that this corrective step worked?

  1. Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.
  2. 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. Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  4. Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter.

Answer & Explanations

Correct answer: A

A.

Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. This directly tests whether the chosen intervention works: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. The causal mechanism is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria.

B.

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: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

C.

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: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

D.

Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter. That test is for another requirement: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. It does not verify the stated outcome; the relevant check is: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

Question 344

A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. Which unsafe investigation or automation shortcut must be rejected?

  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. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.
  4. Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view.

Answer & Explanations

Correct answer: D

A.

Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. That is an appropriate action for the separate case: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. It is not the unsafe shortcut asked about here. Reject: Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view. Its risk is: Other analysts draw inconsistent conclusions from the same saved view because its filter semantics are misleading.

B.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. That is an appropriate action for the separate case: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. It is not the unsafe shortcut asked about here. Reject: Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view. Its risk is: Other analysts draw inconsistent conclusions from the same saved view because its filter semantics are misleading.

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: Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view. Its risk is: Other analysts draw inconsistent conclusions from the same saved view because its filter semantics are misleading.

D.

Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view. The risk is: Other analysts draw inconsistent conclusions from the same saved view because its filter semantics are misleading. The safer action is: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Confirm by: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

Question 345

A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. 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.
  2. Choose this FortiAnalyzer analyst action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Validate using: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  3. 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.
  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: C

A.

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: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Test with: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

B.

Choose this FortiAnalyzer analyst action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Validate using: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality. This action-and-test pairing concerns another situation: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. The current case needs this action: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Test with: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

C.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Check the result: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. The technical reason is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria.

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 a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Test with: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

Question 346

A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices. What is the most defensible FortiAnalyzer action in this situation?

  1. Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.
  2. Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.
  3. Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.
  4. Verify the report definition's ADOM, selected devices, and time filter match the original logging sources.

Answer & Explanations

Correct answer: C

A.

Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. That action is relevant to a different problem: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Its technical basis is: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. The present case instead requires: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

B.

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: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

C.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. The technical reason is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. Confirm by: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

D.

Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. That action is relevant to a different problem: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. Its technical basis is: FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection. The present case instead requires: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

Question 347

A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices. The reviewed recommendation is: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM.
  2. Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria.
  3. Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo.
  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: B

A.

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: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. Apply it by: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

B.

Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. It explains why the intervention—create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints—addresses the stated problem. Test the mechanism by: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

C.

Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. That principle explains a different situation: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. Here the relevant cause is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. Apply it by: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

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: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. Apply it by: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

Question 348

A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices. The reviewed recommendation is: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. What pilot verification directly establishes the intended result?

  1. Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.
  2. Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
  3. Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter.
  4. Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

Answer & Explanations

Correct answer: D

A.

Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. That test is for another requirement: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. It does not verify the stated outcome; the relevant check is: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

B.

Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. That test is for another requirement: A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. It does not verify the stated outcome; the relevant check is: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

C.

Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter. That test is for another requirement: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. It does not verify the stated outcome; the relevant check is: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

D.

Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. This directly tests whether the chosen intervention works: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. The causal mechanism is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

Question 349

A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices. Which tempting SOC change would undermine the stated requirement?

  1. Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.
  2. Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity.
  3. Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view.
  4. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.

Answer & Explanations

Correct answer: C

A.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. That is an appropriate action for the separate case: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. It is not the unsafe shortcut asked about here. Reject: Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view. Its risk is: Other analysts draw inconsistent conclusions from the same saved view because its filter semantics are misleading.

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: Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view. Its risk is: Other analysts draw inconsistent conclusions from the same saved view because its filter semantics are misleading.

C.

Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view. The risk is: Other analysts draw inconsistent conclusions from the same saved view because its filter semantics are misleading. The safer action is: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Confirm by: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

D.

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: Save an unrestricted all-device dashboard under a case name and present it as a narrowly filtered incident view. Its risk is: Other analysts draw inconsistent conclusions from the same saved view because its filter semantics are misleading. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

Question 350

A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices. 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: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. Validate using: Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter.

Answer & Explanations

Correct answer: A

A.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Check the result: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. The technical reason is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

B.

Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. This action-and-test pairing concerns another situation: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. The current case needs this action: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Test with: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

C.

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: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Test with: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. The fictional case is: A bank analyst prepares a saved dashboard for monitoring a pilot payment segment without exposing unrelated devices.

D.

Choose this FortiAnalyzer analyst action: Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. Validate using: Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter. This action-and-test pairing concerns another situation: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. The current case needs this action: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Test with: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.

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