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 38

Question 370

A managed service provider runs an event report for a hospital while the configuration still points to a different customer ADOM. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Validate using: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.
  2. Choose this FortiAnalyzer analyst action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Validate using: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.
  3. Choose this FortiAnalyzer analyst action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
  4. Choose this FortiAnalyzer analyst action: Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. Validate using: Compare completion times for one representative report before and after off-peak scheduling and verified cache population.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Validate using: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. This action-and-test pairing concerns another situation: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. The current case needs this action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Test with: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. The fictional case is: A managed service provider runs an event report for a hospital while the configuration still points to a different customer ADOM.

B.

Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Check the result: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. The technical reason is: FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection. The fictional case is: A managed service provider runs an event report for a hospital while the configuration still points to a different customer ADOM.

C.

Choose this FortiAnalyzer analyst action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. This action-and-test pairing concerns another situation: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. The current case needs this action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Test with: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. The fictional case is: A managed service provider runs an event report for a hospital while the configuration still points to a different customer ADOM.

D.

Choose this FortiAnalyzer analyst action: Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. Validate using: Compare completion times for one representative report before and after off-peak scheduling and verified cache population. This action-and-test pairing concerns another situation: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. The current case needs this action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Test with: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.

Question 371

A financial SOC adds a report chart referencing a field not present in its FortiAnalyzer log table. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer.
  2. Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.
  3. Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.
  4. Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule.

Answer & Explanations

Correct answer: B

A.

Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer. That action is relevant to a different problem: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. Its technical basis is: Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source. The present case instead requires: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

B.

Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. The technical reason is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. Confirm by: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

C.

Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. That action is relevant to a different problem: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Its technical basis is: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. The present case instead requires: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

D.

Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. That action is relevant to a different problem: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. Its technical basis is: SQL aggregation and report cache processing consume resources that may conflict with log maintenance and can be improved through appropriate report grouping. The present case instead requires: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

Question 372

A financial SOC adds a report chart referencing a field not present in its FortiAnalyzer log table. The reviewed recommendation is: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. A malware or intrusion detection finding does not independently prove whether FortiOS forwarded, blocked, reset, or quarantined an associated flow.
  2. Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields.
  3. Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation.
  4. Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source.

Answer & Explanations

Correct answer: C

A.

A malware or intrusion detection finding does not independently prove whether FortiOS forwarded, blocked, reset, or quarantined an associated flow. That principle explains a different situation: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. Here the relevant cause is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. Apply it by: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

B.

Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. That principle explains a different situation: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Here the relevant cause is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. Apply it by: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

C.

Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. It explains why the intervention—test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling—addresses the stated problem. Test the mechanism by: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

D.

Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source. That principle explains a different situation: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. Here the relevant cause is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. Apply it by: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

Question 373

A financial SOC adds a report chart referencing a field not present in its FortiAnalyzer log table. The reviewed recommendation is: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Which observation best demonstrates that this corrective step worked?

  1. Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.
  2. Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.
  3. Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.
  4. After a controlled log ingestion interval, compare the Archive arrival timestamp with indexed Analytics count and rerun the same report window.

Answer & Explanations

Correct answer: C

A.

Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. That test is for another requirement: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. It does not verify the stated outcome; the relevant check is: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

B.

Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. That test is for another requirement: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. It does not verify the stated outcome; the relevant check is: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

C.

Execute a limited dataset test on a known log period and validate the expected rows before generating the full report. This directly tests whether the chosen intervention works: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. The causal mechanism is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation.

D.

After a controlled log ingestion interval, compare the Archive arrival timestamp with indexed Analytics count and rerun the same report window. That test is for another requirement: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. It does not verify the stated outcome; the relevant check is: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

Question 374

A financial SOC adds a report chart referencing a field not present in its FortiAnalyzer log table. Which unsafe investigation or automation shortcut must be rejected?

  1. Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field.
  2. Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome.
  3. Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer.
  4. Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.

Answer & Explanations

Correct answer: A

A.

Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field. The risk is: The same chart continues to fail while unnecessary detections create extra noise. The safer action is: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Confirm by: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

B.

Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. That is an appropriate action for the separate case: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. It is not the unsafe shortcut asked about here. Reject: Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field. Its risk is: The same chart continues to fail while unnecessary detections create extra noise.

C.

Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer. That is an appropriate action for the separate case: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. It is not the unsafe shortcut asked about here. Reject: Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field. Its risk is: The same chart continues to fail while unnecessary detections create extra noise.

D.

Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. That is an appropriate action for the separate case: A hospital SOC can download a PDF report manually but the daily summary email stopped arriving after SMTP settings changed. It is not the unsafe shortcut asked about here. Reject: Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field. Its risk is: The same chart continues to fail while unnecessary detections create extra noise.

Question 375

A financial SOC adds a report chart referencing a field not present in its FortiAnalyzer log table. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. Validate using: Generate a harmless supported security event and confirm the required log subtype and widget are then populated.
  2. Choose this FortiAnalyzer analyst action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Validate using: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.
  3. Choose this FortiAnalyzer analyst action: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Validate using: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.
  4. Choose this FortiAnalyzer analyst action: Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. Validate using: Inspect a controlled blocked test event and an observed allowed event to compare their exact log action and detection values.

Answer & Explanations

Correct answer: C

A.

Choose this FortiAnalyzer analyst action: Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. Validate using: Generate a harmless supported security event and confirm the required log subtype and widget are then populated. This action-and-test pairing concerns another situation: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. The current case needs this action: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Test with: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

B.

Choose this FortiAnalyzer analyst action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Validate using: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. This action-and-test pairing concerns another situation: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. The current case needs this action: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Test with: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

C.

Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Check the result: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report. The technical reason is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation.

D.

Choose this FortiAnalyzer analyst action: Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. Validate using: Inspect a controlled blocked test event and an observed allowed event to compare their exact log action and detection values. This action-and-test pairing concerns another situation: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. The current case needs this action: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Test with: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

Question 376

A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated. What is the most defensible FortiAnalyzer action in this situation?

  1. Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.
  2. Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule.
  3. Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity.
  4. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

Answer & Explanations

Correct answer: A

A.

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

B.

Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. That action is relevant to a different problem: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. Its technical basis is: SQL aggregation and report cache processing consume resources that may conflict with log maintenance and can be improved through appropriate report grouping. The present case instead requires: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. The fictional case is: A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated.

C.

Distinguish report schedule and delivery settings from rendering success and verify enabled scheduling, recipient, and mail-server connectivity. That action is relevant to a different problem: A hospital SOC can download a PDF report manually but the daily summary email stopped arriving after SMTP settings changed. Its technical basis is: Generating a report creates an artifact but automatic scheduling and delivery require separate configured and functioning execution and mail dependencies. The present case instead requires: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

D.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. That action is relevant to a different problem: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. Its technical basis is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. The present case instead requires: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

Question 377

A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated. The reviewed recommendation is: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. What FortiAnalyzer mechanism supports the recommended analysis?

  1. A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope.
  2. Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM.
  3. Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source.
  4. Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation.

Answer & Explanations

Correct answer: D

A.

A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. That principle explains a different situation: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. Here the relevant cause is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. Apply it by: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

B.

Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM. That principle explains a different situation: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. Here the relevant cause is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. Apply it by: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling.

C.

Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source. That principle explains a different situation: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. Here the relevant cause is: Report charts depend on valid dataset queries against the Analytics database and invalid SQL expressions prevent proper aggregation. Apply it by: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. The fictional case is: A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated.

D.

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

Question 378

A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated. The reviewed recommendation is: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. What pilot verification directly establishes the intended result?

  1. Compare completion times for one representative report before and after off-peak scheduling and verified cache population.
  2. Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.
  3. Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.
  4. Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

Answer & Explanations

Correct answer: B

A.

Compare completion times for one representative report before and after off-peak scheduling and verified cache population. That test is for another requirement: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. It does not verify the stated outcome; the relevant check is: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

B.

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

C.

Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. That test is for another requirement: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. It does not verify the stated outcome; the relevant check is: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report. The fictional case is: A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated.

D.

Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. That test is for another requirement: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. It does not verify the stated outcome; the relevant check is: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

Question 379

A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated. Which tempting SOC change would undermine the stated requirement?

  1. Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule.
  2. Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.
  3. Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
  4. Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field.

Answer & Explanations

Correct answer: D

A.

Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. That is an appropriate action for the separate case: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. It is not the unsafe shortcut asked about here. Reject: Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field. Its risk is: The same chart continues to fail while unnecessary detections create extra noise.

B.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. That is an appropriate action for the separate case: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. It is not the unsafe shortcut asked about here. Reject: Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field. Its risk is: The same chart continues to fail while unnecessary detections create extra noise.

C.

Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. That is an appropriate action for the separate case: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. It is not the unsafe shortcut asked about here. Reject: Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field. Its risk is: The same chart continues to fail while unnecessary detections create extra noise.

D.

Enable every event handler and expect that action to correct a SQL query referring to a nonexistent field. The risk is: The same chart continues to fail while unnecessary detections create extra noise. The safer action is: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Confirm by: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report. The fictional case is: A university custom report times out after a recent SQL edit and engineers need the failing dataset isolated.

Question 380

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

  1. Choose this FortiAnalyzer analyst action: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Validate using: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.
  2. Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.
  3. Choose this FortiAnalyzer analyst action: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Validate using: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.
  4. Choose this FortiAnalyzer analyst action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Validate using: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.

Answer & Explanations

Correct answer: C

A.

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

B.

Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. This action-and-test pairing concerns another situation: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. The current case needs this action: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Test with: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

C.

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

D.

Choose this FortiAnalyzer analyst action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Validate using: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. This action-and-test pairing concerns another situation: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. The current case needs this action: Test the report's actual SQL dataset and inspect referenced table names, columns, and parameters before rescheduling. Test with: Execute a limited dataset test on a known log period and validate the expected rows before generating the full report.

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