Question 764 of 997
Monitor, troubleshoot, and optimize Azure solutionsmediumMultiple ChoiceObjective-mapped

AZ-204 Practice Question: Application Insights adaptive sampling to reduce…

This AZ-204 practice question tests your understanding of monitor, troubleshoot, and optimize azure solutions. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. A key principle to apply: adaptive sampling. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A high-traffic API sends approximately 80,000 telemetry events per second to Application Insights. Monthly ingestion costs are too high. The team wants to reduce data volume by roughly 80 percent while still seeing representative samples of all request types. What should the developer configure?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Enable adaptive sampling in the Application Insights SDK and set a target events-per-second limit

Adaptive sampling in the Application Insights SDK automatically adjusts the volume of telemetry sent to the service, targeting a specified rate of events per second. By setting a target that reduces the original 80,000 events/sec to roughly 20%, the SDK will intelligently sample all request types proportionally, preserving representative data while cutting costs.

Key principle: Adaptive sampling

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Enable adaptive sampling in the Application Insights SDK and set a target events-per-second limit

    Why this is correct

    Adaptive sampling runs in the SDK. It monitors the outgoing telemetry rate and automatically raises or lowers the sample percentage to stay near the target rate. All operation types are sampled proportionally, so statistical trends remain meaningful even at 20 percent of raw volume. Data is reduced before transmission, lowering both network and ingestion costs.

    Related concept

    Adaptive sampling

  • Configure ingestion sampling in the Azure portal to retain 20 percent of incoming telemetry

    Why it's wrong here

    Ingestion sampling discards 80 percent of events after they arrive at the Application Insights endpoint. The data is still transmitted from the application, so network bandwidth is unchanged. It reduces storage and query costs but not the cost of transmitting data from the app.

  • Increase the TelemetryClient flush interval from 30 seconds to 5 minutes to batch events

    Why it's wrong here

    Flush interval controls when buffered events are sent, not how many are sent. Flushing less frequently does not reduce the number of events — it only changes the timing. Total event volume and ingestion cost remain the same.

  • Filter all events with HTTP status code 200 from the telemetry pipeline before sending

    Why it's wrong here

    Filtering out 200-OK requests removes all evidence of successful operations. Metrics like response time percentiles, throughput, and dependency success rates become meaningless. Sampling preserves proportional representation; hard filtering destroys observability for the majority of traffic.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse ingestion sampling (a portal-level fixed filter) with adaptive sampling (an SDK-level dynamic filter), assuming any sampling in the portal will suffice, but only adaptive sampling can meet the dual goals of volume reduction and representativeness across all request types.

Detailed technical explanation

How to think about this question

Adaptive sampling uses a dynamic algorithm that monitors the current ingestion rate and adjusts the sampling percentage per telemetry type (e.g., requests, dependencies, exceptions) to stay near the configured target. Under the hood, the SDK maintains a per-second rate counter and applies a sampling decision early in the pipeline, before any expensive serialization or transmission, which minimizes CPU and network overhead. In high-traffic scenarios, this ensures that even during sudden bursts, the system gracefully throttles without overwhelming the backend or exceeding budget.

KKey Concepts to Remember

  • Adaptive sampling
  • Ingestion sampling
  • Telemetry data volume
  • Application Insights SDK

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Adaptive sampling

Real-world example

How this comes up in practice

A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

What to study next

Got this wrong? Here's your next step.

Review adaptive sampling, then practise related AZ-204 questions on the same topic to reinforce the concept.

Related practice questions

Related AZ-204 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-204 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-204 question test?

Monitor, troubleshoot, and optimize Azure solutions — This question tests Monitor, troubleshoot, and optimize Azure solutions — Adaptive sampling.

What is the correct answer to this question?

The correct answer is: Enable adaptive sampling in the Application Insights SDK and set a target events-per-second limit — Adaptive sampling in the Application Insights SDK automatically adjusts the volume of telemetry sent to the service, targeting a specified rate of events per second. By setting a target that reduces the original 80,000 events/sec to roughly 20%, the SDK will intelligently sample all request types proportionally, preserving representative data while cutting costs.

What should I do if I get this AZ-204 question wrong?

Review adaptive sampling, then practise related AZ-204 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Adaptive sampling

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More AZ-204 practice questions

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.