Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5
AZ-204 Practice Question: Monitor, troubleshoot, and optimize Azure solutions
Arrange the steps to create a CI/CD pipeline using Azure DevOps for an Azure App Service in the correct order.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a repository and push application code, then create a build pipeline, then configure CI trigger, then create a release pipeline, then set up approval gates.
The correct sequence for setting up a CI/CD pipeline in Azure DevOps is: First, create a repository and push your application code. Next, create a build pipeline to compile and package your application. Then, configure the CI trigger within the build pipeline to automate builds on code changes. After that, create a release pipeline to define the deployment steps for the build artifacts. Finally, set up approval gates within the release pipeline to control deployments to different environments.
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 a repository and push application code, then create a build pipeline, then create a release pipeline, then configure CI trigger, then set up approval gates.
Why it's wrong here
This order ensures code is available before building, build produces artifacts for release, release is created before adding triggers and gates, CI trigger is configured after build pipeline exists, and approval gates are added to the release pipeline after its creation.
- ✓
Create a repository and push application code, then create a build pipeline, then configure CI trigger, then create a release pipeline, then set up approval gates.
Why this is correct
This is incorrect because the CI trigger should be configured after the release pipeline is created, as the trigger initiates the build which then feeds into the release. Setting the CI trigger before creating the release pipeline may cause confusion if the release pipeline isn't ready to use the build artifacts.
- ✗
Create a build pipeline, then create a repository and push application code, then create a release pipeline, then configure CI trigger, then set up approval gates.
Why it's wrong here
A build pipeline's fundamental purpose is to process source code, meaning it requires a repository with application code to be present and specified as its source. Attempting to create a build pipeline *before* the repository exists and contains the necessary code will result in an invalid or non-functional pipeline definition. Azure DevOps build definitions explicitly link to a source repository, making this sequence illogical as there would be no code to fetch, compile, or package into artifacts.
- ✗
Create a repository and push application code, then create a release pipeline, then create a build pipeline, then configure CI trigger, then set up approval gates.
Why it's wrong here
This is incorrect because the release pipeline requires build artifacts from the build pipeline. Creating the release pipeline before the build pipeline means the release pipeline will have no artifacts to deploy, leading to failure.
Visual reference
Go deeper
Related to this question
About these practice questions
This AZ-204 question is part of Courseiva's 881-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.