Design a Docker artifact system for cost, traceability, and speed

WHAT THIS TESTS: This question evaluates whether you can design a socio-technical system, not just pick a tool. The interviewer cares about lifecycle governance: how you trade off storage cost against deployment latency and compliance traceability at organizational scale. They want to see awareness of immutable infrastructure, tiered storage economics, and the operational reality of thousands of engineers pushing artifacts daily.

A GOOD ANSWER COVERS: A good answer hits four things in order. First, a tiered storage architecture with automated lifecycle policies: hot storage for recent production images, warm for staged releases, and cold or deleted for old dev builds, with rules triggered by age, tag patterns, or branch names. Second, traceability through immutable content-addressable digests rather than mutable tags, plus metadata linking each artifact to a git commit SHA, CI pipeline ID, and build timestamp, ideally stored in an artifact metadata store or SBOM repository. Third, performance through regional distribution: a primary registry in each major geography, pull-through caches in clusters, and local registry mirrors so node pulls do not traverse continents or hit a single global endpoint. Fourth, cost control through garbage collection of untagged manifests and orphaned layers, team-level storage quotas, and retention rules that differentiate between ephemeral feature branch images and signed production releases that must be kept for years.

COMMON WRONG ANSWERS: Common wrong answers include relying on a mutable latest tag for deployments, which destroys traceability and causes cache coherency bugs. Another red flag is proposing manual cleanup scripts without retention SLAs, which inevitably fail and turn the registry into an expensive dumping ground. Suggesting a single global registry without regional caches shows inexperience with distributed deployment latency. Ignoring layer deduplication or manifest lists also signals shallow knowledge of container registry internals.

LIKELY FOLLOW-UPS: Interviewers often push deeper with three questions. How would you handle base image updates when all tags are immutable? They expect you to discuss rebuild pipelines and new digests. What happens if the registry is down during a production incident? They want failover registries or pre-pulled images on nodes. How do you charge storage back to teams? They want showback or quota enforcement per business unit.

ONE CONCRETE EXAMPLE: A concrete example is a platform with three registries: a fast dev registry with a seven-day TTL on untagged images and no geo-replication; a staging registry with thirty-day retention and vulnerability scanning gates; and a production registry geo-replicated across three continents, requiring image signing, storing SBOMs for two years, and keeping release artifacts indefinitely. Each Kubernetes cluster runs a pull-through cache, and a nightly job garbage-collects orphaned blobs, reducing storage growth by roughly sixty percent in the first quarter.