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 69

Question 680

A retailer's security team operates many reports with nearly identical SQL grouping and wants to verify hcache effectiveness. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Validate using: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report.

Answer & Explanations

Correct answer: B

A.

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: Evaluate reusable chart datasets, report grouping, and appropriate hcache auto-cache behavior for the actual reporting workload. Test with: Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent.

B.

Evaluate reusable chart datasets, report grouping, and appropriate hcache auto-cache behavior for the actual reporting workload. Check the result: Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent. The technical reason is: Precomputed cache or aggregated query results can reduce repeated heavy SQL calculations when supported by report design and cache readiness. The fictional case is: A retailer's security team operates many reports with nearly identical SQL grouping and wants to verify hcache effectiveness.

C.

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. This action-and-test pairing concerns another situation: A hospital reports on production clinical firewalls but one laboratory FortiGate must remain excluded from regulatory metrics. The current case needs this action: Evaluate reusable chart datasets, report grouping, and appropriate hcache auto-cache behavior for the actual reporting workload. Test with: Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent. The fictional case is: A retailer's security team operates many reports with nearly identical SQL grouping and wants to verify hcache effectiveness.

D.

Choose this FortiAnalyzer analyst action: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Validate using: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report. This action-and-test pairing concerns another situation: A bank SOC wants its report to count blocked destinations by subnet but the new chart has no dataset query. The current case needs this action: Evaluate reusable chart datasets, report grouping, and appropriate hcache auto-cache behavior for the actual reporting workload. Test with: Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent.

Question 681

A university needs a chart of high-severity security events but the dataset counts ordinary allowed sessions instead. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records.
  2. Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.
  3. Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it.
  4. Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

Answer & Explanations

Correct answer: D

A.

Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records. That action is relevant to a different problem: A hospital custom report uses an obsolete column name after a log field mapping change and the associated chart returns nothing. Its technical basis is: A report chart cannot produce a meaningful result when its dataset references nonexistent columns or the wrong log type. The present case instead requires: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

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: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

C.

Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. That action is relevant to a different problem: A bank SOC wants its report to count blocked destinations by subnet but the new chart has no dataset query. Its technical basis is: A dataset defines the database query that produces chart data while the chart formats returned rows and the report template arranges the output. The present case instead requires: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

D.

Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. The technical reason is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. Confirm by: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

Question 682

A university needs a chart of high-severity security events but the dataset counts ordinary allowed sessions instead. The reviewed recommendation is: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition.
  2. SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields.
  3. A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule.
  4. A report chart cannot produce a meaningful result when its dataset references nonexistent columns or the wrong log type.

Answer & Explanations

Correct answer: B

A.

Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. That principle explains a different situation: A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. Here the relevant cause is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. Apply it by: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

B.

SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. It explains why the intervention—review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset—addresses the stated problem. Test the mechanism by: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

C.

A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. That principle explains a different situation: A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. Here the relevant cause is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. Apply it by: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

D.

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: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. Apply it by: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

Question 683

A university needs a chart of high-severity security events but the dataset counts ordinary allowed sessions instead. The reviewed recommendation is: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Which observation best demonstrates that this corrective step worked?

  1. Generate the report against a known test device list and confirm its contributing sources match the approved compliance inventory.
  2. Run test queries for known traffic and security records and confirm the chart counts only the intended category.
  3. Run a limited dataset test with one known indexed event and confirm correct field extraction and grouped output before rerunning the report.
  4. Build a test chart from a scoped log sample and compare its grouped totals to the same verified Log View data interval.

Answer & Explanations

Correct answer: B

A.

Generate the report against a known test device list and confirm its contributing sources match the approved compliance inventory. That test is for another requirement: A hospital reports on production clinical firewalls but one laboratory FortiGate must remain excluded from regulatory metrics. It does not verify the stated outcome; the relevant check is: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

B.

Run test queries for known traffic and security records and confirm the chart counts only the intended category. This directly tests whether the chosen intervention works: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. The causal mechanism is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields.

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: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

D.

Build a test chart from a scoped log sample and compare its grouped totals to the same verified Log View data interval. That test is for another requirement: A hospital analyst wants a reusable chart of blocked web categories derived from a filtered FortiAnalyzer Log View search. It does not verify the stated outcome; the relevant check is: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

Question 684

A university needs a chart of high-severity security events but the dataset counts ordinary allowed sessions instead. Which unsafe investigation or automation shortcut must be rejected?

  1. Check administrator profiles, ADOM permissions, and report-object access before changing global database or log storage settings.
  2. Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it.
  3. Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status.
  4. Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries.

Answer & Explanations

Correct answer: C

A.

Check administrator profiles, ADOM permissions, and report-object access before changing global database or log storage settings. That is an appropriate action for the separate case: A managed service provider allows one hospital analyst to view its weekly report while another authorized role gets permission denied. It is not the unsafe shortcut asked about here. Reject: Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status. Its risk is: Management receives inflated incident figures and the report cannot support its security claims.

B.

Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. That is an appropriate action for the separate case: A bank SOC wants its report to count blocked destinations by subnet but the new chart has no dataset query. It is not the unsafe shortcut asked about here. Reject: Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status. Its risk is: Management receives inflated incident figures and the report cannot support its security claims.

C.

Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status. The risk is: Management receives inflated incident figures and the report cannot support its security claims. The safer action is: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Confirm by: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

D.

Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries. That is an appropriate action for the separate case: A multinational bank reports an end-of-month login spike on the wrong day after generating a FortiAnalyzer report in a different time zone. It is not the unsafe shortcut asked about here. Reject: Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status. Its risk is: Management receives inflated incident figures and the report cannot support its security claims.

Question 685

A university needs a chart of high-severity security events but the dataset counts ordinary allowed sessions instead. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Validate using: Run test queries for known traffic and security records and confirm the chart counts only the intended category.
  2. Choose this FortiAnalyzer analyst action: Check administrator profiles, ADOM permissions, and report-object access before changing global database or log storage settings. Validate using: Run the same non-sensitive report as an approved administrator and a restricted analyst to verify intended access boundaries.
  3. Choose this FortiAnalyzer analyst action: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Validate using: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report.
  4. Choose this FortiAnalyzer analyst action: Use supported chart and dataset editing or Chart Builder tools to translate the intended log query into a validated reusable report chart. Validate using: Build a test chart from a scoped log sample and compare its grouped totals to the same verified Log View data interval.

Answer & Explanations

Correct answer: A

A.

Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Check the result: Run test queries for known traffic and security records and confirm the chart counts only the intended category. The technical reason is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields.

B.

Choose this FortiAnalyzer analyst action: Check administrator profiles, ADOM permissions, and report-object access before changing global database or log storage settings. Validate using: Run the same non-sensitive report as an approved administrator and a restricted analyst to verify intended access boundaries. This action-and-test pairing concerns another situation: A managed service provider allows one hospital analyst to view its weekly report while another authorized role gets permission denied. The current case needs this action: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Test with: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

C.

Choose this FortiAnalyzer analyst action: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Validate using: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report. This action-and-test pairing concerns another situation: A bank SOC wants its report to count blocked destinations by subnet but the new chart has no dataset query. The current case needs this action: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Test with: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

D.

Choose this FortiAnalyzer analyst action: Use supported chart and dataset editing or Chart Builder tools to translate the intended log query into a validated reusable report chart. Validate using: Build a test chart from a scoped log sample and compare its grouped totals to the same verified Log View data interval. This action-and-test pairing concerns another situation: A hospital analyst wants a reusable chart of blocked web categories derived from a filtered FortiAnalyzer Log View search. The current case needs this action: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Test with: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

Question 686

A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes. What is the most defensible FortiAnalyzer action in this situation?

  1. Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow.
  2. Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records.
  3. Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.
  4. Use supported chart and dataset editing or Chart Builder tools to translate the intended log query into a validated reusable report chart.

Answer & Explanations

Correct answer: C

A.

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: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

B.

Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records. That action is relevant to a different problem: A hospital custom report uses an obsolete column name after a log field mapping change and the associated chart returns nothing. Its technical basis is: A report chart cannot produce a meaningful result when its dataset references nonexistent columns or the wrong log type. The present case instead requires: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. The fictional case is: A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes.

C.

Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. The technical reason is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. Confirm by: Run test queries for known traffic and security records and confirm the chart counts only the intended category. The fictional case is: A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes.

D.

Use supported chart and dataset editing or Chart Builder tools to translate the intended log query into a validated reusable report chart. That action is relevant to a different problem: A hospital analyst wants a reusable chart of blocked web categories derived from a filtered FortiAnalyzer Log View search. Its technical basis is: Interactive filters and report datasets serve related but distinct purposes and a report requires a correctly defined query for the displayed chart. The present case instead requires: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

Question 687

A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes. The reviewed recommendation is: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. What FortiAnalyzer mechanism supports the recommended analysis?

  1. SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields.
  2. A dataset defines the database query that produces chart data while the chart formats returned rows and the report template arranges the output.
  3. A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule.
  4. Templates organize visual structure while report definitions specify scope and execution settings and generated files are snapshots from prior runs.

Answer & Explanations

Correct answer: A

A.

SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. It explains why the intervention—review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset—addresses the stated problem. Test the mechanism by: Run test queries for known traffic and security records and confirm the chart counts only the intended category. The fictional case is: A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes.

B.

A dataset defines the database query that produces chart data while the chart formats returned rows and the report template arranges the output. That principle explains a different situation: A bank SOC wants its report to count blocked destinations by subnet but the new chart has no dataset query. Here the relevant cause is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. Apply it by: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

C.

A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. That principle explains a different situation: A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. Here the relevant cause is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. Apply it by: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. The fictional case is: A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes.

D.

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: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. Apply it by: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

Question 688

A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes. The reviewed recommendation is: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. What pilot verification directly establishes the intended result?

  1. Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.
  2. Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report.
  3. Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events.
  4. Run test queries for known traffic and security records and confirm the chart counts only the intended category.

Answer & Explanations

Correct answer: D

A.

Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. That test is for another requirement: A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. It does not verify the stated outcome; the relevant check is: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

B.

Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report. That test is for another requirement: A bank SOC wants its report to count blocked destinations by subnet but the new chart has no dataset query. It does not verify the stated outcome; the relevant check is: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

C.

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: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

D.

Run test queries for known traffic and security records and confirm the chart counts only the intended category. This directly tests whether the chosen intervention works: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. The causal mechanism is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. The fictional case is: A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes.

Question 689

A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes. Which tempting SOC change would undermine the stated requirement?

  1. Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records.
  2. Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.
  3. Use supported chart and dataset editing or Chart Builder tools to translate the intended log query into a validated reusable report chart.
  4. Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status.

Answer & Explanations

Correct answer: D

A.

Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records. That is an appropriate action for the separate case: A hospital custom report uses an obsolete column name after a log field mapping change and the associated chart returns nothing. It is not the unsafe shortcut asked about here. Reject: Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status. Its risk is: Management receives inflated incident figures and the report cannot support its security claims.

B.

Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. That is an appropriate action for the separate case: A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. It is not the unsafe shortcut asked about here. Reject: Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status. Its risk is: Management receives inflated incident figures and the report cannot support its security claims.

C.

Use supported chart and dataset editing or Chart Builder tools to translate the intended log query into a validated reusable report chart. That is an appropriate action for the separate case: A hospital analyst wants a reusable chart of blocked web categories derived from a filtered FortiAnalyzer Log View search. It is not the unsafe shortcut asked about here. Reject: Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status. Its risk is: Management receives inflated incident figures and the report cannot support its security claims.

D.

Use a universal count of all database rows as the number of confirmed incidents without filtering or investigation status. The risk is: Management receives inflated incident figures and the report cannot support its security claims. The safer action is: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Confirm by: Run test queries for known traffic and security records and confirm the chart counts only the intended category. The fictional case is: A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes.

Question 690

A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  3. Choose this FortiAnalyzer analyst action: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Validate using: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report.
  4. Choose this FortiAnalyzer analyst action: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Validate using: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

Answer & Explanations

Correct answer: D

A.

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: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Test with: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

B.

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: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Test with: Run test queries for known traffic and security records and confirm the chart counts only the intended category.

C.

Choose this FortiAnalyzer analyst action: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Validate using: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report. This action-and-test pairing concerns another situation: A bank SOC wants its report to count blocked destinations by subnet but the new chart has no dataset query. The current case needs this action: Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Test with: Run test queries for known traffic and security records and confirm the chart counts only the intended category. The fictional case is: A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes.

D.

Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. Check the result: Run test queries for known traffic and security records and confirm the chart counts only the intended category. The technical reason is: SQL tables store distinct event and traffic records and meaningful report metrics require explicit selection and aggregation of the intended fields. The fictional case is: A bank reports an incident total from FortiAnalyzer log rows without selecting the actual incident or detection attributes.

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