Correct Answer: Release Gates (Query Work Items)
Release Gates in Classic Release pipelines automate pre-deployment or post-deployment checks. By configuring the 'Query Work Items' gate, the pipeline will run an Azure Boards quer...
Correct Answer
Release Gates (Query Work Items)
Why This Answer Is Correct
Release Gates in Classic Release pipelines automate pre-deployment or post-deployment checks. By configuring the 'Query Work Items' gate, the pipeline will run an Azure Boards query (e.g., 'Find active high severity bugs'). If the query returns any results, the gate fails and the deployment pauses until the bugs are closed.
This question evaluates your knowledge of Azure Pipelines — a core concept tested in Microsoft Certified: DevOps Engineer Expert (AZ-400). Understanding Azure Pipelines is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
Your organization uses Azure Pipelines for CI/CD. You have a pipeline that takes 45 minutes to run and requires compiling large C++ binaries. You are currently using Microsoft-hosted agents, but the build times are unacceptable. You want to reduce build times by utilizing incremental builds and cached dependencies. Which type of agent pool should you configure?
You are using Azure Pipelines environments to deploy to production. Before the deployment proceeds to the production environment, you need an external IT Service Management (ITSM) tool (like ServiceNow) to approve the change request ticket automatically. How do you implement this in Azure Pipelines?
Your organization has 50 different microservices, each with its own Azure Pipeline YAML file. All pipelines share the exact same 15-step security scanning and build process. You need to centralize this logic so that updating a security step applies to all microservices instantly without editing 50 files. What should you use?