Fortinet FCP_FAZ_AN-7.6 Dumps
Fortinet FCP_FAZ_AN-7.6 Practice Test 29
Question 280
A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View. Which combined analytic action and validation test best solve this case?
Answer & Explanations
Correct answer: A
Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Check the result: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected. The technical reason is: FortiAnalyzer log and incident views are constrained by administrative domain and selected device filters so absent data may reflect scope rather than missing logs. The fictional case is: A university analyst needs to correlate campus and laboratory firewall logs but had selected a single device filter in Log View.
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 ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
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: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
Choose this FortiAnalyzer analyst action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Validate using: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. This action-and-test pairing concerns another situation: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. The current case needs this action: Verify ADOM device membership and explicitly scope the Log View search to the right authorized devices and time range. Test with: Run a controlled search with known test events from both entitled devices and confirm each appears only when its authorized scope is selected.
Question 281
A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. Which FortiAnalyzer analyst action best addresses the stated operational requirement?
Answer & Explanations
Correct answer: B
Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. That action is relevant to a different problem: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Its technical basis is: FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. The present case instead requires: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. The technical reason is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. Confirm by: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
Question 282
A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. The reviewed recommendation is: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Which technical principle explains why the proposed FortiAnalyzer action works?
Answer & Explanations
Correct answer: D
FortiView visualizations summarize distinct dimensions and swapping initiator with target can invert the inferred attack direction. That principle explains a different situation: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. Here the relevant cause is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. Apply it by: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
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: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. Apply it by: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
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: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. Apply it by: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. It explains why the intervention—apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events—addresses the stated problem. Test the mechanism by: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
Question 283
A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. The reviewed recommendation is: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Which observation best demonstrates that this corrective step worked?
Answer & Explanations
Correct answer: 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: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. This directly tests whether the chosen intervention works: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. The causal mechanism is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window.
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: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
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: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
Question 284
A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. Which unsafe investigation or automation shortcut must be rejected?
Answer & Explanations
Correct answer: 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: Block the top byte-count source from the widget without checking its destination or authorized business process. Its risk is: Legitimate scheduled data transfer is interrupted while actual malicious low-volume flows may be overlooked.
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: Block the top byte-count source from the widget without checking its destination or authorized business process. Its risk is: Legitimate scheduled data transfer is interrupted while actual malicious low-volume flows may be overlooked.
Block the top byte-count source from the widget without checking its destination or authorized business process. The risk is: Legitimate scheduled data transfer is interrupted while actual malicious low-volume flows may be overlooked. The safer action is: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Confirm by: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
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: Block the top byte-count source from the widget without checking its destination or authorized business process. Its risk is: Legitimate scheduled data transfer is interrupted while actual malicious low-volume flows may be overlooked.
Question 285
A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. Which FortiAnalyzer action and acceptance test are correctly paired?
Answer & Explanations
Correct answer: 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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Test with: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Test with: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Check the result: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. The technical reason is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window.
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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Test with: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
Question 286
A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment. What is the most defensible FortiAnalyzer action in this situation?
Answer & Explanations
Correct answer: 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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. The fictional case is: A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment.
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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. The fictional case is: A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment.
Check required log types and relevant device logging configuration before interpreting an unavailable FortiView widget as zero threat activity. That action is relevant to a different problem: A university expects a FortiView threat summary but has enabled only basic traffic logs from its campus FortiGate. Its technical basis is: Different widgets depend on corresponding source logs and can appear unavailable when their required event subtype has never been recorded in the ADOM. The present case instead requires: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. The technical reason is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. Confirm by: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. The fictional case is: A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment.
Question 287
A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment. The reviewed recommendation is: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. What FortiAnalyzer mechanism supports the recommended analysis?
Answer & Explanations
Correct answer: 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: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. Apply it by: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. The fictional case is: A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment.
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: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. Apply it by: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. It explains why the intervention—apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events—addresses the stated problem. Test the mechanism by: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. The fictional case is: A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment.
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: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. Apply it by: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events.
Question 288
A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment. The reviewed recommendation is: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. What pilot verification directly establishes the intended result?
Answer & Explanations
Correct answer: D
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: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
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: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
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: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. This directly tests whether the chosen intervention works: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. The causal mechanism is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. The fictional case is: A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment.
Question 289
A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment. Which tempting SOC change would undermine the stated requirement?
Answer & Explanations
Correct answer: A
Block the top byte-count source from the widget without checking its destination or authorized business process. The risk is: Legitimate scheduled data transfer is interrupted while actual malicious low-volume flows may be overlooked. The safer action is: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Confirm by: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. The fictional case is: A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment.
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: Block the top byte-count source from the widget without checking its destination or authorized business process. Its risk is: Legitimate scheduled data transfer is interrupted while actual malicious low-volume flows may be overlooked.
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: Block the top byte-count source from the widget without checking its destination or authorized business process. Its risk is: Legitimate scheduled data transfer is interrupted while actual malicious low-volume flows may be overlooked.
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: Block the top byte-count source from the widget without checking its destination or authorized business process. Its risk is: Legitimate scheduled data transfer is interrupted while actual malicious low-volume flows may be overlooked.
Question 290
A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment. Which combined analytic action and validation test best solve this case?
Answer & Explanations
Correct answer: C
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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Test with: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
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. This action-and-test pairing concerns another situation: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. The current case needs this action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Test with: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Check the result: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. The technical reason is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. The fictional case is: A retailer sees one headquarters address top the FortiView bandwidth widget and needs to identify the real application before containment.
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: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Test with: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst (FCP_FAZ_AN-7.6) Practice Tests
- Fortinet FCP_FAZ_AN-7.6 Practice Test 27 - 10 Questions (Last Reviewed 25-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 28 - 10 Questions (Last Reviewed 24-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 29 - 10 Questions (Last Reviewed 23-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 30 - 10 Questions (Last Reviewed 22-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 31 - 10 Questions (Last Reviewed 21-Oct-2026)