Skip to main content

DevOps Engineer Interview Questions

 DevOps Engineer Interview Questions You Must Crack to Land That 20+ LPA Package


𝐋𝐢𝐧𝐮𝐱 & 𝐒𝐜𝐫𝐢𝐩𝐭𝐢𝐧𝐠

1. What are some common Linux commands you use daily as a DevOps engineer, and in what scenarios?

2. How would you troubleshoot a Linux server with high CPU or memory usage?


𝐕𝐞𝐫𝐬𝐢𝐨𝐧 𝐂𝐨𝐧𝐭𝐫𝐨𝐥 (𝐆𝐢𝐭 & 𝐆𝐢𝐭𝐇𝐮𝐛/𝐆𝐢𝐭𝐋𝐚𝐛)

3. Explain Git branching strategies (Git Flow, Trunk Based). Which one do you prefer and why?

4. How do you resolve a Git merge conflict in a CI/CD pipeline?


𝐂𝐈/𝐂𝐃 (𝐉𝐞𝐧𝐤𝐢𝐧𝐬 / 𝐆𝐢𝐭𝐋𝐚𝐛 𝐂𝐈 / 𝐆𝐢𝐭𝐇𝐮𝐛 𝐀𝐜𝐭𝐢𝐨𝐧𝐬)

5. Walk me through how you would design a CI/CD pipeline for a microservices-based application.

6. How do you secure credentials and secrets in a Jenkins or GitLab pipeline?


𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 (𝐃𝐨𝐜𝐤𝐞𝐫)

7. What is the difference between Docker image and container?

8. How do you reduce the size of a Docker image in production?


𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬

9. What are the different types of Kubernetes services (ClusterIP, NodePort, LoadBalancer)?

10. How do you handle pod failures and application auto-scaling in Kubernetes?


𝐈𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐚𝐬 𝐂𝐨𝐝𝐞 (𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦)

11. What is the difference between terraform import and terraform taint?

12. How do you manage Terraform state in a team environment?


𝐂𝐥𝐨𝐮𝐝 (𝐀𝐖𝐒)

13. What are the differences between Auto Scaling Groups and Kubernetes HPA in AWS?

14. How would you design a highly available system on AWS using Load Balancer + ASG?


𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 & 𝐋𝐨𝐠𝐠𝐢𝐧𝐠

15. What is the difference between monitoring and observability?

16. How do you set up centralized logging for a microservices application?


𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 & 𝐃𝐞𝐯𝐒𝐞𝐜𝐎𝐩𝐬

17. How do you scan Docker images for vulnerabilities?

18. What are some best practices for securing a CI/CD pipeline?


𝐆𝐞𝐧𝐞𝐫𝐚𝐥 𝐃𝐞𝐯𝐎𝐩𝐬 𝐂𝐮𝐥𝐭𝐮𝐫𝐞 & 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬

19. What does “Shift-Left” mean in DevOps?

20. Can you explain a real incident you resolved in production and what you learned from it?

Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...