Question 150
A Splunk Enterprise administrator is investigating this situation: While evaluating a healthcare monitoring network in a regulatory evidence review, operations report: A HEC sender receives HTTP success responses but does not know whether configured indexer acknowledgment is in use. Which corrective action is the best next step?
Explanation
Correct Answer
Review HEC token and acknowledgment settings and test the intended delivery confirmation workflow. The important distinction is that HTTP acceptance and explicit indexer acknowledgment can provide different assurance semantics. Verify the result with this check: The client demonstrates the expected receipt or acknowledgment status for a test batch.
Incorrect Answers
That action is aimed at another operational symptom: A partner needs an HTTPS event ingest path but wants to avoid embedding user administrator passwords in its code. The reported issue instead depends on this requirement: HTTP acceptance and explicit indexer acknowledgment can provide different assurance semantics. The expected validation is The client demonstrates the expected receipt or acknowledgment status for a test batch.
This alternative addresses the separate case “At a cloud migration program during a verification workshop, reviewers observe the following: An application sends JSON to an HTTP collector endpoint but is rejected because no HEC token is configured”. Enable HTTP Event Collector where required and create an authorized token with the correct index permissions. The deciding requirement here is “Review HEC token and acknowledgment settings and test the intended delivery confirmation workflow”.
The option would apply to “An operations group needs remote Windows performance data but the monitored hosts cannot accept a new agent”. Evaluate a supported Windows-based WMI collection host with appropriate permissions and network reachability. This question instead requires “Review HEC token and acknowledgment settings and test the intended delivery confirmation workflow”.