Fortinet FCP_FAZ_AN-7.6 Practice Test 14 - Prepaway
Practice Exams:

Pass Fortinet FCP_FAZ_AN-7.6 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

FCP_FAZ_AN-7.6 Premium ETE File


  • Premium File 63 Questions & Answers. Last Update: Nov 12, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FAZ_AN-7.6 Practice Test 14

Question 130

A SOC response plan for pump telemetry security detections and management logs at a wastewater treatment utility must include both a justified correction and measurable proof. Incident: A newly enabled threat-response playbook runs for every incident, including harmless configuration and maintenance warnings. Evidence: The incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. Which combined action-and-verification pair best fits this case?

  1. Action: Validate indicator types and permitted remediation scope before using trigger/output values in any connector action, and log refusal reasons. Proof: A legitimate test indicator is processed while reserved-management or malformed values are rejected without changing devices. Perform both using approved pump telemetry security detections and management logs test cases.
  2. Action: Add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior. Proof: Approved high-risk incidents trigger the automation once while benign maintenance cases remain unmodified. Perform both using approved pump telemetry security detections and management logs test cases.
  3. Action: Configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Proof: A controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. Perform both using approved pump telemetry security detections and management logs test cases.
  4. Action: Narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. Proof: Only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts. Perform both using approved pump telemetry security detections and management logs test cases.

Explanation

Correct Answer

B:

The needed change is to add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior. A controlled check should show that approved high-risk incidents trigger the automation once while benign maintenance cases remain unmodified. Perform both using approved pump telemetry security detections and management logs test cases. In this case, the incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. A default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation.

Incorrect Answers

A:

The appropriate repair is to validate indicator types and permitted remediation scope before using trigger/output values in any connector action, and log refusal reasons. The acceptance test should confirm that a legitimate test indicator is processed while reserved-management or malformed values are rejected without changing devices. Perform both using approved pump telemetry security detections and management logs test cases. Automation variables carry source data, not implicit trust; unsafe input handling can turn a detection into an unauthorized response. The diagnostic evidence here is the incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. The correction is to add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior. Validation should establish that approved high-risk incidents trigger the automation once while benign maintenance cases remain unmodified.

C:

The preferred remedy is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. The outcome can be verified by confirming that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. Perform both using approved pump telemetry security detections and management logs test cases. Playbook triggers govern execution initiation independently of which tasks the playbook contains. The diagnostic evidence here is the incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. The appropriate repair is to add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior. The acceptance test should confirm that approved high-risk incidents trigger the automation once while benign maintenance cases remain unmodified.

D:

To resolve the observed issue, narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. Validation should establish that only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts. Perform both using approved pump telemetry security detections and management logs test cases. Basic event handler rule matching differs from correlation sequence logic; rule composition controls alert specificity. The diagnostic evidence here is the incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. The needed change is to add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior. A controlled check should show that approved high-risk incidents trigger the automation once while benign maintenance cases remain unmodified.

Question 131

The security team at a regional hospital network proposes this controlled action for outpatient booking logs and perimeter threat alerts: Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. The original condition was: A branch FortiGate sends no telemetry to its newly deployed FortiAnalyzer although local security events continue to occur. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. Controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  2. A test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  3. A controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  4. Each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records. Validate with representative outpatient booking logs and perimeter threat alerts traffic.

Explanation

Correct Answer

B:

A test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. In this case, FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The corresponding correction is to configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport.

Incorrect Answers

A:

Controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. The diagnostic evidence here is FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The required outcome is that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector.

C:

A controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. The diagnostic evidence here is FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The required outcome is that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector.

D:

Each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records. FortiAnalyzer ADOM scoping controls device and log context; working collection does not guarantee correct tenancy or isolation. The diagnostic evidence here is FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The required outcome is that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector.

Question 132

During an investigation of point-of-sale cyber alerts and stock gateway logs at a neighborhood grocery cooperative, business exceptions need validated reporting and ownership. The reported failure is: An account-takeover detection should alert when repeated login failures are followed by success, but no event appears for a controlled attack simulation. The analyst confirms: The correlation rule sequence places success before failures and the evaluation window never matches the observed order. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Repair the handler's notification profile, transport credentials and escalation mapping, then test an alert end to end. Scope the action to the affected point-of-sale cyber alerts and stock gateway logs environment.
  2. Define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. Scope the action to the affected point-of-sale cyber alerts and stock gateway logs environment.
  3. Group qualifying authentication attempts by the relevant source or user dimensions and validate threshold scope. Scope the action to the affected point-of-sale cyber alerts and stock gateway logs environment.
  4. Add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. Scope the action to the affected point-of-sale cyber alerts and stock gateway logs environment.

Explanation

Correct Answer

B:

Define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. Scope the action to the affected point-of-sale cyber alerts and stock gateway logs environment. Stateful event correlation depends on temporal ordering and shared identifiers, not just the presence of the same log types. The needed change is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. Verify that test failures followed by success raise one correlated event and reversed benign order does not.

Incorrect Answers

A:

Repair the handler's notification profile, transport credentials and escalation mapping, then test an alert end to end. Scope the action to the affected point-of-sale cyber alerts and stock gateway logs environment. Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. The diagnostic evidence here is the correlation rule sequence places success before failures and the evaluation window never matches the observed order. The appropriate repair is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields.

C:

Group qualifying authentication attempts by the relevant source or user dimensions and validate threshold scope. Scope the action to the affected point-of-sale cyber alerts and stock gateway logs environment. Event-handler grouping keys determine whether a count describes one suspect behavior or unrelated population activity. The diagnostic evidence here is the correlation rule sequence places success before failures and the evaluation window never matches the observed order. The preferred remedy is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields.

D:

Add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. Scope the action to the affected point-of-sale cyber alerts and stock gateway logs environment. Event occurrence frequency does not imply repeated state-changing actions are necessary or safe. The diagnostic evidence here is the correlation rule sequence places success before failures and the evaluation window never matches the observed order. To resolve the observed issue, define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields.

Question 133

The security team at a rural broadband provider proposes this controlled action for subscriber abuse alerts and customer-edge firewall logs: Add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. The original condition was: An event fires five times in one minute and automation repeatedly attempts the same endpoint quarantine with resulting alert storms. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. A controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value. Validate with representative subscriber abuse alerts and customer-edge firewall logs traffic.
  2. An on-demand test refuses missing inputs, while the incident-started test uses the intended case fields. Validate with representative subscriber abuse alerts and customer-edge firewall logs traffic.
  3. The escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment. Validate with representative subscriber abuse alerts and customer-edge firewall logs traffic.
  4. Ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences. Validate with representative subscriber abuse alerts and customer-edge firewall logs traffic.

Explanation

Correct Answer

D:

Ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences. Event occurrence frequency does not imply repeated state-changing actions are necessary or safe. In this case, event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. The corresponding correction is to add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation.

Incorrect Answers

A:

A controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value. Threat indicators must preserve their type and canonical representation to support meaningful enrichment and correlation. The diagnostic evidence here is event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. The required outcome is that ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences.

B:

An on-demand test refuses missing inputs, while the incident-started test uses the intended case fields. Trigger-derived variables exist only when the execution context supplies them; manual execution does not invent incident metadata. The diagnostic evidence here is event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. The required outcome is that ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences.

C:

The escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment. Playbook task ordering matters to operational completeness, and downstream messages should reflect actual upstream completion. The diagnostic evidence here is event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. The required outcome is that ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences.

Question 134

A SOC response plan for barcode scanner connectivity alerts and egress gateway events at an industrial parts distributor must include both a justified correction and measurable proof. Incident: A regional FortiAnalyzer Collector receives logs but the design expects it alone to run analytics reports and SOC event correlation in the same manner as a full Analyzer. Evidence: Deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. Which combined action-and-verification pair best fits this case?

  1. Action: Calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Proof: Representative lab noise is downgraded without suppressing truly critical authentication anomalies, and escalation follows the approved priority matrix. Perform both using approved barcode scanner connectivity alerts and egress gateway events test cases.
  2. Action: Choose or customize a supported parser and map source values into appropriate normalized fields, validating representative events before production use. Proof: Two different test identities and addresses normalize into the expected searchable fields and raw originals stay available for audit. Perform both using approved barcode scanner connectivity alerts and egress gateway events test cases.
  3. Action: Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Proof: A test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. Perform both using approved barcode scanner connectivity alerts and egress gateway events test cases.
  4. Action: Establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. Proof: Sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay. Perform both using approved barcode scanner connectivity alerts and egress gateway events test cases.

Explanation

Correct Answer

D:

The appropriate repair is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. The outcome can be verified by confirming that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay. Perform both using approved barcode scanner connectivity alerts and egress gateway events test cases. In this case, deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. Collection, central processing and report generation are distinct roles in distributed FortiAnalyzer architectures.

Incorrect Answers

A:

A focused response is to calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. A suitable test should demonstrate that representative lab noise is downgraded without suppressing truly critical authentication anomalies, and escalation follows the approved priority matrix. Perform both using approved barcode scanner connectivity alerts and egress gateway events test cases. Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. The diagnostic evidence here is deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. The preferred remedy is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. The outcome can be verified by confirming that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay.

B:

The correction is to choose or customize a supported parser and map source values into appropriate normalized fields, validating representative events before production use. The acceptance test should confirm that two different test identities and addresses normalize into the expected searchable fields and raw originals stay available for audit. Perform both using approved barcode scanner connectivity alerts and egress gateway events test cases. Field normalization is a semantic mapping step between received raw logs and common analytics queries; transmission alone does not create correct fields. The diagnostic evidence here is deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. To resolve the observed issue, establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. Validation should establish that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay.

C:

The practical next step is to configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. A controlled check should show that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. Perform both using approved barcode scanner connectivity alerts and egress gateway events test cases. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. The diagnostic evidence here is deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. A focused response is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. A suitable test should demonstrate that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay.

Question 135

A security analyst at a pediatric clinic consortium is investigating an anomaly in care referral alerts and clinic firewall telemetry. The reported behavior is: A scheduled management report displays only the original four stores after a fifth FortiGate was registered correctly. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Dataset filters reference normalized srcip while the updated parser writes the relevant address into an unsupported custom field. Verify this observation against care referral alerts and clinic firewall telemetry.
  2. The event window excludes the earlier login and only includes later DNS or data-transfer entries. Verify this observation against care referral alerts and clinic firewall telemetry.
  3. The search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. Verify this observation against care referral alerts and clinic firewall telemetry.
  4. Report Settings uses an explicit device list that was never updated for the fifth device. Verify this observation against care referral alerts and clinic firewall telemetry.

Explanation

Correct Answer

D:

Report Settings uses an explicit device list that was never updated for the fifth device. Report source-device filters are independent from device registration and must track the intended scope. The practical next step is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. Verify that a control event from the fifth store appears in the next generated report and unrelated tenants remain excluded.

Incorrect Answers

A:

Dataset filters reference normalized srcip while the updated parser writes the relevant address into an unsupported custom field. Report datasets depend on consistent field schema between ingestion normalization and the query definition. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. To resolve the observed issue, reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries.

B:

The event window excludes the earlier login and only includes later DNS or data-transfer entries. Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. A focused response is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries.

C:

The search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. The correction is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries.

Question 136

A security analyst at a commercial fishing cooperative is investigating an anomaly in cold-store cyber alerts and billing gateway events. The reported behavior is: An outsourced SOC analyst assigned to customer A can open security views for customer B after a role migration. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. Verify this observation against cold-store cyber alerts and billing gateway events.
  2. Source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. Verify this observation against cold-store cyber alerts and billing gateway events.
  3. FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. Verify this observation against cold-store cyber alerts and billing gateway events.
  4. The user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. Verify this observation against cold-store cyber alerts and billing gateway events.

Explanation

Correct Answer

D:

The user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. SOC features inherit administrative and ADOM authorization boundaries; visibility settings alone are not isolation controls. The appropriate repair is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests. Verify that the user can analyze customer A events but cannot access customer B dashboards, incidents or report data through alternative views.

Incorrect Answers

A:

Serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. Security Fabric analytics depend on consistent device identities and membership, not simply identical display names. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. A focused response is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.

B:

Source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. The correction is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.

C:

FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. The practical next step is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.

Question 137

A security analyst at a community health insurer is investigating an anomaly in claims portal access anomalies and web security logs. The reported behavior is: A top-applications view suggests a branch has no unknown applications after a policy change, but users report unclassified SaaS traffic. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Application-control logs are absent for the relevant policy or the widget excludes unknown application categories. Verify this observation against claims portal access anomalies and web security logs.
  2. Related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. Verify this observation against claims portal access anomalies and web security logs.
  3. Report Settings uses an explicit device list that was never updated for the fifth device. Verify this observation against claims portal access anomalies and web security logs.
  4. The view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. Verify this observation against claims portal access anomalies and web security logs.

Explanation

Correct Answer

A:

Application-control logs are absent for the relevant policy or the widget excludes unknown application categories. Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. The correction is to check application-control logging prerequisites and include unclassified categories in a scoped dashboard query. Verify that an authorized synthetic unclassified flow is visible as such and the known-application totals continue to reconcile to log records.

Incorrect Answers

B:

Related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. The diagnostic evidence here is application-control logs are absent for the relevant policy or the widget excludes unknown application categories. The practical next step is to check application-control logging prerequisites and include unclassified categories in a scoped dashboard query.

C:

Report Settings uses an explicit device list that was never updated for the fifth device. Report source-device filters are independent from device registration and must track the intended scope. The diagnostic evidence here is application-control logs are absent for the relevant policy or the widget excludes unknown application categories. The appropriate repair is to check application-control logging prerequisites and include unclassified categories in a scoped dashboard query.

D:

The view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. The diagnostic evidence here is application-control logs are absent for the relevant policy or the widget excludes unknown application categories. The needed change is to check application-control logging prerequisites and include unclassified categories in a scoped dashboard query.

Question 138

During a FortiAnalyzer 7.6 design review covering nonemergency dispatch audit events and perimeter alerts at a regional emergency response center, the incident is: Analysts cannot reconstruct last month's malware spread despite new events arriving normally in the correct ADOM. Key diagnostic evidence: Device/ADOM analytics retention and rolling policies have removed the older logs before the investigation's mandated retention period. Which underlying security-analytics or reporting principle explains the behavior?

  1. FortiAnalyzer ADOM scoping controls device and log context; working collection does not guarantee correct tenancy or isolation. Apply this reasoning to nonemergency dispatch audit events and perimeter alerts.
  2. Field normalization is a semantic mapping step between received raw logs and common analytics queries; transmission alone does not create correct fields. Apply this reasoning to nonemergency dispatch audit events and perimeter alerts.
  3. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. Apply this reasoning to nonemergency dispatch audit events and perimeter alerts.
  4. Analyzable history is constrained by log aging policies and storage allocation, not just whether the current logging connection is healthy. Apply this reasoning to nonemergency dispatch audit events and perimeter alerts.

Explanation

Correct Answer

D:

Analyzable history is constrained by log aging policies and storage allocation, not just whether the current logging connection is healthy. In this case, device/ADOM analytics retention and rolling policies have removed the older logs before the investigation's mandated retention period. The preferred remedy is to align storage quota, Analytics versus Archive retention and external backup with the approved evidence period, monitoring projected growth. Verify that a time-window retention test preserves required historical events and disk usage stays within policy under projected daily volume.

Incorrect Answers

A:

FortiAnalyzer ADOM scoping controls device and log context; working collection does not guarantee correct tenancy or isolation. The diagnostic evidence here is device/ADOM analytics retention and rolling policies have removed the older logs before the investigation's mandated retention period. The controlling principle here is that analyzable history is constrained by log aging policies and storage allocation, not just whether the current logging connection is healthy.

B:

Field normalization is a semantic mapping step between received raw logs and common analytics queries; transmission alone does not create correct fields. The diagnostic evidence here is device/ADOM analytics retention and rolling policies have removed the older logs before the investigation's mandated retention period. The controlling principle here is that analyzable history is constrained by log aging policies and storage allocation, not just whether the current logging connection is healthy.

C:

The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. The diagnostic evidence here is device/ADOM analytics retention and rolling policies have removed the older logs before the investigation's mandated retention period. The controlling principle here is that analyzable history is constrained by log aging policies and storage allocation, not just whether the current logging connection is healthy.

Question 139

A security analyst at a rural broadband provider is investigating an anomaly in subscriber abuse alerts and customer-edge firewall logs. The reported behavior is: Critical URL blocks from one branch never trigger a configured security handler used successfully at headquarters. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Playbook Monitor details show the initial task Success and a subsequent task Failed rather than an all-or-nothing transaction. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  2. The handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  3. Notification profile still references a retired email webhook or destination without delivery confirmation. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  4. The correlation rule sequence places success before failures and the evaluation window never matches the observed order. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.

Explanation

Correct Answer

B:

The handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. Event-handler data selectors define source scope separately from the underlying rule expression. The needed change is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. Verify that branch and headquarters controls trigger their expected events, and a third-party tenant's logs never match.

Incorrect Answers

A:

Playbook Monitor details show the initial task Success and a subsequent task Failed rather than an all-or-nothing transaction. Overall playbook job failure does not imply every prior action rolled back; task-level results determine safe recovery. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. The appropriate repair is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions.

C:

Notification profile still references a retired email webhook or destination without delivery confirmation. Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. The preferred remedy is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions.

D:

The correlation rule sequence places success before failures and the evaluation window never matches the observed order. Stateful event correlation depends on temporal ordering and shared identifiers, not just the presence of the same log types. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. To resolve the observed issue, extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions.

Question 140

During a FortiAnalyzer 7.6 design review covering checkout firewall alerts and replenishment system logs at a high-street retail chain, the incident is: A newly enabled threat-response playbook runs for every incident, including harmless configuration and maintenance warnings. Key diagnostic evidence: The incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. Which underlying security-analytics or reporting principle explains the behavior?

  1. Trigger-derived variables exist only when the execution context supplies them; manual execution does not invent incident metadata. Apply this reasoning to checkout firewall alerts and replenishment system logs.
  2. Upstream device reachability and local task configuration are separate causes of automation failure. Apply this reasoning to checkout firewall alerts and replenishment system logs.
  3. A default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation. Apply this reasoning to checkout firewall alerts and replenishment system logs.
  4. Event-handler grouping keys determine whether a count describes one suspect behavior or unrelated population activity. Apply this reasoning to checkout firewall alerts and replenishment system logs.

Explanation

Correct Answer

C:

A default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation. In this case, the incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. To resolve the observed issue, add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior. Verify that approved high-risk incidents trigger the automation once while benign maintenance cases remain unmodified.

Incorrect Answers

A:

Trigger-derived variables exist only when the execution context supplies them; manual execution does not invent incident metadata. The diagnostic evidence here is the incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. The controlling principle here is that a default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation.

B:

Upstream device reachability and local task configuration are separate causes of automation failure. The diagnostic evidence here is the incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. The controlling principle here is that a default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation.

D:

Event-handler grouping keys determine whether a count describes one suspect behavior or unrelated population activity. The diagnostic evidence here is the incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. The controlling principle here is that a default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation.

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