Exam PL-600 All Questions

View all questions & answers for the PL-600 exam

Exam PL-600 topic 3 question 20 discussion

Actual exam question from Microsoft's PL-600

Question #: 20
Topic #: 3

DRAG DROP
-

A company uses Microsoft Power Platform solutions.

The company plans to set up application lifecycle management (ALM) capabilities to store the solutions in source control, which will be used to automate the release process.

You need to set up the initial ALM infrastructure to store the solutions in source control.
Which four actions should you perform in sequence?

To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Show Suggested Answer

Suggested Answer:

by Schinna at March 23, 2023, 2:55 a.m.

Comments

Submit Cancel

Schinna

Highly Voted 1 year, 8 months ago

For me 6..5..3..2 . because Exporting from current environment and check out and unpack solution to repo will add to source control as branch

upvoted 12 times

mx007

6 days, 22 hours ago

based on the article how to setup and create such pipeline it should be 6,5,1,4, there is not export type pipeline and only release. In the article is no mention of running it only to set up the infrastructure.

upvoted 1 times

...

rober13

1 year, 4 months ago

Create project Install tools asociate a pipeline. run pipeline Reference : https://learn.microsoft.com/en-us/power-platform/alm/devops-build-tools

upvoted 1 times

...

Ninashnash

1 year, 7 months ago

Agree 6532 is correct

upvoted 3 times

Ninashnash

1 year, 7 months ago

The goal is to "Store the solution in source control", so anything related to importing the solution is not required for this question.

upvoted 1 times

...

ah2006

Most Recent 10 months, 2 weeks ago

The question is only to store the solution in the source control - not to import it to a target environment. So I go with: Create an Azure DevOps Project: You need a project container where all the ALM process components, like source control, build pipelines, and release pipelines, will reside. It's the foundational step before setting up specific ALM processes. Install the Microsoft Power Platform Build Tools: These tools are necessary for automating the build and deployment process of Power Platform solutions. They include tasks like exporting a solution from an environment, checking it into source control, and deploying solutions to target environments. Create an Export pipeline: Before you can release a solution, you need to have it exported from the development environment. The export pipeline facilitates the automation of extracting the solution from the Power Platform environment so that it can be stored in source control. Run the pipeline So: 6,5,3,2

upvoted 3 times

...

MEG_Florida

1 year, 4 months ago

You this one is a little trigger without a little more details 5.6.3.2 1. (5) You should install the tools first, not after you create the project so 5 first 2. (6) Create your Azure Dev Ops Project 3. (3) Now you can create your Export Pipeline. For me, dont be confused by the fact about naming. You can call your pipeline whatever you want and yes you can easily create a pipeline that Exports the solution. It just happens in this answer to be called Export Pipeline 4. (2) Now you need to run the pipeline to put the stuff into DevOps and commit it

upvoted 2 times

No_Doubt

1 week, 6 days ago

I don't agree with you, should be 6 then 5 The reason "Install the Microsoft Power Platform Build Tools" typically happens after creating the Azure DevOps project is that the build tools need to be configured within the context of a specific project in Azure DevOps.

upvoted 1 times

...

yf

1 year, 5 months ago

5,6,1,4 5 global Azure DevOps extension, I would install this first before making an project and then return to install it. | 6 need a project first 1 create a pipeline, this on is tricky only a release pipeline exists in Azure DevOps. 4 finally add the task to the pipeline. 2: No mention of running the pipeline in the question 3: No Export pipeline in Azure DevOps.

upvoted 2 times

MEG_Florida

1 year, 4 months ago

You can call your pipeline whatever you want. Creating one that does the Export is easy and I think they are just using the term Export pipeline to just mean the steps you are taking to export it. And not 4 because you aren't importing anything. You just need to run the pipeline, which should take the files and commit them

upvoted 1 times

...

xanr4711

1 year, 7 months ago

There is no Export Pipeline... so does it mean the "export pipeline" includes all the steps necessary to export the solution, extract it and import it into GIT repository? Then yes, should be 6-5-3-2

upvoted 4 times

...

MarioM

1 year, 8 months ago

6, 5, 3, 4

upvoted 2 times

...