Microsoft DevOps Engineer Expert AZ-400 Practice Question

Your organization has 20 developers working on a single Azure Repos Git repository for an internal microservice. The microservice is deployed to production multiple times per day via a fully automated pipeline. Management reports that long-lived feature branches being merged at the end of each sprint often cause complex merge conflicts and delay releases. You need to redesign the branching strategy to reduce integration pain while still allowing developers to experiment in isolation for a few hours. Which branching approach should you recommend?

  • Require each developer to work in a personal fork and submit periodic patches directly to the main branch without pull-request validation.

  • Adopt trunk-based development by requiring every change to merge into the main branch within 24 hours through short-lived feature branches and mandatory pull requests.

  • Switch to a GitFlow model with permanent develop and release branches, merging feature branches only after user acceptance testing.

  • Continue using feature branches but extend branch lifetimes to the full release cycle and freeze the main branch except for hotfixes.

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.

Bash, the Crucial Exams Chat Bot
AI Bot