OTCA Study Plan

How to prepare for the OpenTelemetry Certified Associate exam — a structured study plan covering all domains in priority order.

Prerequisites before you start

Basic observability concepts (metrics, traces, logs). Familiarity with Prometheus helps. Understanding of microservices architecture.

4-week OTCA study schedule

This schedule works whether you have 4 weeks or 4 months — compress or expand each week based on your available time. Engineers with relevant background can often move faster through early weeks.

• Week 1
  OpenTelemetry API and SDK (46%)

  The largest domain by far: OTel API vs SDK split (API is the interface, SDK is the implementation), TracerProvider, MeterProvider, LoggerProvider, context propagation, baggage, W3C TraceContext, sampling strategies (head vs tail). This domain alone is nearly half the exam.

• Week 2
  OpenTelemetry Collector (26%)

  Collector architecture: receivers, processors, exporters, connectors, extensions pipeline. Collector deployment modes: agent vs gateway. Configuration YAML structure. Common processors: batch, memory_limiter, attributes, transform. Common exporters: OTLP, Prometheus, logging.

• Week 3
  Observability Fundamentals & Pipeline Maintenance

  Fundamentals of Observability (18%): the three pillars (traces, metrics, logs), distributed tracing concepts, span relationships, trace context. Maintaining and Debugging Observability Pipelines (10%): troubleshooting collector pipelines, data quality, telemetry backpressure, zPages for health.

• Week 4
  Mock Exams & Targeted Review

  Run timed mocks targeting 85%+. The API/SDK domain is both the largest and most technically precise — review instrumentation patterns, context propagation, and sampling strategies. Collector pipeline configuration is the second highest-value review area.

Study tips for OTCA

• The OpenTelemetry API and SDK domain is 46% of the exam — understand the separation of concerns: API defines interfaces, SDK implements them. Instrumentation libraries use the API; backends need the SDK.
• Context propagation and W3C TraceContext are heavily tested. Know what trace-id, span-id, and trace-flags are and how they flow across service boundaries.
• Sampling is a nuanced topic: head-based sampling (decision at trace start) vs tail-based sampling (decision after trace completion). Know the tradeoffs.
• The Collector is the operational component most teams interact with — understand the receivers → processors → exporters pipeline deeply.

Mock exam strategy

Mock exams are the most important study tool for associate-level CNCF certs. Here is how to use them effectively:

• Take your first mock without studying — use the results as a diagnostic to see your baseline and find your weakest domains.
• Study the domains you missed most, not the ones you already know.
• Always do mocks under real conditions: no notes, 90-minute timer, no pausing.
• Review every wrong answer after each mock. Understanding why wrong answers are wrong is as valuable as knowing the right answer.
• Target 85%+ consistently before booking the real exam. The extra buffer protects against nerves on exam day.

Recommended OTCA resources

• Official CNCF OTCA curriculum — the authoritative list of topics. Use it as your checklist.
• The OTCA exam is closed-book — read official documentation now, not on exam day.
• Community Slack channels (CNCF Slack #certifications) have real candidates discussing recent exam experiences.