Fortinet FCP_FAZ_AN-7.6 Questions & Answers

This safeguard, “Bundle referenced datasets and charts during report imports”, reduces a different source-defined risk: A report was imported to another ADOM but a chart references a dataset name that does not exist there, producing an object-not-found error. That risk depends on: Report charts depend on datasets within a specific ADOM context, not on identically named objects elsewhere. The recurring problem here is an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The originally selected control “Validate all report layout references after removing charts, macros, or templates” is more specific because a missing layout object can break one rendered component without affecting unrelated dataset queries.

This safeguard, “Benchmark report queries against maximum required lookback periods”, reduces a different source-defined risk: A custom chart query times out only for a year-long period; one-week queries finish quickly and data ingestion is healthy. That risk depends on: Large historical scans can be expensive even when the query is logically valid and recent periods complete. The recurring problem here is an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The originally selected control “Validate all report layout references after removing charts, macros, or templates” is more specific because a missing layout object can break one rendered component without affecting unrelated dataset queries.

This safeguard, “Document time-zone and DST behavior for calendar-based scheduled reports”, reduces a different source-defined risk: A report generated for a supposed 24-hour window contains 23 hours of data during a daylight-saving change, and the operator calls it a database loss. That risk depends on: A local calendar day can differ from exactly 24 hours during daylight-saving transitions without missing records. The recurring problem here is an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The originally selected control “Validate all report layout references after removing charts, macros, or templates” is more specific because a missing layout object can break one rendered component without affecting unrelated dataset queries.

The action “Review report chart/table row display limits and any top-N or pagination settings before changing collection” addresses a separate source case: An analyst exports a report that is truncated at an unexpectedly low row count, despite the underlying dataset containing many more records. Its underlying reason is: A presentation-level row limit can suppress displayed detail without removing records from the Analytics database. This question instead describes a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The original answer “Review join cardinality and distinct event keys in the dataset before attempting to suppress a chart warning” targets that failure because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The action “Verify operation mode and perform reporting from the associated Analyzer rather than troubleshooting browser cache” addresses a separate source case: The reports pane is missing entirely for an operator using a FortiAnalyzer configured as Collector, although raw archives are present. Its underlying reason is: Collector mode does not provide the full Reports feature set offered in Analyzer mode. This question instead describes a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The original answer “Review join cardinality and distinct event keys in the dataset before attempting to suppress a chart warning” targets that failure because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The action “Check report timezone and daylight-saving boundary semantics against UTC event times” addresses a separate source case: A report generated for a supposed 24-hour window contains 23 hours of data during a daylight-saving change, and the operator calls it a database loss. Its underlying reason is: A local calendar day can differ from exactly 24 hours during daylight-saving transitions without missing records. This question instead describes a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The original answer “Review join cardinality and distinct event keys in the dataset before attempting to suppress a chart warning” targets that failure because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The action “Persistent hcache tables consume storage; obsolete cached workloads can outlive the immediate report generation need” addresses a separate source case: A monthly report consumes growing disk because auto-cache stores intermediates for dozens of historical queries that no longer appear in active reports. Its underlying reason is: Persistent hcache tables consume storage; obsolete cached workloads can outlive the immediate report generation need. This question instead describes a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The original answer “Many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct” targets that failure because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The action “A local calendar day can differ from exactly 24 hours during daylight-saving transitions without missing records” addresses a separate source case: A report generated for a supposed 24-hour window contains 23 hours of data during a daylight-saving change, and the operator calls it a database loss. Its underlying reason is: A local calendar day can differ from exactly 24 hours during daylight-saving transitions without missing records. This question instead describes a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The original answer “Many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct” targets that failure because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The action “Local generation success does not prove external storage upload or retention succeeded” addresses a separate source case: An externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. Its underlying reason is: Local generation success does not prove external storage upload or retention succeeded. This question instead describes a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The original answer “Many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct” targets that failure because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The proposed observation “Branch A and B outputs differ as expected on controlled disjoint source logs” would check a different original case: A report returns identical threat totals for two different branches because the custom SQL dataset ignores the report's selected-device filter variable. Its mechanism is: Report-level filters must be passed into applicable dataset queries; a query that ignores device context can produce misleading shared counts. In the present case, a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records; the more direct acceptance evidence is “The corrected result counts each event once and percentages reconcile to the defined total” because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The proposed observation “The corrected explanation and query cover the intended local-day period with UTC-aligned source logs” would check a different original case: A report generated for a supposed 24-hour window contains 23 hours of data during a daylight-saving change, and the operator calls it a database loss. Its mechanism is: A local calendar day can differ from exactly 24 hours during daylight-saving transitions without missing records. In the present case, a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records; the more direct acceptance evidence is “The corrected result counts each event once and percentages reconcile to the defined total” because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The proposed observation “A controlled report displays the required number of entries after adjusting its output limit” would check a different original case: An analyst exports a report that is truncated at an unexpectedly low row count, despite the underlying dataset containing many more records. Its mechanism is: A presentation-level row limit can suppress displayed detail without removing records from the Analytics database. In the present case, a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records; the more direct acceptance evidence is “The corrected result counts each event once and percentages reconcile to the defined total” because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

This safeguard, “Validate all report layout references after removing charts, macros, or templates”, reduces a different source-defined risk: An export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. That risk depends on: A missing layout object can break one rendered component without affecting unrelated dataset queries. The recurring problem here is a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The originally selected control “Add duplicate-key and reconciliation assertions to complex report datasets” is more specific because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

This safeguard, “Specify and test maximum row counts for evidence-bearing reports”, reduces a different source-defined risk: An analyst exports a report that is truncated at an unexpectedly low row count, despite the underlying dataset containing many more records. That risk depends on: A presentation-level row limit can suppress displayed detail without removing records from the Analytics database. The recurring problem here is a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The originally selected control “Add duplicate-key and reconciliation assertions to complex report datasets” is more specific because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

This safeguard, “Require validation after custom SQL edits and retain rollback versions”, reduces a different source-defined risk: A FortiAnalyzer report task fails with SQL syntax error after a custom dataset edit, and the administrator immediately increases disk quota. That risk depends on: A SQL parsing or validation failure is a query-definition problem, not inherently a storage capacity issue. The recurring problem here is a report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. The originally selected control “Add duplicate-key and reconciliation assertions to complex report datasets” is more specific because many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct.

The action “Verify operation mode and perform reporting from the associated Analyzer rather than troubleshooting browser cache” addresses a separate source case: The reports pane is missing entirely for an operator using a FortiAnalyzer configured as Collector, although raw archives are present. Its underlying reason is: Collector mode does not provide the full Reports feature set offered in Analyzer mode. This question instead describes a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The original answer “Compare requested lookback to available Analytics partitions and revise retention or reporting expectations accordingly” targets that failure because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The action “Test external report destination connectivity, path, credentials, and permitted storage quota” addresses a separate source case: An externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. Its underlying reason is: Local generation success does not prove external storage upload or retention succeeded. This question instead describes a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The original answer “Compare requested lookback to available Analytics partitions and revise retention or reporting expectations accordingly” targets that failure because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The action “Identify both scheduling definitions, retain the intended owner schedule, and disable the redundant one” addresses a separate source case: A scheduled email report becomes duplicated after a migration because two identical report definitions with independent schedules are active in different ADOMs. Its underlying reason is: Separate report definitions can each generate and notify recipients; duplicate delivery need not indicate a transport retry. This question instead describes a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The original answer “Compare requested lookback to available Analytics partitions and revise retention or reporting expectations accordingly” targets that failure because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The action “Collector mode does not provide the full Reports feature set offered in Analyzer mode” addresses a separate source case: The reports pane is missing entirely for an operator using a FortiAnalyzer configured as Collector, although raw archives are present. Its underlying reason is: Collector mode does not provide the full Reports feature set offered in Analyzer mode. This question instead describes a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The original answer “Archive-only historical data may not be immediately queryable by Analytics-backed report datasets” targets that failure because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The action “Changing normalized severity representation alters grouping even when the number of raw detections has not changed” addresses a separate source case: A threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale. Its underlying reason is: Changing normalized severity representation alters grouping even when the number of raw detections has not changed. This question instead describes a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The original answer “Archive-only historical data may not be immediately queryable by Analytics-backed report datasets” targets that failure because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The action “Report output can be incomplete if its source Analytics records have not yet become queryable when execution begins” addresses a separate source case: A report task produces an empty file because the schedule starts before new Analytics log partitions finish processing after a nightly collection batch. Its underlying reason is: Report output can be incomplete if its source Analytics records have not yet become queryable when execution begins. This question instead describes a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The original answer “Archive-only historical data may not be immediately queryable by Analytics-backed report datasets” targets that failure because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The proposed observation “The rescheduled report includes the delayed batch and matches its reference log count” would check a different original case: A report task produces an empty file because the schedule starts before new Analytics log partitions finish processing after a nightly collection batch. Its mechanism is: Report output can be incomplete if its source Analytics records have not yet become queryable when execution begins. In the present case, a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files; the more direct acceptance evidence is “The corrected period returns actual available rows and unavailable history is identified explicitly” because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The proposed observation “The next cycle produces one intended notification with the correct ADOM-scoped report” would check a different original case: A scheduled email report becomes duplicated after a migration because two identical report definitions with independent schedules are active in different ADOMs. Its mechanism is: Separate report definitions can each generate and notify recipients; duplicate delivery need not indicate a transport retry. In the present case, a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files; the more direct acceptance evidence is “The corrected period returns actual available rows and unavailable history is identified explicitly” because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The proposed observation “A controlled report displays the required number of entries after adjusting its output limit” would check a different original case: An analyst exports a report that is truncated at an unexpectedly low row count, despite the underlying dataset containing many more records. Its mechanism is: A presentation-level row limit can suppress displayed detail without removing records from the Analytics database. In the present case, a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files; the more direct acceptance evidence is “The corrected period returns actual available rows and unavailable history is identified explicitly” because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

This safeguard, “Monitor remote delivery acknowledgments and archive availability independently”, reduces a different source-defined risk: An externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. That risk depends on: Local generation success does not prove external storage upload or retention succeeded. The recurring problem here is a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The originally selected control “Align report schedules and retention settings with business reporting windows” is more specific because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

This safeguard, “Review chart-specific filters during report layout revisions”, reduces a different source-defined risk: A report intended to compare incident severities includes only one category because an old chart-level filter still restricts results to Critical. That risk depends on: Chart-level filters can narrow otherwise valid dataset rows independently of the report-wide settings. The recurring problem here is a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The originally selected control “Align report schedules and retention settings with business reporting windows” is more specific because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

This safeguard, “Audit active cache dependencies and disk usage after removing old reports”, reduces a different source-defined risk: A monthly report consumes growing disk because auto-cache stores intermediates for dozens of historical queries that no longer appear in active reports. That risk depends on: Persistent hcache tables consume storage; obsolete cached workloads can outlive the immediate report generation need. The recurring problem here is a report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. The originally selected control “Align report schedules and retention settings with business reporting windows” is more specific because archive-only historical data may not be immediately queryable by Analytics-backed report datasets.

The action “Compare requested lookback to available Analytics partitions and revise retention or reporting expectations accordingly” addresses a separate source case: A report job fails when an ADOM's Analytics retention is shorter than the requested reporting period but the administrator searches only archive files. Its underlying reason is: Archive-only historical data may not be immediately queryable by Analytics-backed report datasets. This question instead describes a report task produces an empty file because the schedule starts before new Analytics log partitions finish processing after a nightly collection batch. The original answer “Move the report run after the supported ingestion/indexing completion window and verify delayed records” targets that failure because report output can be incomplete if its source Analytics records have not yet become queryable when execution begins.

The action “Test external report destination connectivity, path, credentials, and permitted storage quota” addresses a separate source case: An externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. Its underlying reason is: Local generation success does not prove external storage upload or retention succeeded. This question instead describes a report task produces an empty file because the schedule starts before new Analytics log partitions finish processing after a nightly collection batch. The original answer “Move the report run after the supported ingestion/indexing completion window and verify delayed records” targets that failure because report output can be incomplete if its source Analytics records have not yet become queryable when execution begins.

The action “Update the output profile's approved relay credentials and test outbound delivery separately from report generation” addresses a separate source case: A scheduled report output profile fails to authenticate to an external mail relay after the account password rotates. Its underlying reason is: Email transport authentication is independent of dataset correctness or report layout. This question instead describes a report task produces an empty file because the schedule starts before new Analytics log partitions finish processing after a nightly collection batch. The original answer “Move the report run after the supported ingestion/indexing completion window and verify delayed records” targets that failure because report output can be incomplete if its source Analytics records have not yet become queryable when execution begins.

The action “Chart-level filters can narrow otherwise valid dataset rows independently of the report-wide settings” addresses a separate source case: A report intended to compare incident severities includes only one category because an old chart-level filter still restricts results to Critical. Its underlying reason is: Chart-level filters can narrow otherwise valid dataset rows independently of the report-wide settings. This question instead describes a report task produces an empty file because the schedule starts before new Analytics log partitions finish processing after a nightly collection batch. The original answer “Report output can be incomplete if its source Analytics records have not yet become queryable when execution begins” targets that failure because report output can be incomplete if its source Analytics records have not yet become queryable when execution begins.

The action “Collector mode does not provide the full Reports feature set offered in Analyzer mode” addresses a separate source case: The reports pane is missing entirely for an operator using a FortiAnalyzer configured as Collector, although raw archives are present. Its underlying reason is: Collector mode does not provide the full Reports feature set offered in Analyzer mode. This question instead describes a report task produces an empty file because the schedule starts before new Analytics log partitions finish processing after a nightly collection batch. The original answer “Report output can be incomplete if its source Analytics records have not yet become queryable when execution begins” targets that failure because report output can be incomplete if its source Analytics records have not yet become queryable when execution begins.

The action “Report charts depend on datasets within a specific ADOM context, not on identically named objects elsewhere” addresses a separate source case: A report was imported to another ADOM but a chart references a dataset name that does not exist there, producing an object-not-found error. Its underlying reason is: Report charts depend on datasets within a specific ADOM context, not on identically named objects elsewhere. This question instead describes a report task produces an empty file because the schedule starts before new Analytics log partitions finish processing after a nightly collection batch. The original answer “Report output can be incomplete if its source Analytics records have not yet become queryable when execution begins” targets that failure because report output can be incomplete if its source Analytics records have not yet become queryable when execution begins.