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

Question 200

A SOC response plan for public event portal traffic and staff system alerts at a city parks administration must include both a justified correction and measurable proof. Incident: An incident in one customer's ADOM triggers an automation that attempts to block an address on another customer's firewall. Evidence: The connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. Which combined action-and-verification pair best fits this case?

  1. Action: Restore allowed connector path, credentials and trust, then run a harmless connectivity and task-specific test. Proof: The formerly failing connector task succeeds and its upstream endpoint is validated without exposing broader egress. Perform both using approved public event portal traffic and staff system alerts test cases.
  2. Action: Restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. Proof: A controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched. Perform both using approved public event portal traffic and staff system alerts 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 public event portal traffic and staff system alerts test cases.
  4. Action: Prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples. Proof: Benign software updates do not trigger but an approved critical detection emits the handler event with the expected severity. Perform both using approved public event portal traffic and staff system alerts test cases.

Explanation

Correct Answer

B:

The needed change is to restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. A controlled check should show that a controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched. Perform both using approved public event portal traffic and staff system alerts test cases. In this case, the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. Automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants.

Incorrect Answers

A:

The appropriate repair is to restore allowed connector path, credentials and trust, then run a harmless connectivity and task-specific test. The acceptance test should confirm that the formerly failing connector task succeeds and its upstream endpoint is validated without exposing broader egress. Perform both using approved public event portal traffic and staff system alerts test cases. Upstream device reachability and local task configuration are separate causes of automation failure. The diagnostic evidence here is the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The correction is to restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. Validation should establish that a controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched.

C:

The preferred remedy 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. Perform both using approved public event portal traffic and staff system alerts test cases. Threat indicators must preserve their type and canonical representation to support meaningful enrichment and correlation. The diagnostic evidence here is the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The appropriate repair is to restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. The acceptance test should confirm that a controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched.

D:

To resolve the observed issue, prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples. Validation should establish that benign software updates do not trigger but an approved critical detection emits the handler event with the expected severity. Perform both using approved public event portal traffic and staff system alerts test cases. Unstructured text matching may not have the same semantics as typed security-log severity attributes. The diagnostic evidence here is the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The needed change is to restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. A controlled check should show that a controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched.

Question 201

The security team at a cloud software support provider proposes this controlled action for customer ticket service events and engineer VPN logs: Align chart field mappings with the dataset's actual result columns and preview the query on representative logs. The original condition was: A custom report's chart displays an SQL error after the dataset was updated to rename its grouping column. 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 customer ticket service events and engineer VPN logs traffic.
  2. The chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases. Validate with representative customer ticket service events and engineer VPN logs traffic.
  3. The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Validate with representative customer ticket service events and engineer VPN logs traffic.
  4. Back-to-back customer A and B runs show correct segregated records and no cross-tenant source values. Validate with representative customer ticket service events and engineer VPN logs traffic.

Explanation

Correct Answer

B:

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. In this case, chart expects src_host alias while the revised dataset returns source_name with no matching field. The corresponding correction is to align chart field mappings with the dataset's actual result columns and preview the query on representative logs.

Incorrect Answers

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. The diagnostic evidence here is chart expects src_host alias while the revised dataset returns source_name with no matching field. The required outcome is that the chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases.

C:

The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Report identity includes its time-zone semantics, not just the stored PDF bytes. The diagnostic evidence here is chart expects src_host alias while the revised dataset returns source_name with no matching field. The required outcome is that the chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases.

D:

Back-to-back customer A and B runs show correct segregated records and no cross-tenant source values. Report filter caching and query scope require tenant-aware validation, especially when a definition is reused. The diagnostic evidence here is chart expects src_host alias while the revised dataset returns source_name with no matching field. The required outcome is that the chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases.

Question 202

The security team at a sports venue operations group proposes this controlled action for turnstile system alerts and concession network logs: Narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. The original condition was: A broad event handler generates dozens of security events from routine activity after two independent matching rules are enabled. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. The formerly failing connector task succeeds and its upstream endpoint is validated without exposing broader egress. Validate with representative turnstile system alerts and concession network logs traffic.
  2. The second-host test is surfaced as actionable after closure, and the first case remains auditable. Validate with representative turnstile system alerts and concession network logs traffic.
  3. A controlled severity-specific alert reaches the intended on-call channel with an event ID and records successful delivery. Validate with representative turnstile system alerts and concession network logs traffic.
  4. Only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts. Validate with representative turnstile system alerts and concession network logs traffic.

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

The formerly failing connector task succeeds and its upstream endpoint is validated without exposing broader egress. Upstream device reachability and local task configuration are separate causes of automation failure. The diagnostic evidence here is each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. The required outcome is that only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts.

B:

The second-host test is surfaced as actionable after closure, and the first case remains auditable. Administrative closure does not invalidate later observed evidence or prove all related assets are contained. The diagnostic evidence here is each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. The required outcome is that only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts.

C:

A controlled severity-specific alert reaches the intended on-call channel with an event ID and records successful delivery. Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. The diagnostic evidence here is each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. The required outcome is that only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts.

Question 203

A security analyst at a wastewater treatment utility is investigating an anomaly in pump telemetry security detections and management logs. The reported behavior is: A weekly intrusion report is blank for a new firewall even though ordinary permitted traffic appears in a different report. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. The target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. Verify this observation against pump telemetry security detections and management logs.
  2. The view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. Verify this observation against pump telemetry security detections and management logs.
  3. Report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. Verify this observation against pump telemetry security detections and management logs.
  4. Report time zone and previous-day window definitions use a different offset from the incident site's local time. Verify this observation against pump telemetry security detections and management logs.

Explanation

Correct Answer

A:

The target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. Chart data depend on specific log types and fields; traffic-log availability does not imply every security report dataset is populated. The needed change is to use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging. Verify that a controlled test signature generates the appropriate security log and the report shows its event after regeneration. 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

B:

The view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. The diagnostic evidence here is the target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. The preferred remedy is to use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging.

C:

Report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. A successful data query and a correctly delivered report artifact are separate stages that require their own checks. The diagnostic evidence here is the target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. To resolve the observed issue, use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging. The question describes: A security analyst at a wastewater treatment utility is investigating an anomaly in pump telemetry security detections and management logs.

D:

Report time zone and previous-day window definitions use a different offset from the incident site's local time. Report scheduling window boundaries and display-time conversion influence which events enter a report. The diagnostic evidence here is the target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. A focused response is to use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging.

Question 204

The security team at a hydrology research nonprofit proposes this controlled action for river sensor gateway logs and remote site alerts: Provide explicit safe input values for manual runs or use a supported incident-context execution path with validated trigger variables. The original condition was: An analyst starts a playbook on demand and expects the incident's user and source-IP trigger variables to populate automatically. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. An on-demand test refuses missing inputs, while the incident-started test uses the intended case fields. Validate with representative river sensor gateway logs and remote site alerts traffic.
  2. An incident test receives the expected generated report from the current task, and missing source outputs are logged explicitly. Validate with representative river sensor gateway logs and remote site alerts traffic.
  3. A legitimate test indicator is processed while reserved-management or malformed values are rejected without changing devices. Validate with representative river sensor gateway logs and remote site alerts traffic.
  4. The test run records enrichment output before dependent action and never quarantines an endpoint when confidence data is absent. Validate with representative river sensor gateway logs and remote site alerts traffic.

Explanation

Correct Answer

A:

An on-demand test refuses missing inputs, while the incident-started test uses the intended case fields. Trigger-derived variables exist only when the execution context supplies them; manual execution does not invent incident metadata. In this case, oN_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. The corresponding correction is to provide explicit safe input values for manual runs or use a supported incident-context execution path with validated trigger variables. The question describes: The security team at a hydrology research nonprofit proposes this controlled action for river sensor gateway logs and remote site alerts: Provide explicit safe input values for manual runs or use a supported incident-context.

Incorrect Answers

B:

An incident test receives the expected generated report from the current task, and missing source outputs are logged explicitly. Task output variables must match the playbook's real dependency graph and task identities after export/import changes. The diagnostic evidence here is oN_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. The required outcome is that an on-demand test refuses missing inputs, while the incident-started test uses the intended case fields.

C:

A legitimate test indicator is processed while reserved-management or malformed values are rejected without changing devices. Automation variables carry source data, not implicit trust; unsafe input handling can turn a detection into an unauthorized response. The diagnostic evidence here is oN_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. The required outcome is that an on-demand test refuses missing inputs, while the incident-started test uses the intended case fields.

D:

The test run records enrichment output before dependent action and never quarantines an endpoint when confidence data is absent. In a playbook task graph, data dependencies and execution ordering must be explicit rather than assumed from visual placement. The diagnostic evidence here is oN_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. The required outcome is that an on-demand test refuses missing inputs, while the incident-started test uses the intended case fields.

Question 205

A SOC response plan for specimen database access events and archive security alerts at a natural-history archive must include both a justified correction and measurable proof. Incident: 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. Evidence: Dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. Which combined action-and-verification pair best fits this case?

  1. Action: Restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. Proof: A controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. Perform both using approved specimen database access events and archive security alerts test cases.
  2. Action: Add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. Proof: Synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim. Perform both using approved specimen database access events and archive security alerts test cases.
  3. Action: Align chart field mappings with the dataset's actual result columns and preview the query on representative logs. Proof: The chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases. Perform both using approved specimen database access events and archive security alerts test cases.
  4. 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 specimen database access events and archive security alerts test cases.

Explanation

Correct Answer

A:

The correction is to restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. The acceptance test should confirm that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. Perform both using approved specimen database access events and archive security alerts test cases. In this case, dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. SQL datasets can only filter and aggregate attributes that exist in their selected log schema.

Incorrect Answers

B:

The practical next step is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. A controlled check should show that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim. Perform both using approved specimen database access events and archive security alerts test cases. Report aggregation keys define the claim's granularity; an IP address does not guarantee a stable user identity. The diagnostic evidence here is dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. A focused response is to restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. A suitable test should demonstrate that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data.

C:

The appropriate repair is to align chart field mappings with the dataset's actual result columns and preview the query on representative logs. The outcome can be verified by confirming that the chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases. Perform both using approved specimen database access events and archive security alerts test cases. 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 correction is to restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. The acceptance test should confirm that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data.

D:

The needed change is to label top-N limitations and include an explicit rare/high-severity indicator query where completeness is required. Validation should establish 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 specimen database access events and archive security alerts test cases. Rankings are summaries, not exhaustive evidence; a low-frequency critical signal can sit below a volume cutoff. 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 practical next step is to restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. A controlled check should show that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data.

Question 206

During an investigation of resident portal events and privileged-access logs at a public housing services agency, casework records need least-privilege incident handling. 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. Update the widget's authorized device/log group selection and verify filter semantics against source logs. Scope the action to the affected resident portal events and privileged-access logs environment.
  2. Compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. Scope the action to the affected resident portal events and privileged-access logs environment.
  3. Correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields. Scope the action to the affected resident portal events and privileged-access logs environment.
  4. Inspect actual log schema and build a supported OR-aware search across relevant username fields while retaining IP/time constraints. Scope the action to the affected resident portal events and privileged-access logs environment.

Explanation

Correct Answer

A:

Update the widget's authorized device/log group selection and verify filter semantics against source logs. Scope the action to the affected resident portal events and privileged-access logs environment. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. A focused response is to 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

B:

Compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. Scope the action to the affected resident portal events and privileged-access logs environment. A successful data query and a correctly delivered report artifact are separate stages that require their own checks. 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.

C:

Correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields. Scope the action to the affected resident portal events and privileged-access logs environment. FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. 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.

D:

Inspect actual log schema and build a supported OR-aware search across relevant username fields while retaining IP/time constraints. Scope the action to the affected resident portal events and privileged-access logs environment. 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 appropriate repair is to update the widget's authorized device/log group selection and verify filter semantics against source logs.

Question 207

A SOC response plan for port gate security events and vessel system telemetry at a coastal shipping authority must include both a justified correction and measurable proof. Incident: Critical URL blocks from one branch never trigger a configured security handler used successfully at headquarters. Evidence: The handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. Which combined action-and-verification pair best fits this case?

  1. 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 port gate security events and vessel system telemetry 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 port gate security events and vessel system telemetry test cases.
  3. Action: Attach an auditable evidence extract with source reference, time, ADOM/device and hash where supported, keeping the underlying logs preserved. Proof: A second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone. Perform both using approved port gate security events and vessel system telemetry test cases.
  4. Action: Extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. Proof: Branch and headquarters controls trigger their expected events, and a third-party tenant's logs never match. Perform both using approved port gate security events and vessel system telemetry test cases.

Explanation

Correct Answer

D:

To resolve the observed issue, extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. The acceptance test should confirm that branch and headquarters controls trigger their expected events, and a third-party tenant's logs never match. Perform both using approved port gate security events and vessel system telemetry test cases. In this case, 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.

Incorrect Answers

A:

The appropriate repair 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 port gate security events and vessel system telemetry test cases. A shared indicator does not establish common incident ownership across isolated administrative domains. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. The correction is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. The acceptance test should confirm that branch and headquarters controls trigger their expected events, and a third-party tenant's logs never match.

B:

The needed change 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. Perform both using approved port gate security events and vessel system telemetry test cases. A default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. The practical next step is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. A controlled check should show that branch and headquarters controls trigger their expected events, and a third-party tenant's logs never match.

C:

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. A suitable test should demonstrate that a second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone. Perform both using approved port gate security events and vessel system telemetry test cases. Incident handling requires provenance and reproducible evidence, not just a narrative label attached to a case. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. The appropriate repair is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. The outcome can be verified by confirming that branch and headquarters controls trigger their expected events, and a third-party tenant's logs never match.

Question 208

A security analyst at a rural broadband provider is investigating an anomaly in subscriber abuse alerts and customer-edge firewall logs. The reported behavior is: An MSSP analyst opens a customer ADOM and finds one branch firewall entirely missing while its logs appear in another customer's dashboards. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. The user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  2. Device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  3. Source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  4. FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.

Explanation

Correct Answer

B:

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 appropriate repair is to reassign the authorized device into its proper administrative domain with preserved evidence handling and tenant-aware permissions. Verify that each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records. The question describes: A security analyst at a rural broadband provider is investigating an anomaly in subscriber abuse alerts and customer-edge firewall logs.

Incorrect Answers

A:

The user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. SOC features inherit administrative and ADOM authorization boundaries; visibility settings alone are not isolation controls. The diagnostic evidence here is device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. The practical next step is to reassign the authorized device into its proper administrative domain with preserved evidence handling and tenant-aware permissions.

C:

Source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. The diagnostic evidence here is device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. The needed change is to reassign the authorized device into its proper administrative domain with preserved evidence handling and tenant-aware permissions.

D:

FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. 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 preferred remedy is to reassign the authorized device into its proper administrative domain with preserved evidence handling and tenant-aware permissions.

Question 209

A SOC response plan for river sensor gateway logs and remote site alerts at a hydrology research nonprofit must include both a justified correction and measurable proof. Incident: A quarterly report file name says the day after its actual time period and auditors suspect data tampering. Evidence: Generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. Which combined action-and-verification pair best fits this case?

  1. Action: Bind the chart to a compatible supported dataset and validate log type, field mappings and sample aggregates. Proof: A controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. Perform both using approved river sensor gateway logs and remote site alerts test cases.
  2. Action: Move resource-heavy report jobs to a safe window, optimize datasets and consider supported capacity tuning without disabling essential security logging. Proof: Peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Perform both using approved river sensor gateway logs and remote site alerts test cases.
  3. 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 river sensor gateway logs and remote site alerts test cases.
  4. Action: Standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. Proof: The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Perform both using approved river sensor gateway logs and remote site alerts test cases.

Explanation

Correct Answer

D:

The correction is to standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. The outcome can be verified by confirming that the PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Perform both using approved river sensor gateway logs and remote site alerts test cases. In this case, generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. Report identity includes its time-zone semantics, not just the stored PDF bytes.

Incorrect Answers

A:

The preferred remedy is to bind the chart to a compatible supported dataset and validate log type, field mappings and sample aggregates. A suitable test should demonstrate that a controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. Perform both using approved river sensor gateway logs and remote site alerts test cases. 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 generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. The appropriate repair is to standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. The outcome can be verified by confirming that The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight.

B:

To resolve the observed issue, move resource-heavy report jobs to a safe window, optimize datasets and consider supported capacity tuning without disabling essential security logging. The acceptance test should confirm that peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Perform both using approved river sensor gateway logs and remote site alerts test cases. Reporting workloads consume shared processing resources; analytics capacity planning must include peak query as well as log ingestion demand. The diagnostic evidence here is generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. The needed change is to standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. Validation should establish that The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight.

C:

A focused response 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 river sensor gateway logs and remote site alerts test cases. Report type and output profile jointly control distribution, which must respect privacy and ADOM boundaries. The diagnostic evidence here is generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. The preferred remedy is to standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. A suitable test should demonstrate that The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight.

Question 210

During a FortiAnalyzer 7.6 design review covering public Wi-Fi events and staff application log streams at a county public library network, the incident is: Dashboard shows hundreds of malware events and management assumes hundreds of infected hosts. Key diagnostic evidence: Log sample and device inventory reveal many repeated detections from the same endpoint and indicator. Which underlying security-analytics or reporting principle explains the behavior?

  1. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. Apply this reasoning to public Wi-Fi events and staff application log streams.
  2. Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence. Apply this reasoning to public Wi-Fi events and staff application log streams.
  3. Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. Apply this reasoning to public Wi-Fi events and staff application log streams.
  4. Security-event frequency and affected-asset cardinality are different measurements with different incident implications. Apply this reasoning to public Wi-Fi events and staff application log streams.

Explanation

Correct Answer

D:

In this case, log sample and device inventory reveal many repeated detections from the same endpoint and indicator. A focused response is to separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. Verify that a replay of multiple alerts from one endpoint increments total events while unique affected-host count remains one.

Incorrect Answers

A:

FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is log sample and device inventory reveal many repeated detections from the same endpoint and indicator.

B:

Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence. The diagnostic evidence here is log sample and device inventory reveal many repeated detections from the same endpoint and indicator.

C:

Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. The diagnostic evidence here is log sample and device inventory reveal many repeated detections from the same endpoint and indicator.

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