Question 490
During an approved dashboard reliability review for Driftwood Telecom in its multi-tenant Falcon environment, a SIEM platform engineer reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: An internal API logs identity actions under nested JSON paths but searches cannot filter by user or action. The authorized diagnostic packet is NGSIEM-LAB-0123. A stable event identifier and measured ingestion timestamp are present in the evidence. Keep events from other unaffected source integrations available. Which independently observable result BEST demonstrates this particular SIEM engineering issue has been corrected?
Explanation
Correct Answer
Option C is best answer to this acceptance evidence question. The directly observable acceptance result is: A synthetic policy-update record can be found by the expected normalized user and action. This verifies that Write a custom parser extracting the correct nested paths into common actor and action fields addresses the specific observation (An internal API logs identity actions under nested JSON paths but searches cannot filter by user or action). The technical distinction is: Raw JSON is stored without extracting and normalizing the nested security-relevant attributes.
Incorrect Answers
Option A would verify a separate condition: A vendor sends two incompatible severity concepts and a parser silently treats both as a single normalized severity. The observed issue here is: An internal API logs identity actions under nested JSON paths but searches cannot filter by user or action. The necessary acceptance evidence is: A synthetic policy-update record can be found by the expected normalized user and action.
Option B would verify a separate condition: A new custom parser extracts fields but omits the dataset and source tags required by cross-source search filters. The observed issue here is: An internal API logs identity actions under nested JSON paths but searches cannot filter by user or action. The necessary acceptance evidence is: A synthetic policy-update record can be found by the expected normalized user and action.
Option D would verify a separate condition: A proprietary building-access device emits fixed-width records unsupported by built-in SIEM parsers. The observed issue here is: An internal API logs identity actions under nested JSON paths but searches cannot filter by user or action. The necessary acceptance evidence is: A synthetic policy-update record can be found by the expected normalized user and action.