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

Question 170

A security analyst at a manufacturing quality laboratory is investigating an anomaly in inspection platform threats and production network logs. The reported behavior is: A security analyst builds an automated incident enrichment playbook but it never runs when new incidents are raised. 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 inspection platform threats and production network logs.
  2. The playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. Verify this observation against inspection platform threats and production network logs.
  3. Notification profile still references a retired email webhook or destination without delivery confirmation. Verify this observation against inspection platform threats and production network logs.
  4. The notification branch runs in parallel and does not depend on successful evidence aggregation. Verify this observation against inspection platform threats and production network logs.

Explanation

Correct Answer

B:

The playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. Playbook triggers govern execution initiation independently of which tasks the playbook contains. A focused response is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Verify that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. The question describes: A security analyst at a manufacturing quality laboratory is investigating an anomaly in inspection platform threats and production 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 the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. To resolve the observed issue, configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. The question describes: A security analyst at a manufacturing quality laboratory is investigating an anomaly in inspection platform threats and production network logs.

C:

Notification profile still references a retired email webhook or destination without delivery confirmation. Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. The diagnostic evidence here is the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The correction is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed.

D:

The notification branch runs in parallel and does not depend on successful evidence aggregation. Playbook task ordering matters to operational completeness, and downstream messages should reflect actual upstream completion. The diagnostic evidence here is the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The practical next step is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed.

Question 171

During an investigation of outpatient booking logs and perimeter threat alerts at a regional hospital network, patient systems need verifiable incident triage during shift changes. The reported failure is: A branch FortiGate sends no telemetry to its newly deployed FortiAnalyzer although local security events continue to occur. The analyst confirms: FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. Scope the action to the affected outpatient booking logs and perimeter threat alerts environment.
  2. Configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. Scope the action to the affected outpatient booking logs and perimeter threat alerts environment.
  3. Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Scope the action to the affected outpatient booking logs and perimeter threat alerts environment.
  4. Verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline. Scope the action to the affected outpatient booking logs and perimeter threat alerts environment.

Explanation

Correct Answer

C:

Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Scope the action to the affected outpatient booking logs and perimeter threat alerts environment. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. The practical next step is to configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Verify that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector.

Incorrect Answers

A:

Map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. Scope the action to the affected outpatient booking logs and perimeter threat alerts environment. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. A focused response is to configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport.

B:

Configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. Scope the action to the affected outpatient booking logs and perimeter threat alerts environment. Archival retention and analytics database availability have different uses; event handlers and reports require appropriate processed analytics data. The diagnostic evidence here is FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The correction is to configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport.

D:

Verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline. Scope the action to the affected outpatient booking logs and perimeter threat alerts environment. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. The diagnostic evidence here is FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The appropriate repair is to configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport.

Question 172

A SOC response plan for nonemergency dispatch audit events and perimeter alerts at a regional emergency response center must include both a justified correction and measurable proof. Incident: A weekly operations report misses the current Monday's urgent incidents because its date range means the previous calendar week. Evidence: Settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. Which combined action-and-verification pair best fits this case?

  1. Action: Repair the external report storage account or credentials and implement expiry/transfer failure monitoring. Proof: A controlled generated report arrives in the authorized archive with matching checksum and no extra copies. Perform both using approved nonemergency dispatch audit events and perimeter alerts test cases.
  2. 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 nonemergency dispatch audit events and perimeter alerts test cases.
  3. 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 nonemergency dispatch audit events and perimeter alerts test cases.
  4. Action: Verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. Proof: Back-to-back customer A and B runs show correct segregated records and no cross-tenant source values. Perform both using approved nonemergency dispatch audit events and perimeter alerts test cases.

Explanation

Correct Answer

B:

The needed change is to select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior. Validation should establish 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 nonemergency dispatch audit events and perimeter alerts test cases. In this case, settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. Calendar-period and rolling-window selectors have different semantics even when both appear weekly.

Incorrect Answers

A:

The appropriate repair is to repair the external report storage account or credentials and implement expiry/transfer failure monitoring. The outcome can be verified by confirming that a controlled generated report arrives in the authorized archive with matching checksum and no extra copies. Perform both using approved nonemergency dispatch audit events and perimeter alerts test cases. Generating a report and exporting it to external storage are independently failure-prone steps. The diagnostic evidence here is settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. The correction 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.

C:

The preferred remedy is to regenerate the report for the specified period after approving the new definition and preserve historical version provenance. A suitable test should demonstrate that the new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time. Perform both using approved nonemergency dispatch audit events and perimeter alerts test cases. Report definitions control future generation; they do not retroactively rewrite previously generated report artifacts. The diagnostic evidence here is settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. The appropriate repair is to select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior. The outcome can be verified by confirming that events at the start and end of the intended period appear exactly once and date-range labels match the actual query.

D:

To resolve the observed issue, verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. The acceptance test should confirm that back-to-back customer A and B runs show correct segregated records and no cross-tenant source values. Perform both using approved nonemergency dispatch audit events and perimeter alerts test cases. Report filter caching and query scope require tenant-aware validation, especially when a definition is reused. The diagnostic evidence here is settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. The needed change is to select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior. Validation should establish that events at the start and end of the intended period appear exactly once and date-range labels match the actual query.

Question 173

A SOC response plan for branch authentication alerts and payment traffic logs at a regional banking cooperative must include both a justified correction and measurable proof. Incident: A privileged-access anomaly creates an incident but remains unassigned while a different analyst team receives unrelated application cases. Evidence: Incident rules or analyst assignment policy use the source device group rather than the service owner or event classification. Which combined action-and-verification pair best fits this case?

  1. Action: Configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Proof: A controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. Perform both using approved branch authentication alerts and payment traffic logs test cases.
  2. Action: Map event categories to approved incident assignment and escalation rules with explicit fallback for unmapped sources. Proof: Sample incidents route to their responsible team with auditable ownership and none remain orphaned past the response time target. Perform both using approved branch authentication alerts and payment traffic logs test cases.
  3. 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 branch authentication alerts and payment traffic logs test cases.
  4. Action: Update the supported upstream task-output mapping and verify the imported task graph and variable resolution before enabling production automation. Proof: An incident test receives the expected generated report from the current task, and missing source outputs are logged explicitly. Perform both using approved branch authentication alerts and payment traffic logs test cases.

Explanation

Correct Answer

B:

The preferred remedy is to map event categories to approved incident assignment and escalation rules with explicit fallback for unmapped sources. A suitable test should demonstrate that sample incidents route to their responsible team with auditable ownership and none remain orphaned past the response time target. Perform both using approved branch authentication alerts and payment traffic logs test cases. In this case, incident rules or analyst assignment policy use the source device group rather than the service owner or event classification. An incident's existence does not guarantee triage ownership; response workflow assignment is an additional operational decision.

Incorrect Answers

A:

The needed change is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Validation should establish that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. Perform both using approved branch authentication alerts and payment traffic logs test cases. Playbook triggers govern execution initiation independently of which tasks the playbook contains. The diagnostic evidence here is incident rules or analyst assignment policy use the source device group rather than the service owner or event classification. The practical next step is to map event categories to approved incident assignment and escalation rules with explicit fallback for unmapped sources. A controlled check should show that sample incidents route to their responsible team with auditable ownership and none remain orphaned past the response time target.

C:

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 branch authentication alerts and payment traffic logs test cases. Event-handler data selectors define source scope separately from the underlying rule expression. The diagnostic evidence here is incident rules or analyst assignment policy use the source device group rather than the service owner or event classification. The needed change is to map event categories to approved incident assignment and escalation rules with explicit fallback for unmapped sources. Validation should establish that sample incidents route to their responsible team with auditable ownership and none remain orphaned past the response time target.

D:

A focused response is to update the supported upstream task-output mapping and verify the imported task graph and variable resolution before enabling production automation. A controlled check should show that an incident test receives the expected generated report from the current task, and missing source outputs are logged explicitly. Perform both using approved branch authentication alerts and payment traffic logs test cases. Task output variables must match the playbook's real dependency graph and task identities after export/import changes. The diagnostic evidence here is incident rules or analyst assignment policy use the source device group rather than the service owner or event classification. The preferred remedy is to map event categories to approved incident assignment and escalation rules with explicit fallback for unmapped sources. A suitable test should demonstrate that sample incidents route to their responsible team with auditable ownership and none remain orphaned past the response time target.

Question 174

The security team at a mid-size hotel group proposes this controlled action for reservations security alerts and guest-network logs: Update approved source-side security log selections and verify FortiAnalyzer log categories and parser coverage without broad uncontrolled log flooding. The original condition was: Web-filter violations are present on the FortiGate locally but the central SOC's logs show only traffic start and end events. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. A controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. Validate with representative reservations security alerts and guest-network logs traffic.
  2. The approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized. Validate with representative reservations security alerts and guest-network logs traffic.
  3. A test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. Validate with representative reservations security alerts and guest-network logs traffic.
  4. A time-window retention test preserves required historical events and disk usage stays within policy under projected daily volume. Validate with representative reservations security alerts and guest-network logs traffic.

Explanation

Correct Answer

A:

A controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. In this case, FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. The corresponding correction is to update approved source-side security log selections and verify FortiAnalyzer log categories and parser coverage without broad uncontrolled log flooding. The question describes: The security team at a mid-size hotel group proposes this controlled action for reservations security alerts and guest-network logs.

Incorrect Answers

B:

The approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized. Receiving a connection and trusting a log-producing device are separate operations; registration and domain placement determine analyst access. The diagnostic evidence here is FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. The required outcome is that a controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. The question describes: The security team at a mid-size hotel group proposes this controlled action for reservations security alerts and guest-network logs.

C:

A test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. 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 required outcome is that a controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent.

D:

A time-window retention test preserves required historical events and disk usage stays within policy under projected daily volume. Analyzable history is constrained by log aging policies and storage allocation, not just whether the current logging connection is healthy. The diagnostic evidence here is FortiGate log forwarding filters include traffic entries while suppressing the relevant security subtype needed for detection. The required outcome is that a controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent.

Question 175

During a FortiAnalyzer 7.6 design review covering ticket validation events and remote-depot firewall logs at a municipal transit operator, the incident is: The first step of a suspicious login-to-exfiltration sequence is missing from the investigation because the query begins after authentication. Key diagnostic evidence: The event window excludes the earlier login and only includes later DNS or data-transfer entries. Which underlying security-analytics or reporting principle explains the behavior?

  1. Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. Apply this reasoning to ticket validation events and remote-depot firewall logs.
  2. Source IP is a temporary network identifier; defensible historical attribution needs time-specific supporting evidence. Apply this reasoning to ticket validation events and remote-depot firewall logs.
  3. A visualization's aggregation window determines which activity dominates rankings; historical volume can conceal short events. Apply this reasoning to ticket validation events and remote-depot firewall logs.
  4. Evidence-driven log searching must account for producer-specific field names and structured filters rather than assuming one universal field. Apply this reasoning to ticket validation events and remote-depot firewall logs.

Explanation

Correct Answer

A:

Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. In this case, the event window excludes the earlier login and only includes later DNS or data-transfer entries. The needed change is to expand the time range based on incident chronology and join evidence by endpoint/user/device with clock-corrected timestamps. Verify that a controlled sequence displays the precursor, detection and follow-up traffic in order without adding unrelated users' activity.

Incorrect Answers

B:

Source IP is a temporary network identifier; defensible historical attribution needs time-specific supporting evidence. The diagnostic evidence here is the event window excludes the earlier login and only includes later DNS or data-transfer entries. The controlling principle here is that incident causality requires a complete relevant time window rather than a convenient snapshot of later logs.

C:

A visualization's aggregation window determines which activity dominates rankings; historical volume can conceal short events. The diagnostic evidence here is the event window excludes the earlier login and only includes later DNS or data-transfer entries. The controlling principle here is that incident causality requires a complete relevant time window rather than a convenient snapshot of later logs.

D:

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 the event window excludes the earlier login and only includes later DNS or data-transfer entries. The controlling principle here is that incident causality requires a complete relevant time window rather than a convenient snapshot of later logs.

Question 176

During an investigation of care referral alerts and clinic firewall telemetry at a pediatric clinic consortium, clinical traffic and security monitoring need clear separation. The reported failure is: A scheduled management report displays only the original four stores after a fifth FortiGate was registered correctly. The analyst confirms: Report Settings uses an explicit device list that was never updated for the fifth device. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. Scope the action to the affected care referral alerts and clinic firewall telemetry environment.
  2. Expand the time range based on incident chronology and join evidence by endpoint/user/device with clock-corrected timestamps. Scope the action to the affected care referral alerts and clinic firewall telemetry environment.
  3. Distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Scope the action to the affected care referral alerts and clinic firewall telemetry environment.
  4. Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Scope the action to the affected care referral alerts and clinic firewall telemetry environment.

Explanation

Correct Answer

A:

Reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. Scope the action to the affected care referral alerts and clinic firewall telemetry environment. Report source-device filters are independent from device registration and must track the intended scope. The preferred remedy is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. Verify that a control event from the fifth store appears in the next generated report and unrelated tenants remain excluded.

Incorrect Answers

B:

Expand the time range based on incident chronology and join evidence by endpoint/user/device with clock-corrected timestamps. Scope the action to the affected care referral alerts and clinic firewall telemetry environment. Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. To resolve the observed issue, reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries.

C:

Distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Scope the action to the affected care referral alerts and clinic firewall telemetry environment. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. A focused response is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries.

D:

Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Scope the action to the affected care referral alerts and clinic firewall telemetry environment. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. The correction is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries.

Question 177

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

  1. A controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. Validate with representative specimen database access events and archive security alerts traffic.
  2. A test run produces the custom view while the original shared template still generates its expected layout. Validate with representative specimen database access events and archive security alerts traffic.
  3. A controlled generated report arrives in the authorized archive with matching checksum and no extra copies. Validate with representative specimen database access events and archive security alerts traffic.
  4. Peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Validate with representative specimen database access events and archive security alerts traffic.

Explanation

Correct Answer

A:

A controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. SQL datasets can only filter and aggregate attributes that exist in their selected log schema. In this case, dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. The corresponding correction is to restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. The question describes: The security team at a natural-history archive proposes this controlled action for specimen database access events and archive security alerts: Restore the correct supported security log source and adapt the dataset fields.

Incorrect Answers

B:

A test run produces the custom view while the original shared template still generates its expected layout. Report customization needs versioned ownership to avoid collateral changes to shared approved reporting assets. The diagnostic evidence here is dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. The required outcome is that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. The question describes: The security team at a natural-history archive proposes this controlled action for specimen database access events and archive security alerts: Restore the correct supported security log source and adapt the dataset fields.

C:

A controlled generated report arrives in the authorized archive with matching checksum and no extra copies. Generating a report and exporting it to external storage are independently failure-prone steps. The diagnostic evidence here is dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. The required outcome is that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data.

D:

Peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Reporting workloads consume shared processing resources; analytics capacity planning must include peak query as well as log ingestion demand. The diagnostic evidence here is dataset preview reveals the attack field is unavailable in the selected traffic type and relevant IPS records are separate. The required outcome is that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data.

Question 178

The security team at a county public library network proposes this controlled action for public Wi-Fi events and staff application log streams: Add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. The original condition was: A custom weekly report claims one account accessed all suspicious destinations, but the workstation address was reassigned between users. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. Sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation. Validate with representative public Wi-Fi events and staff application log streams traffic.
  2. A controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. Validate with representative public Wi-Fi events and staff application log streams traffic.
  3. The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Validate with representative public Wi-Fi events and staff application log streams traffic.
  4. Synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim. Validate with representative public Wi-Fi events and staff application log streams traffic.

Explanation

Correct Answer

D:

Synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim. Report aggregation keys define the claim's granularity; an IP address does not guarantee a stable user identity. In this case, dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The corresponding correction is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. The question describes: The security team at a county public library network proposes this controlled action for public Wi-Fi events and staff application log streams: Add documented identity and time context to the dataset or label IP-only.

Incorrect Answers

A:

Sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation. Aggregation caches trade resources and speed against result detail; not every cached chart is suitable as exact audit evidence. The diagnostic evidence here is dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The required outcome is that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim.

B:

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 dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The required outcome is that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim.

C:

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 dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The required outcome is that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim.

Question 179

During an investigation of baggage application gateway logs and access anomalies at an airport ground-services contractor, incident timelines must survive busy shifts. The reported failure is: An incident timeline places a branch firewall's authentication event several hours after its correlated IPS block although the actions happened together. The analyst confirms: Source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources. Scope the action to the affected baggage application gateway logs and access anomalies environment.
  2. Verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline. Scope the action to the affected baggage application gateway logs and access anomalies environment.
  3. Calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Scope the action to the affected baggage application gateway logs and access anomalies environment.
  4. Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Scope the action to the affected baggage application gateway logs and access anomalies environment.

Explanation

Correct Answer

B:

Verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline. Scope the action to the affected baggage application gateway logs and access anomalies environment. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. The practical next step is to verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline. Verify that controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite.

Incorrect Answers

A:

Register and authorize the intended serial-number identity, assign the correct ADOM and verify logs after authorization without blindly trusting unknown sources. Scope the action to the affected baggage application gateway logs and access anomalies environment. Receiving a connection and trusting a log-producing device are separate operations; registration and domain placement determine analyst access. The diagnostic evidence here is source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The correction is to verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline.

C:

Calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Scope the action to the affected baggage application gateway logs and access anomalies environment. Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. The diagnostic evidence here is source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The appropriate repair is to verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline.

D:

Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Scope the action to the affected baggage application gateway logs and access anomalies environment. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. The diagnostic evidence here is source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The needed change is to verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline.

Question 180

A SOC response plan for benefit portal access alerts and privileged session logs at a pension administration office must include both a justified correction and measurable proof. Incident: Executives receive a zero-page incident PDF even though FortiAnalyzer's report history lists a completed run with populated charts. Evidence: Report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. Which combined action-and-verification pair best fits this case?

  1. Action: Compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. Proof: The delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient. Perform both using approved benefit portal access alerts and privileged session logs test cases.
  2. Action: Validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. Proof: A staged second-host test is identified and tracked instead of being hidden by an administrative closed status. Perform both using approved benefit portal access alerts and privileged session logs test cases.
  3. Action: Evaluate supported auto-cache/high-accuracy options and narrow expensive datasets or schedules while measuring resource impact. Proof: The reworked report completes within its service budget and chart totals match validated sample queries. Perform both using approved benefit portal access alerts and privileged session logs test cases.
  4. Action: Correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields. Proof: A controlled prohibited request shows the intended security action and related traffic context without overcounting allowed sessions. Perform both using approved benefit portal access alerts and privileged session logs test cases.

Explanation

Correct Answer

A:

The needed change is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. The acceptance test should confirm that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient. Perform both using approved benefit portal access alerts and privileged session logs test cases. In this case, 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.

Incorrect Answers

B:

The preferred remedy is to validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. A controlled check should show that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status. Perform both using approved benefit portal access alerts and privileged session logs test cases. Administrative incident status is not technical evidence that the underlying threat has stopped across the environment. The diagnostic evidence here is report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. The appropriate repair is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. A suitable test should demonstrate that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.

C:

To resolve the observed issue, evaluate supported auto-cache/high-accuracy options and narrow expensive datasets or schedules while measuring resource impact. The outcome can be verified by confirming that the reworked report completes within its service budget and chart totals match validated sample queries. Perform both using approved benefit portal access alerts and privileged session logs test cases. Report caching can improve performance but has resource and accuracy tradeoffs; a slow report is not necessarily a malformed report. The diagnostic evidence here is report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. The needed change is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. The acceptance test should confirm that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.

D:

A focused response is to correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields. Validation should establish that a controlled prohibited request shows the intended security action and related traffic context without overcounting allowed sessions. Perform both using approved benefit portal access alerts and privileged session logs test cases. FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. The diagnostic evidence here is report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. The preferred remedy is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. A controlled check should show that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.

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