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 33

Question 320

A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope. Which combined analytic action and validation test best solve this case?

  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: Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. Validate using: Compare completion times for one representative report before and after off-peak scheduling and verified cache population.
  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: 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.

Answer & Explanations

Correct answer: A

A.

Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Check the result: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. The technical reason is: A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

B.

Choose this FortiAnalyzer analyst action: Review report job timing, hcache or auto-cache state, dataset performance, and contention with maintenance tasks before modifying the schedule. Validate using: Compare completion times for one representative report before and after off-peak scheduling and verified cache population. This action-and-test pairing concerns another situation: A retailer schedules dozens of FortiAnalyzer reports during peak payment-hour log aggregation and sees job backlogs. The current case needs this action: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Test with: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample.

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

D.

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: Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates. Test with: Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. The fictional case is: A retail analyst claims source totals differ between dashboards and a report without checking each view's time and device scope.

Question 321

A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Which FortiAnalyzer analyst action best addresses the stated operational requirement?

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

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. 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. Confirm by: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

B.

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: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

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: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

D.

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: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

Question 322

A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. The reviewed recommendation is: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. 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. FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs.
  3. FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection.
  4. Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields.

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: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. Apply it by: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

B.

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: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. Apply it by: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

C.

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: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. Apply it by: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

D.

Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. It explains why the intervention—verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name—addresses the stated problem. Test the mechanism by: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

Question 323

A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. The reviewed recommendation is: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Which observation best demonstrates that this corrective step worked?

  1. Open the saved view as an authorized analyst and verify the intended test sessions appear while unrelated subnet traffic does not.
  2. Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  3. Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.
  4. Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.

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: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

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: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

C.

Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. This directly tests whether the chosen intervention works: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. The causal mechanism is: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields.

D.

Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. That test is for another requirement: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. It does not verify the stated outcome; the relevant check is: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

Question 324

A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Which unsafe investigation or automation shortcut must be rejected?

  1. Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses.
  2. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.
  3. Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
  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.

Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses. The risk is: Analysts cannot reliably attribute traffic to the required policy objects and may produce incorrect object-based statistics. The safer action is: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Confirm by: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

B.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. That is an appropriate action for the separate case: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. It is not the unsafe shortcut asked about here. Reject: Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses. Its risk is: Analysts cannot reliably attribute traffic to the required policy objects and may produce incorrect object-based statistics.

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: Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses. Its risk is: Analysts cannot reliably attribute traffic to the required policy objects and may produce incorrect object-based statistics.

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: Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses. Its risk is: Analysts cannot reliably attribute traffic to the required policy objects and may produce incorrect object-based statistics.

Question 325

A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Which FortiAnalyzer action and acceptance test are correctly paired?

  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: 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.
  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: 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.

B.

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.

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: 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.

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.

Question 326

A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent. What is the most defensible FortiAnalyzer action in this situation?

  1. Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records.
  2. Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome.
  3. Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.
  4. Align FortiView time, device, and log source selection with the report period before comparing derived traffic aggregates.

Answer & Explanations

Correct answer: C

A.

Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records. That action is relevant to a different problem: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. Its technical basis is: AND combines constraints while OR broadens the result set, so wrong boolean logic changes which flows count as evidence. The present case instead requires: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

B.

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

C.

Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. 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. Confirm by: 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.

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: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

Question 327

A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent. The reviewed recommendation is: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. What FortiAnalyzer mechanism supports the recommended analysis?

  1. Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields.
  2. FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs.
  3. A current short-window dashboard and a longer historical report summarize different samples and cannot be directly compared without common scope.
  4. FortiAnalyzer reports use configured log and device scope so a successful job can return zero rows from an inappropriate selection.

Answer & Explanations

Correct answer: A

A.

Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. It explains why the intervention—verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name—addresses the stated problem. Test the mechanism by: 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.

B.

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: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. Apply it by: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. The fictional case is: A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent.

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: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. Apply it by: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name.

D.

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: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. Apply it by: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. 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 328

A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent. The reviewed recommendation is: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. 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. Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.
  3. Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  4. Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

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: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

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: Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object.

C.

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: 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.

Generate a permitted test session with object UUID logging and confirm FortiView resolves the expected source or destination object. This directly tests whether the chosen intervention works: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. The causal mechanism 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.

Question 329

A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent. Which tempting SOC change would undermine the stated requirement?

  1. Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses.
  2. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.
  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.

Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses. The risk is: Analysts cannot reliably attribute traffic to the required policy objects and may produce incorrect object-based statistics. The safer action is: Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. Confirm by: 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.

B.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. That is an appropriate action for the separate case: A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. It is not the unsafe shortcut asked about here. Reject: Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses. Its risk is: Analysts cannot reliably attribute traffic to the required policy objects and may produce incorrect object-based statistics. The fictional case is: A bank report references a policy source object while FortiView cannot filter old sessions because those log identifiers were absent.

C.

Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome. That is an appropriate action for the separate case: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. It is not the unsafe shortcut asked about here. Reject: Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses. Its risk is: Analysts cannot reliably attribute traffic to the required policy objects and may produce incorrect object-based statistics.

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: Rename policy objects in the dashboard and expect FortiAnalyzer to infer absent historical UUID identifiers from raw IP addresses. Its risk is: Analysts cannot reliably attribute traffic to the required policy objects and may produce incorrect object-based statistics. 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 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.

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