The Next-Gen SIEM Connector Dashboard provides visibility into third-party data ingestion, showing metrics such as volume, trends, and connector health over time, including the past 30 days.

When logs have timestamps in a different timezone, cloning the parser and specifying the correct timezone parameter in the parseTimestamp() function ensures accurate time parsing without altering field names or losing data.

The correct answer is B . CrowdStrike LogScale documentation includes parseCEF() , parseJson() , and parseXml() as valid parsing functions. parseCEF() parses CEF-encoded messages, parseJson() parses JSON data into fields, and parseXml() parses XML content into fields.
The other options are incorrect because parseIETF() is not a valid CQL parse function in the documented parsing function set, and option D also contains malformed syntax with parseXml(.

The correct answer is D. Next-Gen SIEM Connector Dashboard .
CrowdStrike describes the Falcon Next-Gen SIEM Connector Dashboard as the place to understand the status and volume of data ingestion for third-party sources. This matches the question's requirement for a dashboard showing third-party ingestion visibility.
The other options are not aimed at third-party SIEM connector ingestion monitoring:
* Sensor Usage Dashboard relates to Falcon sensor usage, not connector-based third-party ingestion.
* Sensor Subscription Dashboard is about licensing/subscription counts.
* Falcon Flex Dashboard is related to subscription consumption and commercial usage, not connector ingestion telemetry.

The correct answer is D .
CrowdStrike's Falcon Next-Gen SIEM materials distinguish between CrowdStrike detections and third- party detections , and also state that Falcon Next-Gen SIEM extends data collection to third-party data sources . That means first-party detections are native to the Falcon platform, while third-party detections originate from data sources outside the platform that have been onboarded into Next-Gen SIEM.
Why the other options are incorrect:
A is wrong because third-party detections are not defined as detections created by the customer's team.
B is wrong because the distinction is not based on visibility permissions.
C is wrong because CrowdStrike does not define first-party detections as inherently higher severity than third- party detections.