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 11

Question 100

A university shortens Analytics storage for performance and must not inadvertently erase older Archive records required for investigations. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Validate using: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.
  2. Choose this FortiAnalyzer analyst action: Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation. Validate using: Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

A.

Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Check the result: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy. The technical reason is: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. The fictional case is: A university shortens Analytics storage for performance and must not inadvertently erase older Archive records required for investigations.

B.

Choose this FortiAnalyzer analyst action: Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation. Validate using: Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope. This action-and-test pairing concerns another situation: A bank wants to review suspicious FortiGate connections together with FortiMail malware events in one analyst investigation context. The current case needs this action: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Test with: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

C.

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: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Test with: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

D.

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: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Test with: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy. The fictional case is: A university shortens Analytics storage for performance and must not inadvertently erase older Archive records required for investigations.

Question 101

A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view.
  2. Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention.
  3. Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.
  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: C

A.

Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. That action is relevant to a different problem: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. Its technical basis is: Real-time arriving logs and Archive files have different lifecycle states from indexed Analytics records that support interactive SQL-backed searches. The present case instead requires: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

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: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

C.

Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. The technical reason is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. Confirm by: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

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: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

Question 102

A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. The reviewed recommendation is: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Which technical principle explains why the proposed FortiAnalyzer action works?

  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. Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values.
  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: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. Apply it by: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

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: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. Apply it by: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

C.

Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. It explains why the intervention—ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields—addresses the stated problem. Test the mechanism by: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

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: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. Apply it by: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

Question 103

A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. The reviewed recommendation is: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Which observation best demonstrates that this corrective step worked?

  1. Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
  2. Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.
  3. Sign in as two scoped analysts and confirm each can investigate only the assigned ADOM's devices and report data.
  4. Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident.

Answer & Explanations

Correct answer: B

A.

Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. That test is for another requirement: A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. It does not verify the stated outcome; the relevant check is: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

B.

Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. This directly tests whether the chosen intervention works: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. The causal mechanism is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values.

C.

Sign in as two scoped analysts and confirm each can investigate only the assigned ADOM's devices and report data. That test is for another requirement: A managed service provider hosts firewall log analysis for two hospitals and must isolate the hospitals' Security Fabric device data. It does not verify the stated outcome; the relevant check is: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

D.

Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident. That test is for another requirement: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. It does not verify the stated outcome; the relevant check is: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

Question 104

A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. Which unsafe investigation or automation shortcut must be rejected?

  1. Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.
  2. Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser.
  3. Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
  4. Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention.

Answer & Explanations

Correct answer: B

A.

Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. That is an appropriate action for the separate case: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. It is not the unsafe shortcut asked about here. Reject: Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser. Its risk is: Correlation rules miss real matches or combine unrelated identities because fields were not normalized correctly.

B.

Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser. The risk is: Correlation rules miss real matches or combine unrelated identities because fields were not normalized correctly. The safer action is: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Confirm by: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

C.

Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. That is an appropriate action for the separate case: A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. It is not the unsafe shortcut asked about here. Reject: Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser. Its risk is: Correlation rules miss real matches or combine unrelated identities because fields were not normalized correctly.

D.

Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention. That is an appropriate action for the separate case: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. It is not the unsafe shortcut asked about here. Reject: Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser. Its risk is: Correlation rules miss real matches or combine unrelated identities because fields were not normalized correctly.

Question 105

A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation. Validate using: Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope.
  2. Choose this FortiAnalyzer analyst action: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Validate using: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Validate using: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation. Validate using: Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope. This action-and-test pairing concerns another situation: A bank wants to review suspicious FortiGate connections together with FortiMail malware events in one analyst investigation context. The current case needs this action: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Test with: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

B.

Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Check the result: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. The technical reason is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values.

C.

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: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Test with: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

D.

Choose this FortiAnalyzer analyst action: Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Validate using: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay. This action-and-test pairing concerns another situation: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. The current case needs this action: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Test with: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

Question 106

A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation. What is the most defensible FortiAnalyzer action in this situation?

  1. Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.
  2. Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.
  3. Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment.
  4. Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

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 action is relevant to a different problem: A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. Its technical basis is: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. The present case instead requires: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

B.

Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. The technical reason is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. Confirm by: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

C.

Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. That action is relevant to a different problem: A university SOC imports a custom web server parser but extracted client addresses appear blank in FortiAnalyzer analytics. Its technical basis is: Parser matching and field extraction govern whether a source is represented correctly in the SIEM database and available for normalized analytics. The present case instead requires: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

D.

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: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

Question 107

A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation. The reviewed recommendation is: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source.
  2. Fabric ADOMs can present eligible different Fortinet product logs and security events together while retaining explicit membership and access control.
  3. FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context.
  4. Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values.

Answer & Explanations

Correct answer: D

A.

Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source. That principle explains a different situation: A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. Here the relevant cause is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. Apply it by: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

B.

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: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. Apply it by: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

C.

FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. That principle explains a different situation: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. Here the relevant cause is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. Apply it by: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.

D.

Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. It explains why the intervention—ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields—addresses the stated problem. Test the mechanism by: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

Question 108

A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation. The reviewed recommendation is: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. What pilot verification directly establishes the intended result?

  1. Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident.
  2. Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.
  3. Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View.
  4. Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

Answer & Explanations

Correct answer: D

A.

Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident. That test is for another requirement: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. It does not verify the stated outcome; the relevant check is: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

B.

Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow. That test is for another requirement: A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. It does not verify the stated outcome; the relevant check is: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

C.

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: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

D.

Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. This directly tests whether the chosen intervention works: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. The causal mechanism is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

Question 109

A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation. Which tempting SOC change would undermine the stated requirement?

  1. Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention.
  2. Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
  3. Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.
  4. Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser.

Answer & Explanations

Correct answer: D

A.

Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention. That is an appropriate action for the separate case: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. It is not the unsafe shortcut asked about here. Reject: Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser. Its risk is: Correlation rules miss real matches or combine unrelated identities because fields were not normalized correctly. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

B.

Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. That is an appropriate action for the separate case: A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. It is not the unsafe shortcut asked about here. Reject: Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser. Its risk is: Correlation rules miss real matches or combine unrelated identities because fields were not normalized correctly. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

C.

Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints. That is an appropriate action for the separate case: A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. It is not the unsafe shortcut asked about here. Reject: Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser. Its risk is: Correlation rules miss real matches or combine unrelated identities because fields were not normalized correctly.

D.

Join unrelated raw text columns by visual resemblance and assume every source produces identical field names with no parser. The risk is: Correlation rules miss real matches or combine unrelated identities because fields were not normalized correctly. The safer action is: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Confirm by: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

Question 110

A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation. 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: Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention. Validate using: Generate a bounded synthetic peak and compare accepted log counts, queue growth, and indexed arrival delay over time.
  3. Choose this FortiAnalyzer analyst action: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Validate using: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.
  4. Choose this FortiAnalyzer analyst action: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Validate using: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

Answer & Explanations

Correct answer: D

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: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Test with: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

B.

Choose this FortiAnalyzer analyst action: Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention. Validate using: Generate a bounded synthetic peak and compare accepted log counts, queue growth, and indexed arrival delay over time. This action-and-test pairing concerns another situation: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. The current case needs this action: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Test with: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

C.

Choose this FortiAnalyzer analyst action: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Validate using: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy. This action-and-test pairing concerns another situation: A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. The current case needs this action: Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Test with: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.

D.

Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. Check the result: Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. The technical reason is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. The fictional case is: A hospital adds a web service log feed to FortiAnalyzer and must map its timestamps and host identity before SIEM correlation.

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