Fortinet FCP_FAZ_AN-7.6 Dumps
Fortinet FCP_FAZ_AN-7.6 Practice Test 27
Question 260
A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset. Which combined analytic action and validation test best solve this case?
Answer & Explanations
Correct answer: C
Choose this FortiAnalyzer analyst action: Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. Validate using: Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs. This action-and-test pairing concerns another situation: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. The current case needs this action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.
Choose this FortiAnalyzer analyst action: Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. Validate using: Drill down into two test sessions and verify the top destination matches the original destination address and intended connection direction. This action-and-test pairing concerns another situation: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. The current case needs this action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.
Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Check the result: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. The technical reason is: Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.
Choose this FortiAnalyzer analyst action: Compare session identifiers, device identity, source and destination context, event type, and event timestamps before deciding case scope. Validate using: Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections. This action-and-test pairing concerns another situation: A retailer sees both traffic and IPS logs for one payment network flow and needs a consolidated view of the same session. The current case needs this action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Test with: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. The fictional case is: A university SOC reviews an endpoint vulnerability linked to an incident and wants confirmation it belongs to the same asset.
Question 261
A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. Which FortiAnalyzer analyst action best addresses the stated operational requirement?
Answer & Explanations
Correct answer: A
Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. The technical reason is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. Confirm by: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
Question 262
A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. The reviewed recommendation is: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Which technical principle explains why the proposed FortiAnalyzer action works?
Answer & Explanations
Correct answer: B
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: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. Apply it by: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. It explains why the intervention—create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes—addresses the stated problem. Test the mechanism by: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
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: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. Apply it by: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
A malware or intrusion detection finding does not independently prove whether FortiOS forwarded, blocked, reset, or quarantined an associated flow. That principle explains a different situation: A retail security team finds a high-severity IPS log from a checkout segment and needs evidence that the matching connection was truly dropped. Here the relevant cause is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. Apply it by: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
Question 263
A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. The reviewed recommendation is: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Which observation best demonstrates that this corrective step worked?
Answer & Explanations
Correct answer: A
Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. This directly tests whether the chosen intervention works: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. The causal mechanism is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure.
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: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
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: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
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: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
Question 264
A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. Which unsafe investigation or automation shortcut must be rejected?
Answer & Explanations
Correct answer: A
Close an automatically generated event and declare all related incident triage work finished without case ownership or review. The risk is: A real attack remains uninvestigated because team members assume someone else handled the raw detection. The safer action is: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Confirm by: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
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: Close an automatically generated event and declare all related incident triage work finished without case ownership or review. Its risk is: A real attack remains uninvestigated because team members assume someone else handled the raw detection.
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: Close an automatically generated event and declare all related incident triage work finished without case ownership or review. Its risk is: A real attack remains uninvestigated because team members assume someone else handled the raw detection.
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: Close an automatically generated event and declare all related incident triage work finished without case ownership or review. Its risk is: A real attack remains uninvestigated because team members assume someone else handled the raw detection.
Question 265
A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. Which FortiAnalyzer action and acceptance test are correctly paired?
Answer & Explanations
Correct answer: 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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Check the result: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. The technical reason is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure.
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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
Choose this FortiAnalyzer analyst action: Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. Validate using: Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. This action-and-test pairing concerns another situation: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. The current case needs this action: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
Question 266
A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps. What is the most defensible FortiAnalyzer action in this situation?
Answer & Explanations
Correct answer: C
Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. That action is relevant to a different problem: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. Its technical basis is: Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly. The present case instead requires: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. The technical reason is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. Confirm by: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.
Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. That action is relevant to a different problem: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Its technical basis is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. The present case instead requires: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
Question 267
A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps. The reviewed recommendation is: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. What FortiAnalyzer mechanism supports the recommended analysis?
Answer & Explanations
Correct answer: D
Time-bound logs from multiple systems must be normalized or interpreted with clock offset and ingest delay so the attack order is not inferred incorrectly. That principle explains a different situation: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. Here the relevant cause is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. Apply it by: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
Endpoint context can link network alerts to observed process identity and software state but those fields require eligible device integration and evidence. That principle explains a different situation: A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. Here the relevant cause is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. Apply it by: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
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: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. Apply it by: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. It explains why the intervention—create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes—addresses the stated problem. Test the mechanism by: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.
Question 268
A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps. The reviewed recommendation is: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. What pilot verification directly establishes the intended result?
Answer & Explanations
Correct answer: D
Use the same approved seven-day interval and device filter in both analyses and compare a known test traffic sample. That test is for another requirement: A hospital team compares the last fifteen minutes in FortiView to an entire month of scheduled firewall traffic reporting. It does not verify the stated outcome; the relevant check is: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
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: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time. That test is for another requirement: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. It does not verify the stated outcome; the relevant check is: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. This directly tests whether the chosen intervention works: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. The causal mechanism is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.
Question 269
A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps. Which tempting SOC change would undermine the stated requirement?
Answer & Explanations
Correct answer: D
Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. That is an appropriate action for the separate case: A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. It is not the unsafe shortcut asked about here. Reject: Close an automatically generated event and declare all related incident triage work finished without case ownership or review. Its risk is: A real attack remains uninvestigated because team members assume someone else handled the raw detection.
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: Close an automatically generated event and declare all related incident triage work finished without case ownership or review. Its risk is: A real attack remains uninvestigated because team members assume someone else handled the raw detection.
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: Close an automatically generated event and declare all related incident triage work finished without case ownership or review. Its risk is: A real attack remains uninvestigated because team members assume someone else handled the raw detection. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.
Close an automatically generated event and declare all related incident triage work finished without case ownership or review. The risk is: A real attack remains uninvestigated because team members assume someone else handled the raw detection. The safer action is: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Confirm by: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.
Question 270
A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps. Which combined analytic action and validation test best solve this case?
Answer & Explanations
Correct answer: B
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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Check the result: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. The technical reason is: Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.
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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved. The fictional case is: A hospital security team sees event-handler output but lacks an incident record describing assessment and next steps.
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: Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes. Test with: Follow a harmless test alert from detection to incident assignment and verify its evidence and status history are preserved.
Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst (FCP_FAZ_AN-7.6) Practice Tests
- Fortinet FCP_FAZ_AN-7.6 Practice Test 25 - 10 Questions (Last Reviewed 27-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 26 - 10 Questions (Last Reviewed 26-Oct-2026)
- 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)