SPLK-4001 practice question 5 of 10

In the Splunk distribution of the OpenTelemetry Collector, what is the difference between the agent_config.yaml and the splunk-otel-collector.conf files?

Full set: 57 questions
Answer options
A: splunk-otel-collector.conf defines the OpenTelemetry pipeline, and agent_config.yaml sets endpoint URLs and access tokens.
B: splunk-otel-collector.conf configures processors and agent_config.yaml sets the memory limits for the collector.
C: agent_config.yaml configures the gateway's address and splunk-otel-collector.conf sets the memory limits for the collector.
D: agent_config.yaml defines the OpenTelemetry pipeline, and splunk-otel-collector.conf sets endpoint URLs and access tokens. Correct answer
Correct Answer:
D. agent_config.yaml defines the OpenTelemetry pipeline, and splunk-otel-collector.conf sets endpoint URLs and access tokens.
Explanation

In Splunk’s OpenTelemetry Collector packages, the YAML files hold the pipeline logic, while the .conf file only provides environment variables the service consumes at startup.
• /etc/otel/collector/agentconfig.yaml is the main Collector configuration: it specifies receivers, processors, exporters, and builds the OpenTelemetry data pipelines.
• /etc/otel/collector/splunk-otel-collector.conf is an environment file read by systemd; you place SPLUNKACCESSTOKEN, SPLUNKREALM, SPLUNKAPIURL, memory limits, and other endpoint-related variables here. Hence, agentconfig.yaml defines the pipeline, and splunk-otel-collector.conf supplies endpoint URLs, tokens, and similar settings.

Why Incorrect

A. Reverses the actual roles; .conf holds env vars, YAML defines pipeline.
B. Memory limits live in the .conf env file; processors are part of the YAML pipeline, not the .conf file.
C. Gateway address is normally in the YAML config; memory limits in .conf, not vice-versa.

References

1. Splunk Observability Cloud Docs, “Install the Splunk Distribution of the OpenTelemetry Collector for Linux”, section “Configuration files”, bullets 1–3 (docs.splunk.com/Observability/gdi/opentelemetry/collector-linux).

2. Splunk Observability Cloud Docs, “Environment variables for the Collector”, paragraph 1–2 (docs.splunk.com/Observability/gdi/opentelemetry/env-vars).

3. GitHub – splunk-otel-collector packaging README, “Default paths and files”, lines 20-35 (https://github.com/signalfx/splunk-otel-collector).

Scroll to Top