Question 420
A search for failed login in SSH audit logs is too broad because records where Source IP matches an approved address must also have Destination Host in a restricted set. Which filter logic meets both requirements?
- Combine the Source IP condition AND the Destination Host condition with appropriate parentheses
- Combine the Source IP condition OR the Destination Host condition
- Use a longer trend interval as the only change
- Group by Source IP and Destination Host without applying attribute filters
Explanation
Correct Answer
A:Both attribute tests must hold for each accepted SSH audit logs record. Conjunction plus explicit grouping prevents a broad OR path from leaking records outside the restricted set.
Incorrect Answers
B:OR accepts records that satisfy only one test, so City Branch would receive results not meeting the two simultaneous restrictions.
C:Changing the trend interval affects time buckets, not whether Source IP and Destination Host must both pass their filters.
D:Under historical or real-time event analysis at the SOC using SSH audit logs: Grouping describes matching results after selection; it does not require either attribute to meet the approved conditions.
Question 421
The North Finance investigation tracks two events in Windows security logs: a denied login P1 followed by a successful login P2. The rule is incorrectly matching different users. Which inter-subpattern constraint should be added?
- A greater-than test between the two event message lengths
- Equality between the relevant Host identity attributes of P1 and P2
- Removal of all grouping keys and inter-subpattern constraints
- Only a larger incident title text field
Explanation
Correct Answer
B:For subpattern correlation at North Finance using Windows security logs: Inter-subpattern comparisons link matching entity keys across both behaviors. Requiring the same Host prevents a different user’s P2 from completing this sequence.
Incorrect Answers
A:In subpattern correlation at North Finance using Windows security logs: Message length does not establish user or entity identity for the P1–P2 correlation.
C:Eliminating identity comparison makes cross-user false matches more likely in North Finance, not less.
D:Under subpattern correlation at North Finance using Windows security logs: Title length affects labeling and cannot prevent a P2 from another Host being joined to the first event.
Question 422
A new FortiSIEM UEBA rule at City Branch matches repeated abuse from 198.51.100.30, but that address never appears in the FortiGate feed. What should be verified on the FortiSIEM side?
- The rule/action or workflow that adds matching source IPs to the intended watchlist
- Configure a FortiGate deny rule that never references the imported dynamic address object
- Whether the dashboard is sorted by host name
- Whether all incidents are marked False Positive immediately
Explanation
Correct Answer
A:Creating an incident is not by itself proof that the watchlist was updated. The 198.51.100.30 attribute and list-update mechanism must connect the analytic outcome to the published feed.
Incorrect Answers
B:For IP feed and FortiGate enforcement at City Branch with the specified 198.51 value: A rule without the feed-backed source object may not match the newly risky IPs learned by FortiSIEM.
C:Widget ordering cannot transfer 198.51.100.30 from an analytic result into a connector-consumable feed.
D:Changing every disposition without examining the rule risks suppressing useful evidence and does not implement watchlist population.
Question 423
The City Branch investigation tracks two events in identity provider events: a denied login P1 followed by a successful login P2. The rule is incorrectly matching different users. Which inter-subpattern constraint should be added?
- Only a larger incident title text field
- Equality between the relevant User identity attributes of P1 and P2
- A greater-than test between the two event message lengths
- Removal of all grouping keys and inter-subpattern constraints
Explanation
Correct Answer
B:For subpattern correlation at City Branch using identity provider events: Inter-subpattern comparisons link matching entity keys across both behaviors. Requiring the same User prevents a different user’s P2 from completing this sequence.
Incorrect Answers
A:In subpattern correlation at City Branch using identity provider events: Title length affects labeling and cannot prevent a P2 from another User being joined to the first event.
C:Considering subpattern correlation at City Branch using identity provider events: Message length does not establish user or entity identity for the P1–P2 correlation.
D:Eliminating identity comparison makes cross-user false matches more likely in City Branch, not less.
Question 424
North Finance needs to remove a previously blocked 198.51.100.15 after analysts verify benign behavior. Which change must be verified end to end?
- Leave the FortiGate external connector permanently unsynchronized
- Remove or expire the IP from the authoritative FortiSIEM list, confirm connector refresh, and retest policy matching
- Configure a static IP list but never refresh changes from the FortiSIEM watchlist
- Delete the source device from unrelated CMDB records
Explanation
Correct Answer
B:For IP feed and FortiGate enforcement at North Finance with the specified 198.51 value: An IP is released only when the FortiGate consumes the updated feed and the relevant rule no longer selects that address. Validation prevents stale restrictions.
Incorrect Answers
A:In IP feed and FortiGate enforcement at North Finance with the specified 198.51 value: Without refresh, the FortiGate may continue applying stale threat-feed entries even after the FortiSIEM source has changed.
C:Considering IP feed and FortiGate enforcement at North Finance with the specified 198.51 value: Without feed synchronization, additions and removals in FortiSIEM need not propagate to the FortiGate enforcement data.
D:Under IP feed and FortiGate enforcement at North Finance with the specified 198.51 value: Asset deletion does not guarantee that the specific feed item is removed or refreshed on FortiGate.
Question 425
Corporate HQ sees a large number of low-confidence events for contractor.r. Why should the analyst not raise incident severity exclusively from the event count?
- The event count is the only supported UEBA data type
- An increase in events requires clearing existing incidents automatically
- Investigate event quality, baselines and contextual severity before escalating
- Every recorded event is automatically a separate confirmed compromise
Explanation
Correct Answer
C:Considering entity-behavior risk evaluation at Corporate HQ: High volume can arise from repetitive benign operations or false alarms. Risk and severity decisions should account for unusualness and asset importance, not raw count alone.
Incorrect Answers
A:In entity-behavior risk evaluation at Corporate HQ: UEBA also uses entity identity, behavior, risk, tags and related analytic attributes that are essential to interpretation.
B:Auto-clearing does not investigate why contractor.r activity increased and may conceal a genuinely active threat.
D:Under entity-behavior risk evaluation at Corporate HQ: Event occurrence is not equivalent to an adjudicated incident, particularly for normal authentication retries and logging noise.
Question 426
An analyst wants separate incidents when the same policy violation burst arises from different Source IP values in North Finance. Which subpattern component separates the candidate event populations?
- Set a higher incident title priority
- Group By the Source IP event attribute
- Use no Group By and count all events globally
- Configure an outbound email recipient for each log entry
Explanation
Correct Answer
B:For correlation-rule investigation at North Finance: Grouping partitions matching records by their Source IP value before applying the rule threshold. This preserves per-actor detection rather than merging every firewall session logs event.
Incorrect Answers
A:For An analyst wants separate incidents when the same policy violation burst arises from different Source IP values in North: In correlation-rule investigation at North Finance: Title wording cannot partition events from different Source IP entities during subpattern evaluation.
C:For An analyst wants separate incidents when the same policy violation burst arises from different Source IP values in North: Considering correlation-rule investigation at North Finance: A global count allows small bursts from unrelated sources to accumulate into a single trigger, losing the per-Source IP boundary.
D:For An analyst wants separate incidents when the same policy violation burst arises from different Source IP values in North: Under correlation-rule investigation at North Finance: Alert recipients do not control the correlation grouping key or the incident identity.
Question 427
The MSSP has a lookup table named ApprovedPrivilegedUsers owned by Corporate HQ; another tenant runs a similarly named enrichment. Which property should be verified before sharing result assumptions across the tenants?
- The organization associated with the lookup-table definition and data
- Join on a display-only attribute that is not the defined lookup key
- The last incident severity used by another customer
- Retrieve only the CMDB inventory view and assume it provides user-maintained lookup values
Explanation
Correct Answer
A:FortiSIEM lookup-table creation selects an Organization. Even if names appear similar, Corporate HQ data and another tenant’s scoped lookup must not be assumed interchangeable.
Incorrect Answers
B:For CMDB and lookup-table configuration at Corporate HQ: Lookup enrichment depends on the table’s actual key schema; a plausible label in the UI may not identify the record to return.
C:Alert priority is not an ownership or lookup-data scoping control for the ApprovedPrivilegedUsers repository.
D:Under CMDB and lookup-table configuration at Corporate HQ: Inventory data and user-managed lookup tables serve different purposes; reading CMDB alone need not return the requested mapping.
Question 428
A FortiSIEM correlation design at Research observes P1 (sign-in in identity provider events) and P2 (a related action on host-61). It must require P1 present and no subsequent P2 in the rule window. Which relationship operator best expresses that precise condition?
- NOT-FOLLOWED-BY
- AND-NOT
- OR
- FOLLOWED-BY
- AND
Explanation
Correct Answer
A:In subpattern correlation at Research for host-61 using identity provider events: NOT-FOLLOWED-BY requires P1 and no P2 afterward in the evaluated rule period. It tests lack of follow-up, distinct from unordered AND-NOT.
Incorrect Answers
B:For subpattern correlation at Research for host-61 using identity provider events: AND-NOT requires P1 while P2 is absent, without making absence conditional on a later P2. This distinction matters in the Research event sequence.
C:Considering subpattern correlation at Research for host-61 using identity provider events: OR permits either P1 or P2 to satisfy the rule. It is suited to alternative signals, not a requirement that both occur or that a later stage be missing.
D:FOLLOWED-BY enforces P1 occurring before P2. It captures ordered attack-stage progression for host-61 rather than unordered coincidence.
E:In subpattern correlation at Research for host-61 using identity provider events: AND demands both patterns without specifying sequence. It fits only when simultaneous presence, rather than temporal ordering or absence, is the intended Research test.
Question 429
A FortiSIEM ML model for process executions per account at North Finance has finished training. The analyst next wants to score newly observed values on host-112. Which operation is needed?
- An unrelated case export
- Training the same model without presenting new data for scoring
- Inference using the trained model and incoming feature values
- Deleting all stored training examples first
Explanation
Correct Answer
C:Inference applies the existing learned model to new process executions per account observations for host-112. It is distinct from retraining and should use compatible feature definitions.
Incorrect Answers
A:Exporting cases facilitates handoff, not applying the learned process executions per account pattern to fresh input.
B:Retraining refreshes or rebuilds model parameters but does not by itself describe scoring the newly observed host-112 values.
D:Under machine-learning analysis at North Finance for host-112: Removing relevant history can undermine the ability to retrain or diagnose model quality and does not perform inference.
Question 430
The Cloud Services investigation tracks two events in file integrity alerts: a denied login P1 followed by a successful login P2. The rule is incorrectly matching different users. Which inter-subpattern constraint should be added?
- Removal of all grouping keys and inter-subpattern constraints
- A greater-than test between the two event message lengths
- Only a larger incident title text field
- Equality between the relevant Host identity attributes of P1 and P2
Explanation
Correct Answer
D:Under subpattern correlation at Cloud Services using file integrity alerts: Inter-subpattern comparisons link matching entity keys across both behaviors. Requiring the same Host prevents a different user’s P2 from completing this sequence.
Incorrect Answers
A:Eliminating identity comparison makes cross-user false matches more likely in Cloud Services, not less.
B:For subpattern correlation at Cloud Services using file integrity alerts: Message length does not establish user or entity identity for the P1–P2 correlation.
C:Considering subpattern correlation at Cloud Services using file integrity alerts: Title length affects labeling and cannot prevent a P2 from another Host being joined to the first event.