SPLK-2001 practice question 9 of 15
Which HTTP Event Collector (HEC) endpoint should be used to collect data in the following format? {“message”:“Hello World”, “foo”:“bar”, “pony”:“buttercup”}
Full set: 66 questionsThe services/collector path is the base endpoint for the Splunk HTTP Event Collector (HEC) used for data ingestion. The provided data is a structured JSON object, which is specifically handled by the /services/collector/event endpoint. Since /services/collector/event is not an available option, the base path services/collector is the most appropriate choice. This correctly identifies the data collection service, distinguishing it from REST API endpoints used for configuration or endpoints for different data types.
A. data/inputs/http/{name} is a REST API endpoint for configuring a specific HEC token, not for sending event data.
B. services/collector/raw is the HEC endpoint for sending unstructured, raw text data, not structured JSON objects.
D. data/inputs/http is the base REST API endpoint for managing HEC configurations, not for ingesting data.
1. Splunk Enterprise Documentation, Getting Data In Manual, "Set up and use HTTP Event Collector in Splunk Web": This document specifies the different HEC endpoints. It states, "The two types of HEC endpoints are the /services/collector/event endpoint, for JSON-formatted events, and the /services/collector/raw endpoint, for raw text." This confirms that the provided JSON data is intended for an endpoint under the /services/collector path and that the /raw endpoint is incorrect.
2. Splunk Enterprise Documentation, REST API Reference Manual, "data/inputs/http": This reference describes the endpoints for managing HEC tokens. It states, "Use this endpoint to create, view, and edit HTTP Event Collector tokens." This confirms that the data/inputs/http path (options A and D) is for configuration, not data ingestion.
3. Splunk Enterprise Documentation, Getting Data In Manual, "Format events for HTTP Event Collector": This section details the required JSON wrapper for the /event endpoint. It clarifies that structured JSON like the example is the intended format for the event collector, distinguishing it from the /raw endpoint. The base path for this functionality is services/collector.
Keep practicing
Take the free SPLK-2001 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other SPLK-2001 practice questions
- Question 1Searching “index=_internal metrics | head 3” from Splunk Web returned the following event…
- Question 2In order to successfully accelerate a report, which criteria must the search meet? (Selec…
- Question 3After updating a dashboard in myApp, a Splunk admin moves myApp to a different Splunk ins…
- Question 4How can indexer acknowledgement be enabled for HTTP Event Collector (HEC)? (Select all th…
- Question 5Which of the following is an example of a Splunk KV store use case? (Select all that appl…
- Question 6Data can be added to a KV store collection in which of the following format(s)?
