Question 690
During an approved scheduled threat hunting dry run for Cobalt Telecom in its production SOC telemetry repository, a security telemetry analyst reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A dashboard query uses nested greedy regular expressions on every raw message and times out during busy periods. The authorized diagnostic packet is NGSIEM-LAB-0173. The reviewer has the prior parser version plus a sanitized regression fixture. The proposed test must not expose customer secrets or interrupt production. Which independently observable result BEST demonstrates this particular SIEM engineering issue has been corrected?
Explanation
Correct Answer
Option A is best answer to this acceptance evidence question. The directly observable acceptance result is: Equivalent fixture results are produced with lower query latency and no timeout. This verifies that Prefer available CPS fields or bounded extraction and reduce the search scope before regex work addresses the specific observation (A dashboard query uses nested greedy regular expressions on every raw message and times out during busy periods). The technical distinction is: Expensive per-event pattern matching is repeated rather than using normalized extracted fields.
Incorrect Answers
Option B would verify a separate condition: A correlation query groups by full raw message text and creates an enormous number of distinct result groups. The observed issue here is: A dashboard query uses nested greedy regular expressions on every raw message and times out during busy periods. The necessary acceptance evidence is: Equivalent fixture results are produced with lower query latency and no timeout.
Option C would verify a separate condition: An investigation CQL query returns no results because its time range starts after the actual security event. The observed issue here is: A dashboard query uses nested greedy regular expressions on every raw message and times out during busy periods. The necessary acceptance evidence is: Equivalent fixture results are produced with lower query latency and no timeout.
Option D would verify a separate condition: A scheduled search scans broad historical events before filtering to one specific data source and runs slowly. The observed issue here is: A dashboard query uses nested greedy regular expressions on every raw message and times out during busy periods. The necessary acceptance evidence is: Equivalent fixture results are produced with lower query latency and no timeout.