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

Question 120

A SOC response plan for benefit portal access alerts and privileged session logs at a pension administration office must include both a justified correction and measurable proof. Incident: A reused report definition unexpectedly includes a prior customer's source-IP filter in the next customer's run. Evidence: Report Settings or cached filter values persist from the earlier customer despite selecting a different device set. Which combined action-and-verification pair best fits this case?

  1. Action: Align report macro dataset scope and chart dataset scope to the authorized tenant and time window. Proof: Macros and charts reconcile under a controlled per-tenant sample without leaking another customer's aggregate values. Perform both using approved benefit portal access alerts and privileged session logs test cases.
  2. Action: Configure appropriate per-device or segregated report definitions and output profiles with tenant-specific recipient validation. Proof: Customer A receives only its device's report and cannot recover customer B information from filenames or attachments. Perform both using approved benefit portal access alerts and privileged session logs test cases.
  3. Action: Label top-N limitations and include an explicit rare/high-severity indicator query where completeness is required. Proof: A low-volume but high-severity test source appears in the dedicated exception section even though it remains outside top-ten volume. Perform both using approved benefit portal access alerts and privileged session logs test cases.
  4. Action: Verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. Proof: Back-to-back customer A and B runs show correct segregated records and no cross-tenant source values. Perform both using approved benefit portal access alerts and privileged session logs test cases.

Explanation

Correct Answer

D:

The appropriate repair is to verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. Validation should establish that back-to-back customer A and B runs show correct segregated records and no cross-tenant source values. Perform both using approved benefit portal access alerts and privileged session logs test cases. In this case, report Settings or cached filter values persist from the earlier customer despite selecting a different device set. Report filter caching and query scope require tenant-aware validation, especially when a definition is reused.

Incorrect Answers

A:

A focused response is to align report macro dataset scope and chart dataset scope to the authorized tenant and time window. The acceptance test should confirm that macros and charts reconcile under a controlled per-tenant sample without leaking another customer's aggregate values. Perform both using approved benefit portal access alerts and privileged session logs test cases. Macros are dataset-backed computations and must receive the same scoping assumptions as other report elements. The diagnostic evidence here is report Settings or cached filter values persist from the earlier customer despite selecting a different device set. The preferred remedy is to verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. Validation should establish that back-to-back customer A and B runs show correct segregated records and no cross-tenant source values.

B:

The correction is to configure appropriate per-device or segregated report definitions and output profiles with tenant-specific recipient validation. A controlled check should show that customer A receives only its device's report and cannot recover customer B information from filenames or attachments. Perform both using approved benefit portal access alerts and privileged session logs test cases. Report type and output profile jointly control distribution, which must respect privacy and ADOM boundaries. The diagnostic evidence here is report Settings or cached filter values persist from the earlier customer despite selecting a different device set. To resolve the observed issue, verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. A suitable test should demonstrate that back-to-back customer A and B runs show correct segregated records and no cross-tenant source values.

C:

The practical next step is to label top-N limitations and include an explicit rare/high-severity indicator query where completeness is required. The outcome can be verified by confirming that a low-volume but high-severity test source appears in the dedicated exception section even though it remains outside top-ten volume. Perform both using approved benefit portal access alerts and privileged session logs test cases. Rankings are summaries, not exhaustive evidence; a low-frequency critical signal can sit below a volume cutoff. The diagnostic evidence here is report Settings or cached filter values persist from the earlier customer despite selecting a different device set. A focused response is to verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. The acceptance test should confirm that back-to-back customer A and B runs show correct segregated records and no cross-tenant source values.

Question 121

The security team at a regional hospital network proposes this controlled action for outpatient booking logs and perimeter threat alerts: Group qualifying authentication attempts by the relevant source or user dimensions and validate threshold scope. The original condition was: The SOC sees a brute-force event when many independent users each enter one wrong password on a shared VPN gateway. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. Benign software updates do not trigger but an approved critical detection emits the handler event with the expected severity. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  2. Parallel benign one-off failures remain below threshold but repeated attempts against a target account produce a single intended event. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  3. A controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  4. A second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone. Validate with representative outpatient booking logs and perimeter threat alerts traffic.

Explanation

Correct Answer

B:

Parallel benign one-off failures remain below threshold but repeated attempts against a target account produce a single intended event. Event-handler grouping keys determine whether a count describes one suspect behavior or unrelated population activity. In this case, event grouping uses only destination address and ignores the attempted account or source principal. The corresponding correction is to group qualifying authentication attempts by the relevant source or user dimensions and validate threshold scope.

Incorrect Answers

A:

Benign software updates do not trigger but an approved critical detection emits the handler event with the expected severity. Unstructured text matching may not have the same semantics as typed security-log severity attributes. The diagnostic evidence here is event grouping uses only destination address and ignores the attempted account or source principal. The required outcome is that parallel benign one-off failures remain below threshold but repeated attempts against a target account produce a single intended event.

C:

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 grouping uses only destination address and ignores the attempted account or source principal. The required outcome is that parallel benign one-off failures remain below threshold but repeated attempts against a target account produce a single intended event.

D:

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. The diagnostic evidence here is event grouping uses only destination address and ignores the attempted account or source principal. The required outcome is that parallel benign one-off failures remain below threshold but repeated attempts against a target account produce a single intended event.

Question 122

A SOC response plan for maintenance system incidents and service gateway logs at a metropolitan rail maintenance depot must include both a justified correction and measurable proof. Incident: A custom security dashboard shows no source-IP activity even though raw logs from the affected sites are searchable. Evidence: Widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. Which combined action-and-verification pair best fits this case?

  1. Action: Update the widget's authorized device/log group selection and verify filter semantics against source logs. Proof: The test device's events appear in both its Log View query and the aligned widget for the same time period. Perform both using approved maintenance system incidents and service gateway logs test cases.
  2. Action: Distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Proof: The revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic. Perform both using approved maintenance system incidents and service gateway logs test cases.
  3. Action: Inspect actual log schema and build a supported OR-aware search across relevant username fields while retaining IP/time constraints. Proof: Controlled failed and successful attempts for both identity formats return the expected ordered evidence without unrelated log flood. Perform both using approved maintenance system incidents and service gateway logs test cases.
  4. Action: Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Proof: The report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration. Perform both using approved maintenance system incidents and service gateway logs test cases.

Explanation

Correct Answer

A:

The practical next step is to update the widget's authorized device/log group selection and verify filter semantics against source logs. The outcome can be verified by confirming that the test device's events appear in both its Log View query and the aligned widget for the same time period. Perform both using approved maintenance system incidents and service gateway logs test cases. In this case, widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry.

Incorrect Answers

B:

The appropriate repair is to distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Validation should establish that the revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic. Perform both using approved maintenance system incidents and service gateway logs test cases. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The correction is to update the widget's authorized device/log group selection and verify filter semantics against source logs. 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.

C:

The needed change is to inspect actual log schema and build a supported OR-aware search across relevant username fields while retaining IP/time constraints. A suitable test should demonstrate that controlled failed and successful attempts for both identity formats return the expected ordered evidence without unrelated log flood. Perform both using approved maintenance system incidents and service gateway logs test cases. Evidence-driven log searching must account for producer-specific field names and structured filters rather than assuming one universal field. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The practical next step is to update the widget's authorized device/log group selection and verify filter semantics against source logs. The outcome can be verified by confirming that the test device's events appear in both its Log View query and the aligned widget for the same time period.

D:

The preferred remedy is to treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. The acceptance test should confirm that the report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration. Perform both using approved maintenance system incidents and service gateway logs test cases. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The appropriate repair is to update the widget's authorized device/log group selection and verify filter semantics against source logs. Validation should establish that the test device's events appear in both its Log View query and the aligned widget for the same time period.

Question 123

During a FortiAnalyzer 7.6 design review covering supplier EDI gateway logs and plant incident telemetry at an agricultural equipment manufacturer, 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. SOC features inherit administrative and ADOM authorization boundaries; visibility settings alone are not isolation controls. Apply this reasoning to supplier EDI gateway logs and plant incident telemetry.
  2. Correct source and virtual-domain attribution is necessary for trustworthy SOC conclusions in multi-tenant Fabric deployments. Apply this reasoning to supplier EDI gateway logs and plant incident telemetry.
  3. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. Apply this reasoning to supplier EDI gateway logs and plant incident telemetry.
  4. Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. Apply this reasoning to supplier EDI gateway logs and plant incident telemetry.

Explanation

Correct Answer

D:

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 needed change 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. The question describes: During a FortiAnalyzer 7.6 design review covering supplier EDI gateway logs and plant incident telemetry at an agricultural equipment manufacturer, the incident is.

Incorrect Answers

A:

SOC features inherit administrative and ADOM authorization boundaries; visibility settings alone are not isolation controls. 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:

Correct source and virtual-domain attribution is necessary for trustworthy SOC conclusions in multi-tenant Fabric deployments. 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.

C:

FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. 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 124

The security team at a medical-device field service team proposes this controlled action for field diagnostic VPN events and remote access logs: Map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. The original condition was: The SOC dashboard reports double the expected connection count after a new FortiAnalyzer upstream forwarding relationship is enabled. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. An approved known benign test condition verifies content update health and the SOC documents any coverage gaps rather than claiming nonexistent feeds. Validate with representative field diagnostic VPN events and remote access logs traffic.
  2. New controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors. Validate with representative field diagnostic VPN events and remote access logs traffic.
  3. The live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events. Validate with representative field diagnostic VPN events and remote access logs traffic.
  4. Endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. Validate with representative field diagnostic VPN events and remote access logs traffic.

Explanation

Correct Answer

B:

New controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. In this case, matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. The corresponding correction is to map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source.

Incorrect Answers

A:

An approved known benign test condition verifies content update health and the SOC documents any coverage gaps rather than claiming nonexistent feeds. Enrichment and outbreak intelligence require their own data and service dependencies; raw log retention cannot substitute for an unavailable feed. The diagnostic evidence here is matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. The required outcome is that new controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors.

C:

The live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events. Security Fabric analytics depend on consistent device identities and membership, not simply identical display names. The diagnostic evidence here is matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. The required outcome is that new controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors.

D:

Endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. Log-source classification must match the producing application's schema before common SOC fields can be trusted. The diagnostic evidence here is matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. The required outcome is that new controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors.

Question 125

The security team at a regional courier franchise proposes this controlled action for parcel tracking gateway logs and scanner access alerts: Restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. The original condition was: A custom device-risk report fails with no rows after the author switches the dataset to a traffic log family while filtering an IPS-specific attack field. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. A controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. Validate with representative parcel tracking gateway logs and scanner access alerts traffic.
  2. The new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time. Validate with representative parcel tracking gateway logs and scanner access alerts traffic.
  3. A test run produces the custom view while the original shared template still generates its expected layout. Validate with representative parcel tracking gateway logs and scanner access alerts traffic.
  4. The chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases. Validate with representative parcel tracking gateway logs and scanner access alerts traffic.

Explanation

Correct Answer

A:

A controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. SQL datasets can only filter and aggregate attributes that exist in their selected log schema. In this case, dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. The corresponding correction is to restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating.

Incorrect Answers

B:

The new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time. Report definitions control future generation; they do not retroactively rewrite previously generated report artifacts. The diagnostic evidence here is dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. The required outcome is that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data.

C:

A test run produces the custom view while the original shared template still generates its expected layout. Report customization needs versioned ownership to avoid collateral changes to shared approved reporting assets. The diagnostic evidence here is dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. The required outcome is that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data.

D:

The chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases. A report dataset's schema is a contract for dependent charts and macros. The diagnostic evidence here is dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. The required outcome is that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data.

Question 126

During an investigation of maintenance system incidents and service gateway logs at a metropolitan rail maintenance depot, engineers need to separate security threats from ordinary faults. The reported failure is: A custom security dashboard shows no source-IP activity even though raw logs from the affected sites are searchable. The analyst confirms: Widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. Scope the action to the affected maintenance system incidents and service gateway logs environment.
  2. Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Scope the action to the affected maintenance system incidents and service gateway 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 maintenance system incidents and service gateway logs environment.
  4. Distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Scope the action to the affected maintenance system incidents and service gateway logs environment.

Explanation

Correct Answer

C:

Update the widget's authorized device/log group selection and verify filter semantics against source logs. Scope the action to the affected maintenance system incidents and service gateway logs environment. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. To resolve the observed issue, update the widget's authorized device/log group selection and verify filter semantics against source logs. Verify 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:

Separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. Scope the action to the affected maintenance system incidents and service gateway logs 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 needed change is to update the widget's authorized device/log group selection and verify filter semantics against source logs.

B:

Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Scope the action to the affected maintenance system incidents and service gateway logs environment. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The preferred remedy is to update the widget's authorized device/log group selection and verify filter semantics against source logs.

D:

Distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Scope the action to the affected maintenance system incidents and service gateway logs environment. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. A focused response is to update the widget's authorized device/log group selection and verify filter semantics against source logs.

Question 127

A SOC response plan for maintenance system incidents and service gateway logs at a metropolitan rail maintenance depot must include both a justified correction and measurable proof. Incident: A security analyst can confirm raw archived logs exist but an event handler and scheduled report show no matching events for that time window. Evidence: Archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. Which combined action-and-verification pair best fits this case?

  1. Action: Register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources. Proof: The approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized. Perform both using approved maintenance system incidents and service gateway logs test cases.
  2. Action: Configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. Proof: The targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved. Perform both using approved maintenance system incidents and service gateway logs test cases.
  3. Action: Verify applicable FortiGuard/service entitlement, connectivity and feed update status before relying on outbreak detections. Proof: An approved known benign test condition verifies content update health and the SOC documents any coverage gaps rather than claiming nonexistent feeds. Perform both using approved maintenance system incidents and service gateway logs test cases.
  4. Action: Update approved source-side security log selections and verify FortiAnalyzer log categories and parser coverage without broad uncontrolled log flooding. Proof: A controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. Perform both using approved maintenance system incidents and service gateway logs test cases.

Explanation

Correct Answer

B:

The correction is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. Validation should establish that the targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved. Perform both using approved maintenance system incidents and service gateway logs test cases. In this case, archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. Archival retention and analytics database availability have different uses; event handlers and reports require appropriate processed analytics data.

Incorrect Answers

A:

A focused response is to register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources. The outcome can be verified by confirming that the approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized. Perform both using approved maintenance system incidents and service gateway logs test cases. Receiving a connection and trusting a log-producing device are separate operations; registration and domain placement determine analyst access. The diagnostic evidence here is archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The preferred remedy is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. The acceptance test should confirm that the targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved.

C:

The practical next step is to verify applicable FortiGuard/service entitlement, connectivity and feed update status before relying on outbreak detections. A suitable test should demonstrate that an approved known benign test condition verifies content update health and the SOC documents any coverage gaps rather than claiming nonexistent feeds. Perform both using approved maintenance system incidents and service gateway logs test cases. Enrichment and outbreak intelligence require their own data and service dependencies; raw log retention cannot substitute for an unavailable feed. The diagnostic evidence here is archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. A focused response is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. The outcome can be verified by confirming that the targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved.

D:

The appropriate repair is to update approved source-side security log selections and verify FortiAnalyzer log categories and parser coverage without broad uncontrolled log flooding. The acceptance test should confirm that a controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. Perform both using approved maintenance system incidents and service gateway logs test cases. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. The diagnostic evidence here is archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The correction is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. Validation should establish that the targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved.

Question 128

A security analyst at a convention center operator is investigating an anomaly in visitor registration logs and event Wi-Fi security alerts. The reported behavior is: A broad event handler generates dozens of security events from routine activity after two independent matching rules are enabled. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. The FortiGate automation rule required by the FortiOS connector action was not configured or exposed for this device. Verify this observation against visitor registration logs and event Wi-Fi security alerts.
  2. The playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. Verify this observation against visitor registration logs and event Wi-Fi security alerts.
  3. Each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. Verify this observation against visitor registration logs and event Wi-Fi security alerts.
  4. Reputation results contain differing confidence/status fields and raw user/session evidence is not corroborated. Verify this observation against visitor registration logs and event Wi-Fi security alerts.

Explanation

Correct Answer

C:

Each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. Basic event handler rule matching differs from correlation sequence logic; rule composition controls alert specificity. The correction is to narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. Verify that only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts.

Incorrect Answers

A:

The FortiGate automation rule required by the FortiOS connector action was not configured or exposed for this device. FortiOS connector task actions depend on compatible device-side automation rules, not solely on a connected FortiAnalyzer playbook. The diagnostic evidence here is each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. To resolve the observed issue, narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together.

B:

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 each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. A focused response is to narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together.

D:

Reputation results contain differing confidence/status fields and raw user/session evidence is not corroborated. Threat intelligence enrichment adds context but cannot on its own prove local compromise of every communicating endpoint. The diagnostic evidence here is each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. The practical next step is to narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together.

Question 129

A SOC response plan for point-of-sale cyber alerts and stock gateway logs at a neighborhood grocery cooperative must include both a justified correction and measurable proof. Incident: An account-takeover detection should alert when repeated login failures are followed by success, but no event appears for a controlled attack simulation. Evidence: The correlation rule sequence places success before failures and the evaluation window never matches the observed order. Which combined action-and-verification pair best fits this case?

  1. 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 point-of-sale cyber alerts and stock gateway logs test cases.
  2. Action: Update the supported upstream task-output mapping and verify the imported task graph and variable resolution before enabling production automation. Proof: An incident test receives the expected generated report from the current task, and missing source outputs are logged explicitly. Perform both using approved point-of-sale cyber alerts and stock gateway logs test cases.
  3. 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 point-of-sale cyber alerts and stock gateway logs test cases.
  4. Action: Group qualifying authentication attempts by the relevant source or user dimensions and validate threshold scope. Proof: Parallel benign one-off failures remain below threshold but repeated attempts against a target account produce a single intended event. Perform both using approved point-of-sale cyber alerts and stock gateway logs test cases.

Explanation

Correct Answer

C:

The needed change 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 point-of-sale cyber alerts and stock gateway logs test cases. In this case, 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.

Incorrect Answers

A:

The practical next step is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. A suitable test should demonstrate that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. Perform both using approved point-of-sale cyber alerts and stock gateway logs test cases. Playbook triggers govern execution initiation independently of which tasks the playbook contains. The diagnostic evidence here is the correlation rule sequence places success before failures and the evaluation window never matches the observed order. A focused response is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. The outcome can be verified by confirming that test failures followed by success raise one correlated event and reversed benign order does not.

B:

The appropriate repair is to update the supported upstream task-output mapping and verify the imported task graph and variable resolution before enabling production automation. The acceptance test should confirm that an incident test receives the expected generated report from the current task, and missing source outputs are logged explicitly. Perform both using approved point-of-sale cyber alerts and stock gateway logs test cases. Task output variables must match the playbook's real dependency graph and task identities after export/import changes. The diagnostic evidence here is the correlation rule sequence places success before failures and the evaluation window never matches the observed order. The correction is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. Validation should establish that test failures followed by success raise one correlated event and reversed benign order does not.

D:

The preferred remedy is to group qualifying authentication attempts by the relevant source or user dimensions and validate threshold scope. The outcome can be verified by confirming that parallel benign one-off failures remain below threshold but repeated attempts against a target account produce a single intended event. Perform both using approved point-of-sale cyber alerts and stock gateway logs test cases. 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 appropriate repair is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. The acceptance test should confirm that test failures followed by success raise one correlated event and reversed benign order does not.

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.

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