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 13

Question 120

A regional bank receives SIEM logs with malformed normalized timestamps and needs to test the custom parser before enabling correlation. Which combined analytic action and validation test best solve this case?

  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: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Validate using: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot.
  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: 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.

Answer & Explanations

Correct answer: C

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: Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. Test with: Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View. The fictional case is: A regional bank receives SIEM logs with malformed normalized timestamps and needs to test the custom parser before enabling correlation.

B.

Choose this FortiAnalyzer analyst action: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Validate using: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. This action-and-test pairing concerns another situation: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. The current case needs this action: Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. Test with: Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View.

C.

Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. Check the result: Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View. The technical reason is: Parser matching and field extraction govern whether a source is represented correctly in the SIEM database and available for normalized analytics. The fictional case is: A regional bank receives SIEM logs with malformed normalized timestamps and needs to test the custom parser before enabling correlation.

D.

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: Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. Test with: Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View.

Question 121

A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow.
  2. Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.
  3. Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.
  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: D

A.

Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow. That action is relevant to a different problem: A regional hospital adds a FortiGate at its remote emergency clinic but its FortiAnalyzer still lists the appliance as unauthorized. Its technical basis is: FortiAnalyzer requires the sending device to be registered and authorized before its logs are accepted for collection and analysis. The present case instead requires: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

B.

Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. That action is relevant to a different problem: A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. Its technical basis is: Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. The present case instead requires: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

C.

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: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

D.

Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. The technical reason is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. Confirm by: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

Question 122

A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. The reviewed recommendation is: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. 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. Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values.
  3. Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields.
  4. FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data.

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: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. Apply it by: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

B.

Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values. That principle explains a different situation: A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. Here the relevant cause is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. Apply it by: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

C.

Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. It explains why the intervention—identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format—addresses the stated problem. Test the mechanism by: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

D.

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: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. Apply it by: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

Question 123

A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. The reviewed recommendation is: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Which observation best demonstrates that this corrective step worked?

  1. Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.
  2. Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope.
  3. Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.
  4. 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: A

A.

Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. This directly tests whether the chosen intervention works: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. The causal mechanism is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields.

B.

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: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

C.

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: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

D.

Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay. That test is for another requirement: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. It does not verify the stated outcome; the relevant check is: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

Question 124

A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. Which unsafe investigation or automation shortcut must be rejected?

  1. Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.
  2. Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment.
  3. Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources.
  4. Rebuild the reporting database before checking whether the source has any enabled matching parser.

Answer & Explanations

Correct answer: D

A.

Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. That is an appropriate action for the separate case: A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. It is not the unsafe shortcut asked about here. Reject: Rebuild the reporting database before checking whether the source has any enabled matching parser. Its risk is: The underlying parser configuration defect remains and cross-product analytics continues omitting an important source.

B.

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: Rebuild the reporting database before checking whether the source has any enabled matching parser. Its risk is: The underlying parser configuration defect remains and cross-product analytics continues omitting an important source.

C.

Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. That is an appropriate action for the separate case: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. It is not the unsafe shortcut asked about here. Reject: Rebuild the reporting database before checking whether the source has any enabled matching parser. Its risk is: The underlying parser configuration defect remains and cross-product analytics continues omitting an important source.

D.

Rebuild the reporting database before checking whether the source has any enabled matching parser. The risk is: The underlying parser configuration defect remains and cross-product analytics continues omitting an important source. The safer action is: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Confirm by: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

Question 125

A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. 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.
  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: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Validate using: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot.
  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.

Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Check the result: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. The technical reason is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields.

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: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Test with: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

C.

Choose this FortiAnalyzer analyst action: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Validate using: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. This action-and-test pairing concerns another situation: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. The current case needs this action: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Test with: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

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: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Test with: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

Question 126

A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events. What is the most defensible FortiAnalyzer action in this situation?

  1. Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow.
  2. Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.
  3. Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.
  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.

Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow. That action is relevant to a different problem: A regional hospital adds a FortiGate at its remote emergency clinic but its FortiAnalyzer still lists the appliance as unauthorized. Its technical basis is: FortiAnalyzer requires the sending device to be registered and authorized before its logs are accepted for collection and analysis. The present case instead requires: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

B.

Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. The technical reason is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. Confirm by: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

C.

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: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

D.

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: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

Question 127

A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events. The reviewed recommendation is: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Certain FortiGuard-supplied security automation content depends on valid service licensing and content availability separate from locally built objects.
  2. Fabric ADOMs can present eligible different Fortinet product logs and security events together while retaining explicit membership and access control.
  3. Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields.
  4. FortiAnalyzer requires the sending device to be registered and authorized before its logs are accepted for collection and analysis.

Answer & Explanations

Correct answer: C

A.

Certain FortiGuard-supplied security automation content depends on valid service licensing and content availability separate from locally built objects. That principle explains a different situation: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. Here the relevant cause is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. Apply it by: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

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: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. Apply it by: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

C.

Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. It explains why the intervention—identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format—addresses the stated problem. Test the mechanism by: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

D.

FortiAnalyzer requires the sending device to be registered and authorized before its logs are accepted for collection and analysis. That principle explains a different situation: A regional hospital adds a FortiGate at its remote emergency clinic but its FortiAnalyzer still lists the appliance as unauthorized. Here the relevant cause is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. Apply it by: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.

Question 128

A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events. The reviewed recommendation is: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. What pilot verification directly establishes the intended result?

  1. Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot.
  2. Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay.
  3. Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.
  4. 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: D

A.

Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. That test is for another requirement: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. It does not verify the stated outcome; the relevant check is: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

B.

Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay. That test is for another requirement: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. It does not verify the stated outcome; the relevant check is: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

C.

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: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

D.

Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. This directly tests whether the chosen intervention works: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. The causal mechanism is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

Question 129

A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events. Which tempting SOC change would undermine the stated requirement?

  1. Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.
  2. Rebuild the reporting database before checking whether the source has any enabled matching parser.
  3. Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.
  4. Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow.

Answer & Explanations

Correct answer: B

A.

Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields. That is an appropriate action for the separate case: A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. It is not the unsafe shortcut asked about here. Reject: Rebuild the reporting database before checking whether the source has any enabled matching parser. Its risk is: The underlying parser configuration defect remains and cross-product analytics continues omitting an important source. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

B.

Rebuild the reporting database before checking whether the source has any enabled matching parser. The risk is: The underlying parser configuration defect remains and cross-product analytics continues omitting an important source. The safer action is: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Confirm by: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

C.

Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. That is an appropriate action for the separate case: A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. It is not the unsafe shortcut asked about here. Reject: Rebuild the reporting database before checking whether the source has any enabled matching parser. Its risk is: The underlying parser configuration defect remains and cross-product analytics continues omitting an important source.

D.

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: Rebuild the reporting database before checking whether the source has any enabled matching parser. Its risk is: The underlying parser configuration defect remains and cross-product analytics continues omitting an important source.

Question 130

A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events. Which combined analytic action and validation test best solve this case?

  1. 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.
  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: 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.
  4. 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.

Answer & Explanations

Correct answer: A

A.

Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Check the result: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. The technical reason is: Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. The fictional case is: A financial firm onboarded an Nginx log source but the expected parser was disabled and SIEM searches find no web events.

B.

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. This action-and-test pairing concerns another situation: A regional bank expands to a second SOC and wants selected historical FortiAnalyzer archives while continuing daily firewall log forwarding. The current case needs this action: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Test with: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

C.

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: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Test with: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

D.

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: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Test with: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

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