Exam PL-600 topic 3 question 4 discussion

If source controlling it and the app is inside a solution, solution packager is this answer for source control. Package deployer can be used to deploy the solution. But on a testing environment would use a managed solution as Microsoft's recommendation is to use unmanaged solutions only for Dev environments. Well, if all solution components must be versioned and tracked, probably solution packager would be the right option here. But this question is not clear. Will go with C

100% C, I don't understand why the community votes are so divided. We all agree than unmanaged is not the way to go, so B and D are out. Now the question clearly states that we need to track all solution components, so we need to decompose solution and compose solution from source control and that is done by using Solution Packager. Package Deployer can be used to deploy package, but does not give you anything for version control or trackability, so this answer makes completely no sense. You need to use solution packager and then you need to deploy managed solution, you can do the deployment manually if you want, the question does not say anything about "automation" of deployment. So Solution Packager is a MUST and Package Deployer is OPTIONAL, therefore C

Why not the other options? B. Unmanaged solution Unmanaged solutions are editable and meant for development environments only. C. Solution Packager Used for source control, not deployment. It breaks down solutions into XML files. D. Solution Packager + Unmanaged Again, this is for development/source control, not for deploying to UAT.

A. Use Package Deployer and deploy a managed solution. it allows you to deploy solution packages efficiently in managed mode. Solution packager on the other hand is used for extracting and packaging solution components.

Was on the exam today 2023-12-22. I got 100% on this part of the exam. My answer was C.

Unmanaged: "Use managed solutions to deploy to any environment that is not a development environment, including test, user acceptance testing (UAT), system integration testing (SIT), and production environments." source https://learn.microsoft.com/en-us/training/modules/application-lifecycle-management-architect/3-solutions

I wonder how the original answers come to be? You would never deploy an unmanaged solution to test, regardless of how it got there, if you are using true ALM standards.

Its solution packager - its only editing a power app so a solution is sufficient.

solution packager +managed

C is correct

C is correct

I will go with C. It should be a Managed Solution, because we are talking about Test-environment + in order to track the elements, a decompression of the packages should happen (Solution Packager)

C is better suited

A managed solution is the recommended type to be imported into a UAT environment. The solution packager tool is the needed tool for source control. The first part of the following Microsoft article contains a well written explanation I think - https://learn.microsoft.com/en-us/power-platform/alm/use-source-control-solution-files

I agree

for tracking the version, the best option is the one with the Solution Packager.

A: preferred answer C is a little better than D where traditional undisciplined cowboy developers push code a little at a time into production and then do direct changes in production. C still has the issue of a single solution at a time. Best practice is to brake down solutions into horizontal and vertical partitions. If multiple solutions or not coordinated things can get messy. C&D can however can be orchestrated by using modern DevOps processes. One problem with old school deployments like this is deploying reference data or Power App Portals that need data migration. Also some deployments require custom code to run to modify things (data) before and after deployments. A: solves all these problems. A modern devops process will use Solution packager to extract source code, build/compile plugins and workflows and create the solutions zip files. It will extract reference data and Portals (Power Pages) again from source control. Inject custom code to do transformation. all into one neat Deployment Artifact. This one (tested) package is what is deployed.