Correct Answer: D
There is no direct integration between the source control services (like Git or Team Foundation Version Control) and Dataverse solutions. But you can use the SolutionPackager tool for any source control service. The tool extracts individual files and directories from the solution package. When you are ready to check in your solution, you save, publish and export your solution. The Power Apps portal creates a zip file. Then you use the SolutionPackager tool to extract the components flies from the zip file. After that, you can check in the files into your source control service. If you need to check out the component’s files, you check out the files from the source control management system into your local directory and use the SolutionPackager to create a solution zip file. Then you can import the solution into your development environment.
Option A is incorrect because the Package deployer tool helps administrators deploy a package with one and more solutions on Dataverse instances. But this tool doesn’t extract solution files from the solution.
Option B is incorrect because the Azure Function service doesn’t extract solution files from the solution.
Option C is incorrect because the Azure DevOps service doesn’t extract solution files from the solution. But Azure DevOps can automate the solution deployment and run the SolutionPackager as CI/CD task.
Option E is incorrect because the Dataverse Plug-in Registration tool doesn’t extract solution files from the solution.
For more information about the source control of the solution files, please visit the below URLs:
https://docs.microsoft.com/en-us/power-platform/alm/use-source-control-solution-files
https://crmchap.co.uk/exam-pl-400-revision-notes-using-solutions-to-implement-application-lifecycle-management-alm-capabilities/