AZ-305 Practice Question 71: DCR Transformation Filter Drop Fields

Microsoft Azure Solutions Architect Expert (AZ-305) · Test 8 · question 1 of 10

Identity, Governance & Monitoringhard

A company collects Windows event logs from thousands of VMs using Azure Monitor Agent and a data collection rule (DCR) that sends everything to a Log Analytics workspace. Ingestion costs have grown because many records contain a verbose message field that nobody queries, and the security team wants low severity events dropped entirely before they reach the workspace. You must reduce both the volume and the size of ingested data without deploying a different agent or removing any VM from monitoring.

Select one answer
Show answer and explanation

Answer:

  • C. Add a data collection rule transformation that uses a KQL query to drop low severity records and project out the verbose field before the data is ingested.

DCR transformations run a KQL query against each incoming record before it is stored, so a where clause can drop unwanted severities and a project-away (or project) can remove the verbose field, cutting both the row count and the size of each row that is actually billed. This works with Azure Monitor Agent and requires no new agent or architecture change.

A lower workspace pricing tier only changes the price curve for the data you already send; it does not reduce the volume being ingested, so it does not address the stated requirement. Basic Logs table plans reduce storage cost for infrequently queried tables, but the data has already been ingested and billed for ingestion by that point, and Basic Logs has query limitations that do not help filter unwanted content out beforehand. Streaming to an Event Hub instead of Log Analytics solves a different problem (routing to a SIEM or custom consumer), and by itself does not filter or shrink records or reduce Log Analytics ingestion, since it simply changes the destination.

Reference: Transformations in Azure Monitor

Practice Test 8 ›

Study guides for AZ-305