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 20

Question 190

A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Validate using: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
  2. Choose this FortiAnalyzer analyst action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Validate using: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.
  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: A

A.

Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Check the result: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. The technical reason is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.

B.

Choose this FortiAnalyzer analyst action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Validate using: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. This action-and-test pairing concerns another situation: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. The current case needs this action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.

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: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.

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: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.

Question 191

A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Ensure appropriate SIEM log parsers and normalization are enabled for the data sources and examine the resulting shared fields.
  2. Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody.
  3. Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.
  4. Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.

Answer & Explanations

Correct answer: C

A.

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: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

B.

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: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

C.

Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. The technical reason is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. Confirm by: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

D.

Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. That action is relevant to a different problem: A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. Its technical basis is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. The present case instead requires: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

Question 192

A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. The reviewed recommendation is: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Certain FortiGuard-supplied security automation content depends on valid service licensing and content availability separate from locally built objects.
  2. Real-time arriving logs and Archive files have different lifecycle states from indexed Analytics records that support interactive SQL-backed searches.
  3. FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context.
  4. Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement.

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: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. Apply it by: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

B.

Real-time arriving logs and Archive files have different lifecycle states from indexed Analytics records that support interactive SQL-backed searches. That principle explains a different situation: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. Here the relevant cause is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. Apply it by: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

C.

FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. It explains why the intervention—create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context—addresses the stated problem. Test the mechanism by: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

D.

Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. That principle explains a different situation: A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. Here the relevant cause is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. Apply it by: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

Question 193

A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. The reviewed recommendation is: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Which observation best demonstrates that this corrective step worked?

  1. Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay.
  2. Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member.
  3. Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.
  4. Test an authorized connection with protected transport and confirm security logs are received after the agreed encryption policy is enforced.

Answer & Explanations

Correct answer: C

A.

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: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

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: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

C.

Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. This directly tests whether the chosen intervention works: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. The causal mechanism is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context.

D.

Test an authorized connection with protected transport and confirm security logs are received after the agreed encryption policy is enforced. That test is for another requirement: A hospital firewall sends traffic logs to FortiAnalyzer but security policy has raised the sender's encryption level beyond the receiver configuration. It does not verify the stated outcome; the relevant check is: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

Question 194

A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. Which unsafe investigation or automation shortcut must be rejected?

  1. Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format.
  2. Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view.
  3. Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall.
  4. Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.

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: Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall. Its risk is: Analysts lose the attack sequence and cannot justify a complete detection or response decision.

B.

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: Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall. Its risk is: Analysts lose the attack sequence and cannot justify a complete detection or response decision.

C.

Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall. The risk is: Analysts lose the attack sequence and cannot justify a complete detection or response decision. The safer action is: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Confirm by: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

D.

Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. That is an appropriate action for the separate case: A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. It is not the unsafe shortcut asked about here. Reject: Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall. Its risk is: Analysts lose the attack sequence and cannot justify a complete detection or response decision.

Question 195

A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Validate using: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.
  2. 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.
  3. Choose this FortiAnalyzer analyst action: Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. Validate using: Record a test hypothesis, pivot to original underlying logs, and document the evidence supporting or rejecting it.
  4. Choose this FortiAnalyzer analyst action: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Validate using: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches.

Answer & Explanations

Correct answer: A

A.

Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Check the result: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. The technical reason is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context.

B.

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: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

C.

Choose this FortiAnalyzer analyst action: Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. Validate using: Record a test hypothesis, pivot to original underlying logs, and document the evidence supporting or rejecting it. This action-and-test pairing concerns another situation: A regional university sees one campus IP dominate bandwidth after hours and wants to verify whether it reflects approved backups or exfiltration. The current case needs this action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

D.

Choose this FortiAnalyzer analyst action: Identify an appropriate predefined or supported custom parser and confirm that it is enabled and assigned to the actual log format. Validate using: Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. This action-and-test pairing concerns another situation: A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. The current case needs this action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

Question 196

A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM. 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. Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.
  3. Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources.
  4. Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents.

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: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

B.

Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. The technical reason is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. Confirm by: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

C.

Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. That action is relevant to a different problem: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. Its technical basis is: Certain FortiGuard-supplied security automation content depends on valid service licensing and content availability separate from locally built objects. The present case instead requires: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

D.

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: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

Question 197

A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM. The reviewed recommendation is: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Normalized Fabric log fields permit correlation and analysis across supported heterogeneous source formats when parsers correctly map their original values.
  2. FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context.
  3. An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action.
  4. Real-time arriving logs and Archive files have different lifecycle states from indexed Analytics records that support interactive SQL-backed searches.

Answer & Explanations

Correct answer: B

A.

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: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. Apply it by: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

B.

FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. It explains why the intervention—create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context—addresses the stated problem. Test the mechanism by: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

C.

An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. That principle explains a different situation: A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. Here the relevant cause is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. Apply it by: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.

D.

Real-time arriving logs and Archive files have different lifecycle states from indexed Analytics records that support interactive SQL-backed searches. That principle explains a different situation: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. Here the relevant cause is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. Apply it by: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

Question 198

A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM. The reviewed recommendation is: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. What pilot verification directly establishes the intended result?

  1. Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay.
  2. Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.
  3. Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member.
  4. Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

Answer & Explanations

Correct answer: B

A.

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: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

B.

Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. This directly tests whether the chosen intervention works: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. The causal mechanism is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

C.

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: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

D.

Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records. That test is for another requirement: A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. It does not verify the stated outcome; the relevant check is: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

Question 199

A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM. Which tempting SOC change would undermine the stated requirement?

  1. Verify the configured FortiAnalyzer destination and approve the actual FortiGate device in Device Manager or the supported Fabric authorization flow.
  2. Validate both endpoint log encryption settings and authorization so the supported Fortinet logging transport uses compatible security levels.
  3. Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents.
  4. Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall.

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 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: Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall. Its risk is: Analysts lose the attack sequence and cannot justify a complete detection or response decision.

B.

Validate both endpoint log encryption settings and authorization so the supported Fortinet logging transport uses compatible security levels. That is an appropriate action for the separate case: A hospital firewall sends traffic logs to FortiAnalyzer but security policy has raised the sender's encryption level beyond the receiver configuration. It is not the unsafe shortcut asked about here. Reject: Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall. Its risk is: Analysts lose the attack sequence and cannot justify a complete detection or response decision.

C.

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: Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall. Its risk is: Analysts lose the attack sequence and cannot justify a complete detection or response decision.

D.

Dismiss email and sandbox evidence as irrelevant merely because the first alert arrived from a firewall. The risk is: Analysts lose the attack sequence and cannot justify a complete detection or response decision. The safer action is: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Confirm by: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

Question 200

A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. Choose this FortiAnalyzer analyst action: Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. Validate using: Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member.
  3. Choose this FortiAnalyzer analyst action: 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: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Validate using: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

Answer & Explanations

Correct answer: D

A.

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: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

B.

Choose this FortiAnalyzer analyst action: Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. Validate using: Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member. This action-and-test pairing concerns another situation: A multinational retailer puts regional FortiAnalyzers under a central Fabric supervisor and needs accurate log custody boundaries. The current case needs this action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

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: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

D.

Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Check the result: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. The technical reason is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

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