Question 920
A platform change attempts to resolve the following condition: A team applies a search-time field extraction and expects it to remove secrets from already stored _raw values. What observable outcome would demonstrate success?
Explanation
Correct Answer
A raw-event inspection shows new ingested secrets masked or excluded at the authorized tier. This confirms the desired operational outcome. Search-time presentation controls do not remove confidential bytes already persisted in raw events. The administrator should use an appropriate ingest-time masking or dropping control before sensitive content is indexed.
Incorrect Answers
The option would apply to “An ingestion administrator adds a regex in transforms.conf but nothing happens because the appropriate props.conf stanza never references it”. A newly ingested sample triggers the intended transform while unrelated data does not. This question instead requires “A raw-event inspection shows new ingested secrets masked or excluded at the authorized tier”.
This option serves the scenario “A transformation works on an indexer but a similar stanza on a universal forwarder has no effect”. A controlled event is transformed exactly once at the expected tier. The present scenario is distinguished by “A raw-event inspection shows new ingested secrets masked or excluded at the authorized tier”.
This alternative addresses the separate case “Payment-card numbers appear in raw application events and must not be stored unmasked”. A new test event retains harmless context while raw indexed data does not contain the sample secret. The deciding requirement here is “A raw-event inspection shows new ingested secrets masked or excluded at the authorized tier”.