AZ400-Q: Trunk-based development
Q: A team uses short-lived feature branches that are merged back to
mainfrequently (often same-day) via pull requests with mandatory CI. Releases are cut directly frommain. Which branching strategy does this best describe?
- A) GitFlow
- B) Trunk-based development ✓
- C) Forking workflow
- D) Release branching
Answer: B. Trunk-based development keeps a single long-lived branch (main/trunk) and integrates small, short-lived branches into it continuously, with CI on every merge and releases cut from the trunk. GitFlow uses long-lived develop and release branches; forking relies on copies of the repo; release branching maintains parallel long-lived release branches.
Why it helps
AZ-400 tests your ability to recommend the right branching strategy for a team’s cadence — trunk-based is the correct fit for high-frequency CI/CD.