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 10

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.

Question 91

A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.
  2. Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow.
  3. Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents.
  4. Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view.

Answer & Explanations

Correct answer: A

A.

Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. The technical reason is: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. Confirm by: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

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: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

C.

Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents. That action is relevant to a different problem: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. Its technical basis is: SOC investigation must weigh event context and corroborating evidence before treating a log occurrence as an actionable incident. The present case instead requires: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

D.

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: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

Question 92

A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. The reviewed recommendation is: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. SOC investigation must weigh event context and corroborating evidence before treating a log occurrence as an actionable incident.
  2. FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data.
  3. Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations.
  4. Ingestion throughput and downstream indexing capacity can be bottlenecks even when enough disk space remains for compressed storage.

Answer & Explanations

Correct answer: B

A.

SOC investigation must weigh event context and corroborating evidence before treating a log occurrence as an actionable incident. That principle explains a different situation: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. Here the relevant cause is: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. Apply it by: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

B.

FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. It explains why the intervention—review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed—addresses the stated problem. Test the mechanism by: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

C.

Archive storage preserves compressed raw log evidence while the Analytics database requires indexed data for many searches and report operations. That principle explains a different situation: A financial SOC must regenerate a quarterly report from archived FortiGate records that were aged out of the online Analytics database. Here the relevant cause is: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. Apply it by: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

D.

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: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. Apply it by: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

Question 93

A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. The reviewed recommendation is: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Which observation best demonstrates that this corrective step worked?

  1. Sign in as two scoped analysts and confirm each can investigate only the assigned ADOM's devices and report data.
  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. Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.
  4. 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: C

A.

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: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

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: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

C.

Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy. This directly tests whether the chosen intervention works: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. The causal mechanism is: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data.

D.

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: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

Question 94

A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. Which unsafe investigation or automation shortcut must be rejected?

  1. Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents.
  2. Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody.
  3. Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained.
  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: C

A.

Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents. That is an appropriate action for the separate case: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. It is not the unsafe shortcut asked about here. Reject: Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained. Its risk is: Audit evidence may be deleted prematurely and no longer be reconstructable from the remaining searchable database.

B.

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: Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained. Its risk is: Audit evidence may be deleted prematurely and no longer be reconstructable from the remaining searchable database.

C.

Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained. The risk is: Audit evidence may be deleted prematurely and no longer be reconstructable from the remaining searchable database. The safer action is: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Confirm by: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

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: Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained. Its risk is: Audit evidence may be deleted prematurely and no longer be reconstructable from the remaining searchable database.

Question 95

A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. Which FortiAnalyzer action and acceptance test are correctly paired?

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

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.

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

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

Question 96

A university shortens Analytics storage for performance and must not inadvertently erase older Archive records required for investigations. What is the most defensible FortiAnalyzer action in this situation?

  1. Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation.
  2. Use supported restoration or reimport of the eligible archived log period into Analytics before expecting SQL-backed report queries to find it.
  3. Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.
  4. Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment.

Answer & Explanations

Correct answer: C

A.

Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation. That action is relevant to a different problem: A bank wants to review suspicious FortiGate connections together with FortiMail malware events in one analyst investigation context. Its technical basis is: Fabric ADOMs can present eligible different Fortinet product logs and security events together while retaining explicit membership and access control. The present case instead requires: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

B.

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: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

C.

Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. The technical reason is: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. Confirm by: 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.

D.

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: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

Question 97

A university shortens Analytics storage for performance and must not inadvertently erase older Archive records required for investigations. The reviewed recommendation is: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Fabric ADOMs can present eligible different Fortinet product logs and security events together while retaining explicit membership and access control.
  2. FortiAnalyzer requires the sending device to be registered and authorized before its logs are accepted for collection and analysis.
  3. Forwarding transmits selected logging data according to a configured schedule whereas fetching retrieves previously stored data from a remote source.
  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: 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: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. Apply it by: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

B.

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: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. Apply it by: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

C.

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: FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. Apply it by: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed.

D.

FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. It explains why the intervention—review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed—addresses the stated problem. Test the mechanism by: 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 98

A university shortens Analytics storage for performance and must not inadvertently erase older Archive records required for investigations. The reviewed recommendation is: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. What pilot verification directly establishes the intended result?

  1. Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.
  2. Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View.
  3. Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view.
  4. Capture one newly generated log and one known older test record and verify each travels through the deliberately selected transfer workflow.

Answer & Explanations

Correct answer: A

A.

Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy. This directly tests whether the chosen intervention works: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. The causal mechanism 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.

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

C.

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

D.

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: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy.

Question 99

A university shortens Analytics storage for performance and must not inadvertently erase older Archive records required for investigations. Which tempting SOC change would undermine the stated requirement?

  1. Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.
  2. Enable appropriate ADOM separation and assign administrators and logging devices only to their authorized analytical domains.
  3. Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained.
  4. Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view.

Answer & Explanations

Correct answer: C

A.

Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. That is an appropriate action for the separate case: A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. It is not the unsafe shortcut asked about here. Reject: Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained. Its risk is: Audit evidence may be deleted prematurely and no longer be reconstructable from the remaining searchable database.

B.

Enable appropriate ADOM separation and assign administrators and logging devices only to their authorized analytical domains. That is an appropriate action for the separate case: A managed service provider hosts firewall log analysis for two hospitals and must isolate the hospitals' Security Fabric device data. It is not the unsafe shortcut asked about here. Reject: Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained. Its risk is: Audit evidence may be deleted prematurely and no longer be reconstructable from the remaining searchable database.

C.

Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained. The risk is: Audit evidence may be deleted prematurely and no longer be reconstructable from the remaining searchable database. The safer action is: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Confirm by: 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.

D.

Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. That is an appropriate action for the separate case: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. It is not the unsafe shortcut asked about here. Reject: Reduce Archive retention to zero to free space while promising auditors all historical raw logs will still be retained. Its risk is: Audit evidence may be deleted prematurely and no longer be reconstructable from the remaining searchable database.

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.

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