Which three actions should you perform in sequence?

Case Study 2 – Contoso, Ltd

Background

Contoso, Ltd. is a manufacturing company that has a main office in Chicago.

Contoso plans to improve its IT development and operations processes by implementing Azure DevOps principles. Contoso has an Azure subscription and creates an Azure DevOps organization.

The Azure DevOps organization includes:

• The Docker extension

• A deployment pool named Pool7 that contains 10 Azure virtual machines that run Windows Server 2016

The Azure subscription contains an Azure Automation account.

Contoso plans to create projects in Azure DevOps as shown in the following table.

Technical requirements

Contoso identifies the following technical requirements:

• Implement build agents for Project1.

• Whenever possible, use Azure resources.

• Avoid using deprecated technologies.

• Implement a code flow strategy for Project2 that will:

– Enable Team2 to submit pull requests for Project2.

– Enable Team2 to work independently on changes to a copy of Project2.

– Ensure that any intermediary changes performed by Team2 on a copy of Project2 will be subject to the same restrictions as the ones defined in the build policy of Project2.

• Whenever possible implement automation and minimize administrative effort.

• Implement Project3, Project5, Project6, and Project7 based on the planned changes

• Implement Project4 and configure the project to push Docker images to Azure Container Registry.

You need to implement the code flow strategy for Project2 in Azure DevOps.

Which three 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.

Answer:

Explanation:

Scenario: Implement a code flow strategy for Project2 that will:

Enable Team2 to submit pull requests for Project2.

Enable Team2 to work independently on changes to a copy of Project2. Ensure that any

intermediary changes performed by Team2 on a copy of Project2 will be subject to the same restrictions as the ones defined in the build policy of Project2. Step 1: Create a repository

Step 2: Add a build policy for the master branch

Step 3: Create a branch

Each branch must have a defined policy about how to integrate code into this branch.

References: https://docs.microsoft.com/en-us/azure/devops/learn/devops-at-microsoft/release-flow

Latest AZ-400 Dumps Valid Version with 289 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments