OpenTelemetry Certified Associate (OTCA) free question 1 / 10 · Domain 1: Fundamentals of Observability
What do OpenTelemetry semantic conventions provide?
- The wire protocol that SDKs use to send telemetry to the Collector or to a backend
- The storage layer in which traces, metrics, and logs are kept and then visualized
- The rules that decide which fraction of traces an SDK keeps before exporting them
- Common names for operations and data, standardized across codebases, libraries, and platforms
Show the answer and explanation
Answer: D
Why this is correct
The Semantic Conventions page says they "specify common names for different kinds of operations and data." The benefit is a common naming scheme that can be standardized across a codebase, libraries, and platforms. Conventions exist for traces, metrics, logs, profiles, and resources.
Why the other options are wrong
"The wire protocol that SDKs use to send telemetry to the Collector or to a backend" … That protocol is OTLP, which the Code-based instrumentation page describes as a wire protocol supported by all SDKs. Semantic conventions specify names, not the transport.
"The rules that decide which fraction of traces an SDK keeps before exporting them" … Choosing how much data to keep is the job of sampling. Semantic conventions only standardize the names of operations and data.
"The storage layer in which traces, metrics, and logs are kept and then visualized" … The What is OpenTelemetry page says the backend (storage) and the frontend (visualization) of telemetry data are intentionally left to other tools.
Key points
Semantic conventions standardize names and meanings. They do not define transport, sampling, or storage.