AZ-400: Designing and Implementing Microsoft DevOps Solutions

Approvals in DevOps: How to Handle Approval Process for Deployments

Question

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 Time between re-evaluation of gates option.

Does this meet the goal?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B.

B

Use a gate From Pre-deployment conditions instead.

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates

The solution provided, which is to modify the "Time between re-evaluation of gates" option from Post-deployment conditions, does not meet the goal.

The "Time between re-evaluation of gates" option is used to specify how frequently the system should re-evaluate the gates during a deployment. Gates are used to verify the quality of the release before it is deployed, and they can be used to enforce certain conditions, such as requiring approval from a team leader before the release is deployed.

In this scenario, the problem is that deployments are failing if approvals take longer than two hours, but the policy requires that approvals must occur within eight hours. Modifying the "Time between re-evaluation of gates" option would not address this issue, because it would only affect how frequently the system re-evaluates the gates. It would not change the fact that the deployments are failing if approvals take longer than two hours.

To ensure that deployments only fail if the approvals take longer than eight hours, a different solution would be needed. One possible solution would be to modify the approval process to include a check for the policy stating that approvals must occur within eight hours. If an approval takes longer than eight hours, the deployment should not fail immediately, but instead should be put on hold until the issue can be resolved. Once the approval is granted, the deployment can proceed as normal.