Splunk O11y Cloud Certified Metrics User Free Sample Questions

Description

Covers chart and timechart visualizations, the eval, search and where commands, correlating events into transactions, field extraction, aliases, macros, workflow actions, and the CIM add-on.

12 free sample questions148 in the full practice test

Try simulator

SPLK-4001 Sample Questions

  1. Question 1

    Intermediate

    Get Metrics In with OpenTelemetry · Configure the OTel Collector

    While reviewing /etc/otel/collector/agent_config.yaml on a Linux host, a platform engineer needs to route incoming trace spans through a first pipeline to extract span metrics and then feed those generated metrics directly into a second metrics pipeline within the same Splunk Distribution of the OpenTelemetry Collector instance. The engineer also needs to ensure the health_check extension is active.

    Which Collector component type acts simultaneously as an exporter at the end of the first pipeline and as a receiver at the beginning of the second pipeline, and where must health_check be enabled?

    flowchart LR subgraph P1["Pipeline 1: traces"] R1[OTLP Receiver] --> PR1[Batch Processor] end subgraph P2["Pipeline 2: metrics"] PR2[Memory Limiter] --> E2[SignalFx Exporter] end PR1 --> C{Component ?} C --> PR2
    Answer and explanation

    Correct answer: C

    In the Splunk Distribution of the OpenTelemetry Collector, a Connector links two pipelines by acting as an exporter at the end of the first pipeline and as a receiver at the beginning of the second pipeline. The service section contains two primary elements: extensions (a list of enabled optional capabilities such as health_check) and pipelines (which link receivers, processors, and exporters). Extensions are never placed inside individual pipelines under service.pipelines, and processors only modify telemetry within a pipeline rather than bridging two separate pipelines.

  2. Question 2

    IntermediateMultiple answers

    Get Metrics In with OpenTelemetry · Configure the OTel Collector

    During a configuration audit of a newly deployed Splunk Distribution of the OpenTelemetry Collector on a Linux server, a site reliability engineer inspects how components and pipelines are wired in the YAML configuration file. Which TWO statements accurately describe valid pipeline configuration rules in the Collector? (Select TWO)

    Answer and explanation

    Correct answers: C, E

    A Collector YAML configuration can define multiple pipelines under service.pipelines, and a single receiver or exporter definition can be referenced and reused across multiple pipelines. Furthermore, a single pipeline can include multiple receivers and multiple exporters. Components defined in top-level sections (receivers, processors, exporters) do nothing unless they are explicitly added to a pipeline under service.pipelines, and extensions are enabled under service.extensions rather than inside individual pipelines.

    A single pipeline under service.pipelines can include multiple receivers (for example, jaeger, otlp, and zipkin in the default trace pipeline) as well as multiple exporters (such as otlp_http and signalfx). Additionally, a single receiver or exporter definition can be reused across multiple pipelines.

  3. Question 3

    Beginner

    Get Metrics In with OpenTelemetry · Configure the OTel Collector

    In the default Linux configuration of the Splunk Distribution of the OpenTelemetry Collector, the default trace pipeline includes the Jaeger gRPC, OTLP, and Zipkin receivers, processes data through the Memory Limiter, Batch, and Resource detection processors, and exports telemetry using the OTLP/HTTP exporter and the _____ exporter.

    Answer and explanation

    Correct answer: A

    In the default configuration for the Splunk Distribution of the OpenTelemetry Collector on Linux, the default trace pipeline uses Jaeger gRPC, OTLP receiver, and Zipkin receiver as receivers; Memory Limiter processor, Batch processor, and Resource detection processor as processors; and OTLP/HTTP exporter and SignalFx exporter as exporters. Prometheus and Fluent Forward are used as receivers in default internal metrics and logs pipelines respectively, not as trace pipeline exporters.

  4. Question 4

    Intermediate

    Metrics Concepts · Data resolution, rollups

    An infrastructure architect configures a custom telemetry script to emit standard-resolution gauge datapoints for system.cpu.utilization every 2 seconds to Splunk Infrastructure Monitoring. When an operator later views this metric over a 7-day window in a chart with a custom SignalFlow analytics function applied, how does Splunk Observability Cloud process the resolution and rollup of these datapoints?

    Answer and explanation

    Correct answer: A

    While high-resolution datapoints can keep a native resolution as fine as 1 second, standard-resolution metrics sent more frequently than every 10 seconds are automatically rolled up to an effective native resolution of 10 seconds. For gauge metrics (such as CPU utilization, memory usage, and fan speed), Splunk Observability Cloud uses the average() rollup function by default. Rollups always execute on each individual MTS after datapoints are fetched from storage and before any SignalFlow analytics functions run.

  5. Question 5

    Beginner

    Metrics Concepts · Data resolution, rollups

    While tuning the visual granularity of a dashboard chart in Splunk Observability Cloud, a performance analyst navigates to the Chart Options tab to adjust the Minimum chart resolution setting. Which set of selectable values is available for Minimum chart resolution?

    Answer and explanation

    Correct answer: B

    On the Chart Options tab in Chart Builder, the selectable values for Minimum chart resolution are Auto, One second (1s), Five seconds (5s), Ten seconds (10s), Thirty seconds (30s), One minute (1m), and One hour (1h). Selecting a coarser minimum chart resolution forces the chart to condense datapoints over wider intervals even on shorter time ranges.

  6. Question 6

    Beginner

    Metrics Concepts · Data resolution, rollups

    True or False: When Splunk Infrastructure Monitoring stores datapoints for a metric time series (MTS), it pre-computes interval rollups including Sum, Min, Max, and Count.

    Answer and explanation

    Correct answer: A

    When storing datapoints for a metric time series (MTS), Splunk Infrastructure Monitoring pre-computes interval rollups including Sum, Min, Max, and Count. Pre-computing these values allows Splunk Observability Cloud to rapidly serve rolled-up datapoints (including Average, which is derived from Sum divided by Count) over long time windows.

Register free for 6 more questions

Or unlock all 148 SPLK-4001 questions with explanations, timed mode and flashcards.