You have an app named App1 that you release by using Azure Pipelines. App1 has the versions shown in the following table. You complete a code change to fix a bug that was introduced in version 3.4.3.

Question

Options

• A3.4.4
• B3.4.8
• C3.5.0
• D4.0.1

• A
  2% (1)
• B
  12% (6)
• C
  6% (3)
• D
  80% (40)

Explanation

Explanation

Option D (4.0.1) is correct because when fixing a bug that was introduced in a previous version (3.4.3), you are not simply patching the current codebase - you are making a change that corrects faulty behavior that has affected users across multiple releases, which in Semantic Versioning (SemVer) combined with the context of the existing version table, warrants a major version increment to signal a significant corrective release milestone.

• A (3.4.4) is wrong because a patch increment would only apply if you were making a minor fix to the current latest version in the 3.4.x line, not correcting a bug that has persisted across versions.
• B (3.4.8) is wrong because skipping patch numbers arbitrarily (e.g., jumping to .8) has no logical basis in SemVer and doesn't reflect standard versioning practices.
• C (3.5.0) is wrong because a minor version bump (3.5.0) typically indicates new backward-compatible functionality, not a bug fix to an existing release line.

Memory Tip: Think of it this way - if a bug broke something significant enough to persist across multiple versions, the fix is a major event. In SemVer: Major.Minor.Patch - breaking changes or major corrections = bump the Major number.

No community discussion yet for this question.