priyankagupta7679 / devops-interview-question-bank

# DevOps Interview Question Bank
**529 real DevOps / SRE / Cloud interview questions** gathered from interview experiences people shared publicly
(TCS, Accenture, PwC, product companies, Google SRE loops and more). They are de-duplicated,
grouped by topic and level, and answered in **plain language first**, then with real depth.
Every answer follows the same four steps:
| | |
| --- | --- |
| **In simple words** | An everyday analogy, so the idea makes sense even if you are new to it |
| **Detailed answer** | The real technical explanation, with a step-by-step triage order for scenario questions |
| **Example** | Working commands, YAML, HCL, Jenkinsfiles or scripts you can run or show |
| **What to say to the interviewer** | A crisp 2-3 line answer to practise out loud |
> Where the "model answers" circulating online were wrong, the corrected version is given
> (for example: removing a resource block in Terraform *destroys* it, KMS stores *keys* not secrets,
> Prometheus collects *metrics* not logs, and VPC endpoints reach AWS services, *not* the internet).
---
## Download
- **Full PDF (all 10 topics):** `pdf/DevOps_Interview_Question_Bank.pdf` - 500+ pages with clickable contents and bookmarks
- **One PDF per topic:** `pdf/by-topic/` - handy for revising on your phone
## Topics
| # | Topic | Basic | Advanced | Scenario | Total | Read online | PDF |
| --- | --- | :-: | :-: | :-: | :-: | --- | --- |
| 01 | Linux, Shell Scripting & Networking | 22 | 21 | 43 | **86** | Read | PDF |
| 02 | Docker & Containers | 17 | 13 | 9 | **39** | Read | PDF |
| 03 | Kubernetes (incl. EKS / AKS / GKE, Helm, KEDA) | 31 | 30 | 28 | **89** | Read | PDF |
| 04 | CI/CD, Jenkins, Git, GitOps & Ansible | 38 | 23 | 18 | **79** | Read | PDF |
| 05 | Terraform & Infrastructure as Code | 15 | 20 | 13 | **48** | Read | PDF |
| 06 | AWS | 18 | 36 | 27 | **81** | Read | PDF |
| 07 | GCP, Azure & DevSecOps | 12 | 12 | 8 | **32** | Read | PDF |
| 08 | Monitoring, Observability, SRE & Scale Design | 9 | 15 | 8 | **32** | Read | PDF |
| 09 | Behavioral & Project Experience (STAR samples) | 9 | - | 10 | **19** | Read | PDF |
| 10 | Shell Scripting: 24 real interview scripts | 7 | 8 | 9 | **24** | Read | PDF |
| | **Total** | **178** | **178** | **173** | **529** | | |
## What a question looks like
> **Q. Pods are Running, but users are getting 503 errors. Where do you debug?**
>
> **In simple words:** The shop is open and the staff are at their desks, but the front door
> sign says "closed". Check every step between the customer and the counter.
>
> **Detailed answer:** Follow the request path: DNS -> load balancer -> Ingress controller -> Service ->
> endpoints -> Pod. Empty endpoints (readiness failing or a selector mismatch), unhealthy LB targets,
> Ingress upstream errors, timeouts and HPA at max replicas are the usual culprits...
>
> **What to say to the interviewer:** "I walk the request path hop by hop and check `kubectl get endpoints`
> first. 503 with healthy pods usually me