Contoso collects both CEF and Syslog messages through a Linux log forwarder that runs the Azure Monitor Agent (AMA). A firewall sends CEF messages on a facility that the Syslog data collection rule (DCR) also collects, and the same events appear in both the CommonSecurityLog and Syslog tables. The firewall doesn't let you change its target facility, and both CEF and Syslog collection must continue. What should you do?
Show answer and explanation
Answer: A
Explanation
Using the same facility for both Syslog and CEF messages can duplicate ingestion between the CommonSecurityLog and Syslog tables.[1] If changing the facility on the source appliance isn’t applicable, you add an ingestion-time transformation after creating the DCR to filter CEF messages out of the Syslog stream, so A is correct.[1] Starting with AMA version 1.41, the transformation should check both ProcessName and SyslogMessage to filter CEF messages reliably.[1]
B is the method for source devices that allow configuring the target facility, which this firewall doesn’t.[1] C stops Syslog collection, which violates the requirement to keep both collections. D only changes how the Syslog daemon passes logs to the AMA on the forwarder, and doesn’t separate CEF messages from the Syslog stream.[1]