nerdexam
Microsoft

AZ-400 · Question #441

Drag and Drop Question You are designing a versioning strategy for Git-based packages. You plan to use a Semantic Versioning (SemVer)-based strategy. You need to identify when to change the build vers

The correct answer is Major; Minor; Minor. In Semantic Versioning (SemVer), the version format is MAJOR.MINOR.PATCH. A MAJOR version increment occurs when breaking/incompatible API changes are introduced, meaning existing consumers must update their code. A MINOR version increment occurs when new backward-compatible funct

Submitted by akirajp· Mar 6, 2026Design and implement a package management strategy - specifically understanding SemVer versioning rules to determine when to bump Major, Minor, or Patch versions based on the nature of code changes in Azure DevOps or similar CI/CD pipelines.

Question

Drag and Drop Question You are designing a versioning strategy for Git-based packages. You plan to use a Semantic Versioning (SemVer)-based strategy. You need to identify when to change the build version. What should you identify for each scenario? To answer, drag the appropriate versions to the correct scenarios. Each version may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:

Exhibit

AZ-400 question #441 exhibit

Answer Area

Drag items

MajorMinorPatch

Correct arrangement

  • Major
  • Minor
  • Minor

Explanation

In Semantic Versioning (SemVer), the version format is MAJOR.MINOR.PATCH. A MAJOR version increment occurs when breaking/incompatible API changes are introduced, meaning existing consumers must update their code. A MINOR version increment occurs when new backward-compatible functionality is added - such as adding a new feature or new API endpoint that doesn't break existing consumers. The third scenario also maps to MINOR because adding backward-compatible functionality (even in different forms like new optional parameters or new modules) follows the same rule. Patch is reserved strictly for backward-compatible bug fixes with no new functionality.

Topics

#Semantic Versioning#SemVer#Package Management#Git Versioning Strategy

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-400 Practice