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 24

Question 230

A bank investigation begins with a lateral connection and needs preceding authentication and firewall events across two time zones. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. Validate using: Inspect a controlled blocked test event and an observed allowed event to compare their exact log action and detection values.
  2. Choose this FortiAnalyzer analyst action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Validate using: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  3. Choose this FortiAnalyzer analyst action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Validate using: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.
  4. Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. Validate using: Inspect a controlled blocked test event and an observed allowed event to compare their exact log action and detection values. This action-and-test pairing concerns another situation: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. The current case needs this action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Test with: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.

B.

Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Check the result: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality. The technical reason is: Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly. The fictional case is: A bank investigation begins with a lateral connection and needs preceding authentication and firewall events across two time zones.

C.

Choose this FortiAnalyzer analyst action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Validate using: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. This action-and-test pairing concerns another situation: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. The current case needs this action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Test with: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.

D.

Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. This action-and-test pairing concerns another situation: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. The current case needs this action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Test with: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.

Question 231

A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity.
  2. Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.
  3. Verify the report definition's ADOM, selected devices, and time filter match the original logging sources.
  4. Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.

Answer & Explanations

Correct answer: B

A.

Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. That action is relevant to a different problem: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. Its technical basis is: Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM. The present case instead requires: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

B.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. The technical reason is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. Confirm by: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

C.

Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. That action is relevant to a different problem: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. Its technical basis is: FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection. The present case instead requires: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

D.

Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. That action is relevant to a different problem: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. Its technical basis is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. The present case instead requires: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

Question 232

A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. The reviewed recommendation is: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction.
  2. IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness.
  3. Multiple alerts can describe one traffic or security sequence and unambiguous event identity prevents duplicate investigations.
  4. FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs.

Answer & Explanations

Correct answer: B

A.

FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. That principle explains a different situation: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Here the relevant cause is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. Apply it by: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

B.

IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. It explains why the intervention—enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence—addresses the stated problem. Test the mechanism by: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

C.

Multiple alerts can describe one traffic or security sequence and unambiguous event identity prevents duplicate investigations. That principle explains a different situation: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. Here the relevant cause is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. Apply it by: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

D.

FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. That principle explains a different situation: A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. Here the relevant cause is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. Apply it by: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

Question 233

A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. The reviewed recommendation is: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Which observation best demonstrates that this corrective step worked?

  1. Generate a harmless supported security event and confirm the required log subtype and widget are then populated.
  2. Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.
  3. Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.
  4. Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

Answer & Explanations

Correct answer: D

A.

Generate a harmless supported security event and confirm the required log subtype and widget are then populated. That test is for another requirement: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. It does not verify the stated outcome; the relevant check is: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

B.

Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. That test is for another requirement: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. It does not verify the stated outcome; the relevant check is: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

C.

Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. That test is for another requirement: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. It does not verify the stated outcome; the relevant check is: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

D.

Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. This directly tests whether the chosen intervention works: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. The causal mechanism is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness.

Question 234

A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Which unsafe investigation or automation shortcut must be rejected?

  1. Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer.
  2. Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity.
  3. Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested.
  4. Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.

Answer & Explanations

Correct answer: C

A.

Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer. That is an appropriate action for the separate case: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. It is not the unsafe shortcut asked about here. Reject: Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested. Its risk is: Misapplied reputation can block legitimate systems while the actual source of suspicious traffic remains unresolved.

B.

Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. That is an appropriate action for the separate case: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. It is not the unsafe shortcut asked about here. Reject: Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested. Its risk is: Misapplied reputation can block legitimate systems while the actual source of suspicious traffic remains unresolved.

C.

Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested. The risk is: Misapplied reputation can block legitimate systems while the actual source of suspicious traffic remains unresolved. The safer action is: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Confirm by: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

D.

Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. That is an appropriate action for the separate case: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. It is not the unsafe shortcut asked about here. Reject: Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested. Its risk is: Misapplied reputation can block legitimate systems while the actual source of suspicious traffic remains unresolved.

Question 235

A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Validate using: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.
  2. Choose this FortiAnalyzer analyst action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Validate using: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  3. Choose this FortiAnalyzer analyst action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Validate using: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.
  4. Choose this FortiAnalyzer analyst action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Validate using: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices.

Answer & Explanations

Correct answer: A

A.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Check the result: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. The technical reason is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness.

B.

Choose this FortiAnalyzer analyst action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Validate using: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality. This action-and-test pairing concerns another situation: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. The current case needs this action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Test with: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

C.

Choose this FortiAnalyzer analyst action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Validate using: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. This action-and-test pairing concerns another situation: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. The current case needs this action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Test with: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

D.

Choose this FortiAnalyzer analyst action: Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. Validate using: Run a known test query for two devices and confirm the report includes the intended ADOM member and excludes unrelated devices. This action-and-test pairing concerns another situation: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. The current case needs this action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Test with: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

Question 236

A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs. What is the most defensible FortiAnalyzer action in this situation?

  1. Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.
  2. Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.
  3. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.
  4. Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer.

Answer & Explanations

Correct answer: A

A.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. The technical reason is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. Confirm by: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. The fictional case is: A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs.

B.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. That action is relevant to a different problem: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Its technical basis is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. The present case instead requires: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

C.

Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. That action is relevant to a different problem: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. Its technical basis is: Multiple alerts can describe one traffic or security sequence and unambiguous event identity prevents duplicate investigations. The present case instead requires: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

D.

Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer. That action is relevant to a different problem: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. Its technical basis is: Report datasets usually query indexed Analytics records, while received raw Archive files may not yet be in the SQL reporting source. The present case instead requires: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

Question 237

A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs. The reviewed recommendation is: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. What FortiAnalyzer mechanism supports the recommended analysis?

  1. A malware or intrusion detection finding does not independently prove whether FortiOS forwarded, blocked, reset, or quarantined an associated flow.
  2. FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection.
  3. IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness.
  4. Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly.

Answer & Explanations

Correct answer: C

A.

A malware or intrusion detection finding does not independently prove whether FortiOS forwarded, blocked, reset, or quarantined an associated flow. That principle explains a different situation: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. Here the relevant cause is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. Apply it by: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

B.

FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection. That principle explains a different situation: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. Here the relevant cause is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. Apply it by: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

C.

IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. It explains why the intervention—enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence—addresses the stated problem. Test the mechanism by: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. The fictional case is: A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs.

D.

Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly. That principle explains a different situation: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. Here the relevant cause is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. Apply it by: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.

Question 238

A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs. The reviewed recommendation is: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. What pilot verification directly establishes the intended result?

  1. Generate a harmless supported security event and confirm the required log subtype and widget are then populated.
  2. Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
  3. After a controlled log ingestion interval, compare the Archive arrival timestamp with indexed Analytics count and rerun the same report window.
  4. Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

Answer & Explanations

Correct answer: D

A.

Generate a harmless supported security event and confirm the required log subtype and widget are then populated. That test is for another requirement: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. It does not verify the stated outcome; the relevant check is: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. The fictional case is: A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs.

B.

Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. That test is for another requirement: A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. It does not verify the stated outcome; the relevant check is: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

C.

After a controlled log ingestion interval, compare the Archive arrival timestamp with indexed Analytics count and rerun the same report window. That test is for another requirement: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. It does not verify the stated outcome; the relevant check is: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

D.

Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. This directly tests whether the chosen intervention works: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. The causal mechanism is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. The fictional case is: A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs.

Question 239

A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs. Which tempting SOC change would undermine the stated requirement?

  1. Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested.
  2. Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer.
  3. Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
  4. Verify the report definition's ADOM, selected devices, and time filter match the original logging sources.

Answer & Explanations

Correct answer: A

A.

Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested. The risk is: Misapplied reputation can block legitimate systems while the actual source of suspicious traffic remains unresolved. The safer action is: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Confirm by: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. The fictional case is: A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs.

B.

Check indexing delay and SQL Analytics availability for the report's time range before diagnosing the report renderer. That is an appropriate action for the separate case: A hospital generates a daily report just after a heavy firewall log burst and some newest events have not yet entered Analytics. It is not the unsafe shortcut asked about here. Reject: Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested. Its risk is: Misapplied reputation can block legitimate systems while the actual source of suspicious traffic remains unresolved. The fictional case is: A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs.

C.

Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. That is an appropriate action for the separate case: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. It is not the unsafe shortcut asked about here. Reject: Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested. Its risk is: Misapplied reputation can block legitimate systems while the actual source of suspicious traffic remains unresolved. The fictional case is: A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs.

D.

Verify the report definition's ADOM, selected devices, and time filter match the original logging sources. That is an appropriate action for the separate case: A university uses a copied FortiAnalyzer template built for its old firewall and sees no results for a replacement device. It is not the unsafe shortcut asked about here. Reject: Quarantine every host because a similarly spelled domain appears in an old intelligence feed even when it was never requested. Its risk is: Misapplied reputation can block legitimate systems while the actual source of suspicious traffic remains unresolved.

Question 240

A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Validate using: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.
  2. Choose this FortiAnalyzer analyst action: Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. Validate using: Inspect a controlled blocked test event and an observed allowed event to compare their exact log action and detection values.
  3. Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.
  4. Choose this FortiAnalyzer analyst action: Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. Validate using: Generate a harmless supported security event and confirm the required log subtype and widget are then populated.

Answer & Explanations

Correct answer: A

A.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Check the result: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. The technical reason is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. The fictional case is: A regional insurer receives an IP indicator and needs to confirm that the suspicious address occurred in the relevant FortiGate session logs.

B.

Choose this FortiAnalyzer analyst action: Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. Validate using: Inspect a controlled blocked test event and an observed allowed event to compare their exact log action and detection values. This action-and-test pairing concerns another situation: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. The current case needs this action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Test with: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

C.

Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. This action-and-test pairing concerns another situation: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. The current case needs this action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Test with: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

D.

Choose this FortiAnalyzer analyst action: Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. Validate using: Generate a harmless supported security event and confirm the required log subtype and widget are then populated. This action-and-test pairing concerns another situation: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. The current case needs this action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Test with: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

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