Cloned Solution Version: 5.2.3.1

Correct Answer: C

There are two options for the managed Dataverse solutions updates: To create a patch - a bug fix or some minor solution change.

To clone - a major solution update.

You can select a solution from the Power Apps portal and click on the three dots for more options.

When you choose the Clone menu item, you will see two options: Clone a patch and Clone a solution.

Every solution has a version number with the following structure: <major>.<minor>.<build>.<revision>

The “Clone solution” controls the first two numbers: <major> and <minor>

The Power Platform automatically increments the minor number, e.g., if the basic solution has a 5.2.3.1 version (Number 1), the clone will have by default 5.3.0.0 (Number 2)

Users can change the first two numbers only.

The “Clone a patch” controls the last two numbers: <build> and <revision>

The Power Platform automatically increments the build number, e.g., if the basic solution has a 5.2.3.1 version (Number 1), the patch will have by default 5.2.4.1 (Number 3)

Users can change the last two numbers only.

All other options are incorrect.

For more information about cloning the Dataverse solutions, please visit the below URLs:

When you clone a solution in Power Platform, a new solution is created with the same components and settings as the original solution. However, the version number of the cloned solution may be different from the original solution, depending on the cloning settings you choose.

By default, when you clone a solution, the cloned solution will have a new version number, with the major and minor versions incremented by 1, and the revision and build numbers reset to 0. This is to indicate that the cloned solution is a new version of the original solution.

In this case, the original solution version is 5.2.3.1. If you clone the solution using the default settings, the cloned solution will have the version number 5.3.0.0. This is because the major and minor versions are incremented by 1, and the revision and build numbers are reset to 0.

Option A (5.2.3.2) is not correct, as the revision number is incremented by 1 instead of being reset to 0.

Option B (5.2.4.1) is also not correct, as the major and minor versions are not incremented by 1.

Option D (5.3.3.2) is not correct, as the build number is not carried over from the original solution.

Therefore, the correct answer is C (5.3.0.0).