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 6

Question 50

A university plans branch collectors feeding one analysis cluster and must distinguish buffering capacity from interactive detection capability. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents. Validate using: Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident.
  2. Choose this FortiAnalyzer analyst action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Validate using: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer.
  3. Choose this FortiAnalyzer analyst action: Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. Validate using: Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View.
  4. Choose this FortiAnalyzer analyst action: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Validate using: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents. Validate using: Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident. This action-and-test pairing concerns another situation: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. The current case needs this action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Test with: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer. The fictional case is: A university plans branch collectors feeding one analysis cluster and must distinguish buffering capacity from interactive detection capability.

B.

Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Check the result: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer. The technical reason is: A Collector can buffer and forward logging streams while an Analyzer provides the analysis functions needed for searchable SOC investigation. The fictional case is: A university plans branch collectors feeding one analysis cluster and must distinguish buffering capacity from interactive detection capability.

C.

Choose this FortiAnalyzer analyst action: Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. Validate using: Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View. This action-and-test pairing concerns another situation: A university SOC imports a custom web server parser but extracted client addresses appear blank in FortiAnalyzer analytics. The current case needs this action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Test with: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer. The fictional case is: A university plans branch collectors feeding one analysis cluster and must distinguish buffering capacity from interactive detection capability.

D.

Choose this FortiAnalyzer analyst action: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Validate using: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. This action-and-test pairing concerns another situation: A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. The current case needs this action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Test with: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer.

Question 51

A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode.
  2. Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention.
  3. Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.
  4. Validate both endpoint log encryption settings and authorization so the supported Fortinet logging transport uses compatible security levels.

Answer & Explanations

Correct answer: C

A.

Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. That action is relevant to a different problem: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. Its technical basis is: A Collector can buffer and forward logging streams while an Analyzer provides the analysis functions needed for searchable SOC investigation. The present case instead requires: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

B.

Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention. That action is relevant to a different problem: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. Its technical basis is: Ingestion throughput and downstream indexing capacity can be bottlenecks even when enough disk space remains for compressed storage. The present case instead requires: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

C.

Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. The technical reason is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. Confirm by: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

D.

Validate both endpoint log encryption settings and authorization so the supported Fortinet logging transport uses compatible security levels. That action is relevant to a different problem: A hospital firewall sends traffic logs to FortiAnalyzer but security policy has raised the sender's encryption level beyond the receiver configuration. Its technical basis is: Fortinet proprietary OFTP log transfer requires configured encryption compatibility between sender and FortiAnalyzer receiver. The present case instead requires: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

Question 52

A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. The reviewed recommendation is: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Fabric ADOMs can present eligible different Fortinet product logs and security events together while retaining explicit membership and access control.
  2. FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data.
  3. Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source.
  4. A Collector can buffer and forward logging streams while an Analyzer provides the analysis functions needed for searchable SOC investigation.

Answer & Explanations

Correct answer: C

A.

Fabric ADOMs can present eligible different Fortinet product logs and security events together while retaining explicit membership and access control. That principle explains a different situation: A bank wants to review suspicious FortiGate connections together with FortiMail malware events in one analyst investigation context. Here the relevant cause is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. Apply it by: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

B.

FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. That principle explains a different situation: A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. Here the relevant cause is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. Apply it by: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

C.

Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. It explains why the intervention—choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints—addresses the stated problem. Test the mechanism by: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

D.

A Collector can buffer and forward logging streams while an Analyzer provides the analysis functions needed for searchable SOC investigation. That principle explains a different situation: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. Here the relevant cause is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. Apply it by: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

Question 53

A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. The reviewed recommendation is: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Which observation best demonstrates that this corrective step worked?

  1. Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.
  2. Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View.
  3. Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope.
  4. Generate a bounded synthetic peak and compare accepted log counts, queue growth, and indexed arrival delay over time.

Answer & Explanations

Correct answer: A

A.

Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. This directly tests whether the chosen intervention works: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. The causal mechanism is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source.

B.

Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View. That test is for another requirement: A university SOC imports a custom web server parser but extracted client addresses appear blank in FortiAnalyzer analytics. It does not verify the stated outcome; the relevant check is: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

C.

Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope. That test is for another requirement: A bank wants to review suspicious FortiGate connections together with FortiMail malware events in one analyst investigation context. It does not verify the stated outcome; the relevant check is: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

D.

Generate a bounded synthetic peak and compare accepted log counts, queue growth, and indexed arrival delay over time. That test is for another requirement: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. It does not verify the stated outcome; the relevant check is: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

Question 54

A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. Which unsafe investigation or automation shortcut must be rejected?

  1. Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow.
  2. Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan.
  3. Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation.
  4. Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody.

Answer & Explanations

Correct answer: B

A.

Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow. That is an appropriate action for the separate case: A regional hospital adds a FortiGate at its remote emergency clinic but its FortiAnalyzer still lists the appliance as unauthorized. It is not the unsafe shortcut asked about here. Reject: Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan. Its risk is: Older evidence is absent from an audit despite successful receipt of new current events.

B.

Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan. The risk is: Older evidence is absent from an audit despite successful receipt of new current events. The safer action is: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Confirm by: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

C.

Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation. That is an appropriate action for the separate case: A bank wants to review suspicious FortiGate connections together with FortiMail malware events in one analyst investigation context. It is not the unsafe shortcut asked about here. Reject: Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan. Its risk is: Older evidence is absent from an audit despite successful receipt of new current events.

D.

Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. That is an appropriate action for the separate case: A multinational retailer puts regional FortiAnalyzers under a central Fabric supervisor and needs accurate log custody boundaries. It is not the unsafe shortcut asked about here. Reject: Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan. Its risk is: Older evidence is absent from an audit despite successful receipt of new current events.

Question 55

A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow. Validate using: Inspect device authorization state and generate an innocuous test traffic event that appears under the intended device in Log View.
  2. Choose this FortiAnalyzer analyst action: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Validate using: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.
  3. Choose this FortiAnalyzer analyst action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Validate using: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer.
  4. Choose this FortiAnalyzer analyst action: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Validate using: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow. Validate using: Inspect device authorization state and generate an innocuous test traffic event that appears under the intended device in Log View. This action-and-test pairing concerns another situation: A regional hospital adds a FortiGate at its remote emergency clinic but its FortiAnalyzer still lists the appliance as unauthorized. The current case needs this action: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Test with: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

B.

Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Check the result: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. The technical reason is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source.

C.

Choose this FortiAnalyzer analyst action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Validate using: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer. This action-and-test pairing concerns another situation: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. The current case needs this action: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Test with: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

D.

Choose this FortiAnalyzer analyst action: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Validate using: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. This action-and-test pairing concerns another situation: A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. The current case needs this action: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Test with: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

Question 56

A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection. What is the most defensible FortiAnalyzer action in this situation?

  1. Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.
  2. Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.
  3. Validate both endpoint log encryption settings and authorization so the supported Fortinet logging transport uses compatible security levels.
  4. Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

Answer & Explanations

Correct answer: B

A.

Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. That action is relevant to a different problem: A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. Its technical basis is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. The present case instead requires: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

B.

Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. The technical reason is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. Confirm by: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

C.

Validate both endpoint log encryption settings and authorization so the supported Fortinet logging transport uses compatible security levels. That action is relevant to a different problem: A hospital firewall sends traffic logs to FortiAnalyzer but security policy has raised the sender's encryption level beyond the receiver configuration. Its technical basis is: Fortinet proprietary OFTP log transfer requires configured encryption compatibility between sender and FortiAnalyzer receiver. The present case instead requires: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

D.

Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. That action is relevant to a different problem: A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. Its technical basis is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. The present case instead requires: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

Question 57

A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection. The reviewed recommendation is: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Administrative domains partition FortiAnalyzer device and analysis views so an operator sees the specific log sources their role may manage.
  2. Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields.
  3. Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source.
  4. Fabric ADOMs can present eligible different Fortinet product logs and security events together while retaining explicit membership and access control.

Answer & Explanations

Correct answer: C

A.

Administrative domains partition FortiAnalyzer device and analysis views so an operator sees the specific log sources their role may manage. That principle explains a different situation: A managed service provider hosts firewall log analysis for two hospitals and must isolate the hospitals' Security Fabric device data. Here the relevant cause is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. Apply it by: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

B.

Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. That principle explains a different situation: A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. Here the relevant cause is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. Apply it by: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

C.

Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. It explains why the intervention—choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints—addresses the stated problem. Test the mechanism by: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

D.

Fabric ADOMs can present eligible different Fortinet product logs and security events together while retaining explicit membership and access control. That principle explains a different situation: A bank wants to review suspicious FortiGate connections together with FortiMail malware events in one analyst investigation context. Here the relevant cause is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. Apply it by: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

Question 58

A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection. The reviewed recommendation is: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. What pilot verification directly establishes the intended result?

  1. Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.
  2. Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member.
  3. Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.
  4. Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer.

Answer & Explanations

Correct answer: C

A.

Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. That test is for another requirement: A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. It does not verify the stated outcome; the relevant check is: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

B.

Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member. That test is for another requirement: A multinational retailer puts regional FortiAnalyzers under a central Fabric supervisor and needs accurate log custody boundaries. It does not verify the stated outcome; the relevant check is: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

C.

Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. This directly tests whether the chosen intervention works: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. The causal mechanism is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

D.

Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer. That test is for another requirement: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. It does not verify the stated outcome; the relevant check is: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

Question 59

A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection. Which tempting SOC change would undermine the stated requirement?

  1. Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.
  2. Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan.
  3. Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment.
  4. Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view.

Answer & Explanations

Correct answer: B

A.

Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. That is an appropriate action for the separate case: A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. It is not the unsafe shortcut asked about here. Reject: Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan. Its risk is: Older evidence is absent from an audit despite successful receipt of new current events.

B.

Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan. The risk is: Older evidence is absent from an audit despite successful receipt of new current events. The safer action is: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Confirm by: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

C.

Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. That is an appropriate action for the separate case: A university SOC imports a custom web server parser but extracted client addresses appear blank in FortiAnalyzer analytics. It is not the unsafe shortcut asked about here. Reject: Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan. Its risk is: Older evidence is absent from an audit despite successful receipt of new current events.

D.

Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. That is an appropriate action for the separate case: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. It is not the unsafe shortcut asked about here. Reject: Enable live log forwarding and promise that a preexisting remote archive will automatically appear without a historical retrieval plan. Its risk is: Older evidence is absent from an audit despite successful receipt of new current events.

Question 60

A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Validate using: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer.
  2. Choose this FortiAnalyzer analyst action: Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. Validate using: Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member.
  3. Choose this FortiAnalyzer analyst action: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Validate using: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.
  4. Choose this FortiAnalyzer analyst action: Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow. Validate using: Inspect device authorization state and generate an innocuous test traffic event that appears under the intended device in Log View.

Answer & Explanations

Correct answer: C

A.

Choose this FortiAnalyzer analyst action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Validate using: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer. This action-and-test pairing concerns another situation: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. The current case needs this action: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Test with: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

B.

Choose this FortiAnalyzer analyst action: Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. Validate using: Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member. This action-and-test pairing concerns another situation: A multinational retailer puts regional FortiAnalyzers under a central Fabric supervisor and needs accurate log custody boundaries. The current case needs this action: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Test with: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

C.

Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Check the result: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. The technical reason is: Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

D.

Choose this FortiAnalyzer analyst action: Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow. Validate using: Inspect device authorization state and generate an innocuous test traffic event that appears under the intended device in Log View. This action-and-test pairing concerns another situation: A regional hospital adds a FortiGate at its remote emergency clinic but its FortiAnalyzer still lists the appliance as unauthorized. The current case needs this action: Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. Test with: Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. The fictional case is: A hospital consolidates last month's remote branch logs but the team has configured only a new real-time forwarding connection.

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