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 9

Question 80

A hospital incident analyst needs to explain why the newest network logs are present in raw storage before searchable Analytics completes. 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: 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.
  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: 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: 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: Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Test with: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay.

B.

Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Check the result: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay. The technical reason is: Real-time arriving logs and Archive files have different lifecycle states from indexed Analytics records that support interactive SQL-backed searches. The fictional case is: A hospital incident analyst needs to explain why the newest network logs are present in raw storage before searchable Analytics completes.

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: Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Test with: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay.

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 whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Test with: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay.

Question 81

A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. 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. Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.
  3. Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.
  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 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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

B.

Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. The technical reason is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. Confirm by: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

C.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

D.

Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. That action is relevant to a different problem: A multinational retailer puts regional FortiAnalyzers under a central Fabric supervisor and needs accurate log custody boundaries. Its technical basis is: Fabric synchronization provides coordinated views of device, event, and incident information while each member still has its own collection and storage responsibilities. The present case instead requires: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

Question 82

A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. The reviewed recommendation is: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. 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. Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields.
  3. FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data.
  4. Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations.

Answer & Explanations

Correct answer: D

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: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. Apply it by: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

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: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. Apply it by: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

C.

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: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. Apply it by: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

D.

Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. It explains why the intervention—use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it—addresses the stated problem. Test the mechanism by: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

Question 83

A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. The reviewed recommendation is: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Which observation best demonstrates that this corrective step worked?

  1. Inspect device authorization state and generate an innocuous test traffic event that appears under the intended device in Log View.
  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. Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.
  4. 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: D

A.

Inspect device authorization state and generate an innocuous test traffic event that appears under the intended device in Log View. That test is for another requirement: A regional hospital adds a FortiGate at its remote emergency clinic but its FortiAnalyzer still lists the appliance as unauthorized. It does not verify the stated outcome; the relevant check is: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

B.

Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. That test is for another requirement: A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. It does not verify the stated outcome; the relevant check is: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

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: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

D.

Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. This directly tests whether the chosen intervention works: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. The causal mechanism is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations.

Question 84

A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. Which unsafe investigation or automation shortcut must be rejected?

  1. Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation.
  2. Delete older Archive files as unusable because they are absent from the current Analytics time range.
  3. Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody.
  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.

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: Delete older Archive files as unusable because they are absent from the current Analytics time range. Its risk is: Required historical evidence is lost even though recoverable raw records existed before the deletion.

B.

Delete older Archive files as unusable because they are absent from the current Analytics time range. The risk is: Required historical evidence is lost even though recoverable raw records existed before the deletion. The safer action is: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Confirm by: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

C.

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: Delete older Archive files as unusable because they are absent from the current Analytics time range. Its risk is: Required historical evidence is lost even though recoverable raw records existed before the deletion.

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: Delete older Archive files as unusable because they are absent from the current Analytics time range. Its risk is: Required historical evidence is lost even though recoverable raw records existed before the deletion.

Question 85

A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

A.

Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Check the result: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. The technical reason is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations.

B.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Test with: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

C.

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. This action-and-test pairing concerns another situation: A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. The current case needs this action: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Test with: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

D.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Test with: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

Question 86

A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone. What is the most defensible FortiAnalyzer action in this situation?

  1. Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.
  2. Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow.
  3. Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.
  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: A

A.

Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. The technical reason is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. Confirm by: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

B.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

C.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

Question 87

A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone. The reviewed recommendation is: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. What FortiAnalyzer mechanism supports the recommended analysis?

  1. A hypothesis-driven investigation uses corroborated time-bound source and destination observations rather than declaring compromise from one aggregate chart.
  2. Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source.
  3. Ingestion throughput and downstream indexing capacity can be bottlenecks even when enough disk space remains for compressed storage.
  4. Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations.

Answer & Explanations

Correct answer: D

A.

A hypothesis-driven investigation uses corroborated time-bound source and destination observations rather than declaring compromise from one aggregate chart. That principle explains a different situation: A regional university sees one campus IP dominate bandwidth after hours and wants to verify whether it reflects approved backups or exfiltration. Here the relevant cause is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. Apply it by: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

B.

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: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. Apply it by: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

C.

Ingestion throughput and downstream indexing capacity can be bottlenecks even when enough disk space remains for compressed storage. That principle explains a different situation: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. Here the relevant cause is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. Apply it by: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.

D.

Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. It explains why the intervention—use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it—addresses the stated problem. Test the mechanism by: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

Question 88

A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone. The reviewed recommendation is: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. 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. Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.
  4. Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot.

Answer & Explanations

Correct answer: A

A.

Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. This directly tests whether the chosen intervention works: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. The causal mechanism is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

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: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

C.

Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. That test is for another requirement: A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. It does not verify the stated outcome; the relevant check is: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

D.

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: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

Question 89

A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone. Which tempting SOC change would undermine the stated requirement?

  1. Delete older Archive files as unusable because they are absent from the current Analytics time range.
  2. Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation.
  3. Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence.
  4. Choose log forwarding for ongoing eligible streams or log fetching for supported historical retrieval and configure the corresponding endpoints.

Answer & Explanations

Correct answer: A

A.

Delete older Archive files as unusable because they are absent from the current Analytics time range. The risk is: Required historical evidence is lost even though recoverable raw records existed before the deletion. The safer action is: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Confirm by: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

B.

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: Delete older Archive files as unusable because they are absent from the current Analytics time range. Its risk is: Required historical evidence is lost even though recoverable raw records existed before the deletion. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

C.

Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. That is an appropriate action for the separate case: A regional university sees one campus IP dominate bandwidth after hours and wants to verify whether it reflects approved backups or exfiltration. It is not the unsafe shortcut asked about here. Reject: Delete older Archive files as unusable because they are absent from the current Analytics time range. Its risk is: Required historical evidence is lost even though recoverable raw records existed before the deletion.

D.

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: Delete older Archive files as unusable because they are absent from the current Analytics time range. Its risk is: Required historical evidence is lost even though recoverable raw records existed before the deletion.

Question 90

A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone. 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: 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.
  3. 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.
  4. 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.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Test with: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

B.

Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Check the result: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. The technical reason is: Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

C.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Test with: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration.

D.

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: Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it. Test with: Select a harmless archived test window and verify the expected indexed records appear in Log View and a scoped report dataset after restoration. The fictional case is: A hospital privacy investigation asks for an old log query and the team assumes absent online results mean all archived records are gone.

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