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

Question 620

During an investigation of maintenance system incidents and service gateway logs at a metropolitan rail maintenance depot, engineers need to separate security threats from ordinary faults. The reported failure is: A security analyst can confirm raw archived logs exist but an event handler and scheduled report show no matching events for that time window. The analyst confirms: Archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. 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 maintenance system incidents and service gateway logs environment.
  2. 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 maintenance system incidents and service gateway logs environment.
  3. 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 maintenance system incidents and service gateway logs environment.
  4. 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 maintenance system incidents and service gateway logs environment.

Explanation

Correct Answer

D:

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 maintenance system incidents and service gateway logs environment. Archival retention and analytics database availability have different uses; event handlers and reports require appropriate processed analytics data. The needed change is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. Verify that the targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved.

Incorrect Answers

A:

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 maintenance system incidents and service gateway 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 archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The correction is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM.

B:

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 maintenance system incidents and service gateway logs environment. SOC features inherit administrative and ADOM authorization boundaries; visibility settings alone are not isolation controls. The diagnostic evidence here is archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The practical next step is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM.

C:

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 maintenance system incidents and service gateway logs environment. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. The diagnostic evidence here is archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The appropriate repair is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM.

Question 621

The security team at a high-street retail chain proposes this controlled action for checkout firewall alerts and replenishment system logs: Select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples. The original condition was: Endpoint antivirus events are incorrectly treated as firewall traffic, making malware severity and host fields unusable for searches. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. Endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. Validate with representative checkout firewall alerts and replenishment system logs traffic.
  2. 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 checkout firewall alerts and replenishment system logs traffic.
  3. New controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors. Validate with representative checkout firewall alerts and replenishment system 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 checkout firewall alerts and replenishment system logs traffic.

Explanation

Correct Answer

A:

Endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. Log-source classification must match the producing application's schema before common SOC fields can be trusted. In this case, assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The corresponding correction is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples.

Incorrect Answers

B:

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 assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The required outcome is that endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals.

C:

New controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The required outcome is that endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals.

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 assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The required outcome is that endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals.

Question 622

A SOC response plan for archive service audit logs and suspicious DNS events at a museum collections partnership must include both a justified correction and measurable proof. Incident: A compliance team expects an imported customized report every Monday, but no new PDFs appear. Evidence: The report definition was imported with schedule disabled and no output profile selected. Which combined action-and-verification pair best fits this case?

  1. Action: Restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. Proof: A controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. Perform both using approved archive service audit logs and suspicious DNS events test cases.
  2. Action: Add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. Proof: Synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim. Perform both using approved archive service audit logs and suspicious DNS events test cases.
  3. 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 archive service audit logs and suspicious DNS events test cases.
  4. Action: Standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. Proof: The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Perform both using approved archive service audit logs and suspicious DNS events test cases.

Explanation

Correct Answer

C:

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. A suitable test should demonstrate that a controlled scheduled run creates a report and sends it only to the designated recipient group. Perform both using approved archive service audit logs and suspicious DNS events test cases. In this case, the report definition was imported with schedule disabled and no output profile selected. Importing report content is distinct from enabling timed execution and distribution.

Incorrect Answers

A:

The preferred remedy is to restore the correct supported security log source and adapt the dataset fields to actual schema before regenerating. The outcome can be verified by confirming that a controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. Perform both using approved archive service audit logs and suspicious DNS events test cases. SQL datasets can only filter and aggregate attributes that exist in their selected log schema. The diagnostic evidence here is the report definition was imported with schedule disabled and no output profile selected. The appropriate repair is to set an approved schedule and output profile on the imported report and test both generation and delivery with restricted recipients. The acceptance test should confirm that a controlled scheduled run creates a report and sends it only to the designated recipient group.

B:

To resolve the observed issue, add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. Validation should establish that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim. Perform both using approved archive service audit logs and suspicious DNS events test cases. Report aggregation keys define the claim's granularity; an IP address does not guarantee a stable user identity. The diagnostic evidence here is the report definition was imported with schedule disabled and no output profile selected. The needed change is to set an approved schedule and output profile on the imported report and test both generation and delivery with restricted recipients. A controlled check should show that a controlled scheduled run creates a report and sends it only to the designated recipient group.

D:

The correction is to standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. The acceptance test should confirm that the PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight. Perform both using approved archive service audit logs and suspicious DNS events test cases. Report identity includes its time-zone semantics, not just the stored PDF bytes. The diagnostic evidence here is the report definition was imported with schedule disabled and no output profile selected. To resolve the observed issue, 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.

Question 623

A SOC response plan for assessment portal access records and web security alerts at an online education platform must include both a justified correction and measurable proof. Incident: Security Fabric topology shows an obsolete edge device instead of the replacement FortiGate after a branch hardware swap. Evidence: Serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. Which combined action-and-verification pair best fits this case?

  1. Action: Reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection. Proof: The live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events. Perform both using approved assessment portal access records and web security alerts test cases.
  2. 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 assessment portal access records and web security alerts test cases.
  3. 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 assessment portal access records and web security alerts test cases.
  4. Action: Establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. Proof: Sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay. Perform both using approved assessment portal access records and web security alerts test cases.

Explanation

Correct Answer

A:

To resolve the observed issue, reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection. Validation should establish that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events. Perform both using approved assessment portal access records and web security alerts test cases. In this case, serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. Security Fabric analytics depend on consistent device identities and membership, not simply identical display names.

Incorrect Answers

B:

A focused response 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 assessment portal access records and web security alerts test cases. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. The preferred remedy is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection. The outcome can be verified by confirming that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events.

C:

The correction is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples. The acceptance test should confirm 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 assessment portal access records and web security alerts test cases. Log-source classification must match the producing application's schema before common SOC fields can be trusted. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. To resolve the observed issue, reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection. Validation should establish that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events.

D:

The practical next step is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. A controlled check should show that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay. Perform both using approved assessment portal access records and web security alerts test cases. Collection, central processing and report generation are distinct roles in distributed FortiAnalyzer architectures. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. A focused response is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection. A suitable test should demonstrate that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events.

Question 624

During an investigation of turnstile system alerts and concession network logs at a sports venue operations group, peak crowd events need accurate incident windows. The reported failure is: A broad event handler generates dozens of security events from routine activity after two independent matching rules are enabled. The analyst confirms: Each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Scope the action to the affected turnstile system alerts and concession network logs environment.
  2. Normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. Scope the action to the affected turnstile system alerts and concession network logs environment.
  3. Narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. Scope the action to the affected turnstile system alerts and concession network logs environment.
  4. Reopen or create a linked incident and expand scope based on the new affected host while retaining the original case history. Scope the action to the affected turnstile system alerts and concession network logs environment.

Explanation

Correct Answer

C:

Narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. Scope the action to the affected turnstile system alerts and concession network logs environment. Basic event handler rule matching differs from correlation sequence logic; rule composition controls alert specificity. A focused response is to narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. Verify that only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts.

Incorrect Answers

A:

Configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. Scope the action to the affected turnstile system alerts and concession network logs environment. Playbook triggers govern execution initiation independently of which tasks the playbook contains. The diagnostic evidence here is each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. The preferred remedy is to narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together.

B:

Normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. Scope the action to the affected turnstile system alerts and concession network logs environment. Threat indicators must preserve their type and canonical representation to support meaningful enrichment and correlation. The diagnostic evidence here is each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. To resolve the observed issue, narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together.

D:

Reopen or create a linked incident and expand scope based on the new affected host while retaining the original case history. Scope the action to the affected turnstile system alerts and concession network logs environment. Administrative closure does not invalidate later observed evidence or prove all related assets are contained. The diagnostic evidence here is each basic handler rule triggers events independently under its OR semantics and one broad rule matches benign traffic. The correction is to narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together.

Question 625

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: An analyst enters a URL into an IP-only indicator workflow and receives no useful reputation enrichment for the suspicious destination. The analyst confirms: The indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. Scope the action to the affected customer ticket service events and engineer VPN logs environment.
  2. Extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. Scope the action to the affected customer ticket service events and engineer VPN logs environment.
  3. Scope incident aggregation to appropriate tenant and entity context while retaining shared threat intelligence as a separate enrichment signal. Scope the action to the affected customer ticket service events and engineer VPN logs environment.
  4. Narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. Scope the action to the affected customer ticket service events and engineer VPN logs environment.

Explanation

Correct Answer

A:

Normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. Scope the action to the affected customer ticket service events and engineer VPN logs environment. Threat indicators must preserve their type and canonical representation to support meaningful enrichment and correlation. To resolve the observed issue, normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment. Verify that a controlled indicator of each supported type yields correctly typed lookup results and the incident references the expected value.

Incorrect Answers

B:

Extend the authorized device selector to the relevant branch and retain distinct ADOM boundaries and log-type conditions. Scope the action to the affected customer ticket service events and engineer VPN logs environment. Event-handler data selectors define source scope separately from the underlying rule expression. The diagnostic evidence here is the indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. A focused response is to normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment.

C:

Scope incident aggregation to appropriate tenant and entity context while retaining shared threat intelligence as a separate enrichment signal. Scope the action to the affected customer ticket service events and engineer VPN logs environment. A shared indicator does not establish common incident ownership across isolated administrative domains. The diagnostic evidence here is the indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. The correction is to normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment.

D:

Narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. Scope the action to the affected customer ticket service events and engineer VPN logs environment. Basic event handler rule matching differs from correlation sequence logic; rule composition controls alert specificity. The diagnostic evidence here is the indicator record's type does not match its actual value and available enrichment sources only support valid IP, domain or URL inputs. The practical next step is to normalize the indicator value and choose the supported IP/domain/URL type before enrichment and incident attachment.

Question 626

During an investigation of public Wi-Fi events and staff application log streams at a county public library network, guest logs must remain separate from protected staff records. The reported failure is: A regional FortiAnalyzer Collector receives logs but the design expects it alone to run analytics reports and SOC event correlation in the same manner as a full Analyzer. The analyst confirms: Deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?

  1. Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Scope the action to the affected public Wi-Fi events and staff application log streams environment.
  2. Establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. Scope the action to the affected public Wi-Fi events and staff application log streams environment.
  3. Calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Scope the action to the affected public Wi-Fi events and staff application log streams environment.
  4. Verify applicable FortiGuard/service entitlement, connectivity and feed update status before relying on outbreak detections. Scope the action to the affected public Wi-Fi events and staff application log streams environment.

Explanation

Correct Answer

B:

Establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. Scope the action to the affected public Wi-Fi events and staff application log streams environment. Collection, central processing and report generation are distinct roles in distributed FortiAnalyzer architectures. The correction is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. Verify that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay.

Incorrect Answers

A:

Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. Scope the action to the affected public Wi-Fi events and staff application log streams 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 deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. A focused response is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned.

C:

Calibrate event and incident severity using scoped asset criticality, observed behavior and documented response runbooks. Scope the action to the affected public Wi-Fi events and staff application log streams environment. Security operations prioritization must combine event content with operational exposure; raw log count alone is not business impact. The diagnostic evidence here is deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. The practical next step is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned.

D:

Verify applicable FortiGuard/service entitlement, connectivity and feed update status before relying on outbreak detections. Scope the action to the affected public Wi-Fi events and staff application log streams environment. Enrichment and outbreak intelligence require their own data and service dependencies; raw log retention cannot substitute for an unavailable feed. The diagnostic evidence here is deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. The appropriate repair is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned.

Question 627

A SOC response plan for river sensor gateway logs and remote site alerts at a hydrology research nonprofit must include both a justified correction and measurable proof. Incident: An account-takeover detection should alert when repeated login failures are followed by success, but no event appears for a controlled attack simulation. Evidence: The correlation rule sequence places success before failures and the evaluation window never matches the observed order. 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 river sensor gateway logs and remote site alerts test cases.
  2. Action: Restore relevant supported Analytics ingestion/retention and explicitly validate handler matching against processed log rows. Proof: A test threat log produces the expected event in the correct ADOM while raw historical retention remains intact. Perform both using approved river sensor gateway logs and remote site alerts test cases.
  3. 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 river sensor gateway logs and remote site alerts test cases.
  4. Action: Define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. Proof: Test failures followed by success raise one correlated event and reversed benign order does not. Perform both using approved river sensor gateway logs and remote site alerts test cases.

Explanation

Correct Answer

D:

To resolve the observed issue, define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. The acceptance test should confirm that test failures followed by success raise one correlated event and reversed benign order does not. Perform both using approved river sensor gateway logs and remote site alerts test cases. In this case, the correlation rule sequence places success before failures and the evaluation window never matches the observed order. Stateful event correlation depends on temporal ordering and shared identifiers, not just the presence of the same log types.

Incorrect Answers

A:

The appropriate repair is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. The outcome can be verified by confirming that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. Perform both using approved river sensor gateway logs and remote site alerts test cases. Playbook triggers govern execution initiation independently of which tasks the playbook contains. The diagnostic evidence here is the correlation rule sequence places success before failures and the evaluation window never matches the observed order. The correction is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. The acceptance test should confirm that test failures followed by success raise one correlated event and reversed benign order does not.

B:

The needed change is to restore relevant supported Analytics ingestion/retention and explicitly validate handler matching against processed log rows. Validation should establish that a test threat log produces the expected event in the correct ADOM while raw historical retention remains intact. Perform both using approved river sensor gateway logs and remote site alerts test cases. FortiAnalyzer event handlers operate on appropriate Analytics logs and cannot infer events from inaccessible archive-only data. The diagnostic evidence here is the correlation rule sequence places success before failures and the evaluation window never matches the observed order. The practical next step is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. A controlled check should show that test failures followed by success raise one correlated event and reversed benign order does not.

C:

The preferred remedy is to update the supported upstream task-output mapping and verify the imported task graph and variable resolution before enabling production automation. A suitable test should demonstrate that an incident test receives the expected generated report from the current task, and missing source outputs are logged explicitly. Perform both using approved river sensor gateway logs and remote site alerts 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 the correlation rule sequence places success before failures and the evaluation window never matches the observed order. The appropriate repair is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. The outcome can be verified by confirming that test failures followed by success raise one correlated event and reversed benign order does not.

Question 628

A security analyst at a natural-history archive is investigating an anomaly in specimen database access events and archive security alerts. The reported behavior is: An analyst marks all mapped techniques as fully monitored after viewing FortiAnalyzer's MITRE coverage screen, although necessary log types are absent. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. Verify this observation against specimen database access events and archive security alerts.
  2. Device/ADOM analytics retention and rolling policies have removed the older logs before the investigation's mandated retention period. Verify this observation against specimen database access events and archive security alerts.
  3. The visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. Verify this observation against specimen database access events and archive security alerts.
  4. FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. Verify this observation against specimen database access events and archive security alerts.

Explanation

Correct Answer

C:

The visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. A detection mapping describes capability or intent and cannot by itself prove that required telemetry and working rules exist. The needed change is to inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping. Verify that a controlled approved detection scenario produces the mapped event and evidence; untested techniques are clearly labeled as coverage gaps. The question describes: A security analyst at a natural-history archive is investigating an anomaly in specimen database access events and archive security alerts.

Incorrect Answers

A:

Device assignment records show the firewall serial belongs to an unrelated ADOM despite normal log reception. FortiAnalyzer ADOM scoping controls device and log context; working collection does not guarantee correct tenancy or isolation. The diagnostic evidence here is the visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. The practical next step is to inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping. The question describes: A security analyst at a natural-history archive is investigating an anomaly in specimen database access events and archive security alerts.

B:

Device/ADOM analytics retention and rolling policies have removed the older logs before the investigation's mandated retention period. 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 the visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. The appropriate repair is to inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping.

D:

FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. Receiving a connection and trusting a log-producing device are separate operations; registration and domain placement determine analyst access. The diagnostic evidence here is the visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. The preferred remedy is to inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping.

Question 629

A security analyst at a rural broadband provider is investigating an anomaly in subscriber abuse alerts and customer-edge firewall logs. The reported behavior is: An event fires five times in one minute and automation repeatedly attempts the same endpoint quarantine with resulting alert storms. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?

  1. Event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  2. Attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  3. Playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.
  4. Playbook Monitor details show the initial task Success and a subsequent task Failed rather than an all-or-nothing transaction. Verify this observation against subscriber abuse alerts and customer-edge firewall logs.

Explanation

Correct Answer

A:

Event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. Event occurrence frequency does not imply repeated state-changing actions are necessary or safe. The appropriate repair is to add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation. Verify that ten controlled duplicate event logs produce one approved action and the case retains a trace of all occurrences. The question describes: A security analyst at a rural broadband provider is investigating an anomaly in subscriber abuse alerts and customer-edge firewall logs.

Incorrect Answers

B:

Attached screenshots show truncated rows while the source logs contain complete unique identifiers and timestamps. Incident handling requires provenance and reproducible evidence, not just a narrative label attached to a case. The diagnostic evidence here is event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. The needed change is to add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation.

C:

Playbook Monitor labels connector-dependent actions Upstream_failed while local tasks succeed and network tests show blocked connector endpoint. Upstream device reachability and local task configuration are separate causes of automation failure. The diagnostic evidence here is event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. The preferred remedy is to add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation.

D:

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 event log and playbook monitor show multiple trigger matches for one asset while no deduplication or suppression condition is applied. To resolve the observed issue, add risk-appropriate event deduplication, target-state reconciliation and bounded automation triggers rather than blindly rerunning remediation.

Question 630

The security team at a regional hospital network proposes this controlled action for outpatient booking logs and perimeter threat alerts: Expand the time range based on incident chronology and join evidence by endpoint/user/device with clock-corrected timestamps. The original condition was: The first step of a suspicious login-to-exfiltration sequence is missing from the investigation because the query begins after authentication. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?

  1. A controlled sequence displays the precursor, detection and follow-up traffic in order without adding unrelated users' activity. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  2. The test device's events appear in both its Log View query and the aligned widget for the same time period. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  3. The revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic. Validate with representative outpatient booking logs and perimeter threat alerts traffic.
  4. A controlled test signature generates the appropriate security log and the report shows its event after regeneration. Validate with representative outpatient booking logs and perimeter threat alerts traffic.

Explanation

Correct Answer

A:

A controlled sequence displays the precursor, detection and follow-up traffic in order without adding unrelated users' activity. 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 corresponding correction is to expand the time range based on incident chronology and join evidence by endpoint/user/device with clock-corrected timestamps. The question describes: The security team at a regional hospital network proposes this controlled action for outpatient booking logs and perimeter threat alerts: Expand the time range based on incident chronology and join evidence by.

Incorrect Answers

B:

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. The diagnostic evidence here is the event window excludes the earlier login and only includes later DNS or data-transfer entries. The required outcome is that a controlled sequence displays the precursor, detection and follow-up traffic in order without adding unrelated users' activity.

C:

The revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is the event window excludes the earlier login and only includes later DNS or data-transfer entries. The required outcome is that a controlled sequence displays the precursor, detection and follow-up traffic in order without adding unrelated users' activity.

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 the event window excludes the earlier login and only includes later DNS or data-transfer entries. The required outcome is that a controlled sequence displays the precursor, detection and follow-up traffic in order without adding unrelated users' activity.

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