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 34

Question 330

A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Validate using: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.
  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: 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.
  4. 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.

Answer & Explanations

Correct answer: A

A.

Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Check the result: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. The technical reason is: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. The fictional case is: A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent.

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: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Test with: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

C.

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: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Test with: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. The fictional case is: A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent.

D.

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: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Test with: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. The fictional case is: A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent.

Question 331

A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

  1. Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.
  2. Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.
  3. Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome.
  4. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.

Answer & Explanations

Correct answer: A

A.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. The technical reason is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. Confirm by: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

B.

Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. That action is relevant to a different problem: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Its technical basis is: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. The present case instead requires: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

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 the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

D.

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 the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

Question 332

A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. The reviewed recommendation is: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria.
  2. FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction.
  3. Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window.
  4. AND combines constraints while OR broadens the result set, so wrong boolean logic changes which flows count as evidence.

Answer & Explanations

Correct answer: B

A.

Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. That principle explains a different situation: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. Here the relevant cause is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. Apply it by: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

B.

FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. It explains why the intervention—use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields—addresses the stated problem. Test the mechanism by: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

C.

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: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. Apply it by: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

D.

AND combines constraints while OR broadens the result set, so wrong boolean logic changes which flows count as evidence. That principle explains a different situation: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. Here the relevant cause is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. Apply it by: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

Question 333

A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. The reviewed recommendation is: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Which observation best demonstrates that this corrective step worked?

  1. Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.
  2. Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.
  3. Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.
  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: C

A.

Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. That test is for another requirement: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. It does not verify the stated outcome; the relevant check is: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

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: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

C.

Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. This directly tests whether the chosen intervention works: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. The causal mechanism is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction.

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: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

Question 334

A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Which unsafe investigation or automation shortcut must be rejected?

  1. Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance.
  2. Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator.
  3. Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.
  4. Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope.

Answer & Explanations

Correct answer: B

A.

Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. That is an appropriate action for the separate case: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. It is not the unsafe shortcut asked about here. Reject: Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator. Its risk is: Analysts isolate the wrong asset and miss the actual remote endpoint involved in suspicious activity.

B.

Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator. The risk is: Analysts isolate the wrong asset and miss the actual remote endpoint involved in suspicious activity. The safer action is: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Confirm by: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

C.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. That is an appropriate action for the separate case: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. It is not the unsafe shortcut asked about here. Reject: Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator. Its risk is: Analysts isolate the wrong asset and miss the actual remote endpoint involved in suspicious activity.

D.

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: Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator. Its risk is: Analysts isolate the wrong asset and miss the actual remote endpoint involved in suspicious activity.

Question 335

A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Validate using: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.
  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: 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: 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: D

A.

Choose this FortiAnalyzer analyst action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Validate using: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. This action-and-test pairing concerns another situation: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. The current case needs this action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

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 the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

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: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

D.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Check the result: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The technical reason is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction.

Question 336

A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination. What is the most defensible FortiAnalyzer action in this situation?

  1. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.
  2. Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.
  3. Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.
  4. Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

Answer & Explanations

Correct answer: C

A.

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 the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

B.

Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. That action is relevant to a different problem: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Its technical basis is: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. The present case instead requires: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

C.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. The technical reason is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. Confirm by: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

D.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. That action is relevant to a different problem: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. Its technical basis is: Reusable FortiView filters and dashboard configuration improve repeatability but must preserve the same underlying data scope and meaningful criteria. The present case instead requires: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

Question 337

A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination. The reviewed recommendation is: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. What FortiAnalyzer mechanism supports the recommended analysis?

  1. FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction.
  2. Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure.
  3. Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields.
  4. Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM.

Answer & Explanations

Correct answer: A

A.

FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. It explains why the intervention—use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields—addresses the stated problem. Test the mechanism by: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

B.

Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. That principle explains a different situation: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. Here the relevant cause is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. Apply it by: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

C.

Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. That principle explains a different situation: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Here the relevant cause is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. Apply it by: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

D.

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: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. Apply it by: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.

Question 338

A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination. The reviewed recommendation is: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. What pilot verification directly establishes the intended result?

  1. Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.
  2. Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.
  3. Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.
  4. Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

Answer & Explanations

Correct answer: C

A.

Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. That test is for another requirement: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. It does not verify the stated outcome; the relevant check is: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

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: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

C.

Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. This directly tests whether the chosen intervention works: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. The causal mechanism is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

D.

Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. That test is for another requirement: A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. It does not verify the stated outcome; the relevant check is: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

Question 339

A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination. Which tempting SOC change would undermine the stated requirement?

  1. Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator.
  2. Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records.
  3. Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
  4. Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints.

Answer & Explanations

Correct answer: A

A.

Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator. The risk is: Analysts isolate the wrong asset and miss the actual remote endpoint involved in suspicious activity. The safer action is: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Confirm by: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

B.

Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. That is an appropriate action for the separate case: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. It is not the unsafe shortcut asked about here. Reject: Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator. Its risk is: Analysts isolate the wrong asset and miss the actual remote endpoint involved in suspicious activity.

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: Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator. Its risk is: Analysts isolate the wrong asset and miss the actual remote endpoint involved in suspicious activity.

D.

Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. That is an appropriate action for the separate case: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. It is not the unsafe shortcut asked about here. Reject: Assume the largest top-sources bubble always represents the externally attacked service rather than the initiator. Its risk is: Analysts isolate the wrong asset and miss the actual remote endpoint involved in suspicious activity. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

Question 340

A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination. Which combined analytic action and validation test best solve this case?

  1. 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.
  2. 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.
  3. Choose this FortiAnalyzer analyst action: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Validate using: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.
  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: D

A.

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: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

B.

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. This action-and-test pairing concerns another situation: A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. The current case needs this action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

C.

Choose this FortiAnalyzer analyst action: Create a scoped saved filter or supported dashboard widget with documented device, time, and field constraints. Validate using: Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not. This action-and-test pairing concerns another situation: A university SOC repeatedly investigates unusual DNS requests from its research subnet and wants a reusable FortiView filter. The current case needs this action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Test with: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction.

D.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Check the result: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. The technical reason is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. The fictional case is: A retailer hunts an outbound malware connection and needs to distinguish compromised internal source from remote destination.

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