Exam PL-400 topic 3 question 7 discussion

The answer is correct- 10.0.3.1. NB://D365 automatically increments the Build version(Major.Minor.Build.Release) when we patch a solution.

Answer should 1.0.2.2.

The correct answer is: B. 10.0.2.2 ✅ Explanation: Solution versioning in Power Platform follows the semantic versioning pattern: Major.Minor.Build.Revision (e.g., 10.0.2.1) If you're fixing a bug, you typically increment the last segment (Revision) of the version number. Version Part Meaning When to increment Major Breaking changes Major new features/releases Minor Significant enhancements New features, not breaking Build Small updates or hotfix groups Series of minor fixes Revision Minor fix or patch Bug fix or tiny tweak

Bug fixes update the revision number, so the answer should be 10.0.2.2 (There is no new functionality)

ChatGPT: B. 10.0.2.2 Explanation: When fixing a bug, the appropriate versioning practice is to increment the revision number, which is typically the last segment in the version identifier. Given that the current version is 10.0.2.1, the updated version after a bug fix should be 10.0.2.2. Here’s how versioning is typically structured: Major version: Incremented for major updates or breaking changes. Minor version: Incremented for new features or significant changes that are backward compatible. Patch version: Incremented for backward-compatible bug fixes. Revision (optional): Incremented for smaller updates or specific fixes, depending on the versioning scheme. Since this is a bug fix, B is the most appropriate choice.

The correct answer is B. 10.0.2.2. Explanation: When fixing a bug in your application, you typically increment the revision number in the versioning format Major.Minor.Build.Revision. Given the current version 10.0.2.1: Major: Indicates a significant release with breaking changes. Minor: Indicates a release with new features, but backward-compatible. Build: Often incremented for non-breaking enhancements. Revision: Typically incremented for bug fixes or small patches. Since this update is a bug fix: Incrementing the revision number from 1 to 2 results in 10.0.2.2.

Both A and B should work, but I feel this is a update, so should increase the build version, not revision, so A is good one

I would go with Build version so its 10.0.3.1

Did someone really try what is described here?: https://carldesouza.com/how-solution-version-numbers-work-in-the-microsoft-power-platform/ Because "Cloning a Patch" will let you modify only <build>.<revision> while "Cloning a Solution" will let you modify only <major>.<minor> while defaulting to 0 the <build>.<revision>. So the question states "You need to publish an updated version of the solution." meaning you have to "Clone a Solution", so having the initial version "10.0.2.1" it would result in "10.1.0.0" which is not in the answer list and "C - 10.1.0.2" is NOT a valid answer. So it could be "D - 11.0.0" but is missing a last ".0"... so in this case no asnwer is valid?

B is the correct answer. Build number will be changed when we patch, and we will patch if we add or remove entities or their metadata. Fixing a bug will is not changing the structure of solution, hence only revision number will increment.

its A we are talking a bout version

I think B is the right answer because you cannot skip versions. Here we skip version 10.0.3.0. (only 10.0.3.1. is offered)

Should be A The version number of solution is <major>.<minor>.<build>.<revision>. - When exporting solution, revision number is incremented automatically. - When creating a patch, build version is incremented automatically. - When cloning solution, minor version is incremented automatically.

A it is its a minor change

The version identifier you should use is: B. 10.0.2.2 In version numbers, each segment represents a specific level of update: The first segment represents the major version. The second segment represents the minor version. The third segment represents the build version. The fourth segment represents the revision version. When you fix a bug in the code of your application, you typically increment the revision version (the fourth segment) by 1. The major and minor versions remain unchanged. Since the current version is 10.0.2.1, the updated version with the bug fix would be 10.0.2.2.

According ot Microsoft, the format for version numbers is major.minor.build.revision https://learn.microsoft.com/en-us/power-apps/maker/data-platform/update-solutions#understanding-version-numbers-for-updates Therefore, B would be the correct answer.

There is no patch created, just export a new version. So, the answer should be 1.0.2.2. Below post has explained well. https://www.hellosmart.ca/2023/02/tips-dynamics-365-power-apps-power.html