Which Log Analytics table stores ADF pipeline runs in resource-specific mode?
Short answer
A ADFPipelineRun
Question
Key Takeaways
The core trap is confusing the generic 'AzureDiagnostics' table (used in Azure-Diagnostics mode) with service-specific tables created when using Resource-Specific mode, or confusing Pipeline Runs with Trigger Runs.
This question tests the distinction between Azure-Diagnostics and Resource-Specific modes for sending diagnostic logs to Log Analytics. The community consensus confirms that configuring 'pipeline runs' to a resource-specific destination creates the specific ADFPipelineRun table.
Common mistake: Many candidates select D (AzureDiagnostics), assuming all diagnostic logs aggregate there. This is incorrect because the question explicitly specifies 'resource-specific destination,' which bypasses the generic table in favor of dedicated schema tables like ADFPipelineRun.
Expert Analysis
Why the Answer Is Correct
When Diagnostic Settings are configured for Azure Data Factory to send data to a Log Analytics workspace, you must choose between 'Azure-Diagnostics' mode and 'Resource-Specific' mode. In Resource-Specific mode, Azure creates distinct tables for each log category. Since the prompt specifies that 'pipeline runs' are being sent to a resource-specific destination, the data lands in the ADFPipelineRun table. This allows for direct KQL querying without filtering by Category or ResourceProvider.
Why the Other Options Are Wrong
Option D (AzureDiagnostics) is the default consolidated table used only when 'Azure-Diagnostics' mode is selected; it aggregates logs from many services, requiring complex filtering. Option B (ADFTriggerRun) would be correct if the configuration specified sending 'trigger runs' rather than 'pipeline runs.' Option C (ADFActivityRun) is for individual activity executions within a pipeline, not the pipeline run itself.
Community Comment Notes
Comment [1] and [8] correctly identify that the key differentiator is the 'resource-specific' setting, which rules out AzureDiagnostics. Comment [2] reinforces that the logging target ('pipeline runs') directly maps to the ADFPipelineRun table. Comment [9] provides the official Microsoft documentation link confirming the behavior of resource-specific logs.
Official Reference
https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs#resource-specific
This link opens the official vendor documentation in a new tab.
Exam Strategy
Always look for the phrase 'resource-specific' in diagnostic settings questions. If present, ignore the generic AzureDiagnostics table and map the specific log type (e.g., pipeline, trigger, activity) to its corresponding dedicated table (e.g., ADFPipelineRun).
Community Votes
61% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 14 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 14
-
Bill_Walker 👍 7 Answered BThe answer is not D because the workspace was set to Resource-specific. See doc below. I'm torn between A (PipelineRun) vs B (TriggerRun) because the wording is so generic. However, since they mentioned the scheduling of the pipeline, I would lean on B. https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs#send-to-log-analytics-workspace
-
Mausar 👍 6 Answered ARemember that you are setting "pipeline runs" logs from diagnostics settings to be sent to a Log Analytics workspace, not the "trigger runs" or "activity runs" logs. Azure Diagnostics stores resource logs for Azure services that use Azure Diagnostics mode. Resource logs describe the internal operation of Azure resources. Azure services that use resource-specific mode store data in a table specific to that service and do not use the AzureDiagnostics table https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/azurediagnostics
-
Azure_2023 👍 4 Answered BADFTriggerRun The ADFTriggerRun table stores logs related to trigger runs, which are the events that initiate pipeline executions. This table includes the trigger name, pipeline name, run ID, start time, end time, status, and a message about the trigger run. This table is useful for understanding how triggers are firing and how pipelines are being executed.
-
mghf61 👍 3Chat GPT answer: To run KQL queries against the pipeline runs sent to a Log Analytics workspace, you should query the table that corresponds to the pipeline runs. Since you configured pipeline runs to be sent to a resource-specific destination table in the Log Analytics workspace, you should query the table corresponding to pipeline runs. Therefore, the correct table to query is: A. ADFPipelineRun
-
f2a9aa5 👍 3 Answered AA. ADFPipelineRun Here’s why: ADFPipelineRun: This table contains detailed information about the execution of your ADF pipelines, including start and end times, status, and other relevant metrics. It’s the go-to table for querying pipeline run details1.
Show 9 more comments
-
e56bb91 👍 3 Answered Ahttps://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/adfpipelinerun
-
Happynewyear1001 👍 2When you configure pipeline runs to be sent to a Log Analytics workspace in Azure Data Factory, the data is typically stored in the "AzureDiagnostics" table. Therefore, you should query the "AzureDiagnostics" table to retrieve information about pipeline runs. So, the correct answer is: D. AzureDiagnostics
-
KauK 👍 1 Answered ADiagnostic Settings and Log Routing: When configuring diagnostic settings for ADF to send logs to a Log Analytics workspace, you have two modes: Azure-Diagnostics Mode: In this mode, all diagnostic logs are sent to a consolidated table named AzureDiagnostics. This table aggregates various logs, and you can filter the data based on specific services or log types. Resource-Specific Mode: This mode routes logs into distinct tables specific to ADF activities. The relevant tables include: ADFPipelineRun: Contains records of pipeline executions. ADFActivityRun: Details individual activities within pipelines. ADFTriggerRun: Logs trigger executions. https://learn.microsoft.com/en-us/azure/data-factory/monitor-configure-diagnostics
-
Tapaskaro 👍 1Answer is D https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs all data from any diagnostic setting is collected in the AzureDiagnostics table
-
Filda123 👍 1 Answered DPer the other two comments, answer should be D. Adding a voting comment so it can show on "show answer"
-
raymoral 👍 1 Answered Ahttps://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs#resource-specific
-
Oleh777 👍 1IMHO activity run should show all the details
-
evangelist 👍 3 Answered AA is correct
-
vernillen 👍 1 Answered DShould be D.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.