Which Application Insights API aggregates distributor API telemetry?
Short answer
C TrackMetric sends pre-aggregated metric telemetry, which aggregates distributor API values and cuts telemetry traffic and storage costs.
Question
Key Takeaways
Tests the distinction between single-event APIs like TrackEvent and TrackMetric's pre-aggregated metrics; the trap is choosing TrackEvent because telemetry sounds like events.
Application Insights TrackMetric supports pre-aggregated metric telemetry, making it the right API for aggregating distributor API call values at scale. This guide confirms why TrackMetric (C) is correct for reducing telemetry traffic, data costs, and storage costs.
Common mistake: Choosing TrackEvent (A) because 'telemetry values' sounds like custom events, but TrackEvent sends individual events and does not support pre-aggregation, causing high traffic and storage costs.
Expert Analysis
Why the Answer Is Correct
TrackMetric is the Application Insights API method specifically designed to send metric telemetry, and it supports both single measurements and pre-aggregated metrics that include minimum, maximum, standard deviation, and count over an aggregation interval. The case study explicitly requires an aggregate of telemetry values for distributor API calls while reducing telemetry traffic, data costs, and storage costs. Pre-aggregated metrics sent via TrackMetric combine many values into a single telemetry item, directly satisfying that requirement without losing statistically correct analysis. Both Luxlux and Vichu_1607 linked to the official TrackMetric documentation, and 1CY1 explained that Application Insights supports "single measurement and preaggregated metric" telemetry types. Therefore TrackMetric (C) is the correct API method.Why the Other Options Are Wrong
TrackEvent (A) records custom business or user events, and each call produces an individual event item that does not inherently aggregate multiple values, so it would increase telemetry volume rather than reduce it. TrackDependency (B) captures calls to external dependencies such as HTTP endpoints or SQL databases, which is valuable for distributed tracing but not for aggregating custom API resource data. TrackException (D) logs exception details and stack traces, and TrackTrace (E) writes diagnostic trace messages; neither supports pre-aggregated metric values for statistical trend analysis. None of these alternatives provide the pre-aggregation capability that the requirement for reduced traffic, data costs, and storage costs demands.Community Comment Notes
Community consensus strongly favors TrackMetric: Luxlux posted the TrackMetric documentation link, Ciupaz stated, "The correct answer is C. TrackMetric," and Vichu_1607 also answered TrackMetric. AzDeveloper pointed to the Application Insights data model documentation as supporting evidence for the choice. 1CY1 added detail by noting that Application Insights metric telemetry supports "single measurement and preaggregated metric" types, with pre-aggregated metrics specifying minimum, maximum, and standard deviation values. These comments align with Microsoft's guidance that pre-aggregated metrics reduce telemetry volume while preserving statistical accuracy.Official Reference
- https://learn.microsoft.com/en-us/azure/azure-monitor/app/api-custom-events-metrics#trackmetric
- https://learn.microsoft.com/en-us/azure/azure-monitor/app/data-model-complete
These links open the official vendor documentation in a new tab.
Exam Strategy
When a case study asks for aggregation, cost reduction, or statistical accuracy of telemetry, look for TrackMetric with pre-aggregated metrics rather than event-per-call APIs. Remember that TrackEvent, TrackTrace, and TrackException each create individual telemetry items, so they increase volume and cost. Confirm the noun in the requirement: 'metric' or 'aggregate' points to TrackMetric.
Frequently Asked Questions
Why does TrackMetric support aggregation better than TrackEvent for distributor API calls?
How does pre-aggregated metric telemetry reduce Application Insights data and storage costs?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
Luxlux 👍 5 Answered Chttps://learn.microsoft.com/en-us/azure/azure-monitor/app/api-custom-events-metrics#trackmetric
-
1CY1 👍 4Requirement : aggregate of telemetry values for distributor API calls. C : Metric (Correct) Application Insights supports two types of metric telemetry: single measurement and preaggregated metric. Single measurement is just a name and value. Preaggregated metric specifies the minimum and maximum value of the metric in the aggregation interval and the standard deviation of it. Dependency: Represents a call from your app to an external service or storage. Exception: Typically represents an exception that causes an operation to fail. Trace: Used either directly or through an adapter to implement diagnostics logging by using an instrumentation framework that's familiar to you, such as Log4Net or System.Diagnostics. Event: Typically used to capture user interaction with your service to analyze usage patterns.
-
Ciupaz 👍 3 Answered CThe correct answer is C. TrackMetric.
-
AzDeveloper 👍 2It seems C is correct answer https://learn.microsoft.com/en-us/azure/azure-monitor/app/data-model-complete
-
Vichu_1607 👍 1 Answered CTrackMetric
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.