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 72

Question 710

A bank's FortiAnalyzer group report includes a temporary test appliance and the auditor needs the scope corrected. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Select the intended ADOM, devices or device group, time period, and output template before generating the final report. Validate using: Generate the report against a known test device list and confirm its contributing sources match the approved compliance inventory.
  2. Choose this FortiAnalyzer analyst action: Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries. Validate using: Generate a known boundary-hour test event and compare the report's included timestamps under explicitly documented time zone settings.
  3. Choose this FortiAnalyzer analyst action: Group appropriate reports with similar templates and schedule supported runs during controlled off-peak periods. Validate using: Compare total job execution and generated chart consistency before and after grouping and staggering a representative set.
  4. Choose this FortiAnalyzer analyst action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Validate using: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

Answer & Explanations

Correct answer: A

A.

Select the intended ADOM, devices or device group, time period, and output template before generating the final report. Check the result: Generate the report against a known test device list and confirm its contributing sources match the approved compliance inventory. The technical reason is: The report definition determines which indexed logs are queried, and devices outside its scope must not contaminate the result. The fictional case is: A bank's FortiAnalyzer group report includes a temporary test appliance and the auditor needs the scope corrected.

B.

Choose this FortiAnalyzer analyst action: Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries. Validate using: Generate a known boundary-hour test event and compare the report's included timestamps under explicitly documented time zone settings. This action-and-test pairing concerns another situation: A multinational bank reports an end-of-month login spike on the wrong day after generating a FortiAnalyzer report in a different time zone. The current case needs this action: Select the intended ADOM, devices or device group, time period, and output template before generating the final report. Test with: Generate the report against a known test device list and confirm its contributing sources match the approved compliance inventory.

C.

Choose this FortiAnalyzer analyst action: Group appropriate reports with similar templates and schedule supported runs during controlled off-peak periods. Validate using: Compare total job execution and generated chart consistency before and after grouping and staggering a representative set. This action-and-test pairing concerns another situation: A retail chain needs similar site reports for hundreds of branches and wants to avoid repeated high-cost cache construction. The current case needs this action: Select the intended ADOM, devices or device group, time period, and output template before generating the final report. Test with: Generate the report against a known test device list and confirm its contributing sources match the approved compliance inventory.

D.

Choose this FortiAnalyzer analyst action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Validate using: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. This action-and-test pairing concerns another situation: A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. The current case needs this action: Select the intended ADOM, devices or device group, time period, and output template before generating the final report. Test with: Generate the report against a known test device list and confirm its contributing sources match the approved compliance inventory.

Question 711

A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.
  2. Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.
  3. Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow.
  4. Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

Answer & Explanations

Correct answer: B

A.

Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. That action is relevant to a different problem: A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. Its technical basis is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. The present case instead requires: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

B.

Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. The technical reason is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. Confirm by: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

C.

Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow. That action is relevant to a different problem: A bank auditor reviews last month's PDF while the SOC is modifying its current FortiAnalyzer report template. Its technical basis is: Templates organize visual structure while report definitions specify scope and execution settings and generated files are snapshots from prior runs. The present case instead requires: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

D.

Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. That action is relevant to a different problem: A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. Its technical basis is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. The present case instead requires: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

Question 712

A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. The reviewed recommendation is: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. A report chart cannot produce a meaningful result when its dataset references nonexistent columns or the wrong log type.
  2. A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule.
  3. Templates organize visual structure while report definitions specify scope and execution settings and generated files are snapshots from prior runs.
  4. FortiAnalyzer reporting and analysis actions are governed by the user's authorized administrative domain and role privileges.

Answer & Explanations

Correct answer: B

A.

A report chart cannot produce a meaningful result when its dataset references nonexistent columns or the wrong log type. That principle explains a different situation: A hospital custom report uses an obsolete column name after a log field mapping change and the associated chart returns nothing. Here the relevant cause is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. Apply it by: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

B.

A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. It explains why the intervention—enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job—addresses the stated problem. Test the mechanism by: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

C.

Templates organize visual structure while report definitions specify scope and execution settings and generated files are snapshots from prior runs. That principle explains a different situation: A bank auditor reviews last month's PDF while the SOC is modifying its current FortiAnalyzer report template. Here the relevant cause is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. Apply it by: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

D.

FortiAnalyzer reporting and analysis actions are governed by the user's authorized administrative domain and role privileges. That principle explains a different situation: A managed service provider allows one hospital analyst to view its weekly report while another authorized role gets permission denied. Here the relevant cause is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. Apply it by: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

Question 713

A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. The reviewed recommendation is: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Which observation best demonstrates that this corrective step worked?

  1. Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events.
  2. Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged.
  3. Run a limited dataset test with one known indexed event and confirm correct field extraction and grouped output before rerunning the report.
  4. Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

Answer & Explanations

Correct answer: D

A.

Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events. That test is for another requirement: A bank must rerun last year's firewall incident statistics after the original Analytics range was aged into Archive. It does not verify the stated outcome; the relevant check is: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

B.

Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged. That test is for another requirement: A bank auditor reviews last month's PDF while the SOC is modifying its current FortiAnalyzer report template. It does not verify the stated outcome; the relevant check is: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

C.

Run a limited dataset test with one known indexed event and confirm correct field extraction and grouped output before rerunning the report. That test is for another requirement: A hospital custom report uses an obsolete column name after a log field mapping change and the associated chart returns nothing. It does not verify the stated outcome; the relevant check is: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

D.

Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. This directly tests whether the chosen intervention works: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. The causal mechanism is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule.

Question 714

A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. Which unsafe investigation or automation shortcut must be rejected?

  1. Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow.
  2. Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.
  3. Assume saving a report template automatically schedules it every week without any schedule configuration.
  4. Select the intended ADOM, devices or device group, time period, and output template before generating the final report.

Answer & Explanations

Correct answer: C

A.

Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow. That is an appropriate action for the separate case: A bank auditor reviews last month's PDF while the SOC is modifying its current FortiAnalyzer report template. It is not the unsafe shortcut asked about here. Reject: Assume saving a report template automatically schedules it every week without any schedule configuration. Its risk is: No weekly security summary is generated and a required audit reporting cycle is missed.

B.

Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. That is an appropriate action for the separate case: A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. It is not the unsafe shortcut asked about here. Reject: Assume saving a report template automatically schedules it every week without any schedule configuration. Its risk is: No weekly security summary is generated and a required audit reporting cycle is missed.

C.

Assume saving a report template automatically schedules it every week without any schedule configuration. The risk is: No weekly security summary is generated and a required audit reporting cycle is missed. The safer action is: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Confirm by: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

D.

Select the intended ADOM, devices or device group, time period, and output template before generating the final report. That is an appropriate action for the separate case: A hospital reports on production clinical firewalls but one laboratory FortiGate must remain excluded from regulatory metrics. It is not the unsafe shortcut asked about here. Reject: Assume saving a report template automatically schedules it every week without any schedule configuration. Its risk is: No weekly security summary is generated and a required audit reporting cycle is missed.

Question 715

A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. Validate using: Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events.
  2. Choose this FortiAnalyzer analyst action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Validate using: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.
  3. Choose this FortiAnalyzer analyst action: Evaluate reusable chart datasets, report grouping, and appropriate hcache auto-cache behavior for the actual reporting workload. Validate using: Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent.
  4. Choose this FortiAnalyzer analyst action: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Validate using: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. Validate using: Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events. This action-and-test pairing concerns another situation: A bank must rerun last year's firewall incident statistics after the original Analytics range was aged into Archive. The current case needs this action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Test with: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

B.

Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Check the result: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. The technical reason is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule.

C.

Choose this FortiAnalyzer analyst action: Evaluate reusable chart datasets, report grouping, and appropriate hcache auto-cache behavior for the actual reporting workload. Validate using: Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent. This action-and-test pairing concerns another situation: A hospital runs similar monthly traffic charts for twenty sites and needs to avoid unnecessary repeated aggregation. The current case needs this action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Test with: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

D.

Choose this FortiAnalyzer analyst action: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Validate using: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. This action-and-test pairing concerns another situation: A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. The current case needs this action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Test with: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

Question 716

A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup. What is the most defensible FortiAnalyzer action in this situation?

  1. Select the intended ADOM, devices or device group, time period, and output template before generating the final report.
  2. Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.
  3. Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.
  4. Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

Answer & Explanations

Correct answer: D

A.

Select the intended ADOM, devices or device group, time period, and output template before generating the final report. That action is relevant to a different problem: A hospital reports on production clinical firewalls but one laboratory FortiGate must remain excluded from regulatory metrics. Its technical basis is: The report definition determines which indexed logs are queried, and devices outside its scope must not contaminate the result. The present case instead requires: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

B.

Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. That action is relevant to a different problem: A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. Its technical basis is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. The present case instead requires: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

C.

Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. That action is relevant to a different problem: A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. Its technical basis is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. The present case instead requires: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

D.

Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. The technical reason is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. Confirm by: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

Question 717

A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup. The reviewed recommendation is: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Templates organize visual structure while report definitions specify scope and execution settings and generated files are snapshots from prior runs.
  2. A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule.
  3. FortiAnalyzer reporting and analysis actions are governed by the user's authorized administrative domain and role privileges.
  4. Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct.

Answer & Explanations

Correct answer: B

A.

Templates organize visual structure while report definitions specify scope and execution settings and generated files are snapshots from prior runs. That principle explains a different situation: A bank auditor reviews last month's PDF while the SOC is modifying its current FortiAnalyzer report template. Here the relevant cause is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. Apply it by: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

B.

A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. It explains why the intervention—enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job—addresses the stated problem. Test the mechanism by: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

C.

FortiAnalyzer reporting and analysis actions are governed by the user's authorized administrative domain and role privileges. That principle explains a different situation: A managed service provider allows one hospital analyst to view its weekly report while another authorized role gets permission denied. Here the relevant cause is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. Apply it by: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

D.

Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. That principle explains a different situation: A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. Here the relevant cause is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. Apply it by: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

Question 718

A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup. The reviewed recommendation is: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. What pilot verification directly establishes the intended result?

  1. Deliver a non-sensitive test report to the approved external store and check retrievability, file integrity, and access scope.
  2. Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.
  3. Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.
  4. Run the same non-sensitive report as an approved administrator and a restricted analyst to verify intended access boundaries.

Answer & Explanations

Correct answer: C

A.

Deliver a non-sensitive test report to the approved external store and check retrievability, file integrity, and access scope. That test is for another requirement: A university needs to archive monthly FortiAnalyzer incident reports in a governed external evidence repository. It does not verify the stated outcome; the relevant check is: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

B.

Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. That test is for another requirement: A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. It does not verify the stated outcome; the relevant check is: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

C.

Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. This directly tests whether the chosen intervention works: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. The causal mechanism is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

D.

Run the same non-sensitive report as an approved administrator and a restricted analyst to verify intended access boundaries. That test is for another requirement: A managed service provider allows one hospital analyst to view its weekly report while another authorized role gets permission denied. It does not verify the stated outcome; the relevant check is: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

Question 719

A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup. Which tempting SOC change would undermine the stated requirement?

  1. Select the intended ADOM, devices or device group, time period, and output template before generating the final report.
  2. Assume saving a report template automatically schedules it every week without any schedule configuration.
  3. Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate.
  4. Configure a supported external report storage or export destination with verified authorization and retention controls.

Answer & Explanations

Correct answer: B

A.

Select the intended ADOM, devices or device group, time period, and output template before generating the final report. That is an appropriate action for the separate case: A hospital reports on production clinical firewalls but one laboratory FortiGate must remain excluded from regulatory metrics. It is not the unsafe shortcut asked about here. Reject: Assume saving a report template automatically schedules it every week without any schedule configuration. Its risk is: No weekly security summary is generated and a required audit reporting cycle is missed. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

B.

Assume saving a report template automatically schedules it every week without any schedule configuration. The risk is: No weekly security summary is generated and a required audit reporting cycle is missed. The safer action is: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Confirm by: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

C.

Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. That is an appropriate action for the separate case: A bank must rerun last year's firewall incident statistics after the original Analytics range was aged into Archive. It is not the unsafe shortcut asked about here. Reject: Assume saving a report template automatically schedules it every week without any schedule configuration. Its risk is: No weekly security summary is generated and a required audit reporting cycle is missed.

D.

Configure a supported external report storage or export destination with verified authorization and retention controls. That is an appropriate action for the separate case: A university needs to archive monthly FortiAnalyzer incident reports in a governed external evidence repository. It is not the unsafe shortcut asked about here. Reject: Assume saving a report template automatically schedules it every week without any schedule configuration. Its risk is: No weekly security summary is generated and a required audit reporting cycle is missed.

Question 720

A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries. Validate using: Generate a known boundary-hour test event and compare the report's included timestamps under explicitly documented time zone settings.
  2. Choose this FortiAnalyzer analyst action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Validate using: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.
  3. Choose this FortiAnalyzer analyst action: Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. Validate using: Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events.
  4. Choose this FortiAnalyzer analyst action: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Validate using: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries. Validate using: Generate a known boundary-hour test event and compare the report's included timestamps under explicitly documented time zone settings. This action-and-test pairing concerns another situation: A multinational bank reports an end-of-month login spike on the wrong day after generating a FortiAnalyzer report in a different time zone. The current case needs this action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Test with: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

B.

Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Check the result: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. The technical reason is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

C.

Choose this FortiAnalyzer analyst action: Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. Validate using: Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events. This action-and-test pairing concerns another situation: A bank must rerun last year's firewall incident statistics after the original Analytics range was aged into Archive. The current case needs this action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Test with: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time. The fictional case is: A regional hospital creates a weekly incident summary yet its schedule checkbox was left disabled during setup.

D.

Choose this FortiAnalyzer analyst action: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Validate using: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. This action-and-test pairing concerns another situation: A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. The current case needs this action: Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. Test with: Use a safe pilot schedule and confirm the report appears as a job in the calendar and produces an artifact at the expected time.

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