Microsoft DevOps Engineer Expert AZ-400 Practice Question

Trunk-based development keeps a single long-lived trunk (often named main) that every developer merges into at least once per day, so the build pipeline can always build from one branch with a linear history. Short-lived feature branches are created only when necessary and are merged back rapidly, minimizing integration risk. Hotfix and release branches are also cut from the trunk, allowing urgent fixes to ship immediately while normal feature work continues. GitFlow and other long-lived feature branching models intentionally introduce multiple permanent branches (for example, develop or feature branches) that delay integration and complicate the history. A forking workflow spreads work across personal repositories, which hampers the required frequent integration and centralized CI.