Microsoft DevOps Engineer Expert AZ-400 Practice Question

Contoso Ltd. stores its code in an Azure Repos Git repository that uses a default branch named main. The engineering leadership has mandated trunk-based development so that every team integrates code to main at least once per day. Production is deployed at the end of each 2-week sprint, but critical defects must occasionally be patched immediately, without waiting for the next planned release, and the fixes must flow back to main. Which combination of additional branch types best satisfies these requirements while remaining consistent with trunk-based practices?

  • A permanent develop branch for day-to-day work and release branches created at the start of every sprint

  • A single long-lived release branch that receives both feature work and hotfixes and is merged back to main once per quarter

  • Personal fork branches for each developer combined with pull requests to main

  • Short-lived feature branches cut from main and time-boxed release (hotfix) branches created only when an urgent production patch is needed

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