Medium1 markMultiple Choice
Domain 1.1: Logging and MonitoringDomain 1MonitoringApplication InsightsArchitecture

AZ-305 · Question 04 · Domain 1.1: Logging and Monitoring

You are designing an application monitoring strategy using Application Insights. The application consists of a frontend web app, a backend API, and a background worker process, all hosted on Azure App Service.

The development team wants to trace requests end-to-end across all three components. They also need to ensure that telemetry data is not lost if the application experiences a sudden spike in traffic, but they want to control ingestion costs.

Which TWO features should you configure? (Select TWO)

Answer options:

A.

W3C Trace Context

B.

Fixed-rate Sampling

C.

Adaptive Sampling

D.

Azure Monitor Metrics Routing

E.

Availability Tests

How to approach this question

Identify the standard for distributed tracing and the sampling method that dynamically adjusts to traffic volume.

Full Answer

W3C Trace Context, Adaptive Sampling
To trace requests end-to-end across multiple services (distributed tracing), Application Insights uses the W3C Trace Context standard to pass correlation IDs. To manage ingestion costs during traffic spikes without losing all visibility, Adaptive Sampling is used. It runs in the Application Insights SDK and automatically reduces the sampling rate when traffic is high, and increases it when traffic is low.

Common mistakes

Selecting Fixed-rate sampling instead of Adaptive. Fixed-rate doesn't react to sudden spikes dynamically.

Practice the full Azure Solutions Architect Expert AZ-305 Practice Exam 5

55 questions · hints · full answers · grading

More questions from this exam