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

Question 160

During a FortiAnalyzer 7.6 design review covering river sensor gateway logs and remote site alerts at a hydrology research nonprofit, the incident is: A blocked outbound HTTPS attempt is counted as an allowed user session because the analyst examines only the traffic disposition. Key diagnostic evidence: Related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. Which underlying security-analytics or reporting principle explains the behavior?

  1. A successful data query and a correctly delivered report artifact are separate stages that require their own checks. Apply this reasoning to river sensor gateway logs and remote site alerts.
  2. FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. Apply this reasoning to river sensor gateway logs and remote site alerts.
  3. Report scheduling window boundaries and display-time conversion influence which events enter a report. Apply this reasoning to river sensor gateway logs and remote site alerts.
  4. Report datasets depend on consistent field schema between ingestion normalization and the query definition. Apply this reasoning to river sensor gateway logs and remote site alerts.

Explanation

Correct Answer

B:

FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. In this case, related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. The needed change is to correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields. Verify that a controlled prohibited request shows the intended security action and related traffic context without overcounting allowed sessions.

Incorrect Answers

A:

A successful data query and a correctly delivered report artifact are separate stages that require their own checks. The diagnostic evidence here is related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. The controlling principle here is that FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event.

C:

Report scheduling window boundaries and display-time conversion influence which events enter a report. The diagnostic evidence here is related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. The controlling principle here is that FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event.

D:

Report datasets depend on consistent field schema between ingestion normalization and the query definition. The diagnostic evidence here is related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. The controlling principle here is that FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event.

Question 161

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

  1. A staged second-host test is identified and tracked instead of being hidden by an administrative closed status. Validate with representative remote plant intrusion signals and control-network access logs traffic.
  2. The report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration. Validate with representative remote plant intrusion signals and control-network access logs traffic.
  3. Controlled events around the day boundary appear in exactly the correct reporting period with no double counting. Validate with representative remote plant intrusion signals and control-network access logs traffic.
  4. The incident report documents which time windows support FortiView and demonstrates a current-day control record in both Log View and the visualization. Validate with representative remote plant intrusion signals and control-network access logs traffic.

Explanation

Correct Answer

A:

A staged second-host test is identified and tracked instead of being hidden by an administrative closed status. Administrative incident status is not technical evidence that the underlying threat has stopped across the environment. In this case, fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The corresponding correction is to validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate.

Incorrect Answers

B:

The report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The required outcome is that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status.

C:

Controlled events around the day boundary appear in exactly the correct reporting period with no double counting. Report scheduling window boundaries and display-time conversion influence which events enter a report. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The required outcome is that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status.

D:

The incident report documents which time windows support FortiView and demonstrates a current-day control record in both Log View and the visualization. Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. The diagnostic evidence here is fresh correlated logs and indicator matches arrive after the closed incident's timestamp, tied to a second machine. The required outcome is that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status.

Question 162

During a FortiAnalyzer 7.6 design review covering cold-chain telemetry alerts and warehouse firewall events at a chilled-food logistics company, the incident is: A Log View search reports no traffic between two hosts even though users reproduce an application access failure. Key diagnostic evidence: The search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. Which underlying security-analytics or reporting principle explains the behavior?

  1. Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence. Apply this reasoning to cold-chain telemetry alerts and warehouse firewall events.
  2. Security-event frequency and affected-asset cardinality are different measurements with different incident implications. Apply this reasoning to cold-chain telemetry alerts and warehouse firewall events.
  3. Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. Apply this reasoning to cold-chain telemetry alerts and warehouse firewall events.
  4. FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. Apply this reasoning to cold-chain telemetry alerts and warehouse firewall events.

Explanation

Correct Answer

A:

Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence. In this case, the search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. The preferred remedy is to inspect effective action values and build a comprehensive scoped source/destination/time filter before assuming no network evidence exists. Verify that a replayed denied flow appears with the policy/action and the count agrees with the FortiGate local observation.

Incorrect Answers

B:

The diagnostic evidence here is the search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. The controlling principle here is that negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence.

C:

Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. The diagnostic evidence here is the search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. The controlling principle here is that negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence.

D:

FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. The diagnostic evidence here is the search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. The controlling principle here is that negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence.

Question 163

During an investigation of resident portal events and privileged-access logs at a public housing services agency, casework records need least-privilege incident handling. The reported failure is: An analyst uses a high-volume chart's cached top-N values as an exact security incident count for financial certification. The analyst confirms: Underlying full Analytics query returns different long-tail records than the preaggregated hcache result. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Move resource-heavy report jobs to a safe window, optimize datasets and consider supported capacity tuning without disabling essential security logging. Scope the action to the affected resident portal events and privileged-access logs environment.
  2. Document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required. Scope the action to the affected resident portal events and privileged-access logs environment.
  3. Restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. Scope the action to the affected resident portal events and privileged-access logs environment.
  4. Standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. Scope the action to the affected resident portal events and privileged-access logs environment.

Explanation

Correct Answer

B:

Document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required. Scope the action to the affected resident portal events and privileged-access logs environment. Aggregation caches trade resources and speed against result detail; not every cached chart is suitable as exact audit evidence. A focused response is to document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required. Verify that sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation.

Incorrect Answers

A:

Move resource-heavy report jobs to a safe window, optimize datasets and consider supported capacity tuning without disabling essential security logging. Scope the action to the affected resident portal events and privileged-access logs environment. Reporting workloads consume shared processing resources; analytics capacity planning must include peak query as well as log ingestion demand. The diagnostic evidence here is underlying full Analytics query returns different long-tail records than the preaggregated hcache result. To resolve the observed issue, document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required.

C:

Restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. Scope the action to the affected resident portal events and privileged-access logs environment. SQL datasets can only filter and aggregate attributes that exist in their selected log schema. The diagnostic evidence here is underlying full Analytics query returns different long-tail records than the preaggregated hcache result. The correction is to document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required.

D:

Standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. Scope the action to the affected resident portal events and privileged-access logs environment. Report identity includes its time-zone semantics, not just the stored PDF bytes. The diagnostic evidence here is underlying full Analytics query returns different long-tail records than the preaggregated hcache result. The practical next step is to document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required.

Question 164

The security team at a city parks administration proposes this controlled action for public event portal traffic and staff system alerts: Restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. The original condition was: An incident in one customer's ADOM triggers an automation that attempts to block an address on another customer's firewall. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. Two independently staged tenant detections produce separately owned incidents and each preserves its supporting evidence. Validate with representative public event portal traffic and staff system alerts traffic.
  2. A controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value. Validate with representative public event portal traffic and staff system alerts traffic.
  3. A controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched. Validate with representative public event portal traffic and staff system alerts traffic.
  4. Test failures followed by success raise one correlated event and reversed benign order does not. Validate with representative public event portal traffic and staff system alerts traffic.

Explanation

Correct Answer

C:

A controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched. Automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants. In this case, the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The corresponding correction is to restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. The question describes: The security team at a city parks administration proposes this controlled action for public event portal traffic and staff system alerts: Restrict connector targets, map source identity safely and add a negative cross-tenant.

Incorrect Answers

A:

Two independently staged tenant detections produce separately owned incidents and each preserves its supporting evidence. A shared indicator does not establish common incident ownership across isolated administrative domains. The diagnostic evidence here is the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The required outcome is that a controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched.

B:

A controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value. Threat indicators must preserve their type and canonical representation to support meaningful enrichment and correlation. The diagnostic evidence here is the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The required outcome is that a controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched.

D:

Test failures followed by success raise one correlated event and reversed benign order does not. 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 connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The required outcome is that a controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched.

Question 165

During an investigation of customer ticket service events and engineer VPN logs at a cloud software support provider, tenant investigations must not expose other clients. The reported failure is: Third-party authentication events reach FortiAnalyzer, but normalized source-address and user fields are empty in SOC filters. The analyst confirms: Raw syslog records contain source identity strings while the assigned SIEM parser mapping omits their fields. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Choose or customize a supported parser and map source values into appropriate normalized fields, validating representative events before production use. Scope the action to the affected customer ticket service events and engineer VPN logs 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 customer ticket service events and engineer VPN logs environment.
  3. Size the Collector or Analyzer for sustained and peak logs per second, investigate dropped buffers and distribute collectors without relaxing essential log coverage. Scope the action to the affected customer ticket service events and engineer VPN logs environment.
  4. Inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping. Scope the action to the affected customer ticket service events and engineer VPN logs environment.

Explanation

Correct Answer

A:

Choose or customize a supported parser and map source values into appropriate normalized fields, validating representative events before production use. Scope the action to the affected customer ticket service events and engineer VPN logs environment. Field normalization is a semantic mapping step between received raw logs and common analytics queries; transmission alone does not create correct fields. The correction is to choose or customize a supported parser and map source values into appropriate normalized fields, validating representative events before production use. Verify that two different test identities and addresses normalize into the expected searchable fields and raw originals stay available for audit.

Incorrect Answers

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 customer ticket service events and engineer VPN logs environment. Reliable correlation requires normalized time semantics and clock discipline; display-time conversion can otherwise mislead the investigation. The diagnostic evidence here is raw syslog records contain source identity strings while the assigned SIEM parser mapping omits their fields. The practical next step is to choose or customize a supported parser and map source values into appropriate normalized fields, validating representative events before production use.

C:

Size the Collector or Analyzer for sustained and peak logs per second, investigate dropped buffers and distribute collectors without relaxing essential log coverage. Scope the action to the affected customer ticket service events and engineer VPN logs environment. Centralized log collection requires realistic rate and storage capacity planning; adding senders cannot exceed finite ingestion resources without loss. The diagnostic evidence here is raw syslog records contain source identity strings while the assigned SIEM parser mapping omits their fields. The appropriate repair is to choose or customize a supported parser and map source values into appropriate normalized fields, validating representative events before production use.

D:

Inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping. Scope the action to the affected customer ticket service events and engineer VPN logs environment. A detection mapping describes capability or intent and cannot by itself prove that required telemetry and working rules exist. The diagnostic evidence here is raw syslog records contain source identity strings while the assigned SIEM parser mapping omits their fields. The needed change is to choose or customize a supported parser and map source values into appropriate normalized fields, validating representative events before production use.

Question 166

A SOC response plan for claims portal access anomalies and web security logs at a community health insurer must include both a justified correction and measurable proof. Incident: An analyst edits the weekly report template and assumes already distributed PDFs automatically reflect its new chart. Evidence: Report history contains immutable older generated files with the previous layout while the definition has changed. Which combined action-and-verification pair best fits this case?

  1. Action: Regenerate the report for the specified period after approving the new definition and preserve historical version provenance. Proof: The new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time. Perform both using approved claims portal access anomalies and web security logs test cases.
  2. Action: Standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. Proof: The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Perform both using approved claims portal access anomalies and web security logs test cases.
  3. Action: Align report macro dataset scope and chart dataset scope to the authorized tenant and time window. Proof: Macros and charts reconcile under a controlled per-tenant sample without leaking another customer's aggregate values. Perform both using approved claims portal access anomalies and web security logs test cases.
  4. 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 claims portal access anomalies and web security logs test cases.

Explanation

Correct Answer

A:

The needed change is to regenerate the report for the specified period after approving the new definition and preserve historical version provenance. A controlled check should show that the new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time. Perform both using approved claims portal access anomalies and web security logs test cases. In this case, report history contains immutable older generated files with the previous layout while the definition has changed. Report definitions control future generation; they do not retroactively rewrite previously generated report artifacts.

Incorrect Answers

B:

The preferred remedy is to standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. The outcome can be verified by confirming that the PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Perform both using approved claims portal access anomalies and web security logs test cases. Report identity includes its time-zone semantics, not just the stored PDF bytes. The diagnostic evidence here is report history contains immutable older generated files with the previous layout while the definition has changed. The appropriate repair is to regenerate the report for the specified period after approving the new definition and preserve historical version provenance. The acceptance test should confirm that the new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time.

C:

To resolve the observed issue, align report macro dataset scope and chart dataset scope to the authorized tenant and time window. Validation should establish that macros and charts reconcile under a controlled per-tenant sample without leaking another customer's aggregate values. Perform both using approved claims portal access anomalies and web security logs test cases. Macros are dataset-backed computations and must receive the same scoping assumptions as other report elements. The diagnostic evidence here is report history contains immutable older generated files with the previous layout while the definition has changed. The needed change is to regenerate the report for the specified period after approving the new definition and preserve historical version provenance. A controlled check should show that the new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time.

D:

A focused response is to repair the external report storage account or credentials and implement expiry/transfer failure monitoring. A suitable test should demonstrate that a controlled generated report arrives in the authorized archive with matching checksum and no extra copies. Perform both using approved claims portal access anomalies and web security logs test cases. Generating a report and exporting it to external storage are independently failure-prone steps. The diagnostic evidence here is report history contains immutable older generated files with the previous layout while the definition has changed. The preferred remedy is to regenerate the report for the specified period after approving the new definition and preserve historical version provenance. The outcome can be verified by confirming that the new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time.

Question 167

During an investigation of nonemergency dispatch audit events and perimeter alerts at a regional emergency response center, staff require precise escalation without false urgency. The reported failure is: A cyber review reports an internal health-check destination as the organization's most risky website because all DNS and web logs are ranked together. The analyst confirms: Source logs indicate the dominant destination is a scheduled internal agent with a different risk profile from end-user browsing. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Repair documented parser normalization or adapt the dataset to supported field names and test the SQL against sample rows. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment.
  2. Reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment.
  3. Compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment.
  4. Distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment.

Explanation

Correct Answer

D:

Distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. To resolve the observed issue, distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Verify that the revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic.

Incorrect Answers

A:

Repair documented parser normalization or adapt the dataset to supported field names and test the SQL against sample rows. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment. Report datasets depend on consistent field schema between ingestion normalization and the query definition. The diagnostic evidence here is source logs indicate the dominant destination is a scheduled internal agent with a different risk profile from end-user browsing. The appropriate repair is to distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters.

B:

Reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment. Report source-device filters are independent from device registration and must track the intended scope. The diagnostic evidence here is source logs indicate the dominant destination is a scheduled internal agent with a different risk profile from end-user browsing. The needed change is to distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters.

C:

Compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment. A successful data query and a correctly delivered report artifact are separate stages that require their own checks. The diagnostic evidence here is source logs indicate the dominant destination is a scheduled internal agent with a different risk profile from end-user browsing. The preferred remedy is to distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters.

Question 168

During a FortiAnalyzer 7.6 design review covering cold-chain telemetry alerts and warehouse firewall events at a chilled-food logistics company, the incident is: A predefined attack handler never produces detections despite retained raw log files from last week. Key diagnostic evidence: Archive files exist but the handler's required Analytics log rows are absent for that interval. Which underlying security-analytics or reporting principle explains the behavior?

  1. FortiAnalyzer event handlers operate on appropriate Analytics logs and cannot infer events from inaccessible archive-only data. Apply this reasoning to cold-chain telemetry alerts and warehouse firewall events.
  2. Playbook task ordering matters to operational completeness, and downstream messages should reflect actual upstream completion. Apply this reasoning to cold-chain telemetry alerts and warehouse firewall events.
  3. Automation variables carry source data, not implicit trust; unsafe input handling can turn a detection into an unauthorized response. Apply this reasoning to cold-chain telemetry alerts and warehouse firewall events.
  4. Event-handler data selectors define source scope separately from the underlying rule expression. Apply this reasoning to cold-chain telemetry alerts and warehouse firewall events.

Explanation

Correct Answer

A:

FortiAnalyzer event handlers operate on appropriate Analytics logs and cannot infer events from inaccessible archive-only data. In this case, archive files exist but the handler's required Analytics log rows are absent for that interval. The needed change is to restore relevant supported Analytics ingestion/retention and explicitly validate handler matching against processed log rows. Verify that a test threat log produces the expected event in the correct ADOM while raw historical retention remains intact.

Incorrect Answers

B:

Playbook task ordering matters to operational completeness, and downstream messages should reflect actual upstream completion. The diagnostic evidence here is archive files exist but the handler's required Analytics log rows are absent for that interval. The controlling principle here is that FortiAnalyzer event handlers operate on appropriate Analytics logs and cannot infer events from inaccessible archive-only data.

C:

Automation variables carry source data, not implicit trust; unsafe input handling can turn a detection into an unauthorized response. The diagnostic evidence here is archive files exist but the handler's required Analytics log rows are absent for that interval. The controlling principle here is that FortiAnalyzer event handlers operate on appropriate Analytics logs and cannot infer events from inaccessible archive-only data.

D:

Event-handler data selectors define source scope separately from the underlying rule expression. The diagnostic evidence here is archive files exist but the handler's required Analytics log rows are absent for that interval. The controlling principle here is that FortiAnalyzer event handlers operate on appropriate Analytics logs and cannot infer events from inaccessible archive-only data.

Question 169

During an investigation of checkout firewall alerts and replenishment system logs at a high-street retail chain, store-security events need reliable cross-site correlation. The reported failure is: A weekly intrusion report is blank for a new firewall even though ordinary permitted traffic appears in a different report. The analyst confirms: The target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Update the widget's authorized device/log group selection and verify filter semantics against source logs. Scope the action to the affected checkout firewall alerts and replenishment system logs environment.
  2. Use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging. Scope the action to the affected checkout firewall alerts and replenishment system logs environment.
  3. Reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View. Scope the action to the affected checkout firewall alerts and replenishment system logs environment.
  4. Reconstruct identity using time-bounded DHCP and authentication evidence plus endpoint identifiers before attaching alerts to a person or device. Scope the action to the affected checkout firewall alerts and replenishment system logs environment.

Explanation

Correct Answer

B:

Use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging. Scope the action to the affected checkout firewall alerts and replenishment system logs environment. Chart data depend on specific log types and fields; traffic-log availability does not imply every security report dataset is populated. To resolve the observed issue, use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging. Verify that a controlled test signature generates the appropriate security log and the report shows its event after regeneration.

Incorrect Answers

A:

Update the widget's authorized device/log group selection and verify filter semantics against source logs. Scope the action to the affected checkout firewall alerts and replenishment system logs environment. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. The diagnostic evidence here is the target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. The preferred remedy is to use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging.

C:

Reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View. Scope the action to the affected checkout firewall alerts and replenishment system logs environment. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. The diagnostic evidence here is the target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. A focused response is to use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging.

D:

Reconstruct identity using time-bounded DHCP and authentication evidence plus endpoint identifiers before attaching alerts to a person or device. Scope the action to the affected checkout firewall alerts and replenishment system logs environment. Source IP is a temporary network identifier; defensible historical attribution needs time-specific supporting evidence. The diagnostic evidence here is the target report needs IPS/security Analytics records, while that FortiGate policy is not emitting required security-profile logs. The correction is to use Report Guidance or equivalent source checks to validate required log category and enable the approved policy's corresponding logging.

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.

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