Question 830
During a Splunk platform review, the team reports: Payment-card numbers appear in raw application events and must not be stored unmasked. What should the administrator do first?
Explanation
Correct Answer
Apply a supported parsing-time masking transformation to redact the sensitive segment before indexing. It is preferable to the other interventions because sensitive fields must be protected before persistence because downstream search permissions are not equivalent to deletion. The operational acceptance evidence is A new test event retains harmless context while raw indexed data does not contain the sample secret.
Incorrect Answers
That action is aimed at another operational symptom: Debug events marked as nonessential consume excessive ingestion and must be dropped by source-specific criteria. The reported issue instead depends on this requirement: Sensitive fields must be protected before persistence because downstream search permissions are not equivalent to deletion. The expected validation is A new test event retains harmless context while raw indexed data does not contain the sample secret.
The option would apply to “Tenant log records must route to separate indexes based on a trusted field in their contents”. Index routing based on event content requires supported parsing-stage classification, not a search-time dashboard filter. This question instead requires “Apply a supported parsing-time masking transformation to redact the sensitive segment before indexing”.
This addresses an appliance embeds a transient password in a predictable raw text fragment and administrators propose deleting it in dashboards only. rather than the stated case. The narrower corrective action is Apply a supported parsing-time masking transformation to redact the sensitive segment before indexing.