AZ-400 Pipeline creation order Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Create the pipeline, then select the source repository, then configure triggers, then add tasks, then validate the pipeline.

  Why this is correct

  This is the correct order because you first create the pipeline, then specify the source code repository, set up triggers to define when builds should run, add tasks for building and testing, and finally validate the pipeline to ensure it works.

• ✗

  Create the pipeline, then configure triggers, then select the source repository, then add tasks, then validate the pipeline.

  Why it's wrong here

  Configuring triggers before selecting the source repository is invalid because trigger definitions, branch filters, and path filters all reference objects within a specific repository. Without a repository bound to the pipeline, trigger configuration has no target scope and cannot be persisted meaningfully. The repository must be selected first so the trigger settings can be applied to the correct branch and file paths during CI builds.

• ✗

  Create the pipeline, then add tasks, then select the source repository, then configure triggers, then validate the pipeline.

  Why it's wrong here

  Adding tasks before selecting the source repository fails because every build task—compiling, testing, or packaging—requires a checked-out source tree produced by the repository checkout step. In classic pipelines, tasks consume inputs from the fetched source artifacts, and without a repository there are no files to process or publish. The source selection must precede task authoring so tasks can reference the correct root folder and working directory.

• ✗

  Select the source repository, then create the pipeline, then configure triggers, then add tasks, then validate the pipeline.

  Why it's wrong here

  Selecting the source repository before creating the pipeline is not possible because the pipeline definition itself is the container that holds the repository reference. The creation wizard requires you to create or import the pipeline first, then choose the repository during the initial setup steps. Treating repository selection as a standalone pre-creation action reverses the actual Azure DevOps workflow and misrepresents the point at which the repository binding is established.

Go deeper

Related to this question