Question 1

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You plan to update the Azure DevOps strategy of your company.

You need to identify the following issues as they occur during the company's development process:

Licensing violations

Prohibited libraries

Solution: You implement continuous integration.

Does this meet the goal?

Options :

A : Yes

B : No

Answer: A

Question 2

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You plan to update the Azure DevOps strategy of your company.
You need to identify the following issues as they occur during the company's development process:
Licensing violations
Prohibited libraries
Solution: You implement continuous deployment.
Does this meet the goal?

Options :

A : Yes

B : No

Answer: B

Question 3

You have an Azure DevOps project that produces Node Package Manager (npm) packages. Multiple projects consume the packages.

You need to configure Azure Artifacts to ensure that both the latest and pre-release versions of the packages are available for consumption.

What should you do?

Options :

A : Create two feed views named @prerelease and @release, Set @release as the default view. Configure a release pipeline that tags the packages as release after successful testing.

B : Create a feed view named @prerelease. Configure a release pipeline that tags the packages as release after successful testing.

C : Create two feed views named @prerelease and @default. Configure a release pipeline that promotes a package to the @default view after successful testing.

D : Create two feed views named @prerelease and @release. Set @release as the default view. Configure a release pipeline that promotes a package to the @release view after successful testing.

Answer: D

Question 4

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an approval process that contains a condition. The condition requires that releases be approved by a team leader before they are deployed.

You have a policy stating that approvals must occur within eight hours.

You discover that deployment fail if the approvals take longer than two hours.

You need to ensure that the deployments only fail if the approvals take longer than eight hours.

Solution: From Post-deployment conditions, you modify the Timeout setting for post-deployment approvals.

Does this meet the goal?

Options :

A : Yes

B : No

Answer: B

Question 5

Which merge commit you will use to ensure desired commit history ?

Options :

A : Rebase with merge commit

B : Basic merge ( no fast-forward)

C : Squash merge

D : Rebase and fast-forward

Answer: D

Confidently Practice Online with Free AZ-400 Exam Cram

Buying Options: