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

Question 390

A SOC response plan for cold-store cyber alerts and billing gateway events at a commercial fishing cooperative must include both a justified correction and measurable proof. Incident: A junior analyst modifies a standardized compliance template directly to add a device-specific chart, changing every team's future report. Evidence: Report definition history and owner settings show shared template edits rather than a cloned report under separate control. Which combined action-and-verification pair best fits this case?

  1. Action: Select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior. Proof: Events at the start and end of the intended period appear exactly once and date-range labels match the actual query. Perform both using approved cold-store cyber alerts and billing gateway events test cases.
  2. 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 cold-store cyber alerts and billing gateway events test cases.
  3. Action: Clone the report for the authorized variation and apply access/approval controls to preserve the standard template. Proof: A test run produces the custom view while the original shared template still generates its expected layout. Perform both using approved cold-store cyber alerts and billing gateway events test cases.
  4. Action: Set an approved schedule and output profile on the imported report and test both generation and delivery with restricted recipients. Proof: A controlled scheduled run creates a report and sends it only to the designated recipient group. Perform both using approved cold-store cyber alerts and billing gateway events test cases.

Explanation

Correct Answer

C:

To resolve the observed issue, clone the report for the authorized variation and apply access/approval controls to preserve the standard template. The outcome can be verified by confirming that a test run produces the custom view while the original shared template still generates its expected layout. Perform both using approved cold-store cyber alerts and billing gateway events test cases. In this case, report definition history and owner settings show shared template edits rather than a cloned report under separate control. Report customization needs versioned ownership to avoid collateral changes to shared approved reporting assets.

Incorrect Answers

A:

The needed change is to select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior. The acceptance test should confirm that events at the start and end of the intended period appear exactly once and date-range labels match the actual query. Perform both using approved cold-store cyber alerts and billing gateway events test cases. Calendar-period and rolling-window selectors have different semantics even when both appear weekly. The diagnostic evidence here is report definition history and owner settings show shared template edits rather than a cloned report under separate control. The practical next step is to clone the report for the authorized variation and apply access/approval controls to preserve the standard template. Validation should establish that a test run produces the custom view while the original shared template still generates its expected layout.

B:

The preferred remedy is to verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. A controlled check should show that back-to-back customer A and B runs show correct segregated records and no cross-tenant source values. Perform both using approved cold-store cyber alerts and billing gateway events test cases. Report filter caching and query scope require tenant-aware validation, especially when a definition is reused. The diagnostic evidence here is report definition history and owner settings show shared template edits rather than a cloned report under separate control. The appropriate repair is to clone the report for the authorized variation and apply access/approval controls to preserve the standard template. A suitable test should demonstrate that a test run produces the custom view while the original shared template still generates its expected layout.

D:

A focused response is to set an approved schedule and output profile on the imported report and test both generation and delivery with restricted recipients. Validation should establish that a controlled scheduled run creates a report and sends it only to the designated recipient group. Perform both using approved cold-store cyber alerts and billing gateway events test cases. Importing report content is distinct from enabling timed execution and distribution. The diagnostic evidence here is report definition history and owner settings show shared template edits rather than a cloned report under separate control. The preferred remedy is to clone the report for the authorized variation and apply access/approval controls to preserve the standard template. A controlled check should show that a test run produces the custom view while the original shared template still generates its expected layout.

Question 391

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: 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: Regenerate the report for the specified period after approving the new definition and preserve historical version provenance. Proof: The new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time. Perform both using approved point-of-sale cyber alerts and stock gateway logs 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 point-of-sale cyber alerts and stock gateway logs test cases.
  3. 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 point-of-sale cyber alerts and stock gateway logs test cases.
  4. Action: Document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required. Proof: Sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation. Perform both using approved point-of-sale cyber alerts and stock gateway logs test cases.

Explanation

Correct Answer

C:

A focused response 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. Perform both using approved point-of-sale cyber alerts and stock gateway logs 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 regenerate the report for the specified period after approving the new definition and preserve historical version provenance. A controlled check should show that the new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time. Perform both using approved point-of-sale cyber alerts and stock gateway logs test cases. Report definitions control future generation; they do not retroactively rewrite previously generated report artifacts. 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. A suitable test should demonstrate 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 outcome can be verified by confirming that peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Perform both using approved point-of-sale cyber alerts and stock gateway logs 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. The acceptance test should confirm that The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight.

D:

The correction is to document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required. A suitable test should demonstrate that sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation. Perform both using approved point-of-sale cyber alerts and stock gateway logs test cases. Aggregation caches trade resources and speed against result detail; not every cached chart is suitable as exact audit evidence. The diagnostic evidence here is generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. To resolve the observed issue, 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.

Question 392

The security team at a chilled-food logistics company proposes this controlled action for cold-chain telemetry alerts and warehouse firewall events: Register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources. The original condition was: A new security gateway appears in the analyzer authorization queue but analysts cannot find its traffic logs in the intended device group. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. Replayed representative peak log volume shows expected source and severity counts without persistent ingest drops and with measured latency inside the service objective. Validate with representative cold-chain telemetry alerts and warehouse firewall events traffic.
  2. The user can analyze customer A events but cannot access customer B dashboards, incidents or report data through alternative views. Validate with representative cold-chain telemetry alerts and warehouse firewall events traffic.
  3. New controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors. Validate with representative cold-chain telemetry alerts and warehouse firewall events traffic.
  4. The approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized. Validate with representative cold-chain telemetry alerts and warehouse firewall events traffic.

Explanation

Correct Answer

D:

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. In this case, FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. The corresponding correction is to register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources.

Incorrect Answers

A:

Replayed representative peak log volume shows expected source and severity counts without persistent ingest drops and with measured latency inside the service objective. Centralized log collection requires realistic rate and storage capacity planning; adding senders cannot exceed finite ingestion resources without loss. The diagnostic evidence here is FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. The required outcome is that the approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized.

B:

The user can analyze customer A events but cannot access customer B dashboards, incidents or report data through alternative views. SOC features inherit administrative and ADOM authorization boundaries; visibility settings alone are not isolation controls. The diagnostic evidence here is FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. The required outcome is that the approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized.

C:

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. The diagnostic evidence here is FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. The required outcome is that the approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized.

Question 393

During a FortiAnalyzer 7.6 design review covering reservations security alerts and guest-network logs at a mid-size hotel group, the incident is: Analysts can read last month's raw archive files but FortiView's historical widget shows an empty graph for the same period. Key diagnostic evidence: The specified historical range predates retained Analytics data although Archive log files still exist. Which underlying security-analytics or reporting principle explains the behavior?

  1. Report source-device filters are independent from device registration and must track the intended scope. Apply this reasoning to reservations security alerts and guest-network logs.
  2. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. Apply this reasoning to reservations security alerts and guest-network logs.
  3. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. Apply this reasoning to reservations security alerts and guest-network logs.
  4. Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. Apply this reasoning to reservations security alerts and guest-network logs.

Explanation

Correct Answer

D:

Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. In this case, the specified historical range predates retained Analytics data although Archive log files still exist. The correction is to verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. Verify that the incident report documents which time windows support FortiView and demonstrates a current-day control record in both Log View and the visualization.

Incorrect Answers

A:

Report source-device filters are independent from device registration and must track the intended scope. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. The controlling principle here is that dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out.

B:

Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. The controlling principle here is that dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out.

C:

IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. The controlling principle here is that dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out.

Question 394

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 nightly report omits a security event at local midnight even though it is visible in Log View. The analyst confirms: Report time zone and previous-day window definitions use a different offset from the incident site's local time. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment.
  2. Align report time zone and scheduled period with compliance requirements while preserving UTC event times for audit. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment.
  3. Verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment.
  4. Separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment.

Explanation

Correct Answer

B:

Align report time zone and scheduled period with compliance requirements while preserving UTC event times for audit. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment. Report scheduling window boundaries and display-time conversion influence which events enter a report. A focused response is to align report time zone and scheduled period with compliance requirements while preserving UTC event times for audit. Verify that controlled events around the day boundary appear in exactly the correct reporting period with no double counting.

Incorrect Answers

A:

Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is report time zone and previous-day window definitions use a different offset from the incident site's local time. To resolve the observed issue, align report time zone and scheduled period with compliance requirements while preserving UTC event times for audit.

C:

Verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment. Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. The diagnostic evidence here is report time zone and previous-day window definitions use a different offset from the incident site's local time. The correction is to align report time zone and scheduled period with compliance requirements while preserving UTC event times for audit.

D:

Separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. Scope the action to the affected supplier EDI gateway logs and plant incident telemetry environment. The diagnostic evidence here is report time zone and previous-day window definitions use a different offset from the incident site's local time. The practical next step is to align report time zone and scheduled period with compliance requirements while preserving UTC event times for audit.

Question 395

During an investigation of assessment portal access records and web security alerts at an online education platform, peak student sessions require dependable threat detection. The reported failure is: SOC detections appear in the event monitor but assigned analysts receive no actionable notification during off-hours. The analyst confirms: Notification profile still references a retired email webhook or destination without delivery confirmation. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Scope the action to the affected assessment portal access records and web security alerts environment.
  2. Record enrichment source and confidence, corroborate with local detection evidence, and keep unproven cases under investigation. Scope the action to the affected assessment portal access records and web security alerts environment.
  3. Repair the handler's notification profile, transport credentials and escalation mapping, then test an alert end to end. Scope the action to the affected assessment portal access records and web security alerts environment.
  4. Restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. Scope the action to the affected assessment portal access records and web security alerts environment.

Explanation

Correct Answer

C:

Repair the handler's notification profile, transport credentials and escalation mapping, then test an alert end to end. Scope the action to the affected assessment portal access records and web security alerts environment. Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. The practical next step is to repair the handler's notification profile, transport credentials and escalation mapping, then test an alert end to end. Verify that a controlled severity-specific alert reaches the intended on-call channel with an event ID and records successful delivery.

Incorrect Answers

A:

Configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Scope the action to the affected assessment portal access records and web security alerts environment. Playbook triggers govern execution initiation independently of which tasks the playbook contains. The diagnostic evidence here is notification profile still references a retired email webhook or destination without delivery confirmation. A focused response is to repair the handler's notification profile, transport credentials and escalation mapping, then test an alert end to end.

B:

Record enrichment source and confidence, corroborate with local detection evidence, and keep unproven cases under investigation. Scope the action to the affected assessment portal access records and web security alerts environment. Threat intelligence enrichment adds context but cannot on its own prove local compromise of every communicating endpoint. The diagnostic evidence here is notification profile still references a retired email webhook or destination without delivery confirmation. The correction is to repair the handler's notification profile, transport credentials and escalation mapping, then test an alert end to end.

D:

Restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. Scope the action to the affected assessment portal access records and web security alerts environment. Automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants. The diagnostic evidence here is notification profile still references a retired email webhook or destination without delivery confirmation. The appropriate repair is to repair the handler's notification profile, transport credentials and escalation mapping, then test an alert end to end.

Question 396

A security analyst at a university research consortium is investigating an anomaly in research network IPS detections and shared instrument access logs. The reported behavior is: A new security gateway appears in the analyzer authorization queue but analysts cannot find its traffic logs in the intended device group. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. Verify this observation against research network IPS detections and shared instrument access logs.
  2. FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. Verify this observation against research network IPS detections and shared instrument access logs.
  3. Serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. Verify this observation against research network IPS detections and shared instrument access logs.
  4. Entitlement and update health show the associated outbreak content service is unavailable even though ordinary traffic logs and manually created events work. Verify this observation against research network IPS detections and shared instrument access logs.

Explanation

Correct Answer

B:

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 practical next step is to register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources. Verify that the approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized.

Incorrect Answers

A:

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 FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. The correction is to register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources.

C:

Serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. Security Fabric analytics depend on consistent device identities and membership, not simply identical display names. The diagnostic evidence here is FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. The appropriate repair is to register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources.

D:

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 FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. The needed change is to register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources.

Question 397

During an investigation of barcode scanner connectivity alerts and egress gateway events at an industrial parts distributor, warehouse workflows require traceable security evidence. The reported failure is: A custom handler meant for malware severity critical fires on informational antivirus updates containing the word critical in a description. The analyst confirms: Text filter matches the word anywhere while structured severity and subtype conditions are absent or scoped incorrectly. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples. Scope the action to the affected barcode scanner connectivity alerts and egress gateway events environment.
  2. Order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence. Scope the action to the affected barcode scanner connectivity alerts and egress gateway events environment.
  3. Scope incident aggregation to appropriate tenant and entity context while retaining shared threat intelligence as a separate enrichment signal. Scope the action to the affected barcode scanner connectivity alerts and egress gateway events environment.
  4. Restore relevant supported Analytics ingestion/retention and explicitly validate handler matching against processed log rows. Scope the action to the affected barcode scanner connectivity alerts and egress gateway events environment.

Explanation

Correct Answer

A:

Prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples. Scope the action to the affected barcode scanner connectivity alerts and egress gateway events environment. Unstructured text matching may not have the same semantics as typed security-log severity attributes. The practical next step is to prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples. Verify that benign software updates do not trigger but an approved critical detection emits the handler event with the expected severity.

Incorrect Answers

B:

Order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence. Scope the action to the affected barcode scanner connectivity alerts and egress gateway events environment. Playbook task ordering matters to operational completeness, and downstream messages should reflect actual upstream completion. The diagnostic evidence here is text filter matches the word anywhere while structured severity and subtype conditions are absent or scoped incorrectly. The appropriate repair is to prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples.

C:

Scope incident aggregation to appropriate tenant and entity context while retaining shared threat intelligence as a separate enrichment signal. Scope the action to the affected barcode scanner connectivity alerts and egress gateway events environment. A shared indicator does not establish common incident ownership across isolated administrative domains. The diagnostic evidence here is text filter matches the word anywhere while structured severity and subtype conditions are absent or scoped incorrectly. The needed change is to prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples.

D:

Restore relevant supported Analytics ingestion/retention and explicitly validate handler matching against processed log rows. Scope the action to the affected barcode scanner connectivity alerts and egress gateway events environment. FortiAnalyzer event handlers operate on appropriate Analytics logs and cannot infer events from inaccessible archive-only data. The diagnostic evidence here is text filter matches the word anywhere while structured severity and subtype conditions are absent or scoped incorrectly. The preferred remedy is to prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples.

Question 398

A security analyst at a sports venue operations group is investigating an anomaly in turnstile system alerts and concession network logs. The reported behavior is: A scheduled playbook stops responding after a proxy replacement, even though the task JSON and trigger still parse. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Playbook Monitor details show the initial task Success and a subsequent task Failed rather than an all-or-nothing transaction. Verify this observation against turnstile system alerts and concession network logs.
  2. ON_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. Verify this observation against turnstile system alerts and concession network logs.
  3. The connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. Verify this observation against turnstile system alerts and concession network logs.
  4. Playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. Verify this observation against turnstile system alerts and concession network logs.

Explanation

Correct Answer

D:

Playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. Upstream device reachability and local task configuration are separate causes of automation failure. To resolve the observed issue, 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: A security analyst at a sports venue operations group is investigating an anomaly in turnstile system alerts and concession network logs.

Incorrect Answers

A:

Playbook Monitor details show the initial task Success and a subsequent task Failed rather than an all-or-nothing transaction. Overall playbook job failure does not imply every prior action rolled back; task-level results determine safe recovery. The diagnostic evidence here is playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. The appropriate repair is to restore allowed connector path, credentials and trust, then run a harmless connectivity and task-specific test.

B:

ON_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. Trigger-derived variables exist only when the execution context supplies them; manual execution does not invent incident metadata. 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 needed change is to restore allowed connector path, credentials and trust, then run a harmless connectivity and task-specific test.

C:

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. 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 preferred remedy is to restore allowed connector path, credentials and trust, then run a harmless connectivity and task-specific test.

Question 399

The security team at an online education platform proposes this controlled action for assessment portal access records and web security alerts: Validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. The original condition was: A security operator changes an incident status to resolved immediately after one endpoint is isolated, but the same indicator continues appearing from another host. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. A controlled test signature generates the appropriate security log and the report shows its event after regeneration. Validate with representative assessment portal access records and web security alerts traffic.
  2. Controlled events around the day boundary appear in exactly the correct reporting period with no double counting. Validate with representative assessment portal access records and web security alerts traffic.
  3. The revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic. Validate with representative assessment portal access records and web security alerts traffic.
  4. A staged second-host test is identified and tracked instead of being hidden by an administrative closed status. Validate with representative assessment portal access records and web security alerts traffic.

Explanation

Correct Answer

D:

A staged second-host test is identified and tracked instead of being hidden by an administrative closed status. Administrative incident status is not technical evidence that the underlying threat has stopped across the environment. In this case, fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The corresponding correction is to validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. The question describes: The security team at an online education platform proposes this controlled action for assessment portal access records and web security alerts.

Incorrect Answers

A:

A controlled test signature generates the appropriate security log and the report shows its event after regeneration. Chart data depend on specific log types and fields; traffic-log availability does not imply every security report dataset is populated. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The required outcome is that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status.

B:

Controlled events around the day boundary appear in exactly the correct reporting period with no double counting. Report scheduling window boundaries and display-time conversion influence which events enter a report. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The required outcome is that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status. The question describes: The security team at an online education platform proposes this controlled action for assessment portal access records and web security alerts.

C:

The revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The required outcome is that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status.

Question 400

During a FortiAnalyzer 7.6 design review covering reservations security alerts and guest-network logs at a mid-size hotel group, the incident is: Web-filter violations are present on the FortiGate locally but the central SOC's logs show only traffic start and end events. Key diagnostic evidence: FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. Which underlying security-analytics or reporting principle explains the behavior?

  1. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. Apply this reasoning to reservations security alerts and guest-network logs.
  2. Correct source and virtual-domain attribution is necessary for trustworthy SOC conclusions in multi-tenant Fabric deployments. Apply this reasoning to reservations security alerts and guest-network logs.
  3. Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. Apply this reasoning to reservations security alerts and guest-network logs.
  4. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. Apply this reasoning to reservations security alerts and guest-network logs.

Explanation

Correct Answer

A:

The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. In this case, FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. The preferred remedy is to update approved source-side security log selections and verify FortiAnalyzer log categories and parser coverage without broad uncontrolled log flooding. Verify that a controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. The question describes: During a FortiAnalyzer 7.6 design review covering reservations security alerts and guest-network logs at a mid-size hotel group, the incident is: Web-filter violations are present on the FortiGate locally but the central.

Incorrect Answers

B:

Correct source and virtual-domain attribution is necessary for trustworthy SOC conclusions in multi-tenant Fabric deployments. The diagnostic evidence here is FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. The controlling principle here is that the source's selected logging categories determine which evidence is available to downstream analysis and security reporting.

C:

Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. The diagnostic evidence here is FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. The controlling principle here is that the source's selected logging categories determine which evidence is available to downstream analysis and security reporting.

D:

FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. The diagnostic evidence here is FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. The controlling principle here is that the source's selected logging categories determine which evidence is available to downstream analysis and security reporting. The question describes: During a FortiAnalyzer 7.6 design review covering reservations security alerts and guest-network logs at a mid-size hotel group, the incident is: Web-filter violations are present on the FortiGate locally but the central.

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