The Syslog connector via Log Analytics agent is the correct choice because it enables Microsoft Sentinel to collect Syslog messages from on-premises Linux servers by having the Log Analytics agent listen on UDP port 514 for messages forwarded by the Linux rsyslog or syslog-ng daemon, then forwarding them directly to the Log Analytics workspace without requiring format transformation. This connector is purpose-built for standard Syslog ingestion, making it the straightforward solution for security teams needing to analyze on-premises Linux logs in Sentinel. On the AZ-500 exam, this question tests your understanding of legacy versus modern connectors—a common trap is confusing the Syslog connector with the newer Azure Monitor Agent (AMA) based connector, but the exam still emphasizes the Log Analytics agent for on-premises Linux Syslog scenarios. Remember the memory tip: “Syslog on 514, Log Analytics is the gate” to recall that the Log Analytics agent listens on the standard Syslog port for this connector.
AZ-500 Manage identity and access Practice Question
This AZ-500 practice question tests your understanding of manage identity and access. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A security operations team uses Microsoft Sentinel. They need to collect Syslog messages from on-premises Linux servers for analysis. Which data connector should they use to ingest these logs into Sentinel?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Syslog connector via Log Analytics agent
The Syslog connector via Log Analytics agent is the correct choice because it allows Microsoft Sentinel to collect Syslog messages from on-premises Linux servers. The Log Analytics agent (formerly OMS agent) listens on UDP port 514 (or a custom port) for Syslog messages forwarded by the Linux rsyslog or syslog-ng daemon, then forwards them to the Log Analytics workspace. This connector is specifically designed for standard Syslog ingestion without requiring format transformation.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Azure Activity Log connector
Why it's wrong here
This connector ingests Azure subscription activity logs, not on-premises Syslog.
✓
Syslog connector via Log Analytics agent
Why this is correct
This connector uses the Log Analytics agent on Linux to collect Syslog events and send them to Sentinel.
Related concept
Read the scenario before looking for a memorised answer.
✗
Common Event Format (CEF) connector
Why it's wrong here
CEF connector is for specific security appliances that output logs in CEF format, not general Syslog.
✗
Windows Security Events connector
Why it's wrong here
This connector collects Windows security events, not Linux Syslog.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the Syslog connector (for standard Syslog) with the CEF connector (for formatted security logs), mistakenly thinking CEF is required for any Linux Syslog ingestion, when in fact CEF is only needed for specific security appliances that output CEF-formatted logs.
Trap categories for this question
Command / output trap
CEF connector is for specific security appliances that output logs in CEF format, not general Syslog.
Detailed technical explanation
How to think about this question
Under the hood, the Log Analytics agent for Syslog uses a built-in rsyslog configuration that forwards messages to the agent's local TCP or UDP port, which then sends them to the Log Analytics workspace via HTTPS. A subtle behavior is that the agent only collects Syslog messages with facility/severity combinations explicitly configured in the workspace's Syslog settings; unmatched messages are dropped. In a real-world scenario, if a Linux server generates high-volume Syslog data (e.g., from auditd), you must carefully tune the facility/severity filters to avoid exceeding the Log Analytics workspace's ingestion limits.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-500 question in full detail.
Manage identity and access — This question tests Manage identity and access — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Syslog connector via Log Analytics agent — The Syslog connector via Log Analytics agent is the correct choice because it allows Microsoft Sentinel to collect Syslog messages from on-premises Linux servers. The Log Analytics agent (formerly OMS agent) listens on UDP port 514 (or a custom port) for Syslog messages forwarded by the Linux rsyslog or syslog-ng daemon, then forwards them to the Log Analytics workspace. This connector is specifically designed for standard Syslog ingestion without requiring format transformation.
What should I do if I get this AZ-500 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-500 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-500 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.