Fortinet FCP_FAZ_AN-7.6 Questions & Answers

This safeguard, “Validate macro query references whenever report datasets are changed”, reduces a different source-defined risk: A custom report needs one textual total of detected IPS events rather than a complete multirow table of each attack. That risk depends on: Macros can display dataset-derived values within report narrative or layout without requiring a full chart. The recurring problem here is a performance report needs the 95th percentile of traffic bytes per source, but the author displays the median under a label saying peak. The originally selected control “Verify reported statistics with representative numeric datasets before release” is more specific because different statistical aggregations answer different questions; a median is not a 95th percentile.

This safeguard, “Publish clear metric definitions for open, resolved, and excluded incident states”, reduces a different source-defined risk: A critical chart shows average incident response time, but its dataset counts a still-open incident as if it had a completed resolution timestamp. That risk depends on: An average duration metric becomes misleading when unresolved records have no valid completion time. The recurring problem here is a performance report needs the 95th percentile of traffic bytes per source, but the author displays the median under a label saying peak. The originally selected control “Verify reported statistics with representative numeric datasets before release” is more specific because different statistical aggregations answer different questions; a median is not a 95th percentile.

This safeguard, “Match visualizations to the business question rather than relying on default chart types”, reduces a different source-defined risk: A report should display a security-event trend over time, but the author selects a pie chart that obscures hourly sequence. That risk depends on: Chart type should match the measurement dimension; a time series needs ordered intervals rather than only category proportions. The recurring problem here is a performance report needs the 95th percentile of traffic bytes per source, but the author displays the median under a label saying peak. The originally selected control “Verify reported statistics with representative numeric datasets before release” is more specific because different statistical aggregations answer different questions; a median is not a 95th percentile.

The action “Create or select an eligible dataset that aggregates traffic by source IP, then bind it to a chart in the report layout” addresses a separate source case: A compliance analyst wants a report of the ten most active source IPs and inserts a decorative pie chart with no data query attached. Its underlying reason is: FortiAnalyzer datasets retrieve data from log tables and charts visualize the dataset output; a chart without a valid dataset has no measurements. This question instead describes a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The original answer “Migrate or recreate a supported dataset and chart in an ADOM containing the eligible source type” targets that failure because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The action “Align or explicitly document the source data and filter semantics for the two datasets” addresses a separate source case: Two report charts show different total events because one dataset filters by FortiGate intrusion log type while the other includes all normalized event types. Its underlying reason is: Comparing chart totals is valid only when the underlying event populations and time scopes match. This question instead describes a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The original answer “Migrate or recreate a supported dataset and chart in an ADOM containing the eligible source type” targets that failure because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The action “Disable unnecessary auto-cache on lightweight datasets and retain caching only where measured generation time justifies it” addresses a separate source case: An administrator enables auto-cache on hundreds of simple one-row datasets, consuming disk even though those reports already run in seconds. Its underlying reason is: Generating persistent hcache tables consumes compute and disk resources that may outweigh any benefit for fast queries. This question instead describes a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The original answer “Migrate or recreate a supported dataset and chart in an ADOM containing the eligible source type” targets that failure because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The action “SQL aggregation groups source log rows by the intended dimension rather than preserving each input event” addresses a separate source case: An analyst groups thousands of events by destination, but the SQL query returns repeated rows for every session instead of one total per destination. Its underlying reason is: SQL aggregation groups source log rows by the intended dimension rather than preserving each input event. This question instead describes a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The original answer “Charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies” targets that failure because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The action “A valid category-share chart requires mutually understood categories and a common total” addresses a separate source case: A chart must show a share of detections by severity, but the analyst computes independent percentages that sum to more than one hundred. Its underlying reason is: A valid category-share chart requires mutually understood categories and a common total. This question instead describes a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The original answer “Charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies” targets that failure because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The action “A many-to-many SQL join can inflate counts unless key uniqueness is accounted for” addresses a separate source case: A threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. Its underlying reason is: A many-to-many SQL join can inflate counts unless key uniqueness is accounted for. This question instead describes a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The original answer “Charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies” targets that failure because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The proposed observation “The output shows the simulated hourly event peak in chronological order” would check a different original case: A report should display a security-event trend over time, but the author selects a pie chart that obscures hourly sequence. Its mechanism is: Chart type should match the measurement dimension; a time series needs ordered intervals rather than only category proportions. In the present case, a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails; the more direct acceptance evidence is “The destination report renders using an eligible local dataset after import” because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The proposed observation “The report text shows the test event total and matches the underlying aggregate query” would check a different original case: A custom report needs one textual total of detected IPS events rather than a complete multirow table of each attack. Its mechanism is: Macros can display dataset-derived values within report narrative or layout without requiring a full chart. In the present case, a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails; the more direct acceptance evidence is “The destination report renders using an eligible local dataset after import” because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The proposed observation “Three test sessions to one destination produce one summarized row with the correct total” would check a different original case: An analyst groups thousands of events by destination, but the SQL query returns repeated rows for every session instead of one total per destination. Its mechanism is: SQL aggregation groups source log rows by the intended dimension rather than preserving each input event. In the present case, a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails; the more direct acceptance evidence is “The destination report renders using an eligible local dataset after import” because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

This safeguard, “Require dataset validation as a review gate for query edits”, reduces a different source-defined risk: A report query contains a mistyped column alias that passes a plain text editor but fails when FortiAnalyzer attempts to execute it. That risk depends on: Dataset SQL validation checks executable query syntax and supported field references rather than relying on visual inspection. The recurring problem here is a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The originally selected control “Package dataset, chart, and source assumptions together for migrations” is more specific because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

This safeguard, “Store formatted SQL and explain non-obvious field transformations in dataset documentation”, reduces a different source-defined risk: A custom SQL query is difficult to debug because it contains nested expressions without formatting and an analyst changes random field names. That risk depends on: Query formatting improves readability, while Analyze Query exposes validation and relevant query transformation details. The recurring problem here is a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The originally selected control “Package dataset, chart, and source assumptions together for migrations” is more specific because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

This safeguard, “Enable hcache only for costly reports and monitor its storage consumption”, reduces a different source-defined risk: A dataset query returns the expected counts over a month but takes many hours to regenerate from mature historical Analytics partitions. That risk depends on: FortiAnalyzer hcache stores intermediate results on disk for mature log partitions, reducing repeated historical query work. The recurring problem here is a report chart uses a custom dataset built for a device type removed from its ADOM, and importing the chart into a new context fails. The originally selected control “Package dataset, chart, and source assumptions together for migrations” is more specific because charts depend on datasets and ADOM source compatibility, so importing a chart alone may leave unresolved dependencies.

The action “Use a dataset producing a consistent severity-count denominator before plotting proportions” addresses a separate source case: A chart must show a share of detections by severity, but the analyst computes independent percentages that sum to more than one hundred. Its underlying reason is: A valid category-share chart requires mutually understood categories and a common total. This question instead describes a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The original answer “Correct join keys and aggregation cardinality using stable device and event identifiers where available” targets that failure because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The action “Use an approved dataset fallback expression, such as a supported user-to-source-IP representation, and label the metric accordingly” addresses a separate source case: A report needs to distinguish source users from source IPs when usernames are missing, but the analyst discards every log row with a null user. Its underlying reason is: SQL expressions can handle missing identity values, but a fallback address is not proof of the user's identity. This question instead describes a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The original answer “Correct join keys and aggregation cardinality using stable device and event identifiers where available” targets that failure because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The action “Modify the SQL to use well-defined completed cases and suitable duration calculation with explicit null handling” addresses a separate source case: A critical chart shows average incident response time, but its dataset counts a still-open incident as if it had a completed resolution timestamp. Its underlying reason is: An average duration metric becomes misleading when unresolved records have no valid completion time. This question instead describes a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The original answer “Correct join keys and aggregation cardinality using stable device and event identifiers where available” targets that failure because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The action “A valid category-share chart requires mutually understood categories and a common total” addresses a separate source case: A chart must show a share of detections by severity, but the analyst computes independent percentages that sum to more than one hundred. Its underlying reason is: A valid category-share chart requires mutually understood categories and a common total. This question instead describes a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The original answer “A many-to-many SQL join can inflate counts unless key uniqueness is accounted for” targets that failure because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The action “Dataset log type determines the source tables available to SQL; columns from a different device family cannot supply traffic metrics” addresses a separate source case: A dataset query for FortiGate traffic mistakenly selects a FortiMail event log table, then its chart shows no traffic bytes. Its underlying reason is: Dataset log type determines the source tables available to SQL; columns from a different device family cannot supply traffic metrics. This question instead describes a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The original answer “A many-to-many SQL join can inflate counts unless key uniqueness is accounted for” targets that failure because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The action “Comparing chart totals is valid only when the underlying event populations and time scopes match” addresses a separate source case: Two report charts show different total events because one dataset filters by FortiGate intrusion log type while the other includes all normalized event types. Its underlying reason is: Comparing chart totals is valid only when the underlying event populations and time scopes match. This question instead describes a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The original answer “A many-to-many SQL join can inflate counts unless key uniqueness is accounted for” targets that failure because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The proposed observation “The repeated report completes faster with equivalent totals and documented cache resource use” would check a different original case: A dataset query returns the expected counts over a month but takes many hours to regenerate from mature historical Analytics partitions. Its mechanism is: FortiAnalyzer hcache stores intermediate results on disk for mature log partitions, reducing repeated historical query work. In the present case, a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records; the more direct acceptance evidence is “One controlled event appears once in the final dataset and its count matches the original log population” because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The proposed observation “The corrected readable query passes validation and returns representative grouped events” would check a different original case: A custom SQL query is difficult to debug because it contains nested expressions without formatting and an analyst changes random field names. Its mechanism is: Query formatting improves readability, while Analyze Query exposes validation and relevant query transformation details. In the present case, a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records; the more direct acceptance evidence is “One controlled event appears once in the final dataset and its count matches the original log population” because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The proposed observation “The calculated average matches manually verified resolved test cases and excludes unresolved ones” would check a different original case: A critical chart shows average incident response time, but its dataset counts a still-open incident as if it had a completed resolution timestamp. Its mechanism is: An average duration metric becomes misleading when unresolved records have no valid completion time. In the present case, a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records; the more direct acceptance evidence is “One controlled event appears once in the final dataset and its count matches the original log population” because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

This safeguard, “Validate macro query references whenever report datasets are changed”, reduces a different source-defined risk: A custom report needs one textual total of detected IPS events rather than a complete multirow table of each attack. That risk depends on: Macros can display dataset-derived values within report narrative or layout without requiring a full chart. The recurring problem here is a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The originally selected control “Test join cardinality and duplicate event IDs during query reviews” is more specific because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

This safeguard, “Define top-N sorting, tie handling, and category filters in report specifications”, reduces a different source-defined risk: A report's custom chart needs only the ten most frequent destination domains, but the underlying dataset returns every domain and renders a huge unreadable table. That risk depends on: A top-N visualization depends on ranking and row limitation in its data source or chart configuration. The recurring problem here is a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The originally selected control “Test join cardinality and duplicate event IDs during query reviews” is more specific because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

This safeguard, “Enable hcache only for costly reports and monitor its storage consumption”, reduces a different source-defined risk: A dataset query returns the expected counts over a month but takes many hours to regenerate from mature historical Analytics partitions. That risk depends on: FortiAnalyzer hcache stores intermediate results on disk for mature log partitions, reducing repeated historical query work. The recurring problem here is a threat report dataset joins two source tables with a nonunique field and multiplies each event across many matching records. The originally selected control “Test join cardinality and duplicate event IDs during query reviews” is more specific because a many-to-many SQL join can inflate counts unless key uniqueness is accounted for.

The action “Use an appropriate time-bucketed dataset and line or bar chart for temporal comparison” addresses a separate source case: A report should display a security-event trend over time, but the author selects a pie chart that obscures hourly sequence. Its underlying reason is: Chart type should match the measurement dimension; a time series needs ordered intervals rather than only category proportions. This question instead describes a report's custom chart needs only the ten most frequent destination domains, but the underlying dataset returns every domain and renders a huge unreadable table. The original answer “Aggregate, sort, and limit dataset results to the required top categories with explicit inclusion rules” targets that failure because a top-N visualization depends on ranking and row limitation in its data source or chart configuration.

The action “Use a dataset producing a consistent severity-count denominator before plotting proportions” addresses a separate source case: A chart must show a share of detections by severity, but the analyst computes independent percentages that sum to more than one hundred. Its underlying reason is: A valid category-share chart requires mutually understood categories and a common total. This question instead describes a report's custom chart needs only the ten most frequent destination domains, but the underlying dataset returns every domain and renders a huge unreadable table. The original answer “Aggregate, sort, and limit dataset results to the required top categories with explicit inclusion rules” targets that failure because a top-N visualization depends on ranking and row limitation in its data source or chart configuration.

The action “Create or run the appropriate supported normalized dataset inside a Fabric ADOM with eligible source data” addresses a separate source case: A dataset defined in a FortiGate ADOM references normalized third-party SIEM fields and fails validation, although the same fields exist in a Fabric ADOM. Its underlying reason is: FortiAnalyzer Fabric ADOMs support `siemdb` reporting that may not be available in device-restricted ADOMs. This question instead describes a report's custom chart needs only the ten most frequent destination domains, but the underlying dataset returns every domain and renders a huge unreadable table. The original answer “Aggregate, sort, and limit dataset results to the required top categories with explicit inclusion rules” targets that failure because a top-N visualization depends on ranking and row limitation in its data source or chart configuration.

The action “FortiAnalyzer datasets retrieve data from log tables and charts visualize the dataset output; a chart without a valid dataset has no measurements” addresses a separate source case: A compliance analyst wants a report of the ten most active source IPs and inserts a decorative pie chart with no data query attached. Its underlying reason is: FortiAnalyzer datasets retrieve data from log tables and charts visualize the dataset output; a chart without a valid dataset has no measurements. This question instead describes a report's custom chart needs only the ten most frequent destination domains, but the underlying dataset returns every domain and renders a huge unreadable table. The original answer “A top-N visualization depends on ranking and row limitation in its data source or chart configuration” targets that failure because a top-N visualization depends on ranking and row limitation in its data source or chart configuration.

The action “An average duration metric becomes misleading when unresolved records have no valid completion time” addresses a separate source case: A critical chart shows average incident response time, but its dataset counts a still-open incident as if it had a completed resolution timestamp. Its underlying reason is: An average duration metric becomes misleading when unresolved records have no valid completion time. This question instead describes a report's custom chart needs only the ten most frequent destination domains, but the underlying dataset returns every domain and renders a huge unreadable table. The original answer “A top-N visualization depends on ranking and row limitation in its data source or chart configuration” targets that failure because a top-N visualization depends on ranking and row limitation in its data source or chart configuration.

The action “SQL aggregation groups source log rows by the intended dimension rather than preserving each input event” addresses a separate source case: An analyst groups thousands of events by destination, but the SQL query returns repeated rows for every session instead of one total per destination. Its underlying reason is: SQL aggregation groups source log rows by the intended dimension rather than preserving each input event. This question instead describes a report's custom chart needs only the ten most frequent destination domains, but the underlying dataset returns every domain and renders a huge unreadable table. The original answer “A top-N visualization depends on ranking and row limitation in its data source or chart configuration” targets that failure because a top-N visualization depends on ranking and row limitation in its data source or chart configuration.