Crucial Exams

Microsoft DevOps Engineer Expert AZ-400 Practice Question

Your team maintains several microservices in a single Azure DevOps project. Feature branches often remain open for weeks, causing painful merges, and you must be able to ship critical production fixes without blocking ongoing feature work. You need a branch strategy that minimizes integration risk, supports daily continuous integration on the main line, and lets the team deliver parallel hotfixes for supported production versions. Which branching approach meets these requirements?

  • Adopt trunk-based development with short-lived feature branches merged into the main branch at least daily, and create a release branch only when a version is shipped so hotfixes can be applied independently.

  • Adopt trunk-based development where developers commit directly to main with no feature branches, and create a release branch only at ship time for hotfixes.

  • Continue using long-lived feature branches but require developers to rebase and squash-merge into a develop branch, then create a dedicated release branch at the end of each sprint.

  • Switch to GitFlow with separate develop and release branches; all features merge into develop, and a new release branch is created every sprint, merging back into develop and main.

Microsoft DevOps Engineer Expert AZ-400
Design and implement a source control strategy
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Wipe Score
Bash, the Crucial Exams Chat Bot
AI Bot