BenchMark Quizzes by MDFT Pro

Track Aggregate Telemetry in Application Insights

You work as an API Developer for MDFT Pro, a well-known training agency that provides cloud certification courses to students globally. Mark, the Platform Monitoring Lead, has asked you to implement comprehensive monitoring for the Course Content Delivery API that serves course videos, quizzes, and study materials to students.

The API handles requests from multiple clients including the student web portal, mobile applications, and third-party learning management systems. To understand API performance and usage patterns, you need to track aggregated telemetry values such as the total number of API calls per endpoint, average response times across different geographic regions, and peak concurrent request counts during high-traffic periods like exam seasons. These aggregated metrics will be used to trigger auto-scaling rules, generate performance dashboards, and alert the operations team when thresholds are exceeded.

Which Application Insights API method should you use to implement aggregate telemetry tracking for the API calls?

Choose the correct answer from the options below.

Explanations for each answer:

TrackEvent is incorrect. TrackEvent is used to log discrete events or occurrences in your application, such as button clicks or feature usage. While useful for analytics, events don't provide numerical aggregation capabilities needed for tracking cumulative metrics like total API call counts or average response times.
TrackTrace is incorrect. TrackTrace is designed for diagnostic logging and captures text-based log messages. It's used for debugging and understanding application flow but doesn't support numerical aggregations or statistical calculations that metrics require.
TrackDependency is incorrect. TrackDependency records calls to external services like databases, REST APIs, or Azure services. While it tracks timing and success information, it's specifically for monitoring external dependencies, not for implementing custom aggregated metrics for your own API calls.
TrackException is incorrect. TrackException is used to log exceptions and errors that occur in your application. It's designed for error tracking and diagnostics, not for aggregating numerical telemetry data or implementing custom performance metrics.
TrackMetric is correct. TrackMetric is specifically designed to send custom numerical measurements to Application Insights, including pre-aggregated values. It allows you to track cumulative statistics like total API calls, average processing times, and custom business metrics. The SDK can pre-aggregate metric values locally before sending them, making it efficient for high-volume telemetry.

Learn more about Custom Events and Metrics:

Application Insights Custom Metrics

Practice Exam

Track Aggregate Telemetry in Application Insights

Discuss this question on social media: