A high-volume city telemetry API cannot afford to record an X-Ray trace for every request without exploding cost. What sampling approach should the developer apply?
Select an answer to reveal the explanation.
Short Explanation
Tracing every single telemetry hit is like filming every car on the freeway in 4K—you'll learn less than you think and the bill will sting. Dial in a sampling rule so you keep a representative slice without recording everything. That keeps service maps useful and the AWS bill sane.
Full Explanation
AWS X-Ray supports sampling rules so high-throughput applications capture a controlled fraction or reservoir of traces rather than every invocation. Full sampling in production is usually unnecessary and expensive; disabling tracing or multi-region duplication does not solve cost-aware observability. Sensible sampling preserves enough traces to debug latency and errors without unbounded cost.