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 32

Question 310

A university analyst must isolate one lab device's blocked DNS requests and wants explicit boolean filter semantics. Which combined analytic action and validation test best solve this case?

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

A.

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: Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. Test with: Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter. The fictional case is: A university analyst must isolate one lab device's blocked DNS requests and wants explicit boolean filter semantics.

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: Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. Test with: Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter.

C.

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. This action-and-test pairing concerns another situation: A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. The current case needs this action: Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. Test with: Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter.

D.

Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. Check the result: Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter. The technical reason is: AND combines constraints while OR broadens the result set, so wrong boolean logic changes which flows count as evidence. The fictional case is: A university analyst must isolate one lab device's blocked DNS requests and wants explicit boolean filter semantics.

Question 311

A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records.
  2. Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
  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: D

A.

Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. That action is relevant to a different problem: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. Its technical basis is: AND combines constraints while OR broadens the result set, so wrong boolean logic changes which flows count as evidence. The present case instead requires: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

B.

Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. That action is relevant to a different problem: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. Its technical basis is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. The present case instead requires: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

C.

Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. That action is relevant to a different problem: A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. Its technical basis 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 present case instead requires: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

D.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. The technical reason is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. Confirm by: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

Question 312

A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. The reviewed recommendation is: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. AND combines constraints while OR broadens the result set, so wrong boolean logic changes which flows count as evidence.
  2. A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope.
  3. FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection.
  4. Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields.

Answer & Explanations

Correct answer: B

A.

AND combines constraints while OR broadens the result set, so wrong boolean logic changes which flows count as evidence. That principle explains a different situation: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. Here the relevant cause is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. Apply it by: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

B.

A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. It explains why the intervention—align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates—addresses the stated problem. Test the mechanism by: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

C.

FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection. That principle explains a different situation: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. Here the relevant cause is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. Apply it by: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

D.

Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. That principle explains a different situation: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Here the relevant cause is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. Apply it by: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

Question 313

A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. The reviewed recommendation is: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. 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 the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.
  3. Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.
  4. Compare completion times for one representative report before and after off-peak scheduling and verified cache population.

Answer & Explanations

Correct answer: B

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: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

B.

Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. This directly tests whether the chosen intervention works: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. The causal mechanism is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope.

C.

Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. That test is for another requirement: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. It does not verify the stated outcome; the relevant check is: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

D.

Compare completion times for one representative report before and after off-peak scheduling and verified cache population. That test is for another requirement: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. It does not verify the stated outcome; the relevant check is: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

Question 314

A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. Which unsafe investigation or automation shortcut must be rejected?

  1. Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer.
  2. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.
  3. Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.
  4. Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference.

Answer & Explanations

Correct answer: D

A.

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: Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference. Its risk is: An incorrect time window drives false performance and security conclusions in compliance reporting.

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: Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference. Its risk is: An incorrect time window drives false performance and security conclusions in compliance reporting.

C.

Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. That is an appropriate action for the separate case: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. It is not the unsafe shortcut asked about here. Reject: Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference. Its risk is: An incorrect time window drives false performance and security conclusions in compliance reporting.

D.

Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference. The risk is: An incorrect time window drives false performance and security conclusions in compliance reporting. The safer action is: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Confirm by: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

Question 315

A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. 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: 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.
  3. Choose this FortiAnalyzer analyst action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
  4. 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.

Answer & Explanations

Correct answer: B

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: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Test with: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

B.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Check the result: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. The technical reason is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope.

C.

Choose this FortiAnalyzer analyst action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. This action-and-test pairing concerns another situation: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. The current case needs this action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Test with: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

D.

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: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Test with: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

Question 316

A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope. What is the most defensible FortiAnalyzer action in this situation?

  1. Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.
  2. Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance.
  3. Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.
  4. Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity.

Answer & Explanations

Correct answer: A

A.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. The technical reason is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. Confirm by: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

B.

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: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

C.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. That action is relevant to a different problem: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. Its technical basis is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. The present case instead requires: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

D.

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: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

Question 317

A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope. The reviewed recommendation is: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. What FortiAnalyzer mechanism supports the recommended analysis?

  1. FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection.
  2. A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope.
  3. Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields.
  4. Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo.

Answer & Explanations

Correct answer: B

A.

FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection. That principle explains a different situation: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. Here the relevant cause is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. Apply it by: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

B.

A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. It explains why the intervention—align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates—addresses the stated problem. Test the mechanism by: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

C.

Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. That principle explains a different situation: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Here the relevant cause is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. Apply it by: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

D.

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: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. Apply it by: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

Question 318

A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope. The reviewed recommendation is: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. 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 known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.
  3. Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.
  4. Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

Answer & Explanations

Correct answer: C

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: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

B.

Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. That test is for another requirement: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. It does not verify the stated outcome; the relevant check is: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

C.

Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. This directly tests whether the chosen intervention works: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. The causal mechanism is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

D.

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: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

Question 319

A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope. Which tempting SOC change would undermine the stated requirement?

  1. Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference.
  2. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.
  3. Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule.
  4. Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity.

Answer & Explanations

Correct answer: A

A.

Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference. The risk is: An incorrect time window drives false performance and security conclusions in compliance reporting. The safer action is: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Confirm by: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

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: Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference. Its risk is: An incorrect time window drives false performance and security conclusions in compliance reporting. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

C.

Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. That is an appropriate action for the separate case: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. It is not the unsafe shortcut asked about here. Reject: Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference. Its risk is: An incorrect time window drives false performance and security conclusions in compliance reporting.

D.

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: Treat a one-hour widget total as a monthly measure and accuse the reporting engine of losing the difference. Its risk is: An incorrect time window drives false performance and security conclusions in compliance reporting.

Question 320

A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. Choose this FortiAnalyzer analyst action: Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. Validate using: Compare completion times for one representative report before and after off-peak scheduling and verified cache population.
  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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.

Answer & Explanations

Correct answer: A

A.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Check the result: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. The technical reason is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

B.

Choose this FortiAnalyzer analyst action: Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. Validate using: Compare completion times for one representative report before and after off-peak scheduling and verified cache population. This action-and-test pairing concerns another situation: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. The current case needs this action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Test with: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

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: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Test with: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

D.

Choose this FortiAnalyzer analyst action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. This action-and-test pairing concerns another situation: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. The current case needs this action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Test with: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

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