Exam MB-200 All Questions

View all questions & answers for the MB-200 exam

Exam MB-200 topic 6 question 7 discussion

Actual exam question from Microsoft's MB-200

Question #: 7
Topic #: 6

You are a Dynamics 365 for Customer Service developer. You have a solution that uses release version 2.4.2.6. You clone the solution and apply an update.
You must assign the cloned solution a new version number using the Microsoft recommended versioning system.
You need to set the version number for the new solution.
Which version number should you set?

A. 2.4.3.7
B. 2.5.0.1
C. 2.5.3.6
D. 3.1.2.7

Show Suggested Answer

Suggested Answer: B 🗳️
References:
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/use-segmented-solutions-patches-simplify-updates

by mgharably at Sept. 14, 2019, 10:27 p.m.

Comments

Submit Cancel

rsousa

Highly Voted 5 years, 10 months ago

I've tried this, and while I agree that option B (2.5.0.1) is the correct answer by excluding all others, a more accurate answer would be 2.5.0.0, as you cannot change build and revision numbers and 0.0 is the default

upvoted 12 times

Stinner

5 years, 2 months ago

The key here is applying the update. It would default to 2.5.0.0, but the question makes it clear you then apply the update. That is why the correct answer is 2.5.0.1.

upvoted 5 times

...

Suchi

Highly Voted 5 years, 10 months ago

option B is correct because logically 2.5.0.1 will be default next after 2.4.whatever.whatever. I am saying whatever as build and revision values cannot be changed for Cloned solutions.

upvoted 7 times

...

sgupta1985

Most Recent 4 years, 8 months ago

Correct Answer as provided. "A cloned solution must have the version number greater than or equal to the version number of the base solution. For example, for a base solution version 3.1.5.7, a cloned solution could be a version 3.2.0.0, or version 3.1.5.7." Ref: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/use-segmented-solutions-patches-simplify-updates#understanding-version-numbers-for-cloned-solutions-and-patches

upvoted 1 times

...

Ameen

5 years, 2 months ago

In exam

upvoted 1 times

...

kultuze

5 years, 3 months ago

Here the catch is the clone and update... thats the reason its minor version is higher than the base

upvoted 1 times

...

Harish1509

5 years, 4 months ago

A solution’s version has the following format: major.minor.build.revision. A patch must have a higher build or revision number than the parent solution. It can’t have a higher major or minor version. For example, for a base solution version 3.1.5.7, a patch could be a version 3.1.5.8 or version 3.1.7.0, but not version 3.2.0.0. A cloned solution must have the version number greater than or equal to the version number of the base solution. For example, for a base solution version 3.1.5.7, a cloned solution could be a version 3.2.0.0, or version 3.1.5.7. In the UI, you can only set the major and minor version values for a cloned solution, and the build or revision values for a patch

upvoted 2 times

...

elka88

5 years, 5 months ago

in exam

upvoted 1 times

...

MAKHUNXA

5 years, 7 months ago

When you apply Clone Solution, system will let you update first 2 numbers, but last two numbers will be 0,0 and disabled. Which means the right ans should be 2.5.0.0, the close ans is B.

upvoted 1 times

SoMuchConfusion

5 years, 7 months ago

Right, because the question says that after cloning it, you apply an update. So the Clone would have been 2.5.0.0, and then you might bump the revision from 0 to 1 when you update something after cloning. I'm pretty sure B is indeed correct.

upvoted 4 times

...

ned

5 years, 6 months ago

It isnt close answer.. it is the exact answer.. the question also mentions "you apply an update"..

upvoted 3 times

...

FahadShaikh

5 years, 8 months ago

In exam question

upvoted 2 times

...

mgharably

5 years, 10 months ago

why not A ?

upvoted 1 times

Menik

5 years, 10 months ago

When you press 'Clone Solution' it bumps the minor version.

upvoted 2 times

...

Suchi

5 years, 10 months ago

A cloned solution must have the version number greater than or equal to the version number of the base solution. For example, for a base solution version 3.1.5.7, a cloned solution could be a version 3.2.0.0, or version 3.1.5.7. In the UI, you can only set the major and minor version values for a cloned solution, and the build or revision values for a patch. As per the info above, Option C and D cannot be correct because thought in each the version number (2.5 and 3.1) is higher BUT build and version values cannot be changed for cloned solutions.

upvoted 9 times

...