Question 560
An API intermittently times out and developers cannot tell if SQL queries or upstream HTTP calls are slow. Initial testing shows: Slow requests identify the dominant dependency with traceable context. Which limitation should the team still consider?
Explanation
Correct Answer
Sampling may omit rare failures if rates are poorly configured. Distributed traces in Application Insights can correlate dependency spans with request latency. Instrument the supported service and retain correlated SQL dependency telemetry.
Incorrect Answers
That residual-risk statement assumes an invalid guarantee: Correlated per-request dependency telemetry separates SQL time from model or HTTP time.
This limitation misstates what the feature provides: Trace individual slow requests and tail distributions; sampling and correlation matter.
This is not the governing limitation because Sampling and correlated error-span retention must be designed for rare failures and privacy. That assertion removes or misidentifies the relevant residual risk and does not follow from the feature semantics.