AZ-400: which branching strategy suits quarterly releases with a stabilisation period?

The question

I think the second knowledge check on https://www.aguidetocloud.com/guided/az-400/domain-2/branching-strategies/ regarding Nadia’s team is incorrect: “Nadia’s team at Meridian Insurance ships quarterly releases to production. Compliance requires a 4-week stabilisation period before each release. During stabilisation, the development team should continue working on next quarter’s features. Which branching strategy supports this?”

In my opinion the correct answer should be Git Flow, but the answer is wrong - according to the site the correct answer is trunk-based with feature flags, however the explanation also suggest that Git Flow is the correct answer: “Git Flow’s release branches are designed exactly for this: cut a release branch from develop for stabilisation, while the team continues merging new features to develop for the next release. The release branch gets only bug fixes during the 4-week stabilisation period.”

Regards,

Milco

The answer

Hi Milco — good catch again, and it turned out to be the same underlying bug as your other report.

The Knowledge Check widget wasn’t reading the AZ-400 answer key (correct={…}) and was defaulting to marking option A — so it highlighted “Trunk-based development with feature flags” even though the explanation describes Git Flow.

The correct answer is Git Flow with release branches: cut a release branch for the 4-week stabilisation (bug fixes only) while develop keeps taking next quarter’s features — textbook Git Flow, exactly as the explanation says. I’ve fixed the widget and redeployed; it now marks Git Flow correct. Verified live. Really appreciate the detail. 🙏 — Sush

Quick follow-up, Milco — your two reports turned out to be far more valuable than a couple of typos. 🙏

They prompted me to audit every knowledge check on the platform — all 2,382 across 38 certifications — and the same underlying issue (an answer-key prop the quiz widget silently ignored, defaulting to option A) was also hiding in:

• AZ-305 — all 60 checks were affected (authored as correctAnswer= instead of correctIndex=),
• 8 multi-select questions across AZ-140, DP-700, DP-420 and AI-901 that were previously unwinnable.

All fixed and live. I’ve also added a build-time check that now fails the deploy if any quiz has a missing or mis-typed answer key — so this whole class of bug can’t silently ship again. The other 36 certs were already clean.

Genuinely appreciate you taking the time to report these with such detail — they made the site materially better for everyone. — Sush