Fortinet FCP_FAZ_AN-7.6 Practice Test 2 - 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 2

Question 10

During a FortiAnalyzer 7.6 design review covering inspection platform threats and production network logs at a manufacturing quality laboratory, the incident is: During a pivot from FortiView to detailed logs, the analyst concludes a threat disappeared because the default log window differs from the dashboard. Key diagnostic evidence: The view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. Which underlying security-analytics or reporting principle explains the behavior?

  1. Security-event frequency and affected-asset cardinality are different measurements with different incident implications. Apply this reasoning to inspection platform threats and production network logs.
  2. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. Apply this reasoning to inspection platform threats and production network logs.
  3. Source IP is a temporary network identifier; defensible historical attribution needs time-specific supporting evidence. Apply this reasoning to inspection platform threats and production network logs.
  4. Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. Apply this reasoning to inspection platform threats and production network logs.

Explanation

Correct Answer

B:

A graphical summary and underlying records must share the same dimensions before differences can be interpreted. In this case, the view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. The correction is to reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View. Verify that pivoted raw events match the original widget's source set and timeframe, with any residual gaps documented.

Incorrect Answers

A:

The diagnostic evidence here is the view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. The controlling principle here is that a graphical summary and underlying records must share the same dimensions before differences can be interpreted.

C:

Source IP is a temporary network identifier; defensible historical attribution needs time-specific supporting evidence. The diagnostic evidence here is the view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. The controlling principle here is that a graphical summary and underlying records must share the same dimensions before differences can be interpreted.

D:

Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. The diagnostic evidence here is the view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. The controlling principle here is that a graphical summary and underlying records must share the same dimensions before differences can be interpreted.

Question 11

During a FortiAnalyzer 7.6 design review covering public event portal traffic and staff system alerts at a city parks administration, the incident is: A benign lab scan produces many critical incident notifications while privileged-access anomalies affecting production servers remain low priority. Key diagnostic evidence: Event-handler severity defaults and incident prioritization rules are disconnected from protected asset context and analyst response criteria. Which underlying security-analytics or reporting principle explains the behavior?

  1. A detection mapping describes capability or intent and cannot by itself prove that required telemetry and working rules exist. Apply this reasoning to public event portal traffic and staff system alerts.
  2. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. Apply this reasoning to public event portal traffic and staff system alerts.
  3. Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. Apply this reasoning to public event portal traffic and staff system alerts.
  4. 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 public event portal traffic and staff system alerts.

Explanation

Correct Answer

C:

Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. In this case, event-handler severity defaults and incident prioritization rules are disconnected from protected asset context and analyst response criteria. The appropriate repair is to calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Verify that representative lab noise is downgraded without suppressing truly critical authentication anomalies, and escalation follows the approved priority matrix.

Incorrect Answers

A:

A detection mapping describes capability or intent and cannot by itself prove that required telemetry and working rules exist. The diagnostic evidence here is event-handler severity defaults and incident prioritization rules are disconnected from protected asset context and analyst response criteria. The controlling principle here is that security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact.

B:

Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. The diagnostic evidence here is event-handler severity defaults and incident prioritization rules are disconnected from protected asset context and analyst response criteria. The controlling principle here is that security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact.

D:

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 event-handler severity defaults and incident prioritization rules are disconnected from protected asset context and analyst response criteria. The controlling principle here is that security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact.

Question 12

The security team at an industrial parts distributor proposes this controlled action for barcode scanner connectivity alerts and egress gateway events: Add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. The original condition was: A custom weekly report claims one account accessed all suspicious destinations, but the workstation address was reassigned between users. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. Synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim. Validate with representative barcode scanner connectivity alerts and egress gateway events traffic.
  2. Macros and charts reconcile under a controlled per-tenant sample without leaking another customer's aggregate values. Validate with representative barcode scanner connectivity alerts and egress gateway events traffic.
  3. A controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. Validate with representative barcode scanner connectivity alerts and egress gateway events traffic.
  4. A low-volume but high-severity test source appears in the dedicated exception section even though it remains outside top-ten volume. Validate with representative barcode scanner connectivity alerts and egress gateway events traffic.

Explanation

Correct Answer

A:

Synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim. Report aggregation keys define the claim's granularity; an IP address does not guarantee a stable user identity. In this case, dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The corresponding correction is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution.

Incorrect Answers

B:

Macros and charts reconcile under a controlled per-tenant sample without leaking another customer's aggregate values. Macros are dataset-backed computations and must receive the same scoping assumptions as other report elements. The diagnostic evidence here is dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The required outcome is that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim.

C:

A controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. Report charts display the results of selected datasets; a valid chart definition cannot compensate for a query against the wrong log family. The diagnostic evidence here is dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The required outcome is that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim.

D:

A low-volume but high-severity test source appears in the dedicated exception section even though it remains outside top-ten volume. Rankings are summaries, not exhaustive evidence; a low-frequency critical signal can sit below a volume cutoff. The diagnostic evidence here is dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The required outcome is that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim.

Question 13

During a FortiAnalyzer 7.6 design review covering claims portal access anomalies and web security logs at a community health insurer, the incident is: An incident timeline places a branch firewall's authentication event several hours after its correlated IPS block although the actions happened together. Key diagnostic evidence: Source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. Which underlying security-analytics or reporting principle explains the behavior?

  1. Log-source classification must match the producing application's schema before common SOC fields can be trusted. Apply this reasoning to claims portal access anomalies and web security logs.
  2. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. Apply this reasoning to claims portal access anomalies and web security logs.
  3. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. Apply this reasoning to claims portal access anomalies and web security logs.
  4. Archival retention and analytics database availability have different uses; event handlers and reports require appropriate processed analytics data. Apply this reasoning to claims portal access anomalies and web security logs.

Explanation

Correct Answer

C:

Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. In this case, source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The preferred remedy is to verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline. Verify that controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite.

Incorrect Answers

A:

Log-source classification must match the producing application's schema before common SOC fields can be trusted. The diagnostic evidence here is source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The controlling principle here is that reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation.

B:

Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The controlling principle here is that reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation.

D:

Archival retention and analytics database availability have different uses; event handlers and reports require appropriate processed analytics data. The diagnostic evidence here is source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The controlling principle here is that reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation.

Question 14

During a FortiAnalyzer 7.6 design review covering resident portal events and privileged-access logs at a public housing services agency, the incident is: A custom security dashboard shows no source-IP activity even though raw logs from the affected sites are searchable. Key diagnostic evidence: Widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. Which underlying security-analytics or reporting principle explains the behavior?

  1. Administrative incident status is not technical evidence that the underlying threat has stopped across the environment. Apply this reasoning to resident portal events and privileged-access logs.
  2. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. Apply this reasoning to resident portal events and privileged-access logs.
  3. Report scheduling window boundaries and display-time conversion influence which events enter a report. Apply this reasoning to resident portal events and privileged-access logs.
  4. Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. Apply this reasoning to resident portal events and privileged-access logs.

Explanation

Correct Answer

B:

Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. In this case, widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. A controlled check should show that the test device's events appear in both its Log View query and the aligned widget for the same time period.

Incorrect Answers

A:

Administrative incident status is not technical evidence that the underlying threat has stopped across the environment. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The targeted correction is to update the widget's authorized device/log group selection and verify filter semantics against source logs.

C:

Report scheduling window boundaries and display-time conversion influence which events enter a report. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The targeted correction is to update the widget's authorized device/log group selection and verify filter semantics against source logs.

D:

Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The targeted correction is to update the widget's authorized device/log group selection and verify filter semantics against source logs.

Question 15

The security team at an online education platform proposes this controlled action for assessment portal access records and web security alerts: Bind the chart to a compatible supported dataset and validate log type, field mappings and sample aggregates. The original condition was: An executive top-threat chart returns no values although FortiAnalyzer has current antivirus events. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. A controlled scheduled run creates a report and sends it only to the designated recipient group. Validate with representative assessment portal access records and web security alerts traffic.
  2. Events at the start and end of the intended period appear exactly once and date-range labels match the actual query. Validate with representative assessment portal access records and web security alerts traffic.
  3. A controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. Validate with representative assessment portal access records and web security alerts traffic.
  4. Peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Validate with representative assessment portal access records and web security alerts traffic.

Explanation

Correct Answer

C:

A controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. Report charts display the results of selected datasets; a valid chart definition cannot compensate for a query against the wrong log family. In this case, the chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. The corresponding correction is to bind the chart to a compatible supported dataset and validate log type, field mappings and sample aggregates.

Incorrect Answers

A:

A controlled scheduled run creates a report and sends it only to the designated recipient group. Importing report content is distinct from enabling timed execution and distribution. The diagnostic evidence here is the chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. The required outcome is that a controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs.

B:

Events at the start and end of the intended period appear exactly once and date-range labels match the actual query. Calendar-period and rolling-window selectors have different semantics even when both appear weekly. The diagnostic evidence here is the chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. The required outcome is that a controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs.

D:

Peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Reporting workloads consume shared processing resources; analytics capacity planning must include peak query as well as log ingestion demand. The diagnostic evidence here is the chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. The required outcome is that a controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs.

Question 16

A SOC response plan for greenhouse sensor firewall alerts and field WAN logs at a cooperative farm network must include both a justified correction and measurable proof. Incident: An analyst enters a URL into an IP-only indicator workflow and receives no useful reputation enrichment for the suspicious destination. Evidence: The indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. Which combined action-and-verification pair best fits this case?

  1. Action: Define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. Proof: Test failures followed by success raise one correlated event and reversed benign order does not. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases.
  2. Action: Scope incident aggregation to appropriate tenant and entity context while retaining shared threat intelligence as a separate enrichment signal. Proof: Two independently staged tenant detections produce separately owned incidents and each preserves its supporting evidence. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases.
  3. Action: Normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. Proof: A controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases.
  4. Action: Map event categories to approved incident assignment and escalation rules with explicit fallback for unmapped sources. Proof: Sample incidents route to their responsible team with auditable ownership and none remain orphaned past the response time target. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases.

Explanation

Correct Answer

C:

The appropriate repair is to normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. Validation should establish that a controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases. In this case, the indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. Threat indicators must preserve their type and canonical representation to support meaningful enrichment and correlation.

Incorrect Answers

A:

The correction is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. A controlled check should show that test failures followed by success raise one correlated event and reversed benign order does not. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases. 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 indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. To resolve the observed issue, normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. A suitable test should demonstrate that a controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value.

B:

The practical next step is to scope incident aggregation to appropriate tenant and entity context while retaining shared threat intelligence as a separate enrichment signal. The outcome can be verified by confirming that two independently staged tenant detections produce separately owned incidents and each preserves its supporting evidence. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases. A shared indicator does not establish common incident ownership across isolated administrative domains. The diagnostic evidence here is the indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. A focused response is to normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. The acceptance test should confirm that a controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value.

D:

The needed change is to map event categories to approved incident assignment and escalation rules with explicit fallback for unmapped sources. A suitable test should demonstrate that sample incidents route to their responsible team with auditable ownership and none remain orphaned past the response time target. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases. An incident's existence does not guarantee triage ownership; response workflow assignment is an additional operational decision. The diagnostic evidence here is the indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. The practical next step is to normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. The outcome can be verified by confirming that a controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value.

Question 17

During an investigation of field diagnostic VPN events and remote access logs at a medical-device field service team, technician sessions must have distinct accountable identities. The reported failure is: During a pivot from FortiView to detailed logs, the analyst concludes a threat disappeared because the default log window differs from the dashboard. The analyst confirms: The view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Scope the action to the affected field diagnostic VPN events and remote access logs environment.
  2. Expand the time range based on incident chronology and join evidence by endpoint/user/device with clock-corrected timestamps. Scope the action to the affected field diagnostic VPN events and remote access logs environment.
  3. Update the widget's authorized device/log group selection and verify filter semantics against source logs. Scope the action to the affected field diagnostic VPN events and remote access logs environment.
  4. Reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View. Scope the action to the affected field diagnostic VPN events and remote access logs environment.

Explanation

Correct Answer

D:

Reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View. Scope the action to the affected field diagnostic VPN events and remote access logs environment. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. The appropriate repair is to reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View. Verify that pivoted raw events match the original widget's source set and timeframe, with any residual gaps documented.

Incorrect Answers

A:

Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Scope the action to the affected field diagnostic VPN events and remote access logs environment. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is the view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. A focused response is to reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View.

B:

Expand the time range based on incident chronology and join evidence by endpoint/user/device with clock-corrected timestamps. Scope the action to the affected field diagnostic VPN events and remote access logs environment. Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. The diagnostic evidence here is the view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. The correction is to reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View.

C:

Update the widget's authorized device/log group selection and verify filter semantics against source logs. Scope the action to the affected field diagnostic VPN events and remote access logs environment. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. The diagnostic evidence here is the view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. The practical next step is to reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View.

Question 18

The security team at a museum collections partnership proposes this controlled action for archive service audit logs and suspicious DNS events: Attach an auditable evidence extract with source reference, time, ADOM/device and hash where supported, keeping the underlying logs preserved. The original condition was: An investigator exports a list of logs to an incident but omits event IDs, time zone and source-device identity required for later review. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. A second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone. Validate with representative archive service audit logs and suspicious DNS events traffic.
  2. Only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts. Validate with representative archive service audit logs and suspicious DNS events traffic.
  3. Two independently staged tenant detections produce separately owned incidents and each preserves its supporting evidence. Validate with representative archive service audit logs and suspicious DNS events traffic.
  4. A safe test invokes only the intended approved action, while unconfigured actions stay unavailable. Validate with representative archive service audit logs and suspicious DNS events traffic.

Explanation

Correct Answer

A:

A second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone. Incident handling requires provenance and reproducible evidence, not just a narrative label attached to a case. In this case, attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. The corresponding correction is to attach an auditable evidence extract with source reference, time, ADOM/device and hash where supported, keeping the underlying logs preserved.

Incorrect Answers

B:

Only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts. Basic event handler rule matching differs from correlation sequence logic; rule composition controls alert specificity. The diagnostic evidence here is attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. The required outcome is that a second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone.

C:

Two independently staged tenant detections produce separately owned incidents and each preserves its supporting evidence. A shared indicator does not establish common incident ownership across isolated administrative domains. The diagnostic evidence here is attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. The required outcome is that a second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone.

D:

A safe test invokes only the intended approved action, while unconfigured actions stay unavailable. FortiOS connector task actions depend on compatible device-side automation rules, not solely on a connected FortiAnalyzer playbook. The diagnostic evidence here is attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. The required outcome is that a second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone.

Question 19

A security analyst at a mid-size hotel group is investigating an anomaly in reservations security alerts and guest-network logs. The reported behavior is: An investigator exports a list of logs to an incident but omits event IDs, time zone and source-device identity required for later review. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. The handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. Verify this observation against reservations security alerts and guest-network logs.
  2. Attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. Verify this observation against reservations security alerts and guest-network logs.
  3. The attachment step references a hard-coded output from a task ID that changed during import, while the actual report task completed. Verify this observation against reservations security alerts and guest-network logs.
  4. The playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. Verify this observation against reservations security alerts and guest-network logs.

Explanation

Correct Answer

B:

Attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. Incident handling requires provenance and reproducible evidence, not just a narrative label attached to a case. The appropriate repair is to attach an auditable evidence extract with source reference, time, ADOM/device and hash where supported, keeping the underlying logs preserved. Verify that a second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone.

Incorrect Answers

A:

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 diagnostic evidence here is attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. The practical next step is to attach an auditable evidence extract with source reference, time, ADOM/device and hash where supported, keeping the underlying logs preserved.

C:

The attachment step references a hard-coded output from a task ID that changed during import, while the actual report task completed. Task output variables must match the playbook's real dependency graph and task identities after export/import changes. The diagnostic evidence here is attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. The needed change is to attach an auditable evidence extract with source reference, time, ADOM/device and hash where supported, keeping the underlying logs preserved.

D:

The playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. Playbook triggers govern execution initiation independently of which tasks the playbook contains. The diagnostic evidence here is attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. The preferred remedy is to attach an auditable evidence extract with source reference, time, ADOM/device and hash where supported, keeping the underlying logs preserved.

Question 20

During a FortiAnalyzer 7.6 design review covering field diagnostic VPN events and remote access logs at a medical-device field service team, the incident is: A security analyst builds an automated incident enrichment playbook but it never runs when new incidents are raised. Key diagnostic evidence: The playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. 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 field diagnostic VPN events and remote access logs.
  2. Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. Apply this reasoning to field diagnostic VPN events and remote access logs.
  3. Playbook triggers govern execution initiation independently of which tasks the playbook contains. Apply this reasoning to field diagnostic VPN events and remote access logs.
  4. Automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants. Apply this reasoning to field diagnostic VPN events and remote access logs.

Explanation

Correct Answer

C:

Playbook triggers govern execution initiation independently of which tasks the playbook contains. In this case, the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The preferred remedy is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Verify that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it.

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 playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The controlling principle here is that playbook triggers govern execution initiation independently of which tasks the playbook contains.

B:

Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. The diagnostic evidence here is the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The controlling principle here is that playbook triggers govern execution initiation independently of which tasks the playbook contains.

D:

Automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants. The diagnostic evidence here is the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The controlling principle here is that playbook triggers govern execution initiation independently of which tasks the playbook contains.

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