PracticeVideosBlogFlashcardsEspañol
All Practice Exams

100+ Free Datadog APM & Distributed Tracing Fundamentals Practice Questions

Pass your Datadog APM & Distributed Tracing Fundamentals Certification exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
100+ Questions
100% Free
1 / 100
Question 1
Score: 0/0

In Datadog APM, how many services can a single span belong to?

A
B
C
D
to track
2026 Statistics

Key Facts: Datadog APM & Distributed Tracing Fundamentals Exam

$100

Exam Fee (USD)

Datadog

90 questions

75 scored plus 15 unscored pretest

Datadog Exam Guide

2 hours

Maximum Seat Time

Datadog Exam Guide

5 domains

Knowledge areas on the blueprint

Datadog Exam Guide

6 months

Recommended hands-on experience

Datadog (target candidate)

3 years

Certification Validity

Datadog

Datadog's APM & Distributed Tracing Fundamentals exam is a multiple-choice certification delivered via Kryterion Webassessor for a $100 fee, with a 2-hour maximum seat time. It includes 90 questions (75 scored plus 15 unscored pretest), and Datadog does not publicly disclose the passing score. The five domains are APM Fundamentals, Application Instrumentation, Insight Discovery, Visualizing Insights, and Troubleshooting Application using APM. Datadog recommends at least 6 months of hands-on APM experience, and the credential is valid for 3 years.

Sample Datadog APM & Distributed Tracing Fundamentals Practice Questions

Try these sample questions to test your Datadog APM & Distributed Tracing Fundamentals exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1In Datadog APM, what is a trace?
A.The end-to-end journey of a request, represented as a tree of one or more spans
B.A single timed operation, such as one database query or HTTP call
C.A reserved tag used to group telemetry by environment
D.A rolling 15-minute window of raw, unsampled span data
Explanation: A trace tracks the time spent by an application processing a single request, and is composed of one or more spans organized into a parent-child tree. The trace shows the full distributed path of the request across services. Each individual unit of work within that trace is a span.
2What does a single span represent in Datadog APM?
A.A complete request as it flows across every service
B.A named, timed unit of work such as a function call or a database query, with a start time and duration
C.A reserved primary tag applied to all of a service's telemetry
D.An aggregated dashboard widget showing p95 latency
Explanation: A span represents a single logical unit of work over a period of time, such as one HTTP handler invocation or one SQL query. Each span has a name (operation name), a start timestamp, a duration, and tags/metadata. Spans link together via parent-child relationships to form a trace.
3In Datadog APM terminology, what is a 'resource'?
A.A physical host or container that runs the instrumented application
B.The Datadog Agent process that receives traces on port 8126
C.A particular action handled by a service, such as a specific endpoint (GET /users/{id}) or a SQL query, grouped under a span name
D.A saved view in the Trace Explorer
Explanation: A resource is a particular domain-specific action that a service performs, such as a canonical web endpoint or a normalized database query. For a web service, resources are typically the routes (for example GET /users/{id}); for a database service, resources are the queries grouped under a span name like db.query. Resources let you analyze performance per endpoint within a service.
4What is a 'service' in Datadog APM?
A.A single timed operation within a request
B.A saved monitor that alerts on latency
C.A reserved tag whose default value is none
D.A named set of processes that do the same job, grouping together the endpoints, queries, or jobs they handle for scaling and monitoring
Explanation: A service is a named set of processes that perform the same task on behalf of your application, such as a web frontend, an API, or a database. Services are the building blocks of microservice architectures and group together the resources (endpoints, queries, jobs) they serve. The service name is set via DD_SERVICE under unified service tagging.
5What is the primary rationale for adopting APM and distributed tracing in a microservices environment?
A.To follow a single request as it propagates across many services so you can pinpoint where latency and errors originate
B.To replace infrastructure host monitoring entirely
C.To reduce the number of microservices in production
D.To store application source code for version control
Explanation: APM with distributed tracing lets you follow one request end to end as it crosses service boundaries, so you can see exactly which service, resource, or downstream call contributes latency or errors. In a microservices architecture a single user request may touch dozens of services, and tracing stitches those calls into one view via a propagated trace ID. This makes root-cause analysis far faster than examining isolated service logs.
6How is a distributed trace propagated across an HTTP call from one service to another?
A.The full trace tree is serialized into the response body
B.Trace context such as the trace ID and parent span ID is injected into and extracted from HTTP headers so the downstream span links to the upstream trace
C.Each service writes its spans to a shared database that the Agent polls
D.The Datadog Agent broadcasts the trace ID over UDP to all hosts
Explanation: Distributed tracing works by propagating trace context (trace ID, parent span ID, and sampling priority) through request headers. The upstream tracer injects these headers; the downstream tracer extracts them and creates child spans that share the same trace ID. This header propagation is what stitches spans from different services into one continuous trace.
7Which three reserved tags make up Datadog's unified service tagging?
A.host, container, pod
B.team, owner, tier
C.env, service, version
D.trace_id, span_id, parent_id
Explanation: Unified service tagging ties metrics, traces, and logs together using three reserved tags: env, service, and version. These are set through the DD_ENV, DD_SERVICE, and DD_VERSION environment variables (or equivalent config). Using them consistently lets you correlate telemetry and navigate seamlessly between traces, logs, and metrics for the same service and deployment.
8What is the role of the 'env' tag in unified service tagging?
A.It identifies the deployed code version and changes with every release
B.It records the operation name of each span
C.It names the set of processes doing the same job
D.It is the mandatory primary tag identifying the environment (such as prod or staging) that traces are collected from, defaulting to env:none when unset
Explanation: The env tag is the default and mandatory primary tag that scopes telemetry by environment, such as prod, staging, or dev. When data is not tagged with an environment, Datadog assigns env:none. Scoping by env lets you compare and isolate the same service across environments.
9Why does the 'version' tag matter for unified service tagging?
A.It is expected to change with each new deployment so you can compare performance and errors between code versions
B.It must remain constant for the life of a service so dashboards stay stable
C.It is the only tag the Agent uses to route traces
D.It defines the latency threshold T for Apdex
Explanation: The version tag (DD_VERSION) is expected to change with each application deployment, so two different builds carry distinct version values. This enables deployment tracking: you can compare error rates and latency across versions and quickly spot a regression introduced by a new release. It is the foundation of Datadog's version-over-version and canary comparison views.
10In Datadog APM, how many services can a single span belong to?
A.Up to four services depending on tags
B.Exactly one service per span
C.As many services as it has child spans
D.None; spans are not associated with services
Explanation: There can only be one service per span. Each span is attributed to exactly one service, which is why a downstream call appears as a new span owned by the downstream service. This one-to-one mapping is what lets Datadog roll span metrics up cleanly to the owning service.

About the Datadog APM & Distributed Tracing Fundamentals Exam

The Datadog APM & Distributed Tracing Fundamentals certification validates that a candidate can effectively demonstrate overall knowledge of Datadog's APM and Distributed Tracing product, independent of a specific job role. The blueprint covers APM fundamentals such as traces, spans, resources, services, and tracing architectures; application instrumentation with the dd-trace libraries, automatic and custom instrumentation, the Datadog Agent, sampling versus retention, and unified service tagging (env, service, version); insight discovery with the Trace Explorer, service page, flame graphs, and error tracking; visualizing insights through the Service Map, Service Catalog, dashboards, trace metrics, and Apdex; and troubleshooting applications using trace search, log correlation, and monitors. The exam contains 75 scored questions plus 15 unscored pretest questions and is delivered through Kryterion Webassessor.

Questions

90 scored questions

Time Limit

120 minutes (2-hour maximum seat time)

Passing Score

Not publicly disclosed by Datadog

Exam Fee

$100 (Datadog (delivered via Kryterion Webassessor))

Datadog APM & Distributed Tracing Fundamentals Exam Content Outline

~22%

APM Fundamentals

Explains the rationale for APM and Datadog's approach, tracing architectures, the definitions of traces, spans, resources, and services, language-level differences in automatic instrumentation, OOTB versus community tracers, tagging, and retention periods such as the 15-minute Live Search window and 15-day indexed retention.

~26%

Application Instrumentation

Covers the dd-trace tracing libraries, automatic and custom instrumentation, Single Step Instrumentation, the Datadog Agent and trace-agent on port 8126, head-based sampling versus retention, APM data security and SQL obfuscation, trace/log correlation, connecting RUM and traces, profile collection, and deployment tracking via unified service tagging (DD_ENV, DD_SERVICE, DD_VERSION).

~22%

Insight Discovery

Uses the Trace Explorer and service page, key:value search syntax and facets, live versus retained search, flame graphs and the profiler, identifying slow endpoints by latency percentile, error tracking that groups errors into issues, and span summary aggregation.

~16%

Visualizing Insights

Reads the Service Map and Service Catalog, builds service performance dashboards, generates trace and span-based metrics computed on 100% of traffic, and calculates Apdex using the threshold T with satisfied, tolerating (T to 4T), and frustrated (above 4T or error) bands.

~14%

Troubleshooting Application using APM

Applies trace search during incidents, correlates traces with logs and metrics, isolates downstream latency from flame graphs, and configures monitors and alerting on error rate, latency percentiles, and Apdex.

How to Pass the Datadog APM & Distributed Tracing Fundamentals Exam

What You Need to Know

  • Passing score: Not publicly disclosed by Datadog
  • Exam length: 90 questions
  • Time limit: 120 minutes (2-hour maximum seat time)
  • Exam fee: $100

Keys to Passing

  • Complete 500+ practice questions
  • Score 80%+ consistently before scheduling
  • Focus on highest-weighted sections
  • Use our AI tutor for tough concepts

Datadog APM & Distributed Tracing Fundamentals Study Tips from Top Performers

1Master unified service tagging: DD_ENV, DD_SERVICE, and DD_VERSION power correlation, deployment tracking, and version comparisons, and questions frequently hinge on these three reserved tags.
2Know the difference between ingested and indexed spans: Live Search shows all ingested spans for the last 15 minutes with no sampling, while retention filters index spans for 15 days.
3Understand that trace metrics (hits, errors, latency) are computed from 100% of traffic regardless of ingestion sampling, which is why dashboards stay accurate under aggressive sampling.
4Memorize the Apdex bands and formula: satisfied below T, tolerating from T to 4T, frustrated above 4T or on error, with score = (satisfied + tolerating x 0.5) / total.
5Practice reading flame graphs to attribute latency to the right span, and recognize that when a service's own work is fast but total latency is high, a downstream dependency is usually the cause.
6Be fluent in the Trace Explorer search syntax (key:value facets, boolean operators, negation) and know the roles of the service page, Service Map, Service Catalog, and Error Tracking.

Frequently Asked Questions

What are the current exam facts for the Datadog APM & Distributed Tracing Fundamentals exam?

Datadog's APM & Distributed Tracing Fundamentals exam is multiple choice, delivered through Kryterion Webassessor for a $100 fee, with a 2-hour maximum seat time. It includes 90 questions: 75 scored and 15 unscored pretest questions.

What is the passing score for the Datadog APM exam?

Datadog does not publicly disclose a specific passing score or percentage. The exam scores the 75 operational questions, while 15 pretest questions do not affect your result and are not identified during the exam.

Which topics does the Datadog APM exam cover?

The five domains are APM Fundamentals, Application Instrumentation, Insight Discovery, Visualizing Insights, and Troubleshooting Application using APM. Programming, systems architecture, and testing are explicitly out of scope.

How much experience does Datadog recommend before taking the exam?

Datadog recommends ideal candidates have at least 6 months of hands-on experience using the APM & Distributed Tracing product and its associated features, and an understanding of how APM works in production.

How long is the Datadog APM certification valid?

The Datadog APM & Distributed Tracing Fundamentals certification is valid for 3 years from the date you pass, after which you would need to recertify to keep the credential current.

What is the best way to prepare for the Datadog APM exam?

Get hands-on with unified service tagging (env, service, version), the Trace Explorer, flame graphs, retention filters, and Apdex. Then complete Datadog's APM & Distributed Tracing Fundamentals learning path and drill these 100 practice questions until each concept feels routine.