Backend engineering from first request to production · check

Know Docker, Kubernetes and production operations already?

One question for each of the 4 puzzles in this module. A right answer marks that puzzle as passed, so you can jump ahead. A wrong one tells you which puzzle to start with. Nothing is sent anywhere: it's saved in this browser.

Puzzle 13: What goes in a Docker image?

Which path needs write access in this lab?

Not quite. The service only reads its code. Learn it in puzzle 13 →

Right. The image supplies the program. A writable mount supplies the database when the container filesystem is read-only.

Puzzle 14: Who replaces a missing pod?

After a pod replacement, which observation proves the bookmark survived?

Right. A Deployment describes the desired pods. Their storage lifetime depends on the selected volume.

Not quite. The replacement can be ready with an empty directory. Learn it in puzzle 14 →

Puzzle 15: Which users felt the slowdown?

All failed requests return quickly. Which signal is essential alongside response time?

Not quite. Fast failures still hurt availability. Learn it in puzzle 15 →

Right. A percentile describes an ordered sample. Averages can hide a slow group.

Puzzle 16: What evidence earns a release?

Which observation best closes the rollback drill?

Not quite. Starting the image alone does not verify service behavior. Learn it in puzzle 16 →

Right. A release gate connects a reproducible artifact to evidence that the service can serve real requests.

Back to the overview →