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 39

Question 380

A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Validate using: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.
  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: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Validate using: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.
  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: C

A.

Choose this FortiAnalyzer analyst action: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Validate using: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. This action-and-test pairing concerns another situation: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. The current case needs this action: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Test with: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

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: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Test with: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

C.

Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Check the result: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report. The technical reason is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. The fictional case is: A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated.

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: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Test with: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

Question 381

A hospital SOC can download a PDF report manually but the daily summary email stopped arriving after SMTP settings changed. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.
  2. Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer.
  3. Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.
  4. Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

Answer & Explanations

Correct answer: D

A.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. That action is relevant to a different problem: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Its technical basis is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. The present case instead requires: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

B.

Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer. That action is relevant to a different problem: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. Its technical basis is: Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source. The present case instead requires: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

C.

Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. That action is relevant to a different problem: A financial SOC adds a report chart referencing a field not present in its FortiAnalyzer log table. Its technical basis is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. The present case instead requires: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

D.

Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. The technical reason is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. Confirm by: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

Question 382

A hospital SOC can download a PDF report manually but the daily summary email stopped arriving after SMTP settings changed. The reviewed recommendation is: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection.
  2. Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window.
  3. Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies.
  4. Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria.

Answer & Explanations

Correct answer: C

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: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. Apply it by: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

B.

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: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. Apply it by: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

C.

Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. It explains why the intervention—distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity—addresses the stated problem. Test the mechanism by: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

D.

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: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. Apply it by: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

Question 383

A hospital SOC can download a PDF report manually but the daily summary email stopped arriving after SMTP settings changed. The reviewed recommendation is: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Which observation best demonstrates that this corrective step worked?

  1. Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.
  2. Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
  3. Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
  4. After a controlled log ingestion interval, compare the Archive arrival timestamp with indexed Analytics count and rerun the same report window.

Answer & Explanations

Correct answer: A

A.

Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage. This directly tests whether the chosen intervention works: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. The causal mechanism is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies.

B.

Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. That test is for another requirement: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. It does not verify the stated outcome; the relevant check is: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

C.

Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. That test is for another requirement: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. It does not verify the stated outcome; the relevant check is: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

D.

After a controlled log ingestion interval, compare the Archive arrival timestamp with indexed Analytics count and rerun the same report window. That test is for another requirement: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. It does not verify the stated outcome; the relevant check is: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

Question 384

A hospital SOC can download a PDF report manually but the daily summary email stopped arriving after SMTP settings changed. 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. Verify the report definition's ADOM, selected devices, and time filter match the original logging sources.
  3. Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.
  4. Delete the report dataset because an email was not received without checking whether the report itself generated successfully.

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: Delete the report dataset because an email was not received without checking whether the report itself generated successfully. Its risk is: Reports exist locally but compliance stakeholders never receive the required scheduled evidence.

B.

Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. That is an appropriate action for the separate case: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. It is not the unsafe shortcut asked about here. Reject: Delete the report dataset because an email was not received without checking whether the report itself generated successfully. Its risk is: Reports exist locally but compliance stakeholders never receive the required scheduled evidence.

C.

Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. That is an appropriate action for the separate case: A financial SOC adds a report chart referencing a field not present in its FortiAnalyzer log table. It is not the unsafe shortcut asked about here. Reject: Delete the report dataset because an email was not received without checking whether the report itself generated successfully. Its risk is: Reports exist locally but compliance stakeholders never receive the required scheduled evidence.

D.

Delete the report dataset because an email was not received without checking whether the report itself generated successfully. The risk is: Reports exist locally but compliance stakeholders never receive the required scheduled evidence. The safer action is: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Confirm by: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

Question 385

A hospital SOC can download a PDF report manually but the daily summary email stopped arriving after SMTP settings changed. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Validate using: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.
  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: 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: A

A.

Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Check the result: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage. The technical reason is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies.

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: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Test with: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

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: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Test with: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

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: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Test with: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

Question 386

A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy. What is the most defensible FortiAnalyzer action in this situation?

  1. Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
  2. Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule.
  3. Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range.
  4. Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

Answer & Explanations

Correct answer: D

A.

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: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

B.

Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. That action is relevant to a different problem: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. Its technical basis is: SQL aggregation and report cache processing consume resources that may conflict with log maintenance and can be improved through appropriate report grouping. The present case instead requires: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

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: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

D.

Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. The technical reason is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. Confirm by: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

Question 387

A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy. The reviewed recommendation is: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Multiple alerts can describe one traffic or security sequence and unambiguous event identity prevents duplicate investigations.
  2. Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window.
  3. Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies.
  4. FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction.

Answer & Explanations

Correct answer: C

A.

Multiple alerts can describe one traffic or security sequence and unambiguous event identity prevents duplicate investigations. That principle explains a different situation: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. Here the relevant cause is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. Apply it by: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

B.

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: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. Apply it by: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

C.

Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. It explains why the intervention—distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity—addresses the stated problem. Test the mechanism by: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

D.

FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. That principle explains a different situation: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Here the relevant cause is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. Apply it by: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

Question 388

A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy. The reviewed recommendation is: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. What pilot verification directly establishes the intended result?

  1. Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
  2. Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.
  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. Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

Answer & Explanations

Correct answer: D

A.

Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. That test is for another requirement: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. It does not verify the stated outcome; the relevant check is: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

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: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

C.

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: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

D.

Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage. This directly tests whether the chosen intervention works: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. The causal mechanism is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

Question 389

A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy. Which tempting SOC change would undermine the stated requirement?

  1. Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.
  2. Verify the report definition's ADOM, selected devices, and time filter match the original logging sources.
  3. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.
  4. Delete the report dataset because an email was not received without checking whether the report itself generated successfully.

Answer & Explanations

Correct answer: D

A.

Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. That is an appropriate action for the separate case: A financial SOC adds a report chart referencing a field not present in its FortiAnalyzer log table. It is not the unsafe shortcut asked about here. Reject: Delete the report dataset because an email was not received without checking whether the report itself generated successfully. Its risk is: Reports exist locally but compliance stakeholders never receive the required scheduled evidence. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

B.

Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. That is an appropriate action for the separate case: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. It is not the unsafe shortcut asked about here. Reject: Delete the report dataset because an email was not received without checking whether the report itself generated successfully. Its risk is: Reports exist locally but compliance stakeholders never receive the required scheduled evidence. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

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: Delete the report dataset because an email was not received without checking whether the report itself generated successfully. Its risk is: Reports exist locally but compliance stakeholders never receive the required scheduled evidence.

D.

Delete the report dataset because an email was not received without checking whether the report itself generated successfully. The risk is: Reports exist locally but compliance stakeholders never receive the required scheduled evidence. The safer action is: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Confirm by: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

Question 390

A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. Choose this FortiAnalyzer analyst action: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Validate using: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.
  3. Choose this FortiAnalyzer analyst action: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Validate using: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.
  4. Choose this FortiAnalyzer analyst action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Validate using: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.

Answer & Explanations

Correct answer: B

A.

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: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Test with: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

B.

Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Check the result: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage. The technical reason is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. The fictional case is: A bank audit report runs on demand but scheduled jobs are disabled and no manager receives the expected monthly copy.

C.

Choose this FortiAnalyzer analyst action: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Validate using: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. This action-and-test pairing concerns another situation: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. The current case needs this action: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Test with: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

D.

Choose this FortiAnalyzer analyst action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Validate using: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. This action-and-test pairing concerns another situation: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. The current case needs this action: Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. Test with: Run a harmless scheduled report and inspect its generated artifact, schedule result, and mail delivery log to find the failed stage.

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