⚡ ~/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 88 of 135 in Linux & SRE
Senior DevOps / SRE [L2] Linux Linux / SRE — Scenario-Based Interview Questions Production Scenario [L2]
🎯 Target Role / Context: Linux Scenario #47 (L2) · Linux / SRE — Scenario-Based Interview Questions

Q: SSH currently uses password authentication for access to production servers. Describe a certificate-based SSH authentication system for managing access to 1000+ servers without relying on password distribution or key rotation complexity.

Certificate-based SSH (using OpenSSH certificates) eliminates password management and simplifies key rotation across large deployments.

#Linux #L2 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: SSH security architecture, certificate-based auth, key management at scale.. 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: "We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: SSH security architecture, certificate-based auth, key management at scale.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

Certificate-based SSH (using OpenSSH certificates) eliminates password management and simplifies key rotation across large deployments.

🔑 Cryptographic Deep Dive: Understand the Diffie-Hellman and public/private keypair exchange behind SSH: Security Q13: Public Key Cryptography & Asymmetric Encryption in SSH.

  • CA Setup: Designate a secure certificate authority machine that signs user and host SSH keys. Generate a CA key pair:
  • User Authentication: Instead of distributing individual keys, users request a signed certificate:
  • User generates their personal key: ssh-keygen -t rsa -f ~/.ssh/id_rsa
  • User submits their public key to the CA (via secure API or admin approval workflow)
  • CA signs it with a time-limited validity: ssh-keygen -s /path/to/ca/ssh_ca -I user@example.com -n username -V +52w ~/.ssh/id_rsa.pub
  • User receives a ~/.ssh/id_rsa-cert.pub valid for 52 weeks
  • User connects: ssh -i ~/.ssh/id_rsa user@production-server
  • Server Configuration: Add to /etc/ssh/sshd_config on all 1000 servers:
2️⃣

Remediation & Permanent Safeguards

Architecture: Operational Scale: With 1000 servers, update /etc/ssh/user_ca.pub once on all servers (via configuration management like Ansible), and cert-based auth works network-wide without touching private keys.

ssh-keygen -t rsa -f /path/to/ca/ssh_ca
  • Benefits:
  • No password distribution or memorization
  • Automatic expiration (no need to revoke individual keys; certificates naturally expire)
  • Centralized revocation list (CRL) if needed
  • Audit trail: Each certificate embeds username, timestamp, and approval details
  • Zero-trust: Revoke CA instantly, all certificates become invalid without manual key cleanup
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: CA Setup: Designate a secure certificate authority machine that signs user and host SSH keys. Generate a CA key pair:."
⚡ 60-Second Elevator Pitch Talking Points
  • CA Setup: Designate a secure certificate authority machine that signs user and host SSH keys. Gen...
  • User Authentication: Instead of distributing individual keys, users request a signed certificate:
  • User generates their personal key: ssh-keygen -t rsa -f ~/.ssh/id_rsa
⛔ 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 currently uses password 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 currently uses password 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 currently uses password 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 currently uses password 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 →