AZ-400 practice question 18 of 35

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…

Choose your answer, then check it against the explanation.

Domain Develop a security and compliance plan

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 nothave 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 requiresthat 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?

Answer options

Correct Answer:

Explanation

The proposed solution is incorrect because it modifies the timeout for post-deployment approvals. The scenario describes a condition where releases must be approved before they are deployed, which is a pre-deployment approval. Changing the timeout in the post-deployment conditions will not affect the pre-deployment approval process. The deployment will continue to fail after the original two-hour timeout because the relevant pre-deployment approval timeout setting has not been changed. The correct action is to modify the timeout in the Pre-deployment conditions for the specific stage.

Why Incorrect

A. Yes: This is incorrect. The solution addresses the wrong stage of the pipeline (post-deployment) for a pre-deployment approval requirement, and therefore will not resolve the issue.

---

References

1. Microsoft. (n.d.). Release approvals and gates overview. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/devops/pipelines/release/approvals/

Section: "Approvals" - This section distinguishes between pre-deployment and post-deployment approvals

stating

"You can add manual approvals at the start of a stage (pre-deployment approvals) or at the end of a stage (post-deployment approvals)..." This establishes the two distinct locations for approval configuration.

2. Microsoft. (n.d.). Define your multi-stage continuous deployment (CD) pipeline. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/devops/pipelines/release/define-multistage-release-process

Section: "Pre-deployment conditions" - This section details the configuration of pre-deployment approvals

including the "Timeout" policy. It states

"If an approval is not completed within the timeout specified

the deployment is rejected." This confirms the correct location for modifying the setting described in the problem.

3. Microsoft. (n.d.). Configure approvals. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/devops/pipelines/release/approvals/approvals

Sections: "Configure pre-deployment approvals" and "Configure post-deployment approvals" - These sections provide step-by-step instructions and screenshots showing that pre- and post-deployment conditions are configured in separate panels

each with its own independent "Timeout" setting. This reinforces that modifying one does not affect the other.

Question 18 of 35

Keep practicing

Take the free AZ-400 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test