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 17

Question 160

A medical SOC wants new predefined threat handlers from FortiGuard and must distinguish installed local rules from licensed downloads. 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: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Validate using: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer.
  4. 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.

Answer & Explanations

Correct answer: D

A.

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. This action-and-test pairing concerns another 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. The current case needs this action: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Test with: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot.

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

C.

Choose this FortiAnalyzer analyst action: Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. Validate using: Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer. This action-and-test pairing concerns another situation: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. The current case needs this action: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Test with: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. The fictional case is: A medical SOC wants new predefined threat handlers from FortiGuard and must distinguish installed local rules from licensed downloads.

D.

Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Check the result: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. The technical reason is: Certain FortiGuard-supplied security automation content depends on valid service licensing and content availability separate from locally built objects. The fictional case is: A medical SOC wants new predefined threat handlers from FortiGuard and must distinguish installed local rules from licensed downloads.

Question 161

A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.
  2. Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view.
  3. Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources.
  4. Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody.

Answer & Explanations

Correct answer: A

A.

Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. The technical reason is: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. Confirm by: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

B.

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: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

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: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

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: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

Question 162

A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. The reviewed recommendation is: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action.
  2. SOC investigation must weigh event context and corroborating evidence before treating a log occurrence as an actionable incident.
  3. FortiAnalyzer requires the sending device to be registered and authorized before its logs are accepted for collection and analysis.
  4. FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context.

Answer & Explanations

Correct answer: A

A.

An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. It explains why the intervention—distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes—addresses the stated problem. Test the mechanism by: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

B.

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: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. Apply it by: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

C.

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: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. Apply it by: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

D.

FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. That principle explains a different situation: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. Here the relevant cause is: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. Apply it by: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

Question 163

A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. The reviewed recommendation is: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Which observation best demonstrates that this corrective step worked?

  1. Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member.
  2. Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.
  3. Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident.
  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: B

A.

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: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

B.

Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records. This directly tests whether the chosen intervention works: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. The causal mechanism is: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action.

C.

Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident. That test is for another requirement: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. It does not verify the stated outcome; the relevant check is: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

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: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

Question 164

A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. Which unsafe investigation or automation shortcut must be rejected?

  1. Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources.
  2. Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode.
  3. Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view.
  4. Assume opening an incident in the SOC console automatically isolates every involved endpoint.

Answer & Explanations

Correct answer: D

A.

Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. That is an appropriate action for the separate case: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. It is not the unsafe shortcut asked about here. Reject: Assume opening an incident in the SOC console automatically isolates every involved endpoint. Its risk is: Attack traffic remains permitted while the response team incorrectly assumes containment has already succeeded.

B.

Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. That is an appropriate action for the separate case: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. It is not the unsafe shortcut asked about here. Reject: Assume opening an incident in the SOC console automatically isolates every involved endpoint. Its risk is: Attack traffic remains permitted while the response team incorrectly assumes containment has already succeeded.

C.

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: Assume opening an incident in the SOC console automatically isolates every involved endpoint. Its risk is: Attack traffic remains permitted while the response team incorrectly assumes containment has already succeeded.

D.

Assume opening an incident in the SOC console automatically isolates every involved endpoint. The risk is: Attack traffic remains permitted while the response team incorrectly assumes containment has already succeeded. The safer action is: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Confirm by: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

Question 165

A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. Which FortiAnalyzer action and acceptance test are correctly paired?

  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: 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.
  3. Choose this FortiAnalyzer analyst action: Enable appropriate ADOM separation and assign administrators and logging devices only to their authorized analytical domains. Validate using: Sign in as two scoped analysts and confirm each can investigate only the assigned ADOM's devices and report data.
  4. Choose this FortiAnalyzer analyst action: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Validate using: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

Answer & Explanations

Correct answer: D

A.

Choose this FortiAnalyzer analyst action: Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents. Validate using: Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident. This action-and-test pairing concerns another situation: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. The current case needs this action: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Test with: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

B.

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. This action-and-test pairing concerns another 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. The current case needs this action: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Test with: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

C.

Choose this FortiAnalyzer analyst action: Enable appropriate ADOM separation and assign administrators and logging devices only to their authorized analytical domains. Validate using: Sign in as two scoped analysts and confirm each can investigate only the assigned ADOM's devices and report data. This action-and-test pairing concerns another situation: A managed service provider hosts firewall log analysis for two hospitals and must isolate the hospitals' Security Fabric device data. The current case needs this action: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Test with: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

D.

Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Check the result: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records. The technical reason is: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action.

Question 166

A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action. What is the most defensible FortiAnalyzer action in this situation?

  1. Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources.
  2. Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody.
  3. Validate both endpoint log encryption settings and authorization so the supported Fortinet logging transport uses compatible security levels.
  4. Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

Answer & Explanations

Correct answer: D

A.

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: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

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: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

C.

Validate both endpoint log encryption settings and authorization so the supported Fortinet logging transport uses compatible security levels. That action is relevant to a different problem: A hospital firewall sends traffic logs to FortiAnalyzer but security policy has raised the sender's encryption level beyond the receiver configuration. Its technical basis is: Fortinet proprietary OFTP log transfer requires configured encryption compatibility between sender and FortiAnalyzer receiver. The present case instead requires: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

D.

Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. The technical reason is: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. Confirm by: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

Question 167

A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action. The reviewed recommendation is: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. 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. Certain FortiGuard-supplied security automation content depends on valid service licensing and content availability separate from locally built objects.
  3. Real-time arriving logs and Archive files have different lifecycle states from indexed Analytics records that support interactive SQL-backed searches.
  4. An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action.

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: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. Apply it by: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

B.

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: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. Apply it by: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

C.

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: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. Apply it by: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes.

D.

An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. It explains why the intervention—distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes—addresses the stated problem. Test the mechanism by: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

Question 168

A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action. The reviewed recommendation is: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. 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. Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer.
  3. Inspect device authorization state and generate an innocuous test traffic event that appears under the intended device in Log View.
  4. Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

Answer & Explanations

Correct answer: D

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: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

B.

Increase a bounded synthetic log burst on a lab Collector and verify downstream arrival and searchable analytics on the Analyzer. That test is for another requirement: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. It does not verify the stated outcome; the relevant check is: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

C.

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: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

D.

Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records. This directly tests whether the chosen intervention works: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. The causal mechanism is: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

Question 169

A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action. Which tempting SOC change would undermine the stated requirement?

  1. Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources.
  2. Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode.
  3. Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context.
  4. Assume opening an incident in the SOC console automatically isolates every involved endpoint.

Answer & Explanations

Correct answer: D

A.

Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. That is an appropriate action for the separate case: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. It is not the unsafe shortcut asked about here. Reject: Assume opening an incident in the SOC console automatically isolates every involved endpoint. Its risk is: Attack traffic remains permitted while the response team incorrectly assumes containment has already succeeded. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

B.

Evaluate a Collector and Analyzer deployment with appropriate forwarding paths and sizing for each supported FortiAnalyzer operating mode. That is an appropriate action for the separate case: An international hospital group sends heavy firewall logs over constrained regional WANs to a central investigative FortiAnalyzer. It is not the unsafe shortcut asked about here. Reject: Assume opening an incident in the SOC console automatically isolates every involved endpoint. Its risk is: Attack traffic remains permitted while the response team incorrectly assumes containment has already succeeded. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

C.

Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. That is an appropriate action for the separate case: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. It is not the unsafe shortcut asked about here. Reject: Assume opening an incident in the SOC console automatically isolates every involved endpoint. Its risk is: Attack traffic remains permitted while the response team incorrectly assumes containment has already succeeded.

D.

Assume opening an incident in the SOC console automatically isolates every involved endpoint. The risk is: Attack traffic remains permitted while the response team incorrectly assumes containment has already succeeded. The safer action is: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Confirm by: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

Question 170

A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. Choose this FortiAnalyzer analyst action: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Validate using: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation. Validate using: Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope.

Answer & Explanations

Correct answer: B

A.

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: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Test with: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

B.

Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Check the result: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records. The technical reason is: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. The fictional case is: A hospital SOC creates an incident from malicious domain logs but the FortiGate never received a blocking action.

C.

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: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Test with: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

D.

Choose this FortiAnalyzer analyst action: Use an appropriate Security Fabric ADOM and enroll the supported member devices for shared normalized SOC investigation. Validate using: Generate test security events on two authorized product types and confirm both appear within the intended Fabric analysis scope. This action-and-test pairing concerns another situation: A bank wants to review suspicious FortiGate connections together with FortiMail malware events in one analyst investigation context. The current case needs this action: Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. Test with: Trace the event through incident creation and any playbook job to actual authorized FortiGate policy or endpoint change records.

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