Exam MB-200 topic 9 question 1 discussion

This should be unmanaged solution with a custom publisher.

I think it should be A. You can't change the Publisher on Default Solution, however you can change the Prefix on the Default Publisher record itself.

C. Import a managed solution with a custom publisher.

The Default Solution can’t be exported. Therefore, you can’t distribute the Default Solution to another environment. https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/use-solutions-for-your-customizations

Default Solution --> Unmanaged Default Solution --> Default publisher

Default solution cannot be exported. For exporting to PROD , the components of the lamna healthcare would be kept in an unmanaged solution with custom publisher (with unique prefix)in Dev environment. But it should be exported as managed which can then imported as managed in the PROD. I would say the answer is managed with a custom publisher

You can't change the Publisher on Default Solution, and you can't export defaut solution as managed =­> the answer is A : Import an unmanaged solution with a default publisher

You can change the prefix of the default solution so it is A, Unmanaged (since she is working with the default solution) and default publisher (since she uses the default solution, she has changed the default prefix).

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/solutions-overview This also says managed are only used for imports into other organisations, which isn't the case here so it would be unmanaged default solution

Very interesting, Ive never seen anyone using managed solutions for deployments to Production of any iterated customizations BUT on a newly updated documentation Microsoft is suggesting to use Managed. I find this odd.... "In the Package Type step, you must choose whether to export the solution as an Unmanaged or Managed solution. Unmanaged solutions are intended to be used to transport configuration from one development environment to another or to check into your source control system. Managed solutions are intented to be used to transport configuration to all other environments including test and production environments."

You can't change the publisher for the default solution. You also can't export the default solution as a managed solution. So it has to be A.

Why not A? The Default solution can be exported and it is forced as an unmanaged solution. For the publisher, you cannot change the default publisher, but you can change its prefix, that would fit the requirement. That would be an easy way to handle all of this, you will be ensured that the production = sandbox (no missing component, no unmanaged local customization in production would be kept). Am I wrong?

I think this is D. Keeping all components in default solution means when moving changes to production, you can only export default solution and install default solution as an unmanaged solution file. You cannot change publisher for default solution and prefix is only changed by clicked the publisher and changing that!

Default solution (as given in the requirement) can't be exported as managed! So the answer is unmanaged solution. Now I checked it now.. and it's possible to change prefix for the default publisher to whatever you want, though it's not possible to change the default publisher itself for the default solution.. So the question must have more clarity and is ambiguos. Being forced to choose one, I would have chosen "unmanaged solution with a custom publisher.".. as proposed by JNSNW

Why not Managed solution with a default publisher ? Managed solution is completed solution for install, and the customer hold everything inside of default solution...Any suggestion ?

“Install an unmanaged solution only if you want to add all the components to your default solution and overwrite any existing customizations.” https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/solutions-overview So I vote for C

I will go for D. Import an unmanaged solution with a custom publisher.