Practice Test 2 | Designing And Implementing Microsoft DevOps Solutions | AZ-400 | Dumps | Mock Test
View Case Study
Which of the following can be applied to ensure that the application does not get promoted to the next stage in the pipeline if it has active bugs assigned to it?
A. Creating a trigger
B. Creating a deployment gate
C. Creating a pre-deployment approval
D. Creating a post-deployment approval
Answer – B
The requirement is
can be applied to ensure that the application does not get promoted to the next stage in the pipeline if it has active bugs assigned
Option A: Trigger
The triggers directive defines the automated ways in which the Pipeline should be re-triggered.
pipeline trigger help us when a large products have several components that are dependent on each other. These components are often independently built. When an upstream component (a library, for example) changes, the downstream dependencies have to be rebuilt and revalidated.
Hence trigger is not correct solution as not going to stop the promotion of application in next stage.
Ref: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/pipeline-triggers?view=azure-devops&tabs=yaml
Option B: deployment gate
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.
Hence this is correct answer. we can stop the promotion to next stage in the pipeline with any active bug
Ref: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops
Option C: Pre deployment approval
users must manually validate the change request and approve the deployment to a next stage
Hence this is not going to help us to stop the promotion of application to next stage and is not a correct solution
Ref: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/?view=azure-devops
Option D: Post deployment approval
users must manually sign out from the app after deployment before the release is promoted to next stages
Hence this is not going to help us to stop the promotion of application to next stage and is not a correct solution
Ref: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/?view=azure-devops
Comments are closed, but trackbacks and pingbacks are open.