Fortinet FCP_FAZ_AN-7.6 Questions & Answers

The action “Missing or changed raw fields propagate as null through report SQL unless a supported fallback is defined” addresses a separate source case: A report chart shows null values for source usernames after a FortiGate firmware update changed an optional field's availability. Its underlying reason is: Missing or changed raw fields propagate as null through report SQL unless a supported fallback is defined. This question instead describes a threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale. The original answer “Changing normalized severity representation alters grouping even when the number of raw detections has not changed” targets that failure because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

The action “Archive-only historical data may not be immediately queryable by Analytics-backed report datasets” 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 threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale. The original answer “Changing normalized severity representation alters grouping even when the number of raw detections has not changed” targets that failure because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

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 threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale. The original answer “Changing normalized severity representation alters grouping even when the number of raw detections has not changed” targets that failure because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

The proposed observation “The chart displays Critical, High, Medium, and Low sample counts from the same underlying dataset” would check a different original case: A report intended to compare incident severities includes only one category because an old chart-level filter still restricts results to Critical. Its mechanism is: Chart-level filters can narrow otherwise valid dataset rows independently of the report-wide settings. In the present case, a threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale; the more direct acceptance evidence is “Old and new sample log formats map to the expected categories and total event count is conserved” because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

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 threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale; the more direct acceptance evidence is “Old and new sample log formats map to the expected categories and total event count is conserved” because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

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 threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale; the more direct acceptance evidence is “Old and new sample log formats map to the expected categories and total event count is conserved” because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

This safeguard, “Document feature availability by FortiAnalyzer operation mode”, reduces a different source-defined risk: The reports pane is missing entirely for an operator using a FortiAnalyzer configured as Collector, although raw archives are present. That risk depends on: Collector mode does not provide the full Reports feature set offered in Analyzer mode. The recurring problem here is a threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale. The originally selected control “Run cross-version severity mapping tests before applying parser updates” is more specific because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

This safeguard, “Regression-test report SQL against representative logs after source firmware changes”, reduces a different source-defined risk: A report chart shows null values for source usernames after a FortiGate firmware update changed an optional field's availability. That risk depends on: Missing or changed raw fields propagate as null through report SQL unless a supported fallback is defined. The recurring problem here is a threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale. The originally selected control “Run cross-version severity mapping tests before applying parser updates” is more specific because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

This safeguard, “Audit active schedules and recipients after migrations and imports”, reduces a different source-defined risk: A scheduled email report becomes duplicated after a migration because two identical report definitions with independent schedules are active in different ADOMs. That risk depends on: Separate report definitions can each generate and notify recipients; duplicate delivery need not indicate a transport retry. The recurring problem here is a threat chart's numeric counts change after a parser update because the normalized severity field now stores values in a different scale. The originally selected control “Run cross-version severity mapping tests before applying parser updates” is more specific because changing normalized severity representation alters grouping even when the number of raw detections has not changed.

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 an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The original answer “Test external report destination connectivity, path, credentials, and permitted storage quota” targets that failure because local generation success does not prove external storage upload or retention succeeded.

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 an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The original answer “Test external report destination connectivity, path, credentials, and permitted storage quota” targets that failure because local generation success does not prove external storage upload or retention succeeded.

The action “Inspect actual log fields and adjust the dataset's null-safe user expression rather than inventing identities” addresses a separate source case: A report chart shows null values for source usernames after a FortiGate firmware update changed an optional field's availability. Its underlying reason is: Missing or changed raw fields propagate as null through report SQL unless a supported fallback is defined. This question instead describes an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The original answer “Test external report destination connectivity, path, credentials, and permitted storage quota” targets that failure because local generation success does not prove external storage upload or retention succeeded.

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 an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The original answer “Local generation success does not prove external storage upload or retention succeeded” targets that failure because local generation success does not prove external storage upload or retention succeeded.

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 an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The original answer “Local generation success does not prove external storage upload or retention succeeded” targets that failure because local generation success does not prove external storage upload or retention succeeded.

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 an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The original answer “Local generation success does not prove external storage upload or retention succeeded” targets that failure because local generation success does not prove external storage upload or retention succeeded.

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, an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists; the more direct acceptance evidence is “The generated test file arrives at the approved archive and is readable by authorized users” because local generation success does not prove external storage upload or retention succeeded.

The proposed observation “The destination report resolves its chart dependencies and runs a sample query successfully” would check a different original 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 mechanism is: Report charts depend on datasets within a specific ADOM context, not on identically named objects elsewhere. In the present case, an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists; the more direct acceptance evidence is “The generated test file arrives at the approved archive and is readable by authorized users” because local generation success does not prove external storage upload or retention succeeded.

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, an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists; the more direct acceptance evidence is “The generated test file arrives at the approved archive and is readable by authorized users” because local generation success does not prove external storage upload or retention succeeded.

This safeguard, “Monitor relay authentication failures and schedule secure credential rotation”, reduces a different source-defined risk: A scheduled report output profile fails to authenticate to an external mail relay after the account password rotates. That risk depends on: Email transport authentication is independent of dataset correctness or report layout. The recurring problem here is an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The originally selected control “Monitor remote delivery acknowledgments and archive availability independently” is more specific because local generation success does not prove external storage upload or retention succeeded.

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 externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The originally selected control “Monitor remote delivery acknowledgments and archive availability independently” is more specific because local generation success does not prove external storage upload or retention succeeded.

This safeguard, “Add duplicate-key and reconciliation assertions to complex report datasets”, reduces a different source-defined risk: A report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. That risk depends on: Many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct. The recurring problem here is an externally archived report cannot be retrieved though the generation task shows Completed and the local output file exists. The originally selected control “Monitor remote delivery acknowledgments and archive availability independently” is more specific because local generation success does not prove external storage upload or retention succeeded.

The action “Inspect actual log fields and adjust the dataset's null-safe user expression rather than inventing identities” addresses a separate source case: A report chart shows null values for source usernames after a FortiGate firmware update changed an optional field's availability. Its underlying reason is: Missing or changed raw fields propagate as null through report SQL unless a supported fallback is defined. This question instead describes an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The original answer “Inspect report layout dependencies and restore the referenced macro or remove the invalid element” targets that failure 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 an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The original answer “Inspect report layout dependencies and restore the referenced macro or remove the invalid element” targets that failure because a missing layout object can break one rendered component without affecting unrelated dataset queries.

The action “Review join cardinality and distinct event keys in the dataset before attempting to suppress a chart warning” addresses a separate source case: A report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. Its underlying reason is: Many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct. This question instead describes an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The original answer “Inspect report layout dependencies and restore the referenced macro or remove the invalid element” targets that failure because a missing layout object can break one rendered component without affecting unrelated dataset queries.

The action “Missing or changed raw fields propagate as null through report SQL unless a supported fallback is defined” addresses a separate source case: A report chart shows null values for source usernames after a FortiGate firmware update changed an optional field's availability. Its underlying reason is: Missing or changed raw fields propagate as null through report SQL unless a supported fallback is defined. This question instead describes an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The original answer “A missing layout object can break one rendered component without affecting unrelated dataset queries” targets that failure because a missing layout object can break one rendered component without affecting unrelated dataset queries.

The action “A presentation-level row limit can suppress displayed detail without removing records from the Analytics database” 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 an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The original answer “A missing layout object can break one rendered component without affecting unrelated dataset queries” targets that failure because a missing layout object can break one rendered component without affecting unrelated dataset queries.

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 an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly. The original answer “A missing layout object can break one rendered component without affecting unrelated dataset queries” targets that failure because a missing layout object can break one rendered component without affecting unrelated dataset queries.

The proposed observation “The corrected result counts each event once and percentages reconcile to the defined total” would check a different original case: A report calculates percentages above one hundred after joining event and endpoint inventories where endpoints have multiple asset records. Its mechanism is: Many-to-many joins multiply counts and can produce invalid ratios even when the underlying log records are correct. In the present case, an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly; the more direct acceptance evidence is “The restored macro displays a valid test value in a new export” because a missing layout object can break one rendered component without affecting unrelated dataset queries.

The proposed observation “The chart labels known users correctly and explicitly identifies records without user attribution” would check a different original case: A report chart shows null values for source usernames after a FortiGate firmware update changed an optional field's availability. Its mechanism is: Missing or changed raw fields propagate as null through report SQL unless a supported fallback is defined. In the present case, an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly; the more direct acceptance evidence is “The restored macro displays a valid test value in a new export” because a missing layout object can break one rendered component without affecting unrelated dataset queries.

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, an export has a blank chart because the report's layout references a deleted macro, while other charts load correctly; the more direct acceptance evidence is “The restored macro displays a valid test value in a new export” because a missing layout object can break one rendered component without affecting unrelated dataset queries.

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.