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 21

Question 200

A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Validate using: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot.
  2. Choose this FortiAnalyzer analyst action: Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. Validate using: Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member.
  3. Choose this FortiAnalyzer analyst action: Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Validate using: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay.
  4. Choose this FortiAnalyzer analyst action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Validate using: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

Answer & Explanations

Correct answer: D

A.

Choose this FortiAnalyzer analyst action: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Validate using: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. This action-and-test pairing concerns another situation: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. The current case needs this action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

B.

Choose this FortiAnalyzer analyst action: Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. Validate using: Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member. This action-and-test pairing concerns another situation: A multinational retailer puts regional FortiAnalyzers under a central Fabric supervisor and needs accurate log custody boundaries. The current case needs this action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

C.

Choose this FortiAnalyzer analyst action: Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Validate using: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay. This action-and-test pairing concerns another situation: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. The current case needs this action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Test with: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance.

D.

Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Check the result: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. The technical reason is: FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. The fictional case is: A university SOC investigates a FortiSandbox detection and wants to link it to a related firewall connection in the same Fabric ADOM.

Question 201

A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. 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. Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.
  3. Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.
  4. Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

Answer & Explanations

Correct answer: D

A.

Verify that the required FortiOS UUID or object logging is enabled and available before filtering FortiView by object name. That action is relevant to a different problem: A university team wants FortiView results by address object name but its FortiGate has never sent object UUID fields. Its technical basis is: Object-level traffic filtering depends on the relevant object identifiers being included in collected logs and cannot reconstruct missing historic fields. The present case instead requires: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

B.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. That action is relevant to a different problem: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Its technical basis is: IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. The present case instead requires: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

C.

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: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

D.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. The technical reason is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. Confirm by: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

Question 202

A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. The reviewed recommendation is: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Which technical principle explains why the proposed FortiAnalyzer action works?

  1. Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window.
  2. 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.
  3. Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure.
  4. Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo.

Answer & Explanations

Correct answer: D

A.

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: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. Apply it by: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

B.

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: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. Apply it by: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

C.

Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. That principle explains a different situation: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. Here the relevant cause is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. Apply it by: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

D.

Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. It explains why the intervention—correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope—addresses the stated problem. Test the mechanism by: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

Question 203

A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. The reviewed recommendation is: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Which observation best demonstrates that this corrective step worked?

  1. Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.
  2. Filter a test host during an approved backup interval and compare its FortiView volume trend with original application and destination logs.
  3. Review two related test logs and confirm the analysis groups the same session without merging different hosts' connections.
  4. Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter.

Answer & Explanations

Correct answer: A

A.

Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. This directly tests whether the chosen intervention works: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. The causal mechanism is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo.

B.

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 controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

C.

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 controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

D.

Compare a test source IP and port combination under AND and OR and verify only matching sessions remain in the intended narrow filter. That test is for another requirement: A regional bank searches FortiView for one payment terminal and TCP 443 but accidentally includes all HTTPS sessions in the result. It does not verify the stated outcome; the relevant check is: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

Question 204

A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. Which unsafe investigation or automation shortcut must be rejected?

  1. Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution.
  2. Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields.
  3. Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome.
  4. Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it.

Answer & Explanations

Correct answer: A

A.

Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution. The risk is: SOC triage misclassifies routine users and overlooks the coordinated actor spanning multiple account targets. The safer action is: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Confirm by: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

B.

Use the appropriate top-destinations or destinations view and inspect the direction and original source and destination fields. That is an appropriate action for the separate case: A hospital sees high traffic to an external analytics provider but misreads the FortiView source chart as that provider's address. It is not the unsafe shortcut asked about here. Reject: Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution. Its risk is: SOC triage misclassifies routine users and overlooks the coordinated actor spanning multiple account targets.

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: Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution. Its risk is: SOC triage misclassifies routine users and overlooks the coordinated actor spanning multiple account targets.

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: Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution. Its risk is: SOC triage misclassifies routine users and overlooks the coordinated actor spanning multiple account targets.

Question 205

A bank SOC detects a cluster of denied remote administrator logins and must decide whether many accounts share one originating client. Which FortiAnalyzer action and acceptance test are correctly paired?

  1. Choose this FortiAnalyzer analyst action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Validate using: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: B

A.

Choose this FortiAnalyzer analyst action: Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance. Validate using: Replay harmless correlated device events with known timestamps and verify the reconstructed timeline preserves causality. This action-and-test pairing concerns another situation: A university SOC links web-filter and DNS logs but their displayed timestamps differ after a device clock correction. The current case needs this action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Test with: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

B.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Check the result: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. The technical reason is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo.

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: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Test with: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

D.

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: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Test with: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

Question 206

A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username. What is the most defensible FortiAnalyzer action in this situation?

  1. Read the original security log subtype and action fields together with FortiGate policy context and observed session outcome.
  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. Construct an explicit conjunction or disjunction with the correct FortiView field filters and review the returned sample records.

Answer & Explanations

Correct answer: B

A.

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: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

B.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. The technical reason is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. Confirm by: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. The fictional case is: A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username.

C.

Apply FortiView time, source, destination, and application filters before drilling into associated raw traffic events. That action is relevant to a different problem: A hospital FortiView dashboard lists a storage server as the leading source at midnight during authorized imaging backups. Its technical basis is: Aggregate charts identify volume distribution but meaningful conclusions require underlying session context and a representative investigation window. The present case instead requires: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

D.

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: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

Question 207

A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username. The reviewed recommendation is: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. What FortiAnalyzer mechanism supports the recommended analysis?

  1. IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness.
  2. Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo.
  3. Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure.
  4. 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.

Answer & Explanations

Correct answer: B

A.

IOC context is useful only when the source log confirms an actual matching observables and enrichment is interpreted with confidence and freshness. That principle explains a different situation: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. Here the relevant cause is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. Apply it by: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope.

B.

Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. It explains why the intervention—correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope—addresses the stated problem. Test the mechanism by: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. The fictional case is: A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username.

C.

Event generation and incident case management are different stages requiring tracked ownership and assessment before escalation or closure. That principle explains a different situation: A bank SOC receives an unusual login event overnight and needs an analyst-owned case with traceable disposition. Here the relevant cause is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. Apply it by: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. The fictional case is: A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username.

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: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. Apply it by: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. The fictional case is: A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username.

Question 208

A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username. The reviewed recommendation is: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. What pilot verification directly establishes the intended result?

  1. Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.
  2. Inspect a controlled blocked test event and an observed allowed event to compare their exact log action and detection values.
  3. Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.
  4. Use a harmless known test domain in an incident and verify the enrichment result is attached to the same observed value and event time.

Answer & Explanations

Correct answer: C

A.

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: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

B.

Inspect a controlled blocked test event and an observed allowed event to compare their exact log action and detection values. That test is for another requirement: 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 does not verify the stated outcome; the relevant check is: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

C.

Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. This directly tests whether the chosen intervention works: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. The causal mechanism is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. The fictional case is: A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username.

D.

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: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

Question 209

A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username. Which tempting SOC change would undermine the stated requirement?

  1. Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution.
  2. Create or select the appropriate incident case and explicitly record analyst assignment, severity, status, supporting events, and investigation notes.
  3. Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence.
  4. Build an incident chronology from original device timestamps and a sufficiently scoped consistent timeline with source provenance.

Answer & Explanations

Correct answer: A

A.

Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution. The risk is: SOC triage misclassifies routine users and overlooks the coordinated actor spanning multiple account targets. The safer action is: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Confirm by: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. The fictional case is: A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username.

B.

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: Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution. Its risk is: SOC triage misclassifies routine users and overlooks the coordinated actor spanning multiple account targets.

C.

Enrich the indicator with supported threat intelligence and correlate its type, time range, and original related log evidence. That is an appropriate action for the separate case: A hospital incident contains an unfamiliar DNS domain and the analyst wants the reputation and the actual client query evidence before blocking. It is not the unsafe shortcut asked about here. Reject: Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution. Its risk is: SOC triage misclassifies routine users and overlooks the coordinated actor spanning multiple account targets.

D.

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: Escalate every isolated single password typo to a confirmed credential spray without checking source or account distribution. Its risk is: SOC triage misclassifies routine users and overlooks the coordinated actor spanning multiple account targets.

Question 210

A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username. Which combined analytic action and validation test best solve this case?

  1. Choose this FortiAnalyzer analyst action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Validate using: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.
  2. Choose this FortiAnalyzer analyst action: 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.
  3. 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.
  4. Choose this FortiAnalyzer analyst action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Validate using: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host.

Answer & Explanations

Correct answer: A

A.

Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Check the result: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames. The technical reason is: Multiple authentication failures from one source against varied accounts over a bounded period distinguish spraying from a routine single-user typo. The fictional case is: A university analyst reviews password failures across staff and student services but the current filter shows only one isolated username.

B.

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: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Test with: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

C.

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: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Test with: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

D.

Choose this FortiAnalyzer analyst action: Use supported incident endpoint context such as process, software, vulnerability, or asset evidence where the integrated data source provides it. Validate using: Attach a bounded synthetic endpoint observation and confirm the process identity is associated with the correct incident host. This action-and-test pairing concerns another situation: A hospital analyst needs process evidence behind a suspicious firewall connection but the incident initially shows only IP addresses. The current case needs this action: Correlate authentication event logs by source IP, user identity, time interval, and failure outcome in the authorized log scope. Test with: Generate a controlled sequence of failed lab logins and confirm the filtered timeline exposes the shared source and changing usernames.

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