Question 350
A subscription platform builds several HEC inputs. Observed: One client's HEC token defaults to an index not included in its role's write authorization. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Valid token events enter the intended index and forbidden destinations are rejected. It provides case-specific verification that the observed behavior (One client's HEC token defaults to an index not included in its role's write authorization) has changed appropriately.
Incorrect Answers
Option B would be useful evidence if the observed failure were “Indexing stops because outputs.conf still lists the decommissioned receiver endpoints”: it checks “Forwarder internal metrics show active connections to the new receiver pool” after the action “Update the approved forwarding group and remove retired targets” addresses “A stale forwarding destination blocks event delivery after receiver migration”. But the current failure is “One client's HEC token defaults to an index not included in its role's write authorization”, linked to “HEC token permissions and allowed indexes restrict the accepted destination”. Here the targeted action is “Restrict token index allowlist and align payload index with assigned permissions”, and the required proof is “Valid token events enter the intended index and forbidden destinations are rejected”.
The proposed signal relates to: The new version fails to parse known sourcetypes because app-level props.conf was not migrated. The evidence for this Splunk source case must instead show: Valid token events enter the intended index and forbidden destinations are rejected.
This result checks another issue, for which the observed symptom is: Forwarder inputs collect the wrong Windows Event Log channel and omit required security audit records. It does not verify recovery for this situation: One client's HEC token defaults to an index not included in its role's write authorization. The relevant success check is: Valid token events enter the intended index and forbidden destinations are rejected.