nature of task is configuration drift... this cant be checked using Deployment Gate, and requires manual intervention.
Ref: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops
"During release, deployments must not proceed between stages if any active bugs are logged against the release." - so, the approvers should check active bugs that are logged? It's an automatic capability of a Deployment gate - Query Work Items, with defined parameters Query (for instance, Critical Bugs) and Upper threshold.
Deployment gate - You want to ensure there are no active issues in the work item or problem management system before deploying a build to a stage - "Pre-deployment gates". https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/?view=azure-devops#:~:text=Deployments%20to%20each%20stage%20are,completion%20of%20the%20deployment%20pipeline.&text=Some%20users%20must%20manually%20sign,is%20promoted%20to%20other%20stages.
"deployments must not proceed between stages if any active bugs are logged against the release", it don't say "work item of type bug", for that reason I think the answer pre-deploy approval
Litware focuses on writing new code for customers. No resources are provided to refactor or remove existing code. Changes to the code base take a long time, as dependencies are not obvious to individual developers.
Merge operations of the code often take months and involve many developers. Code merging frequently introduces bugs that are difficult to locate and resolve.
Customers report that ownership costs of the retirement fund management system increase continually. The need to merge unrelated code makes even minor code changes expensive.
--- Gates wont catch issues with dependencies and code merge because its a legacy system
Code quality restrictions should not be manually approved or rejected, they should be fully automated and strictly standardized, not subjective. A deployment gate (B) will do that.
B is the answer.
https://learn.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops
Gates allow automatic collection of health signals from external services and then promote the release when all the signals are successful or stop the deployment on timeout. Typically, gates are used in connection with incident management, problem management, change management, monitoring, and external approval systems.
Some common use cases for deployment gates are:
Quality validation: Query pipeline metrics such as pass rate or code coverage and deploy only if they are within a predefined threshold.
B. a deployment gate.
A deployment gate is a release pipeline feature that blocks deployments between stages until certain conditions are met, such as passing tests or meeting code quality standards. In this case, the technical requirements state that deployments must not proceed between stages if any active bugs are logged against the release, making a deployment gate the appropriate choice to implement the code quality restriction.
"Code quality and release quality are critical. During release, deployments must not proceed between stages if any active bugs are logged against the release."
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/?view=azure-devops
"A team wants to ensure there are no active issues in the work item or problem management system before deploying a build to a stage. Pre-deployment gates"
Answer is B
Deployment gate – You want to ensure there are no active issues in the work item or problem management system before deploying a build to a stage – “Pre-deployment gates”.
Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/approvals
In my addled brain, both an approval and a gate can be used. The gate is an automated process, while the approval requires human intervention. If this scenario is emphasizing criticality, I would trust the occasional (in inevitable) human error less than a computer...
On that basis, I would choose B - but with all this there is a "right" answer and a "Microsoft right" answer.
From the LAB
Pre-deployment approvals
Select the users who can approve or reject deployments to this stage
Same for pre-deployment
The approvals is only for next step's (passed) approval :) If something involves to quality code check/security, the deployment gate should be implemented
Quite Confusing
Deployment Gate does Quality validation, which is automatic
Pre-Deployment approval is manual intervention, by checking appropriate work items and bugs
This section is not available anymore. Please use the main Exam Page.AZ-400 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Yanzhi
Highly Voted 4 years, 10 months agorhr
4 years, 9 months agoMefguine
4 years, 5 months agokcinofni
4 years, 5 months agoDev1079
3 years, 10 months agozyxphreez
Highly Voted 4 years, 4 months agoprashantjoge
2 years, 6 months agoHillah
Most Recent 9 months, 1 week agovsvaid
10 months, 1 week agoxRiot007
1 year, 2 months agozellck
1 year, 4 months agoMadbo
1 year, 6 months agosyu31svc
2 years, 2 months agoDrummer
2 years, 3 months agordemontis
2 years, 7 months agofelixeu31
2 years, 8 months agoSara_Mo
2 years, 9 months agoSara_Mo
2 years, 9 months agoQuirkafleeg
2 years, 10 months agoChauPhan
2 years, 11 months agoChauPhan
2 years, 11 months agoAbbas
3 years agoSACHMAM
3 years, 3 months ago