⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 102 of 135 in Linux & SRE
Senior DevOps / SRE [L2] Linux Linux / SRE — Scenario-Based Interview Questions Production Scenario [L2]
🎯 Target Role / Context: Linux Scenario #62 (L2) · Linux / SRE — Scenario-Based Interview Questions

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.

#Linux #L2 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
⚡ Recommended Practice Lab

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."

1️⃣

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 bash or sudo su would be denied.
  • Use command aliases for grouping:
2️⃣

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_MGMT applies to all users in the devops group.
  • Never use ALL=(ALL) ALL for non-admin users—it grants full unrestricted root access.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: ALL=(root): Can execute on any host as the root user.."
⚡ 60-Second Elevator Pitch Talking Points
  • 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...
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. 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.
  2. 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.
  3. 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.
  4. 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).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →