Exam MB-500 topic 14 question 1 discussion

My answers are: -Import the model into a Development environment ->Synchronize the models in the Developer environment by using Get Lastest feature -> Add the package to source control and check in changes -> Build and create a deployment package

I would do: Import the model into a development environment - Synchronize the models in the developer enviroment by using Get Latest feature - Build en create a deployment package - Add the package to source control and check in the changes.

One of the requirements is "You must configure version control and a Build environment." And Build environment is to run Build and create deployment package. In that case: Import the model into Dev environment Add the package to Source control and check in changes Import the model into Build environment Build and create a deployment package

1. Synchronize the models in the Developer environment by using Get latest feature 2. Import the model into a Development environment 3. Add the package to source control and check in changes 4. Build and create a deployment package

Microsoft says: "Deployable packages from third parties can be manually installed on a development VM, and the installed artifacts can then be added to source control. Then, by synchronizing their local workspace, other developers can receive the runtime package on their VMs without having to install the deployable package. The build process on the build VM will help guarantee that the runtime packages for any extensions or other dependencies are available on the build VM." So 1. Import the model into a Development environment 2. Add the package to source control and check in changes 3. Synchronize the models in the Developer environment by using Get Lastest feature 4. Build and create a deployment package https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/manage-runtime-packages#deploying-third-party-code

Import the model into a Development environment Synchronize the models in the Developer environment by using Get Lastest feature Add the package to source control and check in changes Build and create a deployment package

I would do it as in the answer, so Correct. You checkin the changes to reflect if any changes done to the model since it is exported first. Then on the development environment import the model, get latest for the model to get those changes and build - create package.

I would go with: 1. Get latest 2. Import the model into a dev environment 3. Add to source control and check in 4. Build and create a deployable package

Import to QA Build and create a deployment package Add the package to source control and check in Synchronize the model and get latest

I often have to take these steps: - Install the new model - Add the package (including descriptor and bin folders) to the source control so that other development boxes can use it or the daily build can call it up. This step is called separately in this answer area - Create a one-in-all package, usually created by the build server - Finally, other developers can also use the check-ins by clicking "Latest" The correct order shoul be: 3,1,2,4

I could be wrong but it seems to be that you would 1. Import the model into a development environment 2. Add the package to source control and check-in changes 3. Build and create a deployment package 4. Sync the models in the developer environment --> the wording on this is confusing but if you read the linked article, they talk about other developers synchronizing and pulling the 3rd party models into their system. In that case, they won't be able to do that until the code is checked in. Or maybe I'm missing something?

->Synchronize the models in the Developer environment by using Get Lastest feature (check for latest version and Developer2 joins the company and does not have access to a development environment or source control.) ->Import the model into a Development environment -> Add the package to source control and check in changes -> Build and create a deployment package

Actually source control is only allowed after QA testing thus: Import the model into Development environment - Build en create a deployment package - Import the model into a QA environment - Add the package to source control and check in the changes