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 26

Question 250

A university analyst receives duplicated FortiGate security records forwarded through two collectors and must avoid counting them as separate attacks. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.

Answer & Explanations

Correct answer: D

A.

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: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Test with: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections. The fictional case is: A university analyst receives duplicated FortiGate security records forwarded through two collectors and must avoid counting them as separate attacks.

B.

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: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Test with: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.

C.

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. This action-and-test pairing concerns another situation: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. The current case needs this action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Test with: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.

D.

Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Check the result: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections. The technical reason is: Multiple alerts can describe one traffic or security sequence and unambiguous event identity prevents duplicate investigations. The fictional case is: A university analyst receives duplicated FortiGate security records forwarded through two collectors and must avoid counting them as separate attacks.

Question 251

A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.
  2. Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.
  3. Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.
  4. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

Answer & Explanations

Correct answer: A

A.

Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. The technical reason is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. Confirm by: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

B.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. That action is relevant to a different problem: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Its technical basis is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. The present case instead requires: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

C.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. That action is relevant to a different problem: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. Its technical basis is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. The present case instead requires: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

D.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. That action is relevant to a different problem: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. Its technical basis is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. The present case instead requires: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

Question 252

A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. The reviewed recommendation is: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM.
  2. Multiple alerts can describe one traffic or security sequence and unambiguous event identity prevents duplicate investigations.
  3. A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope.
  4. Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence.

Answer & Explanations

Correct answer: D

A.

Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM. That principle explains a different situation: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. Here the relevant cause is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. Apply it by: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

B.

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: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. Apply it by: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

C.

A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. That principle explains a different situation: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. Here the relevant cause is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. Apply it by: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

D.

Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. It explains why the intervention—use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it—addresses the stated problem. Test the mechanism by: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

Question 253

A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. The reviewed recommendation is: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Which observation best demonstrates that this corrective step worked?

  1. Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.
  2. Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.
  3. Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
  4. Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter.

Answer & Explanations

Correct answer: A

A.

Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. This directly tests whether the chosen intervention works: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. The causal mechanism is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence.

B.

Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections. That test is for another requirement: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. It does not verify the stated outcome; the relevant check is: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

C.

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: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

D.

Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter. That test is for another requirement: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. It does not verify the stated outcome; the relevant check is: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

Question 254

A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. Which unsafe investigation or automation shortcut must be rejected?

  1. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.
  2. Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.
  3. Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
  4. Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested.

Answer & Explanations

Correct answer: D

A.

Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. That is an appropriate action for the separate case: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. It is not the unsafe shortcut asked about here. Reject: Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested. Its risk is: The report attributes malicious execution to an unverified file and misdirects containment actions.

B.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. That is an appropriate action for the separate case: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. It is not the unsafe shortcut asked about here. Reject: Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested. Its risk is: The report attributes malicious execution to an unverified file and misdirects containment actions.

C.

Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. That is an appropriate action for the separate case: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. It is not the unsafe shortcut asked about here. Reject: Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested. Its risk is: The report attributes malicious execution to an unverified file and misdirects containment actions.

D.

Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested. The risk is: The report attributes malicious execution to an unverified file and misdirects containment actions. The safer action is: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Confirm by: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

Question 255

A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Validate using: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.
  2. Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.
  3. Choose this FortiAnalyzer analyst action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Validate using: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
  4. Choose this FortiAnalyzer analyst action: Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. Validate using: Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter.

Answer & Explanations

Correct answer: A

A.

Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Check the result: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. The technical reason is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence.

B.

Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections. This action-and-test pairing concerns another situation: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. The current case needs this action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

C.

Choose this FortiAnalyzer analyst action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Validate using: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. This action-and-test pairing concerns another situation: A multi-hospital SOC investigates lateral traffic between two facilities whose FortiGates were assigned to different ADOMs. The current case needs this action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

D.

Choose this FortiAnalyzer analyst action: Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. Validate using: Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter. This action-and-test pairing concerns another situation: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. The current case needs this action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

Question 256

A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset. What is the most defensible FortiAnalyzer action in this situation?

  1. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.
  2. Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.
  3. Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome.
  4. Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

Answer & Explanations

Correct answer: B

A.

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: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

B.

Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. The technical reason is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. Confirm by: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

C.

Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. That action is relevant to a different problem: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. Its technical basis is: A malware or intrusion detection finding does not independently prove whether FortiOS forwarded, blocked, reset, or quarantined an associated flow. The present case instead requires: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

D.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. That action is relevant to a different problem: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. Its technical basis is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. The present case instead requires: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

Question 257

A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset. The reviewed recommendation is: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo.
  2. Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM.
  3. Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence.
  4. Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window.

Answer & Explanations

Correct answer: C

A.

Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. That principle explains a different situation: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. Here the relevant cause is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. Apply it by: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

B.

Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM. That principle explains a different situation: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. Here the relevant cause is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. Apply it by: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

C.

Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. It explains why the intervention—use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it—addresses the stated problem. Test the mechanism by: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

D.

Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. That principle explains a different situation: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. Here the relevant cause is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. Apply it by: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

Question 258

A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset. The reviewed recommendation is: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. 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. Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  3. Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.
  4. Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

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: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

B.

Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality. That test is for another requirement: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. It does not verify the stated outcome; the relevant check is: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

C.

Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. That test is for another requirement: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. It does not verify the stated outcome; the relevant check is: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

D.

Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. This directly tests whether the chosen intervention works: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. The causal mechanism is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

Question 259

A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset. Which tempting SOC change would undermine the stated requirement?

  1. Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.
  2. Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested.
  3. Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity.
  4. Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.

Answer & Explanations

Correct answer: B

A.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. That is an appropriate action for the separate case: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. It is not the unsafe shortcut asked about here. Reject: Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested. Its risk is: The report attributes malicious execution to an unverified file and misdirects containment actions.

B.

Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested. The risk is: The report attributes malicious execution to an unverified file and misdirects containment actions. The safer action is: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Confirm by: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

C.

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: Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested. Its risk is: The report attributes malicious execution to an unverified file and misdirects containment actions.

D.

Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. That is an appropriate action for the separate case: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. It is not the unsafe shortcut asked about here. Reject: Invent a malware process name from aggregate traffic volume when no endpoint process telemetry has been ingested. Its risk is: The report attributes malicious execution to an unverified file and misdirects containment actions. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

Question 260

A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
  2. 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.
  3. Choose this FortiAnalyzer analyst action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Validate using: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.
  4. Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.

Answer & Explanations

Correct answer: C

A.

Choose this FortiAnalyzer analyst action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. This action-and-test pairing concerns another situation: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. The current case needs this action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

B.

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: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

C.

Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Check the result: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. The technical reason is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

D.

Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections. This action-and-test pairing concerns another situation: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. The current case needs this action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.

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