Cleared the Docker Certified Associate exam last week with a 78% and wanted to share what actually mattered vs what I spent too much time on. I studied for about 9 weeks, averaging 1.5-2 hours on weekdays and 4 hours on Saturdays. The exam is 55 questions across 6 domains with a 90-minute limit, which sounds generous but scenario-based questions eat time fast.
Domain 2 (Image Creation, Management, and Registry) and Domain 4 (Networking) made up the bulk of questions in my experience. Lean heavily into multi-stage builds, image layer caching, and overlay network drivers. I spent too much early prep on Swarm orchestration, which showed up way less than I expected.
The hardest questions were around security - content trust, image signing, and secrets management. If you're coming from a dev rather than ops background, that section probably needs extra attention. Spinning up a local lab and running through those scenarios hands-on was worth more than any amount of reading.
The 90-minute limit isn't tight if you're genuinely comfortable with the material. I finished with 18 minutes left. But if you're second-guessing yourself on networking and security, that time pressure adds up quickly.
What practice resources did you use? I've been through the official study guide but it feels thin on the scenario-type questions you're describing. Looking for something with more realistic question formats before I sit for it next month.
Congrats on passing. Networking wrecked me on my first attempt - I didn't fully understand how the IPAM driver worked and got 3 questions wrong on that topic alone. The second time I rebuilt a full overlay network from scratch in my lab and it clicked.
Agree on the Swarm point. The exam still covers it on paper but the real-world questions seem to favor containerization fundamentals over orchestration specifics. Kubernetes barely appears in the official domain breakdown.
This is exactly how I approached it too. I'd get a practice question wrong and just note the right answer, then wonder why it wasn't sticking. The shift that actually helped was forcing myself to explain why each wrong option was wrong, not just what the right one was. Like if you can't articulate why option B is garbage compared to option D, you don't actually understand the concept and the exam will find ways to expose that.
The networking domain especially rewards this. There's so many questions where two answers look almost identical and you've got to know the subtle distinction. I spent probably three full study sessions just on overlay networks and it wasn't memorizing definitions, it was asking "okay but why would you NOT use this in this scenario." Took longer but I stopped second-guessing myself mid-exam, which honestly might be why I finished with 20 minutes to spare.
Congrats on the pass! The thing that clicked for me was actually spending time in the Docker playground just breaking things on purpose. I kept reading the docs and thinking I understood networking but then I'd get a question about overlay networks or ingress routing and completely blank. Once I started spinning up actual Swarm clusters and misconfiguring them intentionally, the troubleshooting questions started making sense in a way that no study guide could really replicate.
Also don't sleep on the image management domain. I didn't think it'd show up much but it's pretty well represented and stuff like multi-stage builds and layer caching wasn't totally obvious to me until I'd actually built a few images from scratch. 78% is solid for this exam, so you clearly had the right approach.
Thanks for this breakdown, it's super helpful. I'm about 5 weeks in and just hit 71% on a practice run last night, which felt decent but I know I've got gaps in the orchestration and security domains. Aiming to sit the real thing in roughly three weeks if my scores keep trending up.
The storage section caught me off guard too, didn't realize how much they'd dig into volume drivers and bind mounts. I've been doing a lot of hands-on labs this week instead of just reading and it's clicking faster that way. Fingers crossed I can get into the mid-70s range consistently before I pull the trigger on scheduling.