nerdexam
Microsoft

AZ-305 · Question #325

Hotspot Question You have an Azure subscription that contains the resources shown in the following table: Log files from App1 are registered to App1Logs. An average of 120 GB of log data is ingested…

To minimize Log Analytics costs while ensuring all logs are ingested and minimizing alert impact, you should modify the App1Logs workspace by configuring a Basic or Auxiliary log tier (or enabling a data collection rule with transformation) to filter out non-error logs before…

Submitted by emma.c· Mar 6, 2026Monitor and maintain Azure resources / Implement monitoring and alerting solutions / Optimize Log Analytics workspace costs using data collection rules and log table tiers

Question

Hotspot Question You have an Azure subscription that contains the resources shown in the following table: Log files from App1 are registered to App1Logs. An average of 120 GB of log data is ingested per day. You configure an Azure Monitor alert that will be triggered if the App1 logs contain error messages. You need to minimize the Log Analytics costs associated with App1. The solution must meet the following requirements: - Ensure that all the log files from App1 are ingested to App1Logs. - Minimize the impact on the Azure Monitor alert. Which resource should you modify, and which modification should you perform? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Exhibits

AZ-305 question #325 exhibit 1
AZ-305 question #325 exhibit 2

Explanation

To minimize Log Analytics costs while ensuring all logs are ingested and minimizing alert impact, you should modify the App1Logs workspace by configuring a Basic or Auxiliary log tier (or enabling a data collection rule with transformation) to filter out non-error logs before ingestion, or implement a table-level data retention and tier strategy. The correct approach is typically to modify the Data Collection Rule (DCR) associated with App1 to add a KQL transformation that filters or reduces the volume of ingested data, sending only relevant log data to the analytics tier while keeping error detection intact. This reduces billable ingestion volume (saving cost on 120GB/day) without dropping error-level logs that trigger the Azure Monitor alert.

Topics

#Azure Monitor#Log Analytics#Data Collection Rules#Cost Optimization

Community Discussion

No community discussion yet for this question.

Full AZ-305 Practice