Kubernetes scenario interview questions

Kubernetes rounds rarely ask what a pod is. They hand you a cluster that is misbehaving and a teammate with a quick fix, then watch whether you read the evidence first: events, exit codes, probe config, resource requests.

Each question below is the exact prompt from a DevOps Ledger challenge. Read it, decide what you would do, then open the challenge to defend that call against pushback.

11 scenarios: 1 beginner, 5 intermediate, 5 advanced. Answer keys reviewed by Branko Petric.

What interviewers probe

  • Reading kubectl describe and logs --previous before changing anything
  • Telling a crashing app apart from a probe or the OOM killer restarting it
  • Requests, limits and what they really do to scheduling and throttling
  • Rolling out and rolling back without dropping traffic

The questions

  1. 01intermediate12 min

    Pods Keep OOMKilling: Scale Up or Fix the Leak?

    A payments worker pod gets OOMKilled every 3 to 4 hours under normal load. You can raise the memory limit and add replicas in minutes, or dig into a suspected memory leak with unknown effort. Production is currently degraded but not down. What do you do, and why?

    Practice this scenario
  2. 02intermediate12 min

    Pod Stuck in CrashLoopBackOff After a Deploy

    After a deploy, a pod is stuck in CrashLoopBackOff. A teammate says just give it more CPU and memory and it will settle. How do you actually diagnose and fix this?

    Practice this scenario
  3. 03intermediate13 min

    A Traffic Spike Caused an Outage. Autoscaling Did Not Save You.

    A traffic spike took your service down even though horizontal autoscaling was enabled - it scaled too slowly to keep up. A teammate says just raise the max replicas way up. What is the real fix?

    Practice this scenario
  4. 04advanced15 min

    Service A Intermittently Cannot Reach Service B

    Service A intermittently fails to reach Service B inside the cluster - roughly one call in twenty times out, the rest are fine. A teammate says just add retries and move on. How do you actually diagnose this?

    Practice this scenario
  5. 05advanced15 min

    A Container in Prod Is Mining Crypto

    You discover a pod in your production cluster is running a crypto miner and making outbound connections to an unknown host. A teammate says just kubectl delete the pod and we are done. How do you actually respond?

    Practice this scenario
  6. 06advanced15 min

    An EKS Pod Needs AWS Access. Attach It to the Node Role?

    A pod in your EKS cluster needs to read from S3. A teammate says just add the S3 permission to the node instance role so the pod can use it immediately. Do you agree, and what should you do instead?

    Practice this scenario
  7. 07advanced14 min

    Under Load, Healthy Pods Keep Restarting. Add Replicas?

    During peak traffic your pods enter a restart loop and latency gets worse, even though the app is not crashing. kubectl shows liveness probe failures and restarts. A teammate says just increase the replica count to spread the load. Do you agree, and what do you do instead?

    Practice this scenario
  8. 08intermediate12 min

    ArgoCD Says OutOfSync Forever. Ignore the Secret Diff and Move On?

    After moving a third-party Helm chart from helm install to ArgoCD, the app is permanently OutOfSync, the admin password keeps resetting, one sync left a component crash-looping on database auth and agents in another cluster failing TLS. The team proposes ignoreDifferences on all the Secrets, turning on auto-sync with selfHeal, or going back to running helm upgrade by hand. Which do you pick, or what do you do instead, and why?

    Practice this scenario
  9. 09beginner8 min

    Pods Stuck Pending on Insufficient CPU. Delete the Requests?

    You scaled a Deployment up and the new pods are stuck Pending with "0/3 nodes are available: 3 Insufficient cpu". A teammate opens a PR that deletes the resources block so the scheduler stops complaining. Do you approve it, and what do you do instead?

    Practice this scenario
  10. 10intermediate12 min

    Every Rolling Deploy Causes 502s. Add Ingress Retries?

    Every rolling deploy of your API causes a short burst of 502s at the load balancer, then it settles. A teammate wants to turn on retries at the ingress and move deploys to the night window. Do you agree, and what do you do instead?

    Practice this scenario
  11. 11advanced14 min

    p99 Spikes With CPU at 40 Percent of Limit. Add Replicas?

    Your pricing API shows p99 latency spikes during bursts, but its average CPU usage is only about 40 percent of the container's CPU limit. A teammate says CPU is clearly fine, so it must be the database, and wants to add replicas while they look. Do you agree, and how do you find and fix the cause?

    Practice this scenario

Worked answers

Free Kubernetes guides

Practice defending your decisions

DevOps Ledger is a scenario-based DevOps and SRE interview practice platform: you pick a real production incident, defend your decision in a chat against a senior-engineer AI that pushes back, and get scored against an answer key written before you started.

A general chatbot makes up an answer on the spot. DevOps Ledger grades you against an answer key written before you started.

One payment. 12 months of access. No subscription, nothing renews.

Get full access - $19

Other topics