OpenTelemetry Certified Associate (OTCA) free question 9 / 10 · Domain 3: The OpenTelemetry Collector
Which classification of Collector components does the scaling guidance use?
- Receivers, processors, and exporters
- Stateless components, scrapers, and stateful components
- Agents, gateways, and sidecars
- Push-based, pull-based, and batch-based components
Show the answer and explanation
Answer: B
Why this is correct
At the how-to-scale step the guidance sorts the components into three types. Most Collector components are stateless, since any state they hold in memory is not relevant for scaling. Scrapers, like the Prometheus receiver, obtain data from external locations. Components like the tail sampling processor keep relevant state in memory and need careful consideration before they are scaled up.
Why the other options are wrong
"Receivers, processors, and exporters" … These are pipeline component types. The scaling guidance groups components by how they behave when scaled.
"Agents, gateways, and sidecars" … These are deployment patterns and forms, not a classification of components.
"Push-based, pull-based, and batch-based components" … The guidance does not group components by how data reaches them. It separates stateless components, scrapers, and stateful components.
Key points
Three types when scaling: stateless (add replicas), scrapers (shard the targets), stateful (route data consistently).