Approval Process Timeout Solution
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 Pre-deployment conditions, you modify the Timeout setting for pre-deployment approvals.
Does this meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.B
Use a gate instead of an approval instead.
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gatesThe proposed solution meets the goal.
The problem states that releases must be approved by a team leader before they are deployed, and that there is a policy stating that approvals must occur within eight hours. Additionally, it is noted that deployment fails if approvals take longer than two hours.
The proposed solution is to modify the Timeout setting for pre-deployment approvals. By increasing the Timeout setting to eight hours, the goal of ensuring that deployments only fail if approvals take longer than eight hours can be met.
Therefore, the proposed solution meets the goal and the answer is A. Yes.
