[🐛 Bug Report] AZ-400

[susanthgit]

Third Knowledge check:
An organisation has three teams: a SaaS platform team (deploys daily), a mobile app team (ships monthly to app stores), and an internal tools team (6 developers, deploys weekly). What branching approach should the organisation adopt?

The correct answer should be that each team uses the strategy that matches their deployment model, but the correct answer is indicated as Standardize all teams on Git Flow?! Again, the explanation supports this reasoning: "Different teams have different deployment models and constraints. The SaaS team benefits from trunk-based or GitHub Flow (daily deploys). The mobile team needs release branching (monthly app store releases). The internal tools team fits GitHub Flow (weekly deploys). Forcing one strategy on all teams creates friction."

---

From: Milco Numan · Related Tool: Cert Study Guides · Category: 🐛 Bug Report · Reply contact provided via form

[susanthgit]

Hi Milco — you're absolutely right, and thank you (two sharp catches in one day 🙏).

This turned out to be a component bug, not just a wrong answer key. The Knowledge Check widget was only reading its correctIndex prop, but the AZ-400 modules pass the answer as correct={…} — so the intended answer was being ignored and every check silently fell back to marking option A. That's exactly why "Standardise all teams on Git Flow" showed as correct even though the explanation argues the opposite.

The correct answer is what you said: each team uses the strategy that matches its deployment model — SaaS → trunk-based / GitHub Flow (daily), mobile → release branching (monthly app-store), internal tools → GitHub Flow (weekly). Forcing one strategy on all three creates friction.

I've fixed the widget and redeployed — it now marks C correctly (and the same bug was quietly affecting the other AZ-400 checks, so those are all fixed in one go). Verified live. Thanks for making the site better. — Sush

[susanthgit]

Follow-up: these two reports of yours actually surfaced a platform-wide issue. I've now audited and fixed the same bug across all 2,382 quizzes (AZ-305 — all 60 checks — and several multi-select questions in AZ-140/DP-700/DP-420/AI-901 were affected too), and added a build guard so it can't recur. Full details on your other thread (#29). Thanks again, Milco — these were great catches. 🙏 — Sush