Intermediate everything in DevOps & Cloud, page 2
Automating chaos in CI/CD for continuous verification?
Run codified experiments against staging or canary with pass/fail on steady-state SLIs; prerequisites are observability, automated abort, and isolation.
Resource faults versus network faults: when each matters?
Resource faults probe local saturation and autoscaling; network faults probe distributed-call resilience like timeouts and retries.
Why does 200ms latency drop requests? Diagnose it.
Little's Law shows added latency raises in-flight requests, exhausting the thread or connection pool; check pool saturation, timeouts, and retries.
How do you run your first production chaos experiment?
Pick a low-risk known weakness, define a measurable hypothesis, brief stakeholders and on-call, run small with an abort, then analyze and fix.
Zero-downtime index migration on a hot table?
Build the index concurrently to avoid table locks, run off-peak with monitoring, and keep it reversible since dropping an index is cheap.
Mitigating risk from an unproven external dependency?
Timeouts and circuit breakers to fail fast, bulkheads to isolate resources, fallbacks or cached/degraded responses.
Reliability patterns for queue-based job processing?
Retries with backoff and jitter for transient faults, dead-letter queues plus a poison-message limit, idempotent handlers and visibility timeouts.
Front-end performance budgets
A performance budget is an enforced limit on metrics like Core Web Vitals and bundle size, checked in CI to fail builds that regress.
Little's Law for capacity planning
L equals lambda times W, concurrency equals arrival rate times time in system; rearrange to size threads or concurrency for a target throughput and latency.
Capacity planning for annual traffic spikes
Forecast peak from history, load-test to find per-unit capacity, use autoscaling with pre-warming and headroom, and protect with caching and graceful degradation.
Diagnose database CPU saturation under load
Find the expensive queries via the database's stats, check for missing indexes and full scans, then fix with indexing, query rewrites, caching, or read replicas.
Client-side vs server-side feature flags
Client-side is fast and offline-capable but exposes flag logic and risks stale or leaked values; server-side keeps logic secret and consistent but adds latency.
Design automated canary analysis scoring
Track the golden-signal SLIs, compare canary to baseline statistically, weight and combine into a score with promote/rollback thresholds.
Diagnose a degraded canary release
Check statistical significance versus baseline, confirm apples-to-apples comparison, isolate the cause via traces and logs, then weigh the regression against SLO budget.
Blue-green deploys with schema migrations
The shared database means both versions hit one schema, so breaking changes must be split into backward-compatible steps via expand-and-contract.
Design automated microservice provisioning workflow
Template scaffolding plus a pipeline that creates repo, CI/CD, and infra as code, with idempotent steps and rollback.
Systematically reduce noisy alert toil
Inventory alerts, measure frequency, actionability, and time cost, then prioritize by volume times effort.
Idempotency in infrastructure provisioning scripts
Idempotency means repeated runs converge to one end state; achieve it via desired-state reconciliation or idempotency keys with read-before-write.
Proximate cause versus root cause
Proximate cause is the immediate trigger, root cause is the systemic condition that allowed it; fix the root to prevent recurrence.
Resolving post-mortem disagreement with data
Anchor the debate in the timeline, deploy events, traces, and metrics; correlate cause and onset; allow multiple contributing factors.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles