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 66

Question 650

A university builds a weekly top-threats chart but only edits the report layout without defining data selection. 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: 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.
  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: Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow. Validate using: Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged.

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: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Test with: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report. The fictional case is: A university builds a weekly top-threats chart but only edits the report layout without defining data selection.

B.

Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Check the result: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report. The technical reason 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 fictional case is: A university builds a weekly top-threats chart but only edits the report layout without defining data selection.

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: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Test with: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report.

D.

Choose this FortiAnalyzer analyst action: Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow. Validate using: Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged. This action-and-test pairing concerns another situation: A bank auditor reviews last month's PDF while the SOC is modifying its current FortiAnalyzer report template. The current case needs this action: Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it. Test with: Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report.

Question 651

A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. 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 supported chart and dataset editing or Chart Builder tools to translate the intended log query into a validated reusable report chart.
  3. Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.
  4. Group appropriate reports with similar templates and schedule supported runs during controlled off-peak periods.

Answer & Explanations

Correct answer: C

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: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

B.

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: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

C.

Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. The technical reason is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. Confirm by: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

D.

Group appropriate reports with similar templates and schedule supported runs during controlled off-peak periods. That action is relevant to a different problem: A retail chain needs similar site reports for hundreds of branches and wants to avoid repeated high-cost cache construction. Its technical basis is: Grouping and intelligent scheduling can reduce repeated hcache work and avoid resource contention with log processing tasks. The present case instead requires: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

Question 652

A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. The reviewed recommendation is: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Templates organize visual structure while report definitions specify scope and execution settings and generated files are snapshots from prior runs.
  2. A report chart cannot produce a meaningful result when its dataset references nonexistent columns or the wrong log type.
  3. Grouping and intelligent scheduling can reduce repeated hcache work and avoid resource contention with log processing tasks.
  4. Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition.

Answer & Explanations

Correct answer: D

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: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. Apply it by: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

B.

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: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. Apply it by: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

C.

Grouping and intelligent scheduling can reduce repeated hcache work and avoid resource contention with log processing tasks. That principle explains a different situation: A retail chain needs similar site reports for hundreds of branches and wants to avoid repeated high-cost cache construction. Here the relevant cause is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. Apply it by: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

D.

Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. It explains why the intervention—use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports—addresses the stated problem. Test the mechanism by: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

Question 653

A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. The reviewed recommendation is: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Which observation best demonstrates that this corrective step worked?

  1. Compare total job execution and generated chart consistency before and after grouping and staggering a representative set.
  2. Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.
  3. Run test queries for known traffic and security records and confirm the chart counts only the intended category.
  4. Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent.

Answer & Explanations

Correct answer: B

A.

Compare total job execution and generated chart consistency before and after grouping and staggering a representative set. That test is for another requirement: A retail chain needs similar site reports for hundreds of branches and wants to avoid repeated high-cost cache construction. It does not verify the stated outcome; the relevant check is: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

B.

Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. This directly tests whether the chosen intervention works: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. The causal mechanism is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition.

C.

Run test queries for known traffic and security records and confirm the chart counts only the intended category. That test is for another requirement: A university needs a chart of high-severity security events but the dataset counts ordinary allowed sessions instead. It does not verify the stated outcome; the relevant check is: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

D.

Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent. That test is for another requirement: A hospital runs similar monthly traffic charts for twenty sites and needs to avoid unnecessary repeated aggregation. It does not verify the stated outcome; the relevant check is: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

Question 654

A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. Which unsafe investigation or automation shortcut must be rejected?

  1. Select the intended ADOM, devices or device group, time period, and output template before generating the final report.
  2. Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.
  3. Hardcode the original firewall serial into every chart query and declare the template universally reusable.
  4. Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset.

Answer & Explanations

Correct answer: C

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: Hardcode the original firewall serial into every chart query and declare the template universally reusable. Its risk is: Copied reports show the wrong device's events while appearing to summarize the selected site.

B.

Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. That is an appropriate action for the separate case: A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. It is not the unsafe shortcut asked about here. Reject: Hardcode the original firewall serial into every chart query and declare the template universally reusable. Its risk is: Copied reports show the wrong device's events while appearing to summarize the selected site.

C.

Hardcode the original firewall serial into every chart query and declare the template universally reusable. The risk is: Copied reports show the wrong device's events while appearing to summarize the selected site. The safer action is: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Confirm by: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

D.

Review actual FortiAnalyzer log table schema and apply correct log type, time, action, and grouping predicates in the dataset. That is an appropriate action for the separate case: A university needs a chart of high-severity security events but the dataset counts ordinary allowed sessions instead. It is not the unsafe shortcut asked about here. Reject: Hardcode the original firewall serial into every chart query and declare the template universally reusable. Its risk is: Copied reports show the wrong device's events while appearing to summarize the selected site.

Question 655

A regional retailer clones one FortiAnalyzer weekly report for several branches but every chart still queries its headquarters device. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. 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.
  2. Choose this FortiAnalyzer analyst action: Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow. Validate using: Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Test with: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

B.

Choose this FortiAnalyzer analyst action: Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow. Validate using: Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged. This action-and-test pairing concerns another situation: A bank auditor reviews last month's PDF while the SOC is modifying its current FortiAnalyzer report template. The current case needs this action: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Test with: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

C.

Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Check the result: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. The technical reason is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition.

D.

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: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Test with: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

Question 656

A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals. What is the most defensible FortiAnalyzer action in this situation?

  1. Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it.
  2. Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.
  3. Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries.
  4. Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.

Answer & Explanations

Correct answer: B

A.

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: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

B.

Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. The technical reason is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. Confirm by: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

C.

Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries. That action is relevant to a different problem: A multinational bank reports an end-of-month login spike on the wrong day after generating a FortiAnalyzer report in a different time zone. Its technical basis is: A time window defined in UTC or a different local time zone can shift events across calendar-day reporting boundaries. The present case instead requires: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

D.

Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job. That action is relevant to a different problem: A university security officer expects Monday morning analytics but only the report template was saved in FortiAnalyzer. Its technical basis is: A report definition alone is not a recurring execution and scheduled generation requires an explicit enabled schedule. The present case instead requires: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

Question 657

A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals. The reviewed recommendation is: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Precomputed cache or aggregated query results can reduce repeated heavy SQL calculations when supported by report design and cache readiness.
  2. Report generation and external distribution require functioning email or storage settings beyond successful local PDF creation.
  3. Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition.
  4. Grouping and intelligent scheduling can reduce repeated hcache work and avoid resource contention with log processing tasks.

Answer & Explanations

Correct answer: C

A.

Precomputed cache or aggregated query results can reduce repeated heavy SQL calculations when supported by report design and cache readiness. That principle explains a different situation: A hospital runs similar monthly traffic charts for twenty sites and needs to avoid unnecessary repeated aggregation. Here the relevant cause is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. Apply it by: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

B.

Report generation and external distribution require functioning email or storage settings beyond successful local PDF creation. That principle explains a different situation: A hospital sends a weekly SOC report to its privacy manager and must verify the FortiAnalyzer mail connector is functional. Here the relevant cause is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. Apply it by: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports.

C.

Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. It explains why the intervention—use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports—addresses the stated problem. Test the mechanism by: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

D.

Grouping and intelligent scheduling can reduce repeated hcache work and avoid resource contention with log processing tasks. That principle explains a different situation: A retail chain needs similar site reports for hundreds of branches and wants to avoid repeated high-cost cache construction. Here the relevant cause is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. Apply it by: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

Question 658

A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals. The reviewed recommendation is: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. What pilot verification directly establishes the intended result?

  1. Run test queries for known traffic and security records and confirm the chart counts only the intended category.
  2. Test the dataset on known indexed test logs and verify that the chart renders the expected grouped count in a draft report.
  3. Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.
  4. Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged.

Answer & Explanations

Correct answer: C

A.

Run test queries for known traffic and security records and confirm the chart counts only the intended category. That test is for another requirement: A university needs a chart of high-severity security events but the dataset counts ordinary allowed sessions instead. It does not verify the stated outcome; the relevant check is: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

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 the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

C.

Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. This directly tests whether the chosen intervention works: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. The causal mechanism is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

D.

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: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

Question 659

A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals. Which tempting SOC change would undermine the stated requirement?

  1. Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow.
  2. Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries.
  3. Hardcode the original firewall serial into every chart query and declare the template universally reusable.
  4. Create or select a supported SQL dataset and bind a chart's measures, grouping, and report template placement to it.

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: Hardcode the original firewall serial into every chart query and declare the template universally reusable. Its risk is: Copied reports show the wrong device's events while appearing to summarize the selected site.

B.

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: Hardcode the original firewall serial into every chart query and declare the template universally reusable. Its risk is: Copied reports show the wrong device's events while appearing to summarize the selected site.

C.

Hardcode the original firewall serial into every chart query and declare the template universally reusable. The risk is: Copied reports show the wrong device's events while appearing to summarize the selected site. The safer action is: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Confirm by: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

D.

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: Hardcode the original firewall serial into every chart query and declare the template universally reusable. Its risk is: Copied reports show the wrong device's events while appearing to summarize the selected site.

Question 660

A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals. Which combined analytic action and validation test best solve this case?

  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: Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow. Validate using: Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged.
  3. 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.
  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: C

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: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Test with: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

B.

Choose this FortiAnalyzer analyst action: Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow. Validate using: Change a harmless template heading and regenerate a test report, confirming the new output reflects the edit while older output remains unchanged. This action-and-test pairing concerns another situation: A bank auditor reviews last month's PDF while the SOC is modifying its current FortiAnalyzer report template. The current case needs this action: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Test with: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

C.

Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Check the result: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device. The technical reason is: Dataset macros or supported query context can provide report selection values without hardcoding one source into every report definition. The fictional case is: A hospital network uses a common report template for clinics and wants device-scoped datasets instead of individually edited SQL literals.

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: Use appropriate FortiAnalyzer dataset parameters or macros to preserve intended report device and time filters across reusable reports. Test with: Run the same report for two authorized test firewalls and verify the underlying data each reflects the selected device.

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