XK0-006 Security Practice Question
To limit the number of processes a user can create, which file should be configured?
⚠ Common exam trap
The trap is confusing PAM configuration files with the actual limits configuration file, or assuming a non-existent /etc/ulimit.conf exists, leading candidates to choose incorrect paths.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
/etc/security/limits.conf
The /etc/security/limits.conf file is used on Linux systems to set resource limits for users and groups, including the maximum number of processes (nproc). This file is read by PAM (Pluggable Authentication Modules) during login to apply ulimit settings. Configuring nproc there limits the number of processes a user can create.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
/etc/pam.d/login
Why it's wrong here
/etc/pam.d/login controls authentication and session modules for local logins, not resource ceilings. Process limits are enforced by the pam_limits module reading /etc/security/limits.conf. It tempts because PAM session hooks can invoke limits, yet editing the login stack itself does not define nproc values, so no per-user cap results.
- ✓
/etc/security/limits.conf
Why this is correct
/etc/security/limits.conf is read by pam_limits and defines per-user or per-group resource limits, including nproc, which caps the number of processes a user may create. This directly satisfies the requirement to limit process creation for a user.
- ✗
/etc/ulimit.conf
Why it's wrong here
No /etc/ulimit.conf file exists on Linux; ulimit is a shell builtin reading kernel limits set elsewhere. Per-user process counts are defined in /etc/security/limits.conf via the nproc item. It tempts because the filename mirrors the ulimit command, but creating it changes nothing, as no daemon parses that path.
- ✗
/etc/systemd/system.conf
Why it's wrong here
systemd/system.conf sets manager-wide defaults such as DefaultTasksMax, applying globally rather than per user. Per-user process caps require pam_limits configured through /etc/security/limits.conf. It tempts because TasksMax genuinely limits processes, but that directive belongs in unit files or the manager configuration, not as a per-user login restriction mechanism.
Go deeper
Related to this question
Learn chapter
File Transfer and Remote Access
Key term
Linux
Linux is an open-source operating system that manages computer hardware and software, widely used in servers, desktops, and embedded systems.
Key term
PAM
Privileged Access Management (PAM) is a security framework that controls, monitors, and audits access to critical systems and accounts with elevated permissions.
About these practice questions
One of 781 original XK0-006 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This XK0-006 practice question is part of Courseiva's free CompTIA 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 XK0-006 exam.