Skip to content
tezvyn:

☁️DevOps & Cloud

Infrastructure, containers, CI/CD, and cloud

538 bites

Test yourself: Top 30 DevOps & Cloud interview questionsMultiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.

Interview questions in DevOps & Cloud, page 6

advanced2 min read

Setting SLOs across a dependency chain

Serial dependencies multiply, so each backend needs a tighter SLO than the target; mitigate with redundancy, caching, and graceful degradation.

easy2 min read

Public and private subnet VPC design

Web server in a public subnet routed to an internet gateway, database in a private subnet with no inbound from the internet, NAT for outbound.

advanced1 min read

Structuring Compose files across environments

A base compose.yaml plus override files, the default override auto-merge, and explicit -f flags or extends per environment.

intermediate2 min read

How would you integrate SAST into CI without alert fatigue?

This tests embedding security into workflow without killing velocity. Run SAST per commit, suppress false positives via rulesets, gate on high-severity findings first and block merges only after calibration. A red flag is zero-tolerance blocking on day one.

advanced2 min read

Launching a risky feature with no error budget left

Bring burn history, what consumed the budget, blast radius, and rollback safety; offer mitigations like flags and canaries.

easy1 min read

Layer 4 vs Layer 7 load balancers

L4 routes on IP and TCP/UDP ports fast and protocol-blind; L7 inspects HTTP for host, path, and headers.

advanced1 min read

Optimizing Dockerfile layer caching

Order instructions least-to-most volatile, copy dependency manifests and install before copying source, and understand any changed layer busts all later layers.

Smoke test fails after canary deployment. Design the automated rollback.
advanced2 min read

Smoke test fails after canary deployment. Design the automated rollback.

Tests self-healing pipeline design: freeze canary traffic, auto-redeploy the last good release, verify rollback health, and keep failed pods for forensics. Red flag: requiring manual approval or in-place fixes instead of an atomic rollout swap.

advanced2 min read

Fixing watermelon SLOs that hide unhappy users

Green-outside, red-inside SLOs come from server-side measurement, coarse aggregation, wrong events, and lax thresholds; fix by measuring at the client and using meaningful SLIs.

easy1 min read

How cloud DNS resolves a URL to an IP

Recursive resolver queries root, then TLD, then your authoritative cloud DNS zone; the matching record returns an IP, cached per TTL.

advanced1 min read

Docker Compose profiles for optional services

Profiles tag services so they stay off by default, activate via --profile or COMPOSE_PROFILES, and unprofiled services always run.

advanced2 min read

How would you diagnose, report, and mitigate E2E flakiness at scale?

Tests metric-driven pipeline hygiene versus retry band-aids. Strong answers baseline flakiness rates, identify offenders via CI history, quarantine chronic flakes from presubmit, and fix root causes like concurrency.

easy2 min read

The three pillars of observability

Metrics show what and when via cheap aggregates, logs give detailed per-event context, traces show where across services.

intermediate1 min read

Connecting two VPCs privately

VPC peering is simple but non-transitive and full-mesh; a Transit Gateway scales hub-and-spoke; PrivateLink exposes one service narrowly.

easy1 min read

Tag and push an image to a private registry

Authenticate with docker login, retag the image to include the registry host and repo path, then docker push that full reference.

easy2 min read

SNAPSHOT and RELEASE versions: differences and appropriate use

SNAPSHOTs are mutable; RELEASEs are immutable and tagged. Use SNAPSHOTs on feature branches and RELEASEs for main.

easy1 min read

Structured vs unstructured logging

Unstructured logs are free-text lines; structured logs are machine-readable key-value or JSON, enabling reliable parsing, filtering, and aggregation.

intermediate1 min read

Process running but load balancer says unhealthy

The probe path, port, protocol, or expected status may mismatch; a security group may block the probe; the app may be up but not ready.

easy1 min read

Why :latest is a production anti-pattern

Latest is mutable so pods run different code, rollbacks and pull policy break, and you should use immutable version tags or digests.

How do you version Docker images: Git SHA or SemVer?
intermediate2 min read

How do you version Docker images: Git SHA or SemVer?

Your grasp of immutable artifacts and traceability versus human-readable releases. Tag every build with Git SHA for immutability, then apply SemVer aliases only on promoted images. Treating floating tags like latest or v1 as safe production targets.

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