AZ-900 Describe Azure architecture and services Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Azure Log Analytics

  Why it's wrong here

  Azure Log Analytics is a log management and analytics platform within Azure Monitor that ingests, stores, and queries structured and unstructured log data using Kusto Query Language (KQL). While it can consume telemetry from various sources, it is not an application performance monitoring (APM) instrument and does not natively generate or correlate distributed traces across microservice calls. Even if you send trace data to Log Analytics, it lacks built-in end-to-end operation correlation and dependency mapping out of the box, so it cannot directly identify where a specific request slows down or fails across services.

• ✓

  Azure Application Insights

  Why this is correct

  Azure Application Insights is the distributed tracing engine inside Azure Monitor designed for application performance monitoring (APM). It automatically instruments services to emit telemetry with operation IDs and parent-child hierarchy, which allows it to reconstruct a single transaction's path across multiple microservices and external dependencies. This end-to-end correlation enables you to isolate bottlenecks, such as slow database queries or delayed calls to a downstream API, by showing the duration of each component in the trace.

• ✗

  Azure Monitor Metrics

  Why it's wrong here

  Azure Monitor Metrics stores time-series numeric data points, such as CPU percentage, memory usage, request count, and latency percentiles, for cloud resources and applications. It is optimized for alerting and dashboards over aggregated values, but it does not track individual requests or maintain the operation context needed to correlate a call as it jumps from one microservice to another. Without the ability to follow a unique transaction through its service-to-service spans, Metrics alone cannot reveal which specific dependency caused a performance problem.

• ✗

  Azure Sentinel

  Why it's wrong here

  Microsoft Sentinel is a cloud-native security information and event management (SIEM) and security orchestration, automation, and response (SOAR) solution that ingests security logs, alerts, and threat intelligence to detect and respond to security incidents. It is focused on analyzing security signals, not on tracing application requests through business transactions, so it lacks the instrumentation and correlation mechanics for distributed tracing. While it might alert on anomalous application behavior, it cannot pinpoint the exact slow microservice or failing dependency inside a call chain like an APM tool would.

Go deeper

Related to this question