nerdexam
Microsoft

AZ-204 · Question #604

You develop an ASP. Net Core application by integrating the Application Insights SDK into your solution. The application sends a very high rate of telemetry in a short time interval. You observe a…

The correct answer is B. Disable adaptive sampling. Enable and configure the fixed-rate sampling module. To address high telemetry volume, costs, and ingestion errors while preserving statistical correctness and correlation in Application Insights, configure sampling within the SDK.

Submitted by eva_at· Mar 30, 2026Monitor, troubleshoot, and optimize Azure solutions

Question

You develop an ASP. Net Core application by integrating the Application Insights SDK into your solution. The application sends a very high rate of telemetry in a short time interval. You observe a reduced number of events, traces, and metrics being recorded and increased error rates for telemetry ingestion. You need to reduce telemetry traffic, data costs, and storage costs while preserving a statistically correct analysis of application telemetry data. Your solution must ensure that you will be able to correlate HTTP request and response data. What should you do?

Options

  • AConfigure a Log Analytics workspace data collection rule (DCR). Use a Kusto Query Language
  • BDisable adaptive sampling. Enable and configure the fixed-rate sampling module.
  • CSet a daily cap on the Log Analytics workspace. Create an Activity log alert rule.
  • DConfigure the TelemetryConfiguration object in the instrumented code. Increase the metric

How the community answered

(19 responses)
  • A
    5% (1)
  • B
    79% (15)
  • C
    11% (2)
  • D
    5% (1)

Why each option

To address high telemetry volume, costs, and ingestion errors while preserving statistical correctness and correlation in Application Insights, configure sampling within the SDK.

AConfigure a Log Analytics workspace data collection rule (DCR). Use a Kusto Query Language

Data collection rules (DCRs) are primarily used for collecting logs into Log Analytics, not for reducing telemetry traffic generated by the Application Insights SDK at the source. KQL is for querying data, not for ingestion control.

BDisable adaptive sampling. Enable and configure the fixed-rate sampling module.Correct

Enabling and configuring the fixed-rate sampling module in the Application Insights SDK directly reduces the volume of telemetry data sent, thereby lowering traffic, data costs, and storage costs. Sampling is designed to preserve statistically correct analysis and ensures correlation by sampling related items together, addressing all specified requirements for high telemetry rates.

CSet a daily cap on the Log Analytics workspace. Create an Activity log alert rule.

A daily cap on a Log Analytics workspace stops data ingestion once reached, leading to data loss and preventing statistically correct analysis, rather than intelligently reducing traffic from the source. It does not reduce the telemetry traffic generated by the application.

DConfigure the TelemetryConfiguration object in the instrumented code. Increase the metric

While `TelemetryConfiguration` is used for configuring sampling, 'increase the metric' is vague and counterproductive to the goal of reducing telemetry traffic. Configuring sampling involves setting a percentage, not 'increasing the metric.'

Concept tested: Application Insights telemetry sampling

Source: https://learn.microsoft.com/en-us/azure/azure-monitor/app/sampling

Topics

#Application Insights#sampling#HTTP correlation#telemetry reduction

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-204 Practice