You have Azure Pipelines and GitHub integrated as a source code repository. The build pipeline has continuous integration enabled. You plan to trigger an automated build whenever code changes are comm

The correct answer is B. batch changes. Batching CI runs If you have many team members uploading changes often, you may want to reduce the number of runs you start. If you set batch to true, when a pipeline is running, the system waits until the run is completed, then starts another run with all changes that have not y

Submitted by katya_ua· Mar 6, 2026Design and implement build and release pipelines

Question

You have Azure Pipelines and GitHub integrated as a source code repository. The build pipeline has continuous integration enabled. You plan to trigger an automated build whenever code changes are committed to the repository. You need to ensure that the system will wait until a build completes before queuing another build. What should you implement?

Options

Apath filters
Bbatch changes
Cscheduled builds
Dbranch filters

How the community answered

(45 responses)

A
9% (4)
B
87% (39)
C
2% (1)
D
2% (1)

Explanation

Batching CI runs If you have many team members uploading changes often, you may want to reduce the number of runs you start. If you set batch to true, when a pipeline is running, the system waits until the run is completed, then starts another run with all changes that have not yet been built. # specific branch build with batching To clarify this example, let us say that a push A to master caused the above pipeline to run. While that pipeline is running, additional pushes B and C occur into the repository. These updates do not start new independent runs immediately. But after the first run is completed, all pushes until that point of time are batched together and a new run is started. https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github

Community Discussion

No community discussion yet for this question.

Full AZ-400 Practice