What is the purpose of the trace ID in context propagation?

To uniquely identify the entire trace across all services

To identify the specific operation within a service

To authenticate the request between services

To store the sampling decision for the trace

How is trace context typically propagated between services in an HTTP-based distributed system?

By storing the trace ID in a shared database accessible to all services

By using the source IP address of the request to identify the trace

By including trace and span identifiers in HTTP headers

By embedding the trace ID in the URL path of each request

A trace for a request shows the following spans: `api-gateway` (100ms), `order-service` (200ms), `payment-service` (150ms), and `database` (50ms). The `order-service` span has an error. The team also sees a metric showing high CPU usage on the `order-service` node at the time of the request. What is the most likely root cause?

The api-gateway is the root cause because it is the first span.

The payment-service is failing, which causes the order-service to error.

The database is slow, causing the order-service to fail.

The order-service itself is experiencing high CPU usage, which is causing it to error.

What is the primary purpose of distributed tracing in an observability strategy?

To aggregate application logs from all services into a central searchable repository

To automatically remediate performance issues by restarting unhealthy containers

To record and correlate the path of a single request as it travels through multiple services

To collect and analyze metrics such as CPU usage and memory consumption across hosts

What is a key trade-off of tail-based sampling compared to head-based sampling?

Tail-based sampling is simpler to implement and requires no additional infrastructure

Tail-based sampling is less accurate because it makes decisions without complete trace data

Tail-based sampling reduces the amount of trace data collected compared to head-based sampling

Tail-based sampling can capture traces with errors or anomalies, but it requires buffering and processing of all traces

LPI DevOps Tools Engineer

Domain 4Objective 4

704.4 Tracing (weight: 2) DEVOPS-TOOLS-ENGINEER Practice Questions (Page 3)

Part of the 704 Security and Observability domain, which makes up ~26% of our current practice bank. Linux Professional Institute does not publish an official question count, but from its 90-minute exam (~35–60 total, ~9–16 in this domain), expect 2–4 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

8concepts

Questions 11–15

11foundation · easy
What is the purpose of the trace ID in context propagation?
Select an answer first
12foundation · easy
How is trace context typically propagated between services in an HTTP-based distributed system?
Select an answer first
13expert · hard
A trace for a request shows the following spans: `api-gateway` (100ms), `order-service` (200ms), `payment-service` (150ms), and `database` (50ms). The `order-service` span has an error. The team also sees a metric showing high CPU usage on the `order-service` node at the time of the request. What is the most likely root cause?
Select an answer first
14foundation · easy
What is the primary purpose of distributed tracing in an observability strategy?
Select an answer first
15foundation · easy
What is a key trade-off of tail-based sampling compared to head-based sampling?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DEVOPS-TOOLS-ENGINEER

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Professional Institute. “DEVOPS-TOOLS-ENGINEER” is a trademark of its owner, used for identification only.