OTCA

OpenTelemetry OTCA practice exams

290 questions in 5 timed practice tests. Each test has about 61 questions and a 90-minute limit. The pass mark is 75%. Results are split across the 4 exam domains.

Exam at a glance

OTCA practice exam settings
Practice tests 5
Questions in total 290
Questions per test About 61
Time limit per test 90 minutes
Pass mark 75%
Question types Single answer and multiple answer (30 multiple-answer questions)
Level Associate
Category DevOps & Cloud Native

These are the settings of our practice tests. Check the official CNCF exam page for the current exam format before you book.

Domains and weights

OTCA exam domains, weights and question counts
Domain Weight Weight bar Questions in our bank
Fundamentals of Observability 18% 52
The OpenTelemetry API and SDK 46% 134
The OpenTelemetry Collector 26% 75
Maintaining and Debugging Observability Pipelines 10% 29

Sample questions

Question 1 of 3

An SRE wants to report the 99th-percentile latency of an API across 40 replicas. Each replica currently computes its own p99 and the team averages those values. Why is this approach misleading, and what is the better instrument choice?

  1. A Per-replica p99 values are already exact; they only need to be weighted by each replica's CPU utilization before averaging
  2. B Averages of percentiles overstate tail latency; record a gauge of the latest request duration on each replica instead
  3. C Percentiles are only valid for counters; record a monotonic counter of total duration on every replica and divide it by the request count
  4. D Percentiles cannot be averaged; record a histogram on each replica and compute the percentile from merged buckets (correct answer)
Why: Percentiles are not additive, so averaging per-replica p99 values does not yield the fleet-wide p99; histograms can be merged bucket by bucket and the percentile estimated from the combined distribution. A gauge of the latest duration samples only one request. Total duration divided by count gives a mean, not a tail percentile, and weighting by CPU does not fix the math.

Question 2 of 3, choose 2

Which statements correctly compare head-based and tail-based sampling? (Choose two.)

  1. A Head-based sampling always keeps more error traces than tail-based sampling
  2. B Tail-based sampling can keep traces with errors or high latency after they finish (correct answer)
  3. C Head-based sampling decides when the trace starts, before its outcome is known (correct answer)
  4. D Head-based sampling requires buffering all spans of a trace in a central component
  5. E Tail-based sampling is decided by the root service's SDK at span start time
Why: Head sampling makes its decision at the start of a trace, which is cheap but blind to errors or latency that occur later. Tail sampling waits until spans are complete so it can keep interesting traces. Buffering complete traces is a tail-sampling requirement, tail sampling is not decided at span start, and head sampling does not favour error traces.

Question 3 of 3, choose 2

A backend that ingests OTLP metrics charges by stored series and works best with delta temporality, while the team's Prometheus server scrapes the same app. Which statements are correct? (Choose two.)

  1. A Prometheus scraping expects cumulative temporality for counters and histograms (correct answer)
  2. B Cumulative temporality cannot be produced for asynchronous counter instruments
  3. C Temporality preference is set per exporter or reader, so each path can choose its own (correct answer)
  4. D Delta temporality is required for any exporter that uses the OTLP protocol
  5. E Temporality is fixed per instrument at creation time and cannot vary by exporter
Why: Temporality is chosen by the MetricReader or exporter, for example via OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE for OTLP, so one app can serve a delta OTLP path and a cumulative Prometheus path. Prometheus is cumulative by design. Instruments do not fix temporality, OTLP supports both temporalities, and asynchronous counters can be exported cumulatively.

What your score report looks like

Example attempt, OTCA practice test 3

79%

Passed
Pass mark 75%

Score by exam domain
DomainWeightYour score%
Fundamentals of Observability 18%
88
The OpenTelemetry API and SDK 46%
81
The OpenTelemetry Collector 26%
76
Maintaining and Debugging Observability Pipelines 10%
58

Study next: Maintaining and Debugging Observability Pipelines. It is below the pass mark and carries 10% of the exam.

Domains and pass mark from our OTCA practice tests. Scores are an example attempt.

Study plans

Two weeks

  1. Day 1: take practice test 1 in exam mode to get a baseline.
  2. Days 2 to 5: domain mode on The OpenTelemetry API and SDK and The OpenTelemetry Collector, the two most heavily weighted domains.
  3. Day 6: practice test 2 in exam mode, then the mistakes quiz.
  4. Days 7 to 12: practice tests 3 to 5, one every other day, each followed by its mistakes quiz.
  5. Days 13 and 14: final mode. Book the exam when your readiness stays above the pass mark.

Four weeks

  1. Week 1: one practice test in practice mode, reading every explanation. Note your two lowest domains.
  2. Week 2: domain mode on those two domains, then a second practice test in exam mode.
  3. Week 3: practice tests 3 and 4 in exam mode, with the mistakes and flagged quizzes after each.
  4. Week 4: practice test 5 and final mode until your readiness holds above the pass mark.

Questions about the OTCA practice exams

Are these real OTCA exam questions?
No. We write every question ourselves and map it to the published OTCA exam objectives. We do not use leaked or recalled questions.
Do the time limit and pass mark match the official exam?
They match the settings of our practice tests. Exam providers change their format from time to time, so check the official exam page before you book.
Can I try it before I pay?
Yes. The free mini exam has 15 questions with full explanations and needs no account.
How long do I keep access?
A single-exam purchase gives you 12 months of access. All-Access includes this exam for as long as your subscription runs.
What happens after I finish a test?
You get a score, a pass or fail against the pass mark, a score per domain and every answer with its explanation.

Last updated November 2026. Written and reviewed by the DevOpsCode Lab team.

DevOpsCode Lab is not affiliated with CNCF. OTCA and related names are trademarks of their owners.

Related exams
Exam Vendor Level Questions Minutes Price
CKSKubernetes Security Specialist (CKS) CNCF Specialty 300 120 $14.99
KSKubernetes Security CNCF Specialty 300 90 $14.99
CAPAArgo CAPA CNCF Associate 300 90 $12.99
CKACertified Kubernetes Administrator (CKA) CNCF Associate 300 120 $12.99
010-160LPI Linux Essentials 010-200 LPI Foundational 200 60 $9.99
GH-900GitHub Foundations GH-900 GitHub Foundational 300 100 $9.99