Question 150A city government report repeatedly times out on an unfiltered high-cardinality dataset across all devices. Which FortiAnalyzer analyst action best addresses the underlying monitoring or response problem? regenerate the report from the saved current definition and verify artifact timestamp constrain query dimensions and dates or optimize using supported aggregation separate report render status from notification delivery diagnostics schedule selective queries and control heavy report concurrency ExplanationCorrect Answer B:The most direct corrective action is to constrain query dimensions and dates or optimize using supported aggregation. The technical reason is: High-cardinality scans can exceed practical reporting time and resource budgets. Confirm improvement by checking that a representative narrowed report runs within the approved limit and preserves needed metrics. Incorrect Answers A:Previously rendered report files do not dynamically update when a dataset changes. This supports a different intervention; the stated problem requires: constrain query dimensions and dates or optimize using supported aggregation. The decisive reason is: High-cardinality scans can exceed practical reporting time and resource budgets. C:Successful document generation does not prove downstream email delivery. This supports a different intervention; the stated problem requires: constrain query dimensions and dates or optimize using supported aggregation. The decisive reason is: High-cardinality scans can exceed practical reporting time and resource budgets. D:Large Analytics queries compete for resources with log indexing and other jobs. This supports a different intervention; the stated problem requires: constrain query dimensions and dates or optimize using supported aggregation. The decisive reason is: High-cardinality scans can exceed practical reporting time and resource budgets.
Question 151A manufacturer wants an alert only when repeated failures are followed by a successful privileged login but uses a one-event rule. After the team acts to design a correlation sequence with time-bounded failure and success conditions, which observation would best verify the correction? the controlled delayed event series triggers at the selected threshold approved maintenance events are ignored while unexpected access still triggers a synthetic failures-then-success series triggers exactly as intended reversing the synthetic event order no longer meets the intended rule ExplanationCorrect Answer C:The most specific verification is that a synthetic failures-then-success series triggers exactly as intended. That result supports the principle: Multi-stage behavior requires ordered correlation rather than one independent log match. It tests the decision to design a correlation sequence with time-bounded failure and success conditions. Incorrect Answers A:A correlation window must cover the expected event sequence without becoming unbounded. The alternative observation tests a different condition. The direct acceptance evidence here is: a synthetic failures-then-success series triggers exactly as intended. B:Negative correlation can suppress known authorized sequences without suppressing all alerts. The alternative observation tests a different condition. The direct acceptance evidence here is: a synthetic failures-then-success series triggers exactly as intended. D:Temporal sequence matters where one event provides context for the next. The alternative observation tests a different condition. The direct acceptance evidence here is: a synthetic failures-then-success series triggers exactly as intended.
Question 152A logistics team compares intrusion events from FortiGate and a third-party sensor using incompatible source address names. An analyst recommends to use normalized Fabric fields and confirm both parsers represent the same address semantics. Which technical principle best supports the recommendation? Unparsed message text does not automatically populate common normalized fields for correlation Normalization requires a parser matching the actual incoming message structure Unsupported log formats may remain viewable as raw syslog without rich SIEM field mapping Common field schemas enable cross-product analysis without guessing vendor column names ExplanationCorrect Answer D:The governing principle is: Common field schemas enable cross-product analysis without guessing vendor column names. This makes it appropriate to use normalized Fabric fields and confirm both parsers represent the same address semantics. Evidence of success is that a joined search identifies the same test host across both technologies. Incorrect Answers A:Unparsed message text does not automatically populate common normalized fields for correlation. That is a different technical consideration. For this problem, the governing mechanism is: Common field schemas enable cross-product analysis without guessing vendor column names. The appropriate action is: use normalized Fabric fields and confirm both parsers represent the same address semantics. B:Normalization requires a parser matching the actual incoming message structure. That is a different technical consideration. For this problem, the governing mechanism is: Common field schemas enable cross-product analysis without guessing vendor column names. The appropriate action is: use normalized Fabric fields and confirm both parsers represent the same address semantics. C:Unsupported log formats may remain viewable as raw syslog without rich SIEM field mapping. That is a different technical consideration. For this problem, the governing mechanism is: Common field schemas enable cross-product analysis without guessing vendor column names. The appropriate action is: use normalized Fabric fields and confirm both parsers represent the same address semantics.
Question 153A university builds a custom report with an unbounded query across years of high-volume traffic logs. Which FortiAnalyzer analyst action best addresses the underlying monitoring or response problem? restrict time, device scope and aggregation to the actual reporting requirement select the appropriate normalized SIEM dataset and verify parser output first verify available dataset columns and choose the matching supported Analytics field normalize the time boundary and test records around midnight ExplanationCorrect Answer A:The most direct corrective action is to restrict time, device scope and aggregation to the actual reporting requirement. The technical reason is: Report dataset performance depends on query selectivity and data volume. Confirm improvement by checking that the scheduled test runs within its approved resource budget and still covers needed evidence. Incorrect Answers B:Fabric normalized log fields are available in the matching SIEM schema, not every vendor table. This supports a different intervention; the stated problem requires: restrict time, device scope and aggregation to the actual reporting requirement. The decisive reason is: Report dataset performance depends on query selectivity and data volume. C:A report SQL query cannot group on a column absent from the queried schema. This supports a different intervention; the stated problem requires: restrict time, device scope and aggregation to the actual reporting requirement. The decisive reason is: Report dataset performance depends on query selectivity and data volume. D:Time filters must use consistent timestamp semantics to avoid missing or double-counting events. This supports a different intervention; the stated problem requires: restrict time, device scope and aggregation to the actual reporting requirement. The decisive reason is: Report dataset performance depends on query selectivity and data volume.
Question 154A regional branch manager requests a one-week traffic summary but the analyst leaves the FortiView time selector at the last hour. Which FortiAnalyzer analyst action best addresses the underlying monitoring or response problem? select the correct ADOM and confirm eligible log sources before diagnosing the widget set the required history window and verify Analytics coverage for that period record and clear active IP filters before generating environment-wide conclusions inspect the widget data requirements and available log types first ExplanationCorrect Answer B:The most direct corrective action is to set the required history window and verify Analytics coverage for that period. The technical reason is: The selected time window directly determines the data used in FortiView aggregation. Confirm improvement by checking that a known event from three days earlier appears in the weekly view. Incorrect Answers A:FortiView data respects the chosen administration domain and available telemetry. This supports a different intervention; the stated problem requires: set the required history window and verify Analytics coverage for that period. The decisive reason is: The selected time window directly determines the data used in FortiView aggregation. C:Dashboard filters change the population represented by summary counts. This supports a different intervention; the stated problem requires: set the required history window and verify Analytics coverage for that period. The decisive reason is: The selected time window directly determines the data used in FortiView aggregation. D:Some FortiView widgets remain blank when their required log category is not collected. This supports a different intervention; the stated problem requires: set the required history window and verify Analytics coverage for that period. The decisive reason is: The selected time window directly determines the data used in FortiView aggregation.
Question 155A retailer extends a dataset with a third-party normalized field but queries the ordinary Fortinet traffic table. Which FortiAnalyzer analyst action best addresses the underlying monitoring or response problem? choose the correct supported distinct-count aggregation for source IP normalize the time boundary and test records around midnight select the appropriate normalized SIEM dataset and verify parser output first restrict time, device scope and aggregation to the actual reporting requirement ExplanationCorrect Answer C:The most direct corrective action is to select the appropriate normalized SIEM dataset and verify parser output first. The technical reason is: Fabric normalized log fields are available in the matching SIEM schema, not every vendor table. Confirm improvement by checking that a controlled external event yields the added column in the report result. Incorrect Answers A:SQL aggregate functions express different questions and cannot be interchanged. This supports a different intervention; the stated problem requires: select the appropriate normalized SIEM dataset and verify parser output first. The decisive reason is: Fabric normalized log fields are available in the matching SIEM schema, not every vendor table. B:Time filters must use consistent timestamp semantics to avoid missing or double-counting events. This supports a different intervention; the stated problem requires: select the appropriate normalized SIEM dataset and verify parser output first. The decisive reason is: Fabric normalized log fields are available in the matching SIEM schema, not every vendor table. D:Report dataset performance depends on query selectivity and data volume. This supports a different intervention; the stated problem requires: select the appropriate normalized SIEM dataset and verify parser output first. The decisive reason is: Fabric normalized log fields are available in the matching SIEM schema, not every vendor table.
Question 156A manufacturing team clones a playbook template but keeps the vendor example connector credentials. Which FortiAnalyzer analyst action best addresses the underlying monitoring or response problem? enable the saved playbook after validating its intended trigger configuration choose an appropriate automatic trigger or explicitly run the on-demand playbook require supported trigger filters and analyst review for high-impact actions replace template secrets and test approved tenant-specific connector identity ExplanationCorrect Answer D:The most direct corrective action is to replace template secrets and test approved tenant-specific connector identity. The technical reason is: Reusable templates require environment-specific authorization before safe execution. Confirm improvement by checking that the test workflow runs with a scoped service account and no default credentials. Incorrect Answers A:A saved disabled playbook does not launch merely because a trigger condition exists. This supports a different intervention; the stated problem requires: replace template secrets and test approved tenant-specific connector identity. The decisive reason is: Reusable templates require environment-specific authorization before safe execution. B:On Demand playbooks execute when initiated, not solely because a log exists. This supports a different intervention; the stated problem requires: replace template secrets and test approved tenant-specific connector identity. The decisive reason is: Reusable templates require environment-specific authorization before safe execution. C:Automated containment must match verified identities and approved response scope. This supports a different intervention; the stated problem requires: replace template secrets and test approved tenant-specific connector identity. The decisive reason is: Reusable templates require environment-specific authorization before safe execution.
Question 157A lab receives firewall logs with a new format after firmware upgrade and SIEM searches no longer recognize device identifiers. Which FortiAnalyzer analyst action best addresses the underlying monitoring or response problem? inspect log-parser compatibility and field extraction against representative new logs validate timestamp mapping and timezone interpretation before enabling production correlation check parser availability and retain raw-message analysis until normalization is supported confirm a supported parser or mapped normalization for the log format ExplanationCorrect Answer A:The most direct corrective action is to inspect log-parser compatibility and field extraction against representative new logs. The technical reason is: Normalization requires a parser matching the actual incoming message structure. Confirm improvement by checking that a post-upgrade test record resolves to the correct source and severity fields. Incorrect Answers B:Timestamp extraction must preserve event chronology across heterogeneous log formats. This supports a different intervention; the stated problem requires: inspect log-parser compatibility and field extraction against representative new logs. The decisive reason is: Normalization requires a parser matching the actual incoming message structure. C:Unsupported log formats may remain viewable as raw syslog without rich SIEM field mapping. This supports a different intervention; the stated problem requires: inspect log-parser compatibility and field extraction against representative new logs. The decisive reason is: Normalization requires a parser matching the actual incoming message structure. D:Unparsed message text does not automatically populate common normalized fields for correlation. This supports a different intervention; the stated problem requires: inspect log-parser compatibility and field extraction against representative new logs. The decisive reason is: Normalization requires a parser matching the actual incoming message structure.
Question 158A university imports a predefined handler that is disabled and assumes its existence means it is active. If the team does not address this issue, what is the most direct avoidable operational or security risk? alert fatigue may conceal a genuine credential attack the SOC can lose detection coverage while relying on inactive rules overbroad conditions can generate false security incidents for normal transactions analysts may stop responding to meaningful alerts hidden among noise ExplanationCorrect Answer B:The direct risk is that the SOC can lose detection coverage while relying on inactive rules. Mitigate it by acting to enable the intended handler and verify its status and trigger behavior. The underlying technical cause is: Predefined handler presence does not mean it generates events while disabled. Incorrect Answers A:Basic event handlers generate events from matching rules and can tune signal volume. This is not the primary failure in the question. The direct unmitigated outcome here is: the SOC can lose detection coverage while relying on inactive rules. C:Event filters must distinguish the triggering log semantics rather than only IP values. This is not the primary failure in the question. The direct unmitigated outcome here is: the SOC can lose detection coverage while relying on inactive rules. D:Alert criteria determine the balance between useful security signals and excessive noise. This is not the primary failure in the question. The direct unmitigated outcome here is: the SOC can lose detection coverage while relying on inactive rules.
Question 159A hospital branch firewall sends daily traffic logs yet the SOC has not confirmed that its serial number matches the asset register. After the team acts to compare device identity and registration against the approved inventory, which observation would best verify the correction? test searches from each tenant show only that tenant's authorized devices new traffic logs appear under the registered serial number in the correct ADOM a controlled test log maps to the expected firewall asset and time authorized test events arrive from the gateway without relaxing authentication for unknown senders ExplanationCorrect Answer C:The most specific verification is that a controlled test log maps to the expected firewall asset and time. That result supports the principle: Device serial and ADOM association establish accountable provenance for security telemetry. It tests the decision to compare device identity and registration against the approved inventory. Incorrect Answers A:ADOM and device-scoped monitoring prevent unrelated tenants from being mixed during analysis. The alternative observation tests a different condition. The direct acceptance evidence here is: a controlled test log maps to the expected firewall asset and time. B:FortiAnalyzer must recognize a sender before collected logs are usefully attributed to its device. The alternative observation tests a different condition. The direct acceptance evidence here is: a controlled test log maps to the expected firewall asset and time. D:Source admission and device identity need compatible settings across NAT and management boundaries. The alternative observation tests a different condition. The direct acceptance evidence here is: a controlled test log maps to the expected firewall asset and time.
Question 160A retail analyst notices a new top source after a proxy rollout and declares a single workstation responsible. Which FortiAnalyzer analyst action best addresses the underlying monitoring or response problem? review application identity, action and firewall policy across related sessions drill down into application identity, destinations and timing before making risk judgments pivot from the destination to unique sources, users and sessions account for shared proxy and NAT egress before attributing traffic ExplanationCorrect Answer D:The most direct corrective action is to account for shared proxy and NAT egress before attributing traffic. The technical reason is: Aggregation by observed source address can group many clients behind one intermediary. Confirm improvement by checking that underlying client metadata or proxy logs separate the individual users. Incorrect Answers A:Application recognition and policy enforcement outcomes must be read together. This supports a different intervention; the stated problem requires: account for shared proxy and NAT egress before attributing traffic. The decisive reason is: Aggregation by observed source address can group many clients behind one intermediary. B:High traffic volume alone does not distinguish approved bulk transfer from exfiltration. This supports a different intervention; the stated problem requires: account for shared proxy and NAT egress before attributing traffic. The decisive reason is: Aggregation by observed source address can group many clients behind one intermediary. C:Aggregate destination rankings hide the distribution of individual clients. This supports a different intervention; the stated problem requires: account for shared proxy and NAT egress before attributing traffic. The decisive reason is: Aggregation by observed source address can group many clients behind one intermediary.