DCA study materials
DCA study resources

Docker Certified Associate study plan

DCA · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Installation and Configuration

  • Install Docker Engine on a Linux VM and confirm the client and daemon versions with docker version and docker info

  • Configure the daemon through /etc/docker/daemon.json (log driver, storage driver, default address pool) and restart to prove the settings apply

  • Create, switch between, and remove Docker contexts to point the CLI at a second host

  • Enable Docker at boot and diagnose a deliberately broken daemon config using journalctl -u docker

Your checkpoint

A Docker host whose daemon.json is committed to a notes repo, plus captured docker info output showing the non-default log driver and address pool in effect.

Week 2

Image Creation, Management, and Registry

  • Write a multi-stage Dockerfile that uses build args and a .dockerignore, then build and tag the image

  • Run a local registry:2 container, push the image to it, delete it locally, and pull it back by tag

  • Shrink the image by switching to a slim base and compare layer sizes with docker history

  • Prune dangling images and volumes and interpret the output of docker system df

Your checkpoint

A Git repo containing the multi-stage Dockerfile and a script that builds, tags, pushes to the local registry, pulls it back, and runs the container successfully, with terminal logs saved.

Week 3

Networking

  • Create user-defined bridge, host, and none networks and attach a container to each

  • Prove name-based DNS resolution between two containers on the same user-defined network

  • Publish a container port with -p and contrast the result with host networking

  • Inspect and troubleshoot a broken network path using docker network inspect and docker exec diagnostics

Your checkpoint

A network lab write-up showing four containers across two user-defined networks, with ping and curl logs proving DNS resolution works on one network and fails across networks.

Week 4

Orchestration & Networking

  • Initialize a swarm with one manager and two workers using join tokens

  • Deploy a replicated service and perform a rolling update followed by a rollback

  • Write a compose v3 stack file with a service, config, and secret and deploy it with docker stack deploy

  • Drain a node, confirm task rescheduling with docker node ls and docker service ps, then reactivate it

Your checkpoint

A running three-node swarm hosting a stack scaled to three replicas, with a logged rolling update and rollback sequence.

Week 5

Security

  • Create a swarm secret and mount it into a service, then verify it appears only under /run/secrets

  • Run a container as a non-root user via USER in the Dockerfile and --user on the CLI, confirming with id

  • Apply --memory, --cpus, and a read-only root filesystem, then test that the limits and read-only mount are enforced

  • Scan an image with a scanner of your choice and remediate at least one reported vulnerability

Your checkpoint

A hardened Dockerfile and compose file that runs as non-root with a read-only rootfs and a secret, plus before/after scan reports showing one fixed vulnerability.

Week 6

Storage and Volumes

  • Create a named volume and a bind mount and demonstrate that data survives container removal only where expected

  • List, inspect, and prune volumes and explain which volumes are safe to remove

  • Mount a tmpfs volume and contrast its contents after a container restart with a named volume

  • Back up and restore a named volume using a helper container that archives to the host

Your checkpoint

A backup/restore script for a named volume, verified by writing data, removing the container, restoring from the archive, and reading the same data back.

Week 7

Orchestration & Image Creation, Management, and Registry & Installation and Configuration & Networking & Security & Storage and Volumes

  • Take a timed 60-question practice exam and record scores per domain

  • Rebuild the two lowest-scoring domains by redoing their labs from scratch

  • Write a one-page command cheat sheet covering all six domains, verifying each command actually runs

  • Fix every missed practice question by reading the relevant official documentation section

Your checkpoint

A practice-exam score of at least 80% with a per-domain breakdown and a committed cheat sheet where every command has been executed at least once.

Week 8

Orchestration & Image Creation, Management, and Registry & Installation and Configuration & Networking & Security & Storage and Volumes

  • Complete two full-length timed practice exams under exam conditions with no notes

  • Map every missed question to the specific documentation page and summarize the fix

  • Re-run all prior lab deliverables end-to-end to confirm nothing has decayed

  • Review the six-domain cheat sheet and trim it to only items you can reproduce from memory

Your checkpoint

Two practice exams scored at 85% or higher and a signed readiness checklist confirming all lab deliverables still run end-to-end.

Milestones

Week 4: All four 17% domains have been labbed: a three-node swarm runs a stack with a secret, a local registry serves a multi-stage image, and containers resolve each other by name on a user-defined network; score at least 70% on a 40-question timed set covering domains 1-4.

Week 6: A container runs as non-root with a read-only rootfs and limited memory/CPU, a named volume has been backed up and restored, and each domain has at least one committed lab artifact.

Week 8: Two full-length timed practice exams scored 85% or higher with every missed question traced to a documentation page, and every lab deliverable re-verified as runnable.