Increasing the memory queue size allows the log collector to buffer more events in memory before processing or forwarding, reducing ingest delays for high-volume streams and improving overall performance.

The NG SIEM Analyst role allows reading case data and writing XDR data while restricting administrative actions such as modifying or writing case templates, aligning with the principle of least privilege.

CrowdStrike LogScale documentation states that groupBy() is used to group events by one or more specified fields, similar to SQL GROUP BY. The documentation also says the function parameter accepts aggregate functions, and its default is count(as=_count). That means the query that explicitly groups by ComputerName, UserName, and CommandLine and applies function=count() is the correct way to output the frequency of each unique combination of those three fields.
Why the other options are incorrect:
A is incorrect because table() formats output rows but does not aggregate unique combinations into frequencies the way groupBy() does. Adding count() after table() does not produce grouped counts for each unique triplet. B is incorrect because table() is not the aggregation function documented for grouped frequency counting; groupBy() is. D is close, but it relies on the default count behavior rather than explicitly specifying function=count(). Since the question asks which query will output the frequency of a unique set, C is the most correct and explicit choice.

The @timestamp field in CrowdStrike Parsing Standard (CPS) uses the ISO 8601 format, which provides a standardized, human-readable, and timezone-aware representation of date and time for consistent log processing and correlation.

The sample log is a comma-delimited record with values separated by commas, and some fields are enclosed in quotes. That structure matches CSV-style parsing . In CrowdStrike LogScale, parseCsv() is used for delimited logs where fields appear in a consistent order and are separated by a defined delimiter. This fits the sample shown.
Why the other options are incorrect:
A). XML is incorrect because the log does not use XML tags.
C). JSON is incorrect because the log is not in brace-based key/value JSON format.
D). Key-Value is incorrect because the fields are not expressed as key=value pairs; they are positional comma- separated values instead.