AKS cluster metrics are normal, but requests between application services intermittently fail. Which addition best explains the failing transaction path?

Choose the single best answer.

A.Increase cluster CPU chart resolution while collecting no application request or dependency spans.
B.Use only managed Prometheus cluster metrics and assume they describe the complete transaction.
C.Add distributed tracing with correlation across application requests and dependencies.
D.Export only cluster management events and use them to infer each application call's result.

Show the answer and explanation

✓ Correct answer

Add distributed tracing with correlation across application requests and dependencies.

Application tracing connects service requests and dependencies, exposing failures beyond cluster-level metrics. CPU resolution and management events do not establish each application's transaction path. Managed Prometheus cluster metrics are useful but cannot replace tracing for this requirement. Source: AZ-305 Study Guide.pdf, PDF page(s) 12.

Read the source reference

This item is flagged for content review.

Read and review here, or open the app to practise and save your results on this device.

Practise in the app

Unofficial study aid; not affiliated with or endorsed by Microsoft. Original practice questions are not real examination questions and do not guarantee an exam result.