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

Question 380

The security team at a vocational college proposes this controlled action for student lab security events and staff-directory logs: Reopen or create a linked incident and expand scope based on the new affected host while retaining the original case history. The original condition was: A case is marked resolved after one host is isolated, but the identical indicator appears again from a second workstation. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. Ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences. Validate with representative student lab security events and staff-directory logs traffic.
  2. Retesting yields one intended quarantine action and a resolved job without duplicating changes or losing the failure record. Validate with representative student lab security events and staff-directory logs traffic.
  3. The second-host test is surfaced as actionable after closure, and the first case remains auditable. Validate with representative student lab security events and staff-directory logs traffic.
  4. The analyst report distinguishes reputation hypothesis from locally observed malicious actions and preserves source attribution. Validate with representative student lab security events and staff-directory logs traffic.

Explanation

Correct Answer

C:

The second-host test is surfaced as actionable after closure, and the first case remains auditable. Administrative closure does not invalidate later observed evidence or prove all related assets are contained. In this case, fresh log evidence postdates the closure and maps to a distinct asset not included in containment verification. The corresponding correction is to reopen or create a linked incident and expand scope based on the new affected host while retaining the original case history.

Incorrect Answers

A:

Ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences. Event occurrence frequency does not imply repeated state-changing actions are necessary or safe. The diagnostic evidence here is fresh log evidence postdates the closure and maps to a distinct asset not included in containment verification. The required outcome is that the second-host test is surfaced as actionable after closure, and the first case remains auditable.

B:

Retesting yields one intended quarantine action and a resolved job without duplicating changes or losing the failure record. Overall playbook job failure does not imply every prior action rolled back; task-level results determine safe recovery. The diagnostic evidence here is fresh log evidence postdates the closure and maps to a distinct asset not included in containment verification. The required outcome is that the second-host test is surfaced as actionable after closure, and the first case remains auditable.

D:

The analyst report distinguishes reputation hypothesis from locally observed malicious actions and preserves source attribution. Threat intelligence enrichment adds context but cannot on its own prove local compromise of every communicating endpoint. The diagnostic evidence here is fresh log evidence postdates the closure and maps to a distinct asset not included in containment verification. The required outcome is that the second-host test is surfaced as actionable after closure, and the first case remains auditable.

Question 381

A security analyst at a county public library network is investigating an anomaly in public Wi-Fi events and staff application log streams. The reported behavior is: A custom weekly report claims one account accessed all suspicious destinations, but the workstation address was reassigned between users. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. Verify this observation against public Wi-Fi events and staff application log streams.
  2. The chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. Verify this observation against public Wi-Fi events and staff application log streams.
  3. Internal report job status is Success while output-profile export logs show authentication errors for the storage destination. Verify this observation against public Wi-Fi events and staff application log streams.
  4. Underlying full Analytics query returns different long-tail records than the preaggregated hcache result. Verify this observation against public Wi-Fi events and staff application log streams.

Explanation

Correct Answer

A:

Dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. Report aggregation keys define the claim's granularity; an IP address does not guarantee a stable user identity. A focused response is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. Verify that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim.

Incorrect Answers

B:

The chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. Report charts display the results of selected datasets; a valid chart definition cannot compensate for a query against the wrong log family. The diagnostic evidence here is dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The correction is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution.

C:

Internal report job status is Success while output-profile export logs show authentication errors for the storage destination. Generating a report and exporting it to external storage are independently failure-prone steps. The diagnostic evidence here is dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The practical next step is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution.

D:

Underlying full Analytics query returns different long-tail records than the preaggregated hcache result. 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 appropriate repair is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution.

Question 382

A SOC response plan for inspection platform threats and production network logs at a manufacturing quality laboratory must include both a justified correction and measurable proof. Incident: The SOC dashboard reports double the expected connection count after a new FortiAnalyzer upstream forwarding relationship is enabled. Evidence: Matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. Which combined action-and-verification pair best fits this case?

  1. Action: Select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples. Proof: Endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. Perform both using approved inspection platform threats and production network logs test cases.
  2. Action: Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Proof: A test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. Perform both using approved inspection platform threats and production network logs test cases.
  3. Action: Map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. Proof: New controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors. Perform both using approved inspection platform threats and production network logs test cases.
  4. Action: Align storage quota, Analytics versus Archive retention and external backup with the approved evidence period, monitoring projected growth. Proof: A time-window retention test preserves required historical events and disk usage stays within policy under projected daily volume. Perform both using approved inspection platform threats and production network logs test cases.

Explanation

Correct Answer

C:

The preferred remedy is to map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. A suitable test should demonstrate that new controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors. Perform both using approved inspection platform threats and production network logs test cases. In this case, matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity.

Incorrect Answers

A:

The appropriate repair is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples. The outcome can be verified by confirming that endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. Perform both using approved inspection platform threats and production network logs test cases. Log-source classification must match the producing application's schema before common SOC fields can be trusted. The diagnostic evidence here is matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. The correction is to map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. The acceptance test should confirm that new controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors.

B:

The needed change is to configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Validation should establish that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. Perform both using approved inspection platform threats and production network logs test cases. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. The diagnostic evidence here is matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. The practical next step is to map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. A controlled check should show that new controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors.

D:

To resolve the observed issue, align storage quota, Analytics versus Archive retention and external backup with the approved evidence period, monitoring projected growth. The acceptance test should confirm that a time-window retention test preserves required historical events and disk usage stays within policy under projected daily volume. Perform both using approved inspection platform threats and production network logs test cases. 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 matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. The needed change is to map the approved forwarding topology and remove overlapping duplicate paths or deduplicate through supported controls while preserving one authoritative source. Validation should establish that new controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors.

Question 383

The security team at an airport ground-services contractor proposes this controlled action for baggage application gateway logs and access anomalies: Verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline. The original condition was: An incident timeline places a branch firewall's authentication event several hours after its correlated IPS block although the actions happened together. 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 baggage application gateway logs and access anomalies traffic.
  2. The live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events. Validate with representative baggage application gateway logs and access anomalies traffic.
  3. Controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite. Validate with representative baggage application gateway logs and access anomalies traffic.
  4. Each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records. Validate with representative baggage application gateway logs and access anomalies traffic.

Explanation

Correct Answer

C:

Controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. In this case, source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The corresponding correction is to verify source NTP and time zone handling, preserve original event time fields and display all correlated activity against an agreed timeline.

Incorrect Answers

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. 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 required outcome is that controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite.

B:

The live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events. Security Fabric analytics depend on consistent device identities and membership, not simply identical display names. The diagnostic evidence here is source timestamps and FortiAnalyzer display-time settings use different time zones, and device clocks are not compared to a common reference. The required outcome is that controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite.

D:

Each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records. FortiAnalyzer ADOM scoping controls device and log context; working collection does not guarantee correct tenancy or isolation. 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 required outcome is that controlled events from geographically separated gateways appear in the correct relative order with documented UTC offsets and no silent data rewrite.

Question 384

A SOC response plan for public Wi-Fi events and staff application log streams at a county public library network must include both a justified correction and measurable proof. Incident: Dashboard shows hundreds of malware events and management assumes hundreds of infected hosts. Evidence: Log sample and device inventory reveal many repeated detections from the same endpoint and indicator. Which combined action-and-verification pair best fits this case?

  1. Action: Check application-control logging prerequisites and include unclassified categories in a scoped dashboard query. Proof: An authorized synthetic unclassified flow is visible as such and the known-application totals continue to reconcile to log records. Perform both using approved public Wi-Fi events and staff application log streams test cases.
  2. Action: Separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. Proof: A replay of multiple alerts from one endpoint increments total events while unique affected-host count remains one. Perform both using approved public Wi-Fi events and staff application log streams test cases.
  3. Action: Repair documented parser normalization or adapt the dataset to supported field names and test the SQL against sample rows. Proof: The dataset previews the expected source counts and the report generation completes without dropping valid third-party records. Perform both using approved public Wi-Fi events and staff application log streams test cases.
  4. Action: Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. Proof: The report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration. Perform both using approved public Wi-Fi events and staff application log streams test cases.

Explanation

Correct Answer

B:

To resolve the observed issue, separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. The acceptance test should confirm that a replay of multiple alerts from one endpoint increments total events while unique affected-host count remains one. Perform both using approved public Wi-Fi events and staff application log streams test cases. In this case, log sample and device inventory reveal many repeated detections from the same endpoint and indicator.

Incorrect Answers

A:

The preferred remedy is to check application-control logging prerequisites and include unclassified categories in a scoped dashboard query. A suitable test should demonstrate that an authorized synthetic unclassified flow is visible as such and the known-application totals continue to reconcile to log records. Perform both using approved public Wi-Fi events and staff application log streams test cases. Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. The diagnostic evidence here is log sample and device inventory reveal many repeated detections from the same endpoint and indicator. The appropriate repair is to separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. The outcome can be verified by confirming that a replay of multiple alerts from one endpoint increments total events while unique affected-host count remains one.

C:

A focused response is to repair documented parser normalization or adapt the dataset to supported field names and test the SQL against sample rows. A controlled check should show that the dataset previews the expected source counts and the report generation completes without dropping valid third-party records. Perform both using approved public Wi-Fi events and staff application log streams test cases. Report datasets depend on consistent field schema between ingestion normalization and the query definition. The diagnostic evidence here is log sample and device inventory reveal many repeated detections from the same endpoint and indicator. The preferred remedy is to separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. A suitable test should demonstrate that a replay of multiple alerts from one endpoint increments total events while unique affected-host count remains one.

D:

The correction is to treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. The outcome can be verified by confirming that the report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration. Perform both using approved public Wi-Fi events and staff application log streams test cases. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is log sample and device inventory reveal many repeated detections from the same endpoint and indicator. To resolve the observed issue, separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. The acceptance test should confirm that a replay of multiple alerts from one endpoint increments total events while unique affected-host count remains one.

Question 385

The security team at a renewable-energy operator proposes this controlled action for remote plant intrusion signals and control-network access logs: Bind the chart to a compatible supported dataset and validate log type, field mappings and sample aggregates. The original condition was: An executive top-threat chart returns no values although FortiAnalyzer has current antivirus events. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Validate with representative remote plant intrusion signals and control-network access logs traffic.
  2. A controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. Validate with representative remote plant intrusion signals and control-network access logs traffic.
  3. Customer A receives only its device's report and cannot recover customer B information from filenames or attachments. Validate with representative remote plant intrusion signals and control-network access logs traffic.
  4. Peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Validate with representative remote plant intrusion signals and control-network access logs traffic.

Explanation

Correct Answer

B:

A controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. Report charts display the results of selected datasets; a valid chart definition cannot compensate for a query against the wrong log family. In this case, the chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. The corresponding correction is to bind the chart to a compatible supported dataset and validate log type, field mappings and sample aggregates. The question describes: The security team at a renewable-energy operator proposes this controlled action for remote plant intrusion signals and control-network access logs: Bind the chart to a compatible supported dataset and validate log type,.

Incorrect Answers

A:

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 the chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. The required outcome is that a controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs.

C:

Customer A receives only its device's report and cannot recover customer B information from filenames or attachments. Report type and output profile jointly control distribution, which must respect privacy and ADOM boundaries. The diagnostic evidence here is the chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. The required outcome is that a controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs.

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 the chart references a traffic-only dataset that lacks antivirus subtype fields instead of the corresponding security log dataset. The required outcome is that a controlled antivirus event appears in chart preview and the resulting report counts align with the underlying security logs. The question describes: The security team at a renewable-energy operator proposes this controlled action for remote plant intrusion signals and control-network access logs: Bind the chart to a compatible supported dataset and validate log type,.

Question 386

During an investigation of live contribution network events and newsdesk access logs at a regional media broadcaster, time-sensitive streams need calibrated alerts. The reported failure is: An outsourced SOC analyst assigned to customer A can open security views for customer B after a role migration. The analyst confirms: The user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. 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 live contribution network events and newsdesk access logs environment.
  2. Update approved source-side security log selections and verify FortiAnalyzer log categories and parser coverage without broad uncontrolled log flooding. Scope the action to the affected live contribution network events and newsdesk access logs environment.
  3. Restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests. Scope the action to the affected live contribution network events and newsdesk access logs environment.
  4. Calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Scope the action to the affected live contribution network events and newsdesk access logs environment.

Explanation

Correct Answer

C:

Restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests. Scope the action to the affected live contribution network events and newsdesk access logs environment. SOC features inherit administrative and ADOM authorization boundaries; visibility settings alone are not isolation controls. A focused response is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests. Verify that the user can analyze customer A events but cannot access customer B dashboards, incidents or report data through alternative views.

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 live contribution network events and newsdesk access logs environment. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. The preferred remedy is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.

B:

Update approved source-side security log selections and verify FortiAnalyzer log categories and parser coverage without broad uncontrolled log flooding. Scope the action to the affected live contribution network events and newsdesk access logs environment. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. To resolve the observed issue, restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.

D:

Calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Scope the action to the affected live contribution network events and newsdesk access logs environment. Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. The correction is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.

Question 387

During an investigation of subscriber abuse alerts and customer-edge firewall logs at a rural broadband provider, subscriber identity must not be confused with shared addresses. The reported failure is: Critical URL blocks from one branch never trigger a configured security handler used successfully at headquarters. The analyst confirms: The handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Update the supported upstream task-output mapping and verify the imported task graph and variable resolution before enabling production automation. Scope the action to the affected subscriber abuse alerts and customer-edge firewall logs environment.
  2. Define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. Scope the action to the affected subscriber abuse alerts and customer-edge firewall logs environment.
  3. Inspect per-task status and reconcile device state before retrying only safe idempotent or compensating steps. Scope the action to the affected subscriber abuse alerts and customer-edge firewall logs environment.
  4. Extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. Scope the action to the affected subscriber abuse alerts and customer-edge firewall logs environment.

Explanation

Correct Answer

D:

Extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. Scope the action to the affected subscriber abuse alerts and customer-edge firewall logs environment. Event-handler data selectors define source scope separately from the underlying rule expression. The practical next step is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. Verify that branch and headquarters controls trigger their expected events, and a third-party tenant's logs never match.

Incorrect Answers

A:

Update the supported upstream task-output mapping and verify the imported task graph and variable resolution before enabling production automation. Scope the action to the affected subscriber abuse alerts and customer-edge firewall logs environment. Task output variables must match the playbook's real dependency graph and task identities after export/import changes. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. To resolve the observed issue, extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions.

B:

Define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. Scope the action to the affected subscriber abuse alerts and customer-edge firewall logs environment. Stateful event correlation depends on temporal ordering and shared identifiers, not just the presence of the same log types. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. A focused response is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions.

C:

Inspect per-task status and reconcile device state before retrying only safe idempotent or compensating steps. Scope the action to the affected subscriber abuse alerts and customer-edge firewall logs environment. Overall playbook job failure does not imply every prior action rolled back; task-level results determine safe recovery. The diagnostic evidence here is the handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. The correction is to extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions.

Question 388

During a FortiAnalyzer 7.6 design review covering baggage application gateway logs and access anomalies at an airport ground-services contractor, the incident is: A top-applications view suggests a branch has no unknown applications after a policy change, but users report unclassified SaaS traffic. Key diagnostic evidence: Application-control logs are absent for the relevant policy or the widget excludes unknown application categories. Which underlying security-analytics or reporting principle explains the behavior?

  1. Report datasets depend on consistent field schema between ingestion normalization and the query definition. Apply this reasoning to baggage application gateway logs and access anomalies.
  2. Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. Apply this reasoning to baggage application gateway logs and access anomalies.
  3. Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence. Apply this reasoning to baggage application gateway logs and access anomalies.
  4. Security-event frequency and affected-asset cardinality are different measurements with different incident implications. Apply this reasoning to baggage application gateway logs and access anomalies.

Explanation

Correct Answer

B:

Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. In this case, application-control logs are absent for the relevant policy or the widget excludes unknown application categories. The correction is to check application-control logging prerequisites and include unclassified categories in a scoped dashboard query. Verify that an authorized synthetic unclassified flow is visible as such and the known-application totals continue to reconcile to log records. The question describes: During a FortiAnalyzer 7.6 design review covering baggage application gateway logs and access anomalies at an airport ground-services contractor, the incident is.

Incorrect Answers

A:

Report datasets depend on consistent field schema between ingestion normalization and the query definition. The diagnostic evidence here is application-control logs are absent for the relevant policy or the widget excludes unknown application categories. The controlling principle here is that application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow.

C:

Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence. The diagnostic evidence here is application-control logs are absent for the relevant policy or the widget excludes unknown application categories. The controlling principle here is that application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. The question describes: During a FortiAnalyzer 7.6 design review covering baggage application gateway logs and access anomalies at an airport ground-services contractor, the incident is.

D:

The diagnostic evidence here is application-control logs are absent for the relevant policy or the widget excludes unknown application categories. The controlling principle here is that application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow.

Question 389

The security team at a public housing services agency proposes this controlled action for resident portal events and privileged-access logs: Update the widget's authorized device/log group selection and verify filter semantics against source logs. The original condition was: A custom security dashboard shows no source-IP activity even though raw logs from the affected sites are searchable. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. An authorized synthetic unclassified flow is visible as such and the known-application totals continue to reconcile to log records. Validate with representative resident portal events and privileged-access logs traffic.
  2. The reworked report completes within its service budget and chart totals match validated sample queries. Validate with representative resident portal events and privileged-access logs traffic.
  3. The test device's events appear in both its Log View query and the aligned widget for the same time period. Validate with representative resident portal events and privileged-access logs traffic.
  4. A controlled test signature generates the appropriate security log and the report shows its event after regeneration. Validate with representative resident portal events and privileged-access logs traffic.

Explanation

Correct Answer

C:

The test device's events appear in both its Log View query and the aligned widget for the same time period. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. In this case, widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The corresponding correction is to update the widget's authorized device/log group selection and verify filter semantics against source logs.

Incorrect Answers

A:

An authorized synthetic unclassified flow is visible as such and the known-application totals continue to reconcile to log records. Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The required outcome is that the test device's events appear in both its Log View query and the aligned widget for the same time period.

B:

The reworked report completes within its service budget and chart totals match validated sample queries. 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 widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The required outcome is that the test device's events appear in both its Log View query and the aligned widget for the same time period.

D:

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 widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The required outcome is that the test device's events appear in both its Log View query and the aligned widget for the same time period.

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.

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