Explanation

When configuring diagnostic settings for Azure Data Factory to send logs to a Log Analytics workspace in resource-specific mode, the logs are routed to dedicated tables specific to each type of ADF operation.

Resource-Specific Tables in Azure Data Factory:

• ADFPipelineRun: Contains detailed information about pipeline executions, including start/end times, status, duration, and execution metrics
• ADFActivityRun: Contains information about individual activities within pipeline runs
• ADFTriggerRun: Contains information about trigger executions that initiate pipeline runs

Analysis of Options:

A. ADFPipelineRun (CORRECT) - This is the optimal choice because:

• The question specifically mentions configuring "pipeline runs" to be sent to Log Analytics
• ADFPipelineRun table contains comprehensive data about pipeline executions including status, duration, and execution details
• This table directly corresponds to the configured diagnostic setting for pipeline runs

B. ADFTriggerRun - Less suitable because:

• This table contains information about trigger executions, not pipeline runs
• While triggers initiate pipeline runs, the actual execution details are stored in ADFPipelineRun
• The question focuses on analyzing "pipeline runs," not trigger events

C. ADFActivityRun - Less suitable because:

• This table contains granular details about individual activities within pipelines
• While related to pipeline execution, it doesn't provide the holistic view of pipeline runs
• The diagnostic setting was specifically configured for pipeline runs, not activity runs

D. AzureDiagnostics - Incorrect because:

• This table is used when diagnostic settings are configured in Azure-Diagnostics mode, not resource-specific mode
• The question explicitly states "resource-specific destination table" configuration
• In resource-specific mode, data goes to dedicated ADF tables, not the consolidated AzureDiagnostics table

Best Practice Consideration:

When working with Azure Data Factory monitoring in Log Analytics, using resource-specific tables provides better query performance, clearer schema, and more intuitive data organization compared to the consolidated AzureDiagnostics table approach.