Exam AZ-400 topic 5 question 38 discussion

B is the answer. https://semver.org/#summary Given a version number MAJOR.MINOR.PATCH, increment the: - MAJOR version when you make incompatible API changes - MINOR version when you add functionality in a backward compatible manner - PATCH version when you make backward compatible bug fixes

The correct answer is NOT 11.2.1 — it is 10.5.2. According to Semantic Versioning (SemVer): MAJOR.MINOR.PATCH The question says: "You change the code of App1 to fix a bug that was introduced in version 10.5.1." This means the bug exists in the 10.x line of versions, and the fix is applied to that same branch — not to the 11.x series. So, the correct next version in the 10.x line after 10.5.1 is 10.5.2. Why not 11.2.1? 11.2.1 would only be correct if the bug existed in version 11.2.0 and was fixed there. But the question makes it clear: the bug was introduced in 10.5.1, so we must patch that version directly. This is a classic SemVer use case: apply PATCH versioning to the same MINOR line when fixing old releases. Correct answer: C. 10.5.2

11.2.1

Copilot IA response: Semantic Versioning (SemVer) follows the pattern of MAJOR.MINOR.PATCH. MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes. Given that you are fixing a bug in the application, you should increment the PATCH version. Since the current version of App1 is 11.2.0, the new version, after the bug fix, should be 11.2.1. So, the correct answer is B. 11.2.1. Even though the bug was introduced in version 10.5.1, the version number should always be incremented from the current version, not the version where the bug was introduced. This is because the new release will also include all the changes made in versions after 10.5.1 up to the current version. Therefore, going back to a previous version number or creating a separate patch version for 10.5.1 would not be appropriate or in line with Semantic Versioning rules.

Agree with B

The SemVer version is made up of three numbers separated by dots: "X.Y.Z", where X is the major number, Y is the minor increment number, and Z is the correction number. Each of these numbers has a specific meaning: Major Number (X): Indicates a significant release that is likely to include backward-incompatible changes. Changes to this number often reflect major updates and fundamental changes to the software. Minor Increment Number (Y): Represents a minor update that does not introduce backward-incompatible changes. May include new features or improvements that do not affect existing functionality. Fix Number (Z): Refers to bug fixes and minor changes that do not significantly affect the overall functionality of the software. These changes are backwards compatible and do not introduce new features.

B - 11.2.1 Why ? The CURRENT version (as in the released version, because the question says nothing about other versions being in production, so we will assume current = live) is 11.2.1. It does not matter in what previous version the bug has been detected.

This is a bit unclear. If the current production version is 10.5.1 and the development version is 11.2.0, then if we want to just release the bugfix, the version should be 10.5.2. Otherwise it should be 11.2.1.

Remember the next version always has to be after the current version. In this case we are fixing a bug which is a patch so only the last digit increments by one.

should be C

B is correct

10.5.2 - because it will be the next version number.