Free Actual Microsoft Azure AZ-204 Actual Exam Questions - Question 14 Discussion
Insights for all telemetry and dependency tracking. The web service reads and writes data to a
database other than Microsoft SQL Server.
You need to ensure that dependency tracking works for calls to the third-party database.
Which two Dependency Telemetry properties should you store in the database? Each correct answer
presents part of the solution.
NOTE: Each correct selection is worth one point.
It’s A and E for me. Operation.Id is key to link the dependency call back to the request, making sure you track the full transaction chain. Then, Name helps identify what specific dependency or operation was called, which is crucial for analysis. Telemetry.Id (C) tracks the telemetry item itself but doesn’t help as much with correlating multiple calls in context. Cloud.RoleInstance (B) is more about where it ran, not the call itself. Session.Id (D) is user-session focused, so less relevant here. So A and E make the most sense to store for effective dependency tracking.
A Telemetry.Context.Operation.Id is definitely needed for correlation. I’d also pick C Telemetry.Id because it uniquely tracks each dependency call, which helps when analyzing individual requests or issues.
Option A is a must for correlation; second pick is E to name the dependency clearly.
Maybe B, since Cloud.RoleInstance can identify the app instance making the call, useful for dependencies.
I agree that Operation.Id (A) is important for correlation across different components, so it has to be one. For the second property, I’d go with Telemetry.Id (C) because it uniquely identifies each telemetry item, which helps track individual database calls. The Name (E) is useful but less critical for linking dependencies compared to these two. So my picks are A and C.
Makes sense to include Operation.Id (A) since it's crucial for correlating distributed traces, and Telemetry.Id (C) uniquely identifies each dependency call, so those two should do the trick.
A/E? Operation.Id helps link telemetry across components, and Name identifies the dependency call. Seen similar tracking setups where these two were key to correlation and clarity.