Which Application Insights API aggregates distributor API telemetry?
Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - Munson’s Pickles and Preserves Farm is an agricultural cooperative corporation based in Washington, US, with farms located across the United States. The company supports agricultural production resources by distributing seeds fertilizers, chemicals, fuel, and farm machinery to the farms. Current Environment - The company is migrating all applications from an on-premises datacenter to Microsoft Azure. Applications support distributors, farmers, and internal company staff. Corporate website - • The company hosts a public website located at http://www.munsonspicklesandpreservesfarm.com. The site supports farmers and distributors who request agricultural production resources. Farms - • The company created a new customer tenant in the Microsoft Entra admin center to support authentication and authorization for applications. Distributors - • Distributors integrate their applications with data that is accessible by using APIs hosted at http://www.munsonspicklesandpreservesfarm.com/api to receive and update resource data. Requirements - The application components must meet the following requirements: Corporate website - • The site must be migrated to Azure App Service. • Costs must be minimized when hosting in Azure. • Applications must automatically scale independent of the compute resources. • All code changes must be validated by internal staff before release to production. • File transfer speeds must improve, and webpage-load performance must increase. • All site settings must be centrally stored, secured without using secrets, and encrypted at rest and in transit. • A queue-based load leveling pattern must be implemented by using Azure Service Bus queues to support high volumes of website agricultural production resource requests. Farms - • Farmers must authenticate to applications by using Microsoft Entra ID. Distributors - • The company must track a custom telemetry value with each API call and monitor performance of all APIs. • API telemetry values must be charted to evaluate variations and trends for resource data. Internal staff - • App and API updates must be validated before release to production. • Staff must be able to select a link to direct them back to the production app when validating an app or API update. • Staff profile photos and email must be displayed on the website once they authenticate to applications by using their Microsoft Entra ID. Security - • All web communications must be secured by using TLS/HTTPS. • Web content must be restricted by country/region to support corporate compliance standards. • The principle of least privilege must be applied when providing any user rights or process access rights. • Managed identities for Azure resources must be used to authenticate services that support Microsoft Entra ID authentication. Issues - Corporate website - • Farmers report HTTP 503 errors at the same time as internal staff report that CPU and memory usage are high. • Distributors report HTTP 502 errors at the same time as internal staff report that average response times and networking traffic are high. • Internal staff report webpage load sizes are large and take a long time to load. • Developers receive authentication errors to Service Bus when they debug locally. Distributors - • Many API telemetry values are sent in a short period of time. Telemetry traffic, data costs, and storage costs must be reduced while preserving a statistically correct analysis of the data points sent by the APIs. You need to implement an aggregate of telemetry values for distributor API calls. Which Application Insights API method should you use?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
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.
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.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
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
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?
TrackMetric accepts pre-aggregated metric telemetry with min, max, and standard deviation, while TrackEvent logs each occurrence as a separate custom event, increasing volume and cost.
How does pre-aggregated metric telemetry reduce Application Insights data and storage costs?
You combine many measurements into a single telemetry item before sending, so fewer items are ingested and stored while statistical analysis remains valid.