The correct answer is B . CrowdStrike states that AI-generated parsers are built from sample log records .
Falcon Next-Gen SIEM analyzes those samples to learn the logs' structure and content, so providing representative examples is the documented way to help the parser interpret and categorize data correctly.
Options A and C are not supported by CrowdStrike documentation. There is no requirement for a minimum parser length, and Next-Gen SIEM parsers are not written as Python or Java programs; CrowdStrike's parser template shows a parser schema and script structure specific to Next-Gen SIEM.

The correct answer is B. sudo logscale-collector enroll < TOKEN > .
Current CrowdStrike LogScale Collector documentation shows the enrollment command using the logscale- collector binary. For example, the macOS custom installation page explicitly shows:
sudo logscale-collector enroll enrolltoken
The Fleet Management enrollment documentation also explains that you copy the enrollment command from the UI and run it on the machine hosting the collector.
Why the other options are incorrect:
A is a Windows path, not Linux. C reflects the older humio-log-collector naming that existed in earlier versions and release history, but the current docs use logscale-collector for the enrollment command. D does not match the documented command syntax. CrowdStrike's current documentation centers the enrollment workflow on logscale-collector enroll < token > .

The correct answer is B. #event.dataset .
CrowdStrike's CPS documentation explicitly lists #event.dataset as one of the CPS-compliant parser tags.
The CPS migration documentation also repeats that CPS-compliant parsers use tags for fields including #ecs.
version , #event.dataset , and #event.kind .
Why the other options are incorrect:
Parser.type and Parser.name are not listed as CPS-compliant tags in the CPS standard.
#event.trigger is also not listed among the CPS-compliant fields/tags.
Therefore, the only CPS-compliant option given is #event.dataset .

CrowdStrike's Fleet Management documentation for Falcon LogScale Collector explains that labels are used to associate metadata with a Fleet Management configuration and with collector instances so they can be tagged, identified, organized, and filtered. The docs specifically describe labels as helping organize collectors by criteria such as environment, region, service, or other custom values. That directly matches option B:
Categorize collectors for group configurations .
Why the other options are incorrect:
Option A is incorrect because labels are not used for authentication or password management.
Option C is incorrect because labels do not perform traffic monitoring; they are metadata for organization and selection.
Option D is incorrect because labels do not assign network settings such as IP addresses.