Q: A junior admin needs root access for specific commands only (restarting services, reading logs), not full unrestricted root access. How do you configure granular sudo access?
The /etc/sudoers file (edited exclusively via visudo to prevent syntax errors) controls which users can run which commands as root.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In an interview, I explain my systematic Linux troubleshooting methodology using Brendan Gregg's USE method. The interviewer is testing: Sudoers configuration, principle of least privilege.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
The /etc/sudoers file (edited exclusively via visudo to prevent syntax errors) controls which users can run which commands as root.
ALL=(root): Can execute on any host as the root user.NOPASSWD:: Don't prompt for password (useful for automation).- Specific commands: Only the exact commands listed are allowed. Running
sudo bashorsudo suwould be denied. - Use command aliases for grouping:
Remediation & Permanent Safeguards
To grant granular access: Key directives: Best practices:
# Allow user 'deploy' to restart nginx and read syslog only
deploy ALL=(root) NOPASSWD: /bin/systemctl restart nginx, /bin/systemctl status nginx, /usr/bin/journalctl -u nginx
- Use group-based rules:
%devops ALL=(root) NOPASSWD: WEB_MGMTapplies to all users in thedevopsgroup. - Never use
ALL=(ALL) ALLfor non-admin users—it grants full unrestricted root access.
- ALL=(root): Can execute on any host as the root user.
- NOPASSWD:: Don't prompt for password (useful for automation).
- Specific commands: Only the exact commands listed are allowed. Running sudo bash or sudo su would...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring junior admin needs SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring junior admin needs
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring junior admin needs Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring junior admin needs
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).