Exam AZ-400 topic 8 question 29 discussion

B is correct - Not such option as gates timeout in pre-deployment approvals. Pre-deployment approvals are for manual approvals and gates are for automatic approvals

Correct answer: A

Answer A meets the goal, with pre-deployment gate option delay set to 8 hours, ensure the deployment will not fail less than 8 hours

B. No Modifying the Time between re-evaluation of gates option will not address the issue of deployments failing if approvals take longer than two hours. This option controls how frequently the gate conditions are re-evaluated during the release deployment process. To ensure that deployments only fail if approvals take longer than eight hours, the Timeout setting for pre-deployment approvals should be modified.

https://learn.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops#define-a-gate-for-a-stage Gates and approvals - For pre-deployment conditions, the default is to prompt for manual (user) approvals first, then evaluate gates afterwards. Changing gate condition will have no effect when you also configured manual (user) approvals

Gates allow automated calls to external services. Since this is a manual approval, we should not work with the gate settings. Answer is No

The answer is A. The Gates section of the Pre-deployment condition has an option for Time between re-evaluation of gates and this is the right feature that needs to be amended to 8 hours. https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops

B is correct answer. Pre-deployment approvals is where timeout settings are changed.

B is the correct answer but not only for the reason explained in the description. You cannot use gates here because we are speaking about manual approval by a team leader. You have to go to Pre-deployment conditions and change on Pre-deployment approvals section the timeout from 2 to 8 hours.

Answer is correct but the explanation is incorrect. You must use the "Pre-deployment approval" which is part of the "Pre-deployment conditions". This has nothing to do with "gates". The question is: The condition requires that releases be approved by a team leader before they are deployed So, gates have nothing to do with it. The answer is correct. The solution is to increase the timeout in Pre-deployment approvals from 2 to 8hs (as is required by policy) According to me justification is as follows: Timeout condition of gate will fail / stop entire deployment process. This timeout option can be configured by expanding evaluation option available in pre-deployment condition -> gates -> evaluation option. Also if "pre-deployment approvals" is enable that means it can add list of users who can approve or reject the deployment. If this option is disable then anyone can approve this request. Microsoft docs states the same with example https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deploy-using-approvals?view=azure-devops

The answer is NO, mainly for one reason, among the requirements it has a manual action and only specifies to do it automatically, modifying the re-evaluation time, which would not meet the requirements or the answer remains incomplete

Answer is No

No. This is an incomplete answer as "The time between re-evaluation of gates" is merely a sampling interval. "The sampling interval and TIMEOUT work TOGETHER so that the gates will call their functions at suitable intervals, and reject the deployment if they don't all succeed during the same sampling interval and within the TIMEOUT period." We should instead also set the TIMEOUT value to 8 hours for the field "The timeout after which gates fail" under "Evaluation options". Both fields are available under https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deploy-using-approvals?view=azure-devops

The time between re-evaluation of gates: The duration after which the gates are re-evaluated. This must be greater than the longest typical response time of the configured gates to allow all responses to be received in each evaluation. It has nothing to do with timeouts, answer B

Timeout after which gates fail. The maximum evaluation period for all gates. The deployment will be rejected if the timeout is reached before all gates succeed during the same sampling interval. The predeployment gate and timeout are covered in MS doc, i think the answer is yes

We could say that the key phrase here is "if the approvals take longer than eight hours.", it means that you are not only waiting for the approval of your team leader, also you are waiting for other approvals. That is the reason why We could think that "gates" answer should be the correct one.

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deploy-using-approvals?view=azure-devops seems to be correct