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!
Fortinet FCP_FAZ_AN-7.6 Practice Test 77
Question 760
During an investigation of specimen database access events and archive security alerts at a natural-history archive, record integrity must be demonstrable in reports. The reported failure is: A playbook builds a remediation command directly from an unvalidated log field and could apply a block to an unintended address. The analyst confirms: Trigger variable contains a malformed or private management address, but the task has no type or allowlist validation. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?
Explanation
Correct Answer
Validate indicator types and permitted remediation scope before using trigger/output values in any connector action, and log refusal reasons. Scope the action to the affected specimen database access events and archive security alerts environment. Automation variables carry source data, not implicit trust; unsafe input handling can turn a detection into an unauthorized response. The practical next step is to validate indicator types and permitted remediation scope before using trigger/output values in any connector action, and log refusal reasons. Verify that a legitimate test indicator is processed while reserved-management or malformed values are rejected without changing devices.
Incorrect Answers
Map event categories to approved incident assignment and escalation rules with explicit fallback for unmapped sources. Scope the action to the affected specimen database access events and archive security alerts environment. An incident's existence does not guarantee triage ownership; response workflow assignment is an additional operational decision. The diagnostic evidence here is trigger variable contains a malformed or private management address, but the task has no type or allowlist validation. The correction is to validate indicator types and permitted remediation scope before using trigger/output values in any connector action, and log refusal reasons.
Add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior. Scope the action to the affected specimen database access events and archive security alerts environment. A default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation. The diagnostic evidence here is trigger variable contains a malformed or private management address, but the task has no type or allowlist validation. 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.
Add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. Scope the action to the affected specimen database access events and archive security alerts environment. Event occurrence frequency does not imply repeated state-changing actions are necessary or safe. The diagnostic evidence here is trigger variable contains a malformed or private management address, but the task has no type or allowlist validation. The needed change is to validate indicator types and permitted remediation scope before using trigger/output values in any connector action, and log refusal reasons.
Question 761
A security analyst at a regional media broadcaster is investigating an anomaly in live contribution network events and newsdesk access logs. The reported behavior is: A playbook attempts to quarantine a source endpoint using a threat score calculated by a previous task, but its action executes with an empty value. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
Task dependency graph does not link the enrichment result to the quarantine step and the variable resolves before the required output exists. In a playbook task graph, data dependencies and execution ordering must be explicit rather than assumed from visual placement. The practical next step is to connect tasks in the intended dependency sequence and use supported output variables from the completed enrichment step. Verify that the test run records enrichment output before dependent action and never quarantines an endpoint when confidence data is absent. The question describes: A security analyst at a regional media broadcaster is investigating an anomaly in live contribution network events and newsdesk access logs.
Incorrect Answers
Fresh log evidence postdates the closure and maps to a distinct asset not included in containment verification. Administrative closure does not invalidate later observed evidence or prove all related assets are contained. The diagnostic evidence here is task dependency graph does not link the enrichment result to the quarantine step and the variable resolves before the required output exists. The appropriate repair is to connect tasks in the intended dependency sequence and use supported output variables from the completed enrichment step. The question describes: A security analyst at a regional media broadcaster is investigating an anomaly in live contribution network events and newsdesk access logs.
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 task dependency graph does not link the enrichment result to the quarantine step and the variable resolves before the required output exists. The needed change is to connect tasks in the intended dependency sequence and use supported output variables from the completed enrichment step.
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 task dependency graph does not link the enrichment result to the quarantine step and the variable resolves before the required output exists. The preferred remedy is to connect tasks in the intended dependency sequence and use supported output variables from the completed enrichment step.
Question 762
During an investigation of pump telemetry security detections and management logs at a wastewater treatment utility, incident response must preserve operational controls. The reported failure is: A newly enabled threat-response playbook runs for every incident, including harmless configuration and maintenance warnings. The analyst confirms: The incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?
Explanation
Correct Answer
Add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior. Scope the action to the affected pump telemetry security detections and management logs environment. A default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation. The needed change is to 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
Add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. Scope the action to the affected pump telemetry security detections and management logs environment. Event occurrence frequency does not imply repeated state-changing actions are necessary or safe. 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.
Restore allowed connector path, credentials and trust, then run a harmless connectivity and task-specific test. Scope the action to the affected pump telemetry security detections and management logs environment. 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 preferred remedy is to add explicit incident severity, source or category conditions and test the supported all-versus-any filter behavior.
Normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. Scope the action to the affected pump telemetry security detections and management logs environment. Threat indicators must preserve their type and canonical representation to support meaningful enrichment and correlation. The diagnostic evidence here is 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.
Question 763
A security analyst at a renewable-energy operator is investigating an anomaly in remote plant intrusion signals and control-network access logs. The reported behavior is: Security Fabric topology shows an obsolete edge device instead of the replacement FortiGate after a branch hardware swap. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
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 needed change is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection. Verify that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events. The question describes: A security analyst at a renewable-energy operator is investigating an anomaly in remote plant intrusion signals and control-network access logs.
Incorrect Answers
Device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. FortiAnalyzer ADOM scoping controls device and log context; working collection does not guarantee correct tenancy or isolation. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. The preferred remedy is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection.
Matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. To resolve the observed issue, reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection.
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. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. A focused response is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection.
Question 764
A SOC response plan for care referral alerts and clinic firewall telemetry at a pediatric clinic consortium must include both a justified correction and measurable proof. Incident: A multisite security team sees alerts tagged to the parent firewall but cannot distinguish the two VDOM tenants that generated them. Evidence: Available raw log fields include device and VDOM values but the dashboard selector groups only by physical serial number. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
The appropriate repair is to preserve VDOM identifiers in the device/ADOM views and event queries and apply separate authorized tenant-aware filters. The outcome can be verified by confirming that matching test policy events in two VDOMs appear with distinct source contexts and the analyst cannot confuse one tenant's evidence with the other. Perform both using approved care referral alerts and clinic firewall telemetry test cases. In this case, available raw log fields include device and VDOM values but the dashboard selector groups only by physical serial number. Correct source and virtual-domain attribution is necessary for trustworthy SOC conclusions in multi-tenant Fabric deployments.
Incorrect Answers
A focused response is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples. A suitable test should demonstrate that endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. Perform both using approved care referral alerts and clinic firewall telemetry test cases. Log-source classification must match the producing application's schema before common SOC fields can be trusted. The diagnostic evidence here is available raw log fields include device and VDOM values but the dashboard selector groups only by physical serial number. The preferred remedy is to preserve VDOM identifiers in the device/ADOM views and event queries and apply separate authorized tenant-aware filters. The outcome can be verified by confirming that matching test policy events in two VDOMs appear with distinct source contexts and the analyst cannot confuse one tenant's evidence with the other.
The correction is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. The acceptance test should confirm 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 care referral alerts and clinic firewall telemetry test cases. Collection, central processing and report generation are distinct roles in distributed FortiAnalyzer architectures. The diagnostic evidence here is available raw log fields include device and VDOM values but the dashboard selector groups only by physical serial number. To resolve the observed issue, preserve VDOM identifiers in the device/ADOM views and event queries and apply separate authorized tenant-aware filters. Validation should establish that matching test policy events in two VDOMs appear with distinct source contexts and the analyst cannot confuse one tenant's evidence with the other.
The practical next step is to inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping. A controlled check should show that a controlled approved detection scenario produces the mapped event and evidence; untested techniques are clearly labeled as coverage gaps. Perform both using approved care referral alerts and clinic firewall telemetry test cases. A detection mapping describes capability or intent and cannot by itself prove that required telemetry and working rules exist. The diagnostic evidence here is available raw log fields include device and VDOM values but the dashboard selector groups only by physical serial number. A focused response is to preserve VDOM identifiers in the device/ADOM views and event queries and apply separate authorized tenant-aware filters. A suitable test should demonstrate that matching test policy events in two VDOMs appear with distinct source contexts and the analyst cannot confuse one tenant's evidence with the other.
Question 765
During a FortiAnalyzer 7.6 design review covering visitor registration logs and event Wi-Fi security alerts at a convention center operator, the incident is: A scheduled playbook stops responding after a proxy replacement, even though the task JSON and trigger still parse. Key diagnostic evidence: Playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. Which underlying security-analytics or reporting principle explains the behavior?
Explanation
Correct Answer
Upstream device reachability and local task configuration are separate causes of automation failure. In this case, playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. A focused response is to restore allowed connector path, credentials and trust, then run a harmless connectivity and task-specific test. Verify that the formerly failing connector task succeeds and its upstream endpoint is validated without exposing broader egress. The question describes: During a FortiAnalyzer 7.6 design review covering visitor registration logs and event Wi-Fi security alerts at a convention center operator, the incident is: A scheduled playbook stops responding after a proxy replacement,.
Incorrect Answers
Overall playbook job failure does not imply every prior action rolled back; task-level results determine safe recovery. The diagnostic evidence here is playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. The controlling principle here is that upstream device reachability and local task configuration are separate causes of automation failure.
Automation variables carry source data, not implicit trust; unsafe input handling can turn a detection into an unauthorized response. The diagnostic evidence here is playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. The controlling principle here is that upstream device reachability and local task configuration are separate causes of automation failure.
Task output variables must match the playbook's real dependency graph and task identities after export/import changes. The diagnostic evidence here is playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. The controlling principle here is that upstream device reachability and local task configuration are separate causes of automation failure.
Question 766
During an investigation of supplier EDI gateway logs and plant incident telemetry at an agricultural equipment manufacturer, factory traffic must not conceal critical detections. The reported failure is: A benign lab scan produces many critical incident notifications while privileged-access anomalies affecting production servers remain low priority. The analyst confirms: Event-handler severity defaults and incident prioritization rules are disconnected from protected asset context and analyst response criteria. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?
Explanation
Correct Answer
Calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment. Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. A focused response 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
Align storage quota, Analytics versus Archive retention and external backup with the approved evidence period, monitoring projected growth. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment. Analyzable history is constrained by log aging policies and storage allocation, not just whether the current logging connection is healthy. The diagnostic evidence here is event-handler severity defaults and incident prioritization rules are disconnected from protected asset context and analyst response criteria. The correction is to calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks.
Map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is event-handler severity defaults and incident prioritization rules are disconnected from protected asset context and analyst response criteria. The practical next step is to calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks.
Preserve VDOM identifiers in the device/ADOM views and event queries and apply separate authorized tenant-aware filters. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment. 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 appropriate repair is to calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks.
Question 767
A security analyst at a wastewater treatment utility is investigating an anomaly in pump telemetry security detections and management logs. The reported behavior is: Endpoint antivirus events are incorrectly treated as firewall traffic, making malware severity and host fields unusable for searches. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
Assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. Log-source classification must match the producing application's schema before common SOC fields can be trusted. The appropriate repair is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples. Verify that endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. The question describes: A security analyst at a wastewater treatment utility is investigating an anomaly in pump telemetry security detections and management logs.
Incorrect Answers
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. The diagnostic evidence here is assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The correction is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples.
Entitlement and update health show the associated outbreak content service is unavailable even though ordinary traffic logs and manually created events work. 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 assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The practical next step is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples.
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. The diagnostic evidence here is assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The needed change is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples.
Question 768
A SOC response plan for remote plant intrusion signals and control-network access logs at a renewable-energy operator must include both a justified correction and measurable proof. Incident: A security operator changes an incident status to resolved immediately after one endpoint is isolated, but the same indicator continues appearing from another host. Evidence: Fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
A focused response is to validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. A controlled check should show that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status. Perform both using approved remote plant intrusion signals and control-network access logs test cases. In this case, fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. Administrative incident status is not technical evidence that the underlying threat has stopped across the environment.
Incorrect Answers
The needed change is to reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View. Validation should establish that pivoted raw events match the original widget's source set and timeframe, with any residual gaps documented. Perform both using approved remote plant intrusion signals and control-network access logs test cases. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The practical next step is to validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. A controlled check should show that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status.
The preferred remedy is to check application-control logging prerequisites and include unclassified categories in a scoped dashboard query. A suitable test should demonstrate that an authorized synthetic unclassified flow is visible as such and the known-application totals continue to reconcile to log records. Perform both using approved remote plant intrusion signals and control-network access logs test cases. Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The appropriate repair is to validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. The outcome can be verified by confirming that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status.
To resolve the observed issue, update the widget's authorized device/log group selection and verify filter semantics against source logs. The acceptance test should confirm 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 remote plant intrusion signals and control-network access logs test cases. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The needed change is to validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. Validation should establish that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status.
Question 769
A SOC response plan for subscriber abuse alerts and customer-edge firewall logs at a rural broadband provider must include both a justified correction and measurable proof. Incident: An event fires five times in one minute and automation repeatedly attempts the same endpoint quarantine with resulting alert storms. Evidence: Event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
To resolve the observed issue, add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. The acceptance test should confirm that ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences. Perform both using approved subscriber abuse alerts and customer-edge firewall logs test cases. In this case, event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. Event occurrence frequency does not imply repeated state-changing actions are necessary or safe.
Incorrect Answers
The preferred remedy is to 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. Perform both using approved subscriber abuse alerts and customer-edge firewall logs test cases. 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 appropriate repair is to add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. The outcome can be verified by confirming that ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences.
A focused response is to order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence. A controlled check should show that the escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment. Perform both using approved subscriber abuse alerts and customer-edge firewall logs test cases. 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 preferred remedy is to add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. A suitable test should demonstrate that ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences.
The correction is to narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. The outcome can be verified by confirming that only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts. Perform both using approved subscriber abuse alerts and customer-edge firewall logs test cases. Basic event handler rule matching differs from correlation sequence logic; rule composition controls alert specificity. 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. To resolve the observed issue, add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. The acceptance test should confirm that ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences.
Question 770
The security team at a rural broadband provider proposes this controlled action for subscriber abuse alerts and customer-edge firewall logs: Reassign the authorized device into its proper administrative domain with preserved evidence handling and tenant-aware permissions. The original condition was: An MSSP analyst opens a customer ADOM and finds one branch firewall entirely missing while its logs appear in another customer's dashboards. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
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. In this case, device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. The corresponding correction is to reassign the authorized device into its proper administrative domain with preserved evidence handling and tenant-aware permissions. The question describes: The security team at a rural broadband provider proposes this controlled action for subscriber abuse alerts and customer-edge firewall logs: Reassign the authorized device into its proper administrative domain with preserved.
Incorrect Answers
A controlled approved detection scenario produces the mapped event and evidence; untested techniques are clearly labeled as coverage gaps. A detection mapping describes capability or intent and cannot by itself prove that required telemetry and working rules exist. The diagnostic evidence here is device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. The required outcome is that each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records.
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 device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. The required outcome is that each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records.
The approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized. Receiving a connection and trusting a log-producing device are separate operations; registration and domain placement determine analyst access. The diagnostic evidence here is device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. The required outcome is that each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records.
Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst (FCP_FAZ_AN-7.6) Practice Tests
- Fortinet FCP_FAZ_AN-7.6 Practice Test 75 - 10 Questions (Last Reviewed 01-Nov-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 76 - 10 Questions (Last Reviewed 31-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 77 - 10 Questions (Last Reviewed 30-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 78 - 10 Questions (Last Reviewed 29-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 79 - 10 Questions (Last Reviewed 28-Oct-2026)