Quick Answer
The answer is `authpriv.* @192.168.1.100`. This directive is correct because the `authpriv` facility in rsyslog is specifically designated for security and authorization messages, which on Linux systems includes all commands executed by root via `sudo` or direct login. By using `authpriv.*` followed by the remote server address with the `@` symbol (which denotes UDP transport), rsyslog captures every root command and forwards it to the remote syslog server at UDP port 514. On the LPIC-2 exam, this question tests your understanding of rsyslog facility names and remote logging syntax, often appearing in scenario-based items where you must distinguish `authpriv` from `auth` or `user` facilities. A common trap is confusing `auth` (for generic authentication) with `authpriv` (for sensitive security events like root commands). Remember the mnemonic: “**Auth**ority is **priv**ate for root’s activity” — `authpriv` is the only facility that reliably captures sudo and root shell commands for remote logging.
This LPIC-2 practice question tests your understanding of system security. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 system administrator wants to ensure that all commands executed by root are logged to a remote syslog server. Which rsyslog configuration directive should be used?
auth.* @192.168.1.100
Why wrong: auth is for general authentication, but authpriv is more specific.
authpriv.* @192.168.1.100
authpriv facility logs security/authorization messages including sudo commands.
user.* @192.168.1.100
Why wrong: user facility is for user-level messages.
kern.* @192.168.1.100
Why wrong: kern is kernel facility, not for root commands.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
authpriv.* @192.168.1.100
Option B is correct because the `authpriv` facility in rsyslog is specifically designated for security and authorization messages, including all commands executed by root via `sudo` or direct login. The directive `authpriv.* @192.168.1.100` sends all messages from this facility to the remote syslog server at UDP port 514. This matches the requirement to log root's commands, as Linux systems typically log such events under the `authpriv` facility.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
auth.* @192.168.1.100
Why it's wrong here
auth is for general authentication, but authpriv is more specific.
authpriv.* @192.168.1.100
Why this is correct
authpriv facility logs security/authorization messages including sudo commands.
Related concept
Read the scenario before looking for a memorised answer.
user.* @192.168.1.100
Why it's wrong here
user facility is for user-level messages.
kern.* @192.168.1.100
Why it's wrong here
kern is kernel facility, not for root commands.
Common exam traps
The trap here is confusing `auth` with `authpriv` — candidates often pick `auth.*` thinking it covers all authentication, but `authpriv` is the correct facility for privileged command logging and is a key distinction tested in LPIC-2.
Trap categories for this question
Command / output trap
kern is kernel facility, not for root commands.
Detailed technical explanation
The `authpriv` facility is defined in RFC 5424 and is used by `sudo` and `login` to log commands and authentication events. By default, `rsyslog` uses UDP port 514 for remote logging, but TCP can be specified with `@@` for reliable delivery. In real-world scenarios, administrators often combine this with `local*` facilities for custom application logs, but `authpriv` is the standard for root command auditing.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
System Security — study guide chapter
Learn the concepts, then practise the questions
System Security practice questions
Targeted practice on this topic area only
All LPIC-2 questions
511 questions across all exam domains
Linux Professional Institute Certification Level 2 LPIC-2 study guide
Full concept coverage aligned to exam objectives
LPIC-2 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise LPIC-2 questions linked to Linux Kernel and System Startup.
Practise LPIC-2 questions linked to Block Devices, Filesystems and Advanced Storage.
Practise LPIC-2 questions linked to Advanced Networking Configuration.
Practise LPIC-2 questions linked to DNS, Web and Mail Services.
Practise LPIC-2 questions linked to File Sharing and Samba.
Practise LPIC-2 questions linked to System Security.
Practise LPIC-2 questions linked to Network Client Management.
Practise LPIC-2 questions linked to LPIC-2 fundamentals.
Practise LPIC-2 questions linked to LPIC-2 scenario.
Practise LPIC-2 questions linked to LPIC-2 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
System Security — This question tests System Security — Read the scenario before looking for a memorised answer..
The correct answer is: authpriv.* @192.168.1.100 — Option B is correct because the `authpriv` facility in rsyslog is specifically designated for security and authorization messages, including all commands executed by root via `sudo` or direct login. The directive `authpriv.* @192.168.1.100` sends all messages from this facility to the remote syslog server at UDP port 514. This matches the requirement to log root's commands, as Linux systems typically log such events under the `authpriv` facility.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 11, 2026
This LPIC-2 practice question is part of Courseiva's free LPI 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 LPIC-2 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.