DevOpsInterviewPrep logo
← Containers & Kubernetes / 34
mediumNewNetflixFlipkartSwiggy

A nightly batch job starves the payment service at peak. Design priority and preemption so it cannot recur.

Priority is one number with three separate effects: scheduling order, preemption victim selection, and eviction order under node pressure. Conflating those is the trap; designing tiers that survive both a full cluster and a hot node is the pass.

Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

Priority is one number with three separate effects: scheduling order, preemption victim selection, and eviction order under node pressure. Conflating those is the trap; designing tiers that survive both a full cluster and a hot node is the pass.

20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25
UP NEXT ON YOUR JOURNEY
Next in this trackWe run three zones and after every incident the recovered zone sits half empty. How do you spread workloads deliberately?Next in this trackProduction runs distroless images with no shell. How do you debug a misbehaving container in place?Next in this trackCPU metrics lag demand by minutes because traffic arrives as queue depth. How should autoscaling react to events?
DISCUSSION · 0

Nothing here yet. Say how you would answer it.