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 Time between re-evaluation of gates option.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.A
Gates allow automatic collection of health signals from external services, and then promote the release when all the signals are successful at the same time or stop the deployment on timeout. Typically, gates are used in connection with incident management, problem management, change management, monitoring, and external approval systems.
Approvals and gates give you additional control over the start and completion of the deployment pipeline. Each stage in a release pipeline can be configured with pre-deployment and post-deployment conditions that can include waiting for users to manually approve or reject deployments, and checking with other automated systems until specific conditions are verified.
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gatesThe proposed solution of modifying the "Time between re-evaluation of gates" option from Pre-deployment conditions will not meet the stated goal.
The "Time between re-evaluation of gates" option is used to specify the time interval after which the approval gates are re-evaluated during the release pipeline. If the approval is pending, the gate checks for approval status again after the specified time interval. However, this option does not affect the total time that a deployment can wait for approval.
In the given scenario, the requirement is to ensure that the deployments only fail if the approvals take longer than eight hours. However, the current setup is configured to fail deployments if approvals take longer than two hours. To meet the goal, the configuration needs to be changed to allow a longer wait time for approvals.
One possible solution to achieve this goal is to modify the approval policy to allow a maximum wait time of eight hours instead of the current limit of two hours. This can be done by modifying the approval policy settings in Azure DevOps or Azure Pipelines to increase the time limit for approval.
Alternatively, another solution could be to implement an automated monitoring mechanism that tracks the time between the start of the deployment and the approval time. If the approval time exceeds eight hours, the deployment would be marked as failed automatically, and a notification would be sent to the relevant team members.
In conclusion, the proposed solution of modifying the "Time between re-evaluation of gates" option will not meet the stated goal. The approval policy needs to be modified to allow a longer wait time for approvals, or an automated monitoring mechanism needs to be implemented to track the approval time and mark the deployment as failed if it exceeds the specified time limit.