Querying Azure Monitor Managed Prometheus Metrics for AKS1 with PromQL
You have an Azure subscription that contains an Azure Kubernetes Service (AKS) instance named AKS1. You collect and analyze metrics for AKS1 by using the Azure Monitor managed service for Prometheus. You need to analyze the performance of AKS1. Which query language should you use?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The Azure Monitor managed service for Prometheus is a PromQL-compatible endpoint, so analyzing metrics from it requires PromQL. KQL addresses Azure Monitor's own logs and metrics tables, not the Prometheus time series written by this managed service.
An AKS instance named AKS1 has its metrics collected and analyzed through the Azure Monitor managed service for Prometheus, and the performance of AKS1 needs to be analyzed. The query language has to match the telemetry store the metrics were written to, otherwise the analysis cannot run.
Reaching for KQL because Azure Monitor is involved. Despite Azure being the host, metrics ingested through the managed Prometheus service are PromQL time series, and Kusto queries do not read that store.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The metrics for AKS1 are collected and analyzed through the Azure Monitor managed service for Prometheus, so the query language must be the one that store exposes. That service provides a Prometheus-compatible metrics endpoint queried with PromQL, which is the language designed for querying time series metrics with selectors, functions, and aggregation. Because the question is about analyzing collected metrics rather than log records, PromQL is the correct choice. The vote was unanimous at 100 for B. uncledana cited the Azure Monitor documentation page for the Prometheus API and PromQL, and nikolayivanov made the identification in one line, pointing out that the phrase using the Azure Monitor managed service for Prometheus is what makes PromQL the answer.Why the Other Options Are Wrong
KQL (D) is the query language for Azure Monitor Logs, meaning Application Insights tables, Log Analytics workspaces, and the general-purpose metrics tables that Azure Monitor collects natively, so it is the natural choice for a typical Azure monitoring scenario. Here, however, the metrics explicitly come from the managed Prometheus service, which is a separate PromQL endpoint, and a Kusto query does not read that store. PL/SQL (A) is Oracle's procedural SQL dialect and has no relationship to any Azure monitoring service. SparkQL is the query language used with Spark SQL against distributed data, and Azure Monitor metrics are not queried that way, so it is not applicable here.Community Comment Notes
The community was unanimous at 100 for B, and the comments are brief because the mapping is direct. uncledana gave the evidentiary link to the Prometheus API and PromQL documentation, which is what makes the answer verifiable rather than merely asserted. nikolayivanov's one-line comment identifies the decisive phrase in the question, noting that the use of the Azure Monitor managed service for Prometheus is what determines the language. No commenter argued for KQL, which is notable given how often KQL is the default answer for Azure Monitor questions in general.Official Reference
Related Analysis
Practice All AZ-400 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-400 Practice Test →