Azure Synapse Diagnostic Settings for Custom Alerts

DP-203 By islever Editorial Last updated

Short answer

A Send to Log Analytics workspace

Question

You have an Azure subscription that contains an Azure Synapse workspace named WS1 and an Azure Monitor action group named Group1. WS1 has a dedicated SQL pool. You plan to archive monitoring data for integration activity runs. You need to ensure that you can configure custom alerts based on the archived data that will execute Group1. The solution must minimize administrative effort. Which diagnostic setting should you select?
  1. Send to Log Analytics workspace Correct Answer
  2. Archive to a storage account
  3. Stream to an event hub
  4. Send to a partner solution

Key Takeaways

Tests the specific destination required for Azure Monitor custom alerts; the trap is choosing storage archiving which lacks native query/alerting capabilities without additional processing.

To configure custom alerts on archived integration activity data in Azure Synapse with minimal effort, send diagnostic logs to a Log Analytics workspace. This is the standard method for enabling Azure Monitor alert rules.

Common mistake: Candidates often select 'Archive to a storage account' because the question mentions 'archive', but this option does not support direct alert configuration via Azure Monitor.

Expert Analysis

Why the Answer Is Correct

Sending diagnostic settings to a Log Analytics workspace allows you to run Kusto Query Language (KQL) queries on the data immediately. Azure Monitor custom alerts are natively built on top of Log Analytics workspaces, enabling you to define alert rules based on specific conditions in the integration activity runs.

Why the Other Options Are Wrong

Archiving to a storage account (Option B) is suitable for long-term retention but requires complex logic (like Azure Functions or Data Factory) to process and alert on data. Streaming to an Event Hub (Option C) is for real-time event ingestion by other services, not for direct alerting. Partner solutions (Option D) vary in capability and do not guarantee native Azure Monitor alert integration.

Community Comment Notes

The community consensus strongly supports Option A, noting that it is the only path to native alerting. Comments confirm that while 'archive' implies storage, the requirement for 'custom alerts' dictates Log Analytics.

Official Reference

Array

This link opens the official vendor documentation in a new tab.

Exam Strategy

When a question asks for 'alerts' or 'monitoring' alongside 'diagnostic settings', prioritize Log Analytics Workspace unless specified otherwise. Do not be misled by keywords like 'archive' if the primary goal is active monitoring or alerting.

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 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 4

  1. Lewiasskick 👍 1
    https://learn.microsoft.com/en-us/azure/sentinel/detect-threats-custom
  2. weyiyaw474 👍 1 Answered A
    Send to Log Analytics workspace
  3. jongert 👍 2
    Correct
  4. evangelist 👍 1 Answered A
    no doubt A

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How to Verify Result Set Cache Usage in Azure Synapse SQL Pools?

S-grade

Which Diagnostic Setting Tracks Query Start and End Times in Synapse SQL Pool?

S-grade

Which Integration Runtime Connects On-Premises Linux Databases to Azure Data Factory?

S-grade

Which Log Analytics table stores ADF pipeline runs in resource-specific mode?

S-grade

← Back to DP-203 Study Guide