You can pass an exam having never made a decision you had to live with.
That gap is why Practiworks exists. Plenty of material will get you through the recall questions. Very little of it makes you practise the judgment calls, which is what the exam is testing and what the job needs on the Monday after.
It started with my own exam prep
The Microsoft Learn paths cover the material well and I still point people at them. What they couldn't tell me was whether I could apply any of it under pressure. I'd read a module, feel like I knew it, and have no way to find out if that was true.
So I built Capacity Command for a Microsoft Fabric community contest. Take the platform admin role at a fictional logistics company, run its analytics platform for a week, and find out what your decisions cost. It sat alongside the learning paths rather than replacing them, and that's still how I think about it.
Nothing about that is specific to Fabric or to data engineering. The same format should work for any certification where the exam is really testing judgment. Practiworks is the attempt to build the rest of them.
Four things worth saying out loud
The exam is a proxy. The job is the point.
We build for the work first and let the certification follow. A track that got you through the exam and left you no better at the job has failed, whatever the pass rate says.
Being wrong should cost something.
A red cross next to a wrong answer teaches you almost nothing. Take a shortcut on Monday and watch it resurface on Tuesday as somebody else's outage, and you'll only need to learn that one once.
Say plainly what's real and what isn't.
The companies are invented. We tuned the numbers so the trade-offs bite. They are not real pricing, and every track says so on the way in.
What is free now, stays free.
Everything on the site today is free, needs no account, and stores nothing about you on a server. What's free now stays free.
A small operation
Practiworks is built by me, Anco van den Berg, a data architect running Microsoft data platforms. That's also where most of the incidents in Capacity Command come from.
"We" is small: one person writing, plus people who have actually held the role a track is about. That's the bar for anything we add. Somebody who has done the job checks the incidents before a track ships.
Which certification should go in next?
The roadmap is shaped by what people ask for. If there's an exam you'd want to prepare for this way, tell us.