系統管理員打造涵蓋 57 項 Microsoft 認證考試的 MsCertQuiz，分享建站時實際遇到的問題

I've been doing enterprise IT for about 13 years. Exchange migrations, hybrid AD, Intune rollouts, the usual. These days I look after Microsoft 365, Entra and Azure for a company with around 4,000 users.

Every time someone on a team I worked with was studying for an AZ-104 or an MS-102, the same thing happened. They'd find a practice test, do 50 questions, and then ask me why answer C was right. Half the time the "correct" answer was out of date. The other half there was no explanation at all, just a green tick.

So about a year ago I started building my own. That turned into MsCertQuiz. It now covers 57 Microsoft exams with 500 questions each. I'm not a developer by trade, so I learned a lot of this the hard way. Here's the stuff I wish someone had told me.

1. Writing questions is easy. Writing correct ones is not.

The first version of my question bank had problems I didn't notice for weeks. A license name Microsoft had renamed. A PowerShell module that was retired. An answer that was right for Azure AD but not quite right for Entra ID.

What fixed it was treating every question like a change request. Each one now has to point back to a specific Microsoft Learn page, and I run it through more than one model to check it, a local Qwen model on my own GPU plus two hosted ones. If they disagree with each other or with the docs, the question gets flagged and I look at it myself. It's slower, but the number of "this answer is wrong" emails dropped a lot.

2. The explanation is the product

I thought people were paying for questions. They aren't. They're paying to understand why the wrong options are wrong.

If you only explain the right answer, people memorise it. If you explain why the other three fail, they actually learn the concept, and they can handle a question worded differently on exam day. Every question I write now has a sentence or two for each option, not just the correct one.

3. Microsoft retires exams faster than you think

When I started, my list was mostly the classic exams. Now there's a whole new wave of AB- and AI- exams, plus GitHub certs and Fabric. Keeping up is a job in itself. I check exam pages every month and keep a "last reviewed" date on the site, mostly to keep myself honest.

4. Payments and tax ate more time than code

Nobody warned me about this one. About half my customers pay with PayPal instead of card, and as a sole trader in Sweden selling to people across the EU, I have to get VAT right for every country. Stripe Tax handles card payments nicely. PayPal took a lot more manual work. If you're planning to sell a digital product in Europe, sort this out before you launch, not after.

5. Building one more site is tempting

Once the Microsoft site worked, people asked about AWS and CompTIA. So I built CertSharp for multiple vendors (AWS, Cisco, CompTIA and Google Cloud), and later CompCertQuiz focused only on CompTIA, because CompTIA people search for CompTIA, not "IT certs".

Same codebase, same rule: original questions written from the published objectives, never brain dumps. Dumps can get your cert revoked, and they don't teach you anything anyway.

What I'd tell another sysadmin thinking about a side project

• Build something for a problem you've watched people struggle with for years. You'll know the edge cases already.
• Your ops habits transfer well. Change control, documentation and monitoring work just as well on a side project.
• Ship the boring stuff early: billing, tax, password reset, refunds. That's where the support emails come from.

If you're studying for a Microsoft, AWS or CompTIA exam and want to try it, every exam has free questions with no card needed. And if you spot a wrong answer, please tell me. That's genuinely the most useful feedback I get.

Happy to answer questions in the comments, especially about M365 and Entra certs.