Question 121 of 997

Quick Answer

The answer is the GetMetric API. This is the correct choice because it is specifically designed for high-volume custom metrics in Application Insights, performing client-side pre-aggregation before transmission. Instead of sending millions of individual events, GetMetric batches and aggregates the data locally, emitting only the aggregated totals (count, sum, min, max, and standard deviation) at a configurable interval, which drastically reduces network traffic, storage costs, and performance overhead. On the AZ-204 exam, this question tests your understanding of telemetry optimization under load—a common trap is choosing TrackMetric, which sends each event individually and would cause severe throttling at high volumes. Remember the memory tip: "Get it aggregated before you send it" — the "Get" in GetMetric stands for gathering data locally first, not for retrieving stored values.

AZ-204 Practice Question: Monitor, troubleshoot, and optimize Azure solutions

This AZ-204 practice question tests your understanding of monitor, troubleshoot, and optimize azure solutions. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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.

You need to emit a custom metric in Application Insights that tracks the number of page views per browser. You expect high volume (millions of events per day). Which API should you use to ensure efficient pre-aggregation and avoid performance issues?

Question 1hardmultiple choice
Full question →

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

GetMetric

C is correct because the GetMetric API (previously known as Pre-Aggregated Metric API) is designed for high-volume telemetry scenarios. It pre-aggregates metrics on the client side before sending them to Application Insights, significantly reducing network traffic and storage costs while avoiding performance bottlenecks from millions of individual events.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • TrackEvent

    Why it's wrong here

    TrackEvent sends each event individually. At millions of events per day, this can lead to high costs and potential throttling.

  • TrackMetric

    Why it's wrong here

    TrackMetric does not support dimensions (like browser type) natively and is less flexible for pre-aggregation.

  • GetMetric

    Why this is correct

    GetMetric is designed for high-volume metrics with dimensions and performs client-side aggregation for efficiency.

    Related concept

    Read the scenario before looking for a memorised answer.

  • TrackDependency

    Why it's wrong here

    TrackDependency is used for recording calls to external dependencies, not for custom metrics like page views.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse TrackEvent (for custom events) with metric tracking, or assume TrackMetric is the correct choice because of its name, not realizing it is deprecated and lacks client-side pre-aggregation.

Detailed technical explanation

How to think about this question

The GetMetric API uses a hash-based aggregation bucket on the client side, combining dimensions (e.g., browser name) into a single metric time series. It supports both aggregation and distribution tracking, and the SDK automatically flushes aggregated data at intervals (default 60 seconds) or when a certain number of distinct aggregation keys are reached. In high-volume scenarios, this reduces the number of telemetry items sent to Application Insights from millions to thousands, while preserving accuracy through statistical counters (count, sum, min, max, standard deviation).

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

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

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

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.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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 — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: GetMetric — C is correct because the GetMetric API (previously known as Pre-Aggregated Metric API) is designed for high-volume telemetry scenarios. It pre-aggregates metrics on the client side before sending them to Application Insights, significantly reducing network traffic and storage costs while avoiding performance bottlenecks from millions of individual events.

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

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

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

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.