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 78

Question 770

A hospital investigator discovers a PDF report missing older logs while their corresponding compressed files remain on FortiAnalyzer. Which combined analytic action and validation test best solve this case?

  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: 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: Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records. Validate using: Run a limited dataset test with one known indexed event and confirm correct field extraction and grouped output before rerunning the report.
  4. 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.

Answer & Explanations

Correct answer: B

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: Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. Test with: Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events.

B.

Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. Check the result: Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events. The technical reason is: Raw Archive retention and indexed Analytics retention are distinct, and report SQL access relies on eligible indexed records. The fictional case is: A hospital investigator discovers a PDF report missing older logs while their corresponding compressed files remain on FortiAnalyzer.

C.

Choose this FortiAnalyzer analyst action: Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records. Validate using: Run a limited dataset test with one known indexed event and confirm correct field extraction and grouped output before rerunning the report. This action-and-test pairing concerns another situation: A hospital custom report uses an obsolete column name after a log field mapping change and the associated chart returns nothing. The current case needs this action: Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. Test with: Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events.

D.

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: Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. Test with: Restore a harmless archived interval into Analytics and confirm the same dataset can now count its expected test events.

Question 771

A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate.
  2. Select the intended ADOM, devices or device group, time period, and output template before generating the final report.
  3. Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records.
  4. Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

Answer & Explanations

Correct answer: D

A.

Confirm indexed Analytics availability and use supported Archive-to-Analytics reimport for the required report interval where appropriate. That action is relevant to a different problem: A bank must rerun last year's firewall incident statistics after the original Analytics range was aged into Archive. Its technical basis is: Raw Archive retention and indexed Analytics retention are distinct, and report SQL access relies on eligible indexed records. The present case instead requires: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

B.

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: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

C.

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: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

D.

Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. The technical reason is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. Confirm by: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

Question 772

A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. The reviewed recommendation is: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Precomputed cache or aggregated query results can reduce repeated heavy SQL calculations when supported by report design and cache readiness.
  2. Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct.
  3. Grouping and intelligent scheduling can reduce repeated hcache work and avoid resource contention with log processing tasks.
  4. Raw Archive retention and indexed Analytics retention are distinct, and report SQL access relies on eligible indexed records.

Answer & Explanations

Correct answer: B

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: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. Apply it by: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

B.

Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. It explains why the intervention—inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy—addresses the stated problem. Test the mechanism by: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

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: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. Apply it by: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

D.

Raw Archive retention and indexed Analytics retention are distinct, and report SQL access relies on eligible indexed records. That principle explains a different situation: A bank must rerun last year's firewall incident statistics after the original Analytics range was aged into Archive. Here the relevant cause is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. Apply it by: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

Question 773

A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. The reviewed recommendation is: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Which observation best demonstrates that this corrective step worked?

  1. Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.
  2. Run the same non-sensitive report as an approved administrator and a restricted analyst to verify intended access boundaries.
  3. Generate a known boundary-hour test event and compare the report's included timestamps under explicitly documented time zone settings.
  4. Compare total job execution and generated chart consistency before and after grouping and staggering a representative set.

Answer & Explanations

Correct answer: A

A.

Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. This directly tests whether the chosen intervention works: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. The causal mechanism is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct.

B.

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: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

C.

Generate a known boundary-hour test event and compare the report's included timestamps under explicitly documented time zone settings. That test is for another requirement: 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 does not verify the stated outcome; the relevant check is: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

D.

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: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

Question 774

A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. Which unsafe investigation or automation shortcut must be rejected?

  1. Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.
  2. Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing.
  3. Select the intended ADOM, devices or device group, time period, and output template before generating the final report.
  4. Configure appropriate scheduled report recipients and supported mail settings and validate a harmless outbound report notification.

Answer & Explanations

Correct answer: B

A.

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: Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing. Its risk is: The reporting problem recurs and useful reusable definitions are lost to destructive troubleshooting.

B.

Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing. The risk is: The reporting problem recurs and useful reusable definitions are lost to destructive troubleshooting. The safer action is: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Confirm by: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

C.

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: Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing. Its risk is: The reporting problem recurs and useful reusable definitions are lost to destructive troubleshooting.

D.

Configure appropriate scheduled report recipients and supported mail settings and validate a harmless outbound report notification. That is an appropriate action for the separate case: A hospital sends a weekly SOC report to its privacy manager and must verify the FortiAnalyzer mail connector is functional. It is not the unsafe shortcut asked about here. Reject: Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing. Its risk is: The reporting problem recurs and useful reusable definitions are lost to destructive troubleshooting.

Question 775

A retailer FortiAnalyzer times out running quarterly reports when its log tables are rolling under high load. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. 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.
  2. 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.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Configure appropriate scheduled report recipients and supported mail settings and validate a harmless outbound report notification. Validate using: Generate one test report and verify the designated recipient received the expected file while unrelated recipients receive nothing.

Answer & Explanations

Correct answer: B

A.

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: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Test with: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

B.

Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Check the result: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. The technical reason is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct.

C.

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: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Test with: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

D.

Choose this FortiAnalyzer analyst action: Configure appropriate scheduled report recipients and supported mail settings and validate a harmless outbound report notification. Validate using: Generate one test report and verify the designated recipient received the expected file while unrelated recipients receive nothing. This action-and-test pairing concerns another situation: A hospital sends a weekly SOC report to its privacy manager and must verify the FortiAnalyzer mail connector is functional. The current case needs this action: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Test with: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

Question 776

A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health. What is the most defensible FortiAnalyzer action in this situation?

  1. Enable the report's schedule with the intended execution frequency and validate the Report Calendar and resulting job.
  2. Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.
  3. Verify report time zone, configured interval boundaries, and device log timestamps before comparing daily or monthly summaries.
  4. Configure appropriate scheduled report recipients and supported mail settings and validate a harmless outbound report notification.

Answer & Explanations

Correct answer: B

A.

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: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

B.

Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. The technical reason is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. Confirm by: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. The fictional case is: A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health.

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: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

D.

Configure appropriate scheduled report recipients and supported mail settings and validate a harmless outbound report notification. That action is relevant to a different problem: A hospital sends a weekly SOC report to its privacy manager and must verify the FortiAnalyzer mail connector is functional. Its technical basis is: Report generation and external distribution require functioning email or storage settings beyond successful local PDF creation. The present case instead requires: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

Question 777

A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health. The reviewed recommendation is: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Interactive filters and report datasets serve related but distinct purposes and a report requires a correctly defined query for the displayed chart.
  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. Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct.
  4. FortiAnalyzer reporting and analysis actions are governed by the user's authorized administrative domain and role privileges.

Answer & Explanations

Correct answer: C

A.

Interactive filters and report datasets serve related but distinct purposes and a report requires a correctly defined query for the displayed chart. That principle explains a different situation: A hospital analyst wants a reusable chart of blocked web categories derived from a filtered FortiAnalyzer Log View search. Here the relevant cause is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. Apply it by: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

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: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. Apply it by: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

C.

Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. It explains why the intervention—inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy—addresses the stated problem. Test the mechanism by: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. The fictional case is: A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health.

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: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. Apply it by: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy.

Question 778

A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health. The reviewed recommendation is: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. What pilot verification directly establishes the intended result?

  1. Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.
  2. Compare a representative report run with and without supported cache population and check the grouped chart totals remain consistent.
  3. Generate a known boundary-hour test event and compare the report's included timestamps under explicitly documented time zone settings.
  4. Generate the report against a known test device list and confirm its contributing sources match the approved compliance inventory.

Answer & Explanations

Correct answer: A

A.

Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. This directly tests whether the chosen intervention works: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. The causal mechanism is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. The fictional case is: A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health.

B.

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: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

C.

Generate a known boundary-hour test event and compare the report's included timestamps under explicitly documented time zone settings. That test is for another requirement: 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 does not verify the stated outcome; the relevant check is: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. The fictional case is: A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health.

D.

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: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

Question 779

A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health. 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. Distinguish reusable report templates, report definitions, chart or dataset resources, and generated output artifacts in the workflow.
  3. Evaluate reusable chart datasets, report grouping, and appropriate hcache auto-cache behavior for the actual reporting workload.
  4. Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing.

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 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: Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing. Its risk is: The reporting problem recurs and useful reusable definitions are lost to destructive troubleshooting. The fictional case is: A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health.

B.

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: Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing. Its risk is: The reporting problem recurs and useful reusable definitions are lost to destructive troubleshooting.

C.

Evaluate reusable chart datasets, report grouping, and appropriate hcache auto-cache behavior for the actual reporting workload. That is an appropriate action for the separate case: A hospital runs similar monthly traffic charts for twenty sites and needs to avoid unnecessary repeated aggregation. It is not the unsafe shortcut asked about here. Reject: Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing. Its risk is: The reporting problem recurs and useful reusable definitions are lost to destructive troubleshooting.

D.

Delete all report datasets whenever a resource-intensive job times out rather than inspecting logs and execution timing. The risk is: The reporting problem recurs and useful reusable definitions are lost to destructive troubleshooting. The safer action is: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Confirm by: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. The fictional case is: A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health.

Question 780

A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records. Validate using: Run a limited dataset test with one known indexed event and confirm correct field extraction and grouped output before rerunning the report.
  2. 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.
  3. 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.
  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: D

A.

Choose this FortiAnalyzer analyst action: Validate the dataset query and field names against the relevant FortiAnalyzer SQL log table schema and test on known indexed records. Validate using: Run a limited dataset test with one known indexed event and confirm correct field extraction and grouped output before rerunning the report. This action-and-test pairing concerns another situation: A hospital custom report uses an obsolete column name after a log field mapping change and the associated chart returns nothing. The current case needs this action: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Test with: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

B.

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: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Test with: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome.

C.

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: Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Test with: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. The fictional case is: A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health.

D.

Inspect report Task Monitor job details, database or hcache state, and maintenance schedule before selecting a targeted performance remedy. Check the result: Record the failing job and rerun it during a low-load period to compare duration, memory pressure, and completion outcome. The technical reason is: Concurrent SQL aggregation, indexing, and log maintenance consume shared resources and can cause timeouts even when report definitions are correct. The fictional case is: A university SOC sees periodic report job failures but has not inspected the task monitor or SQL cache health.

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