AZ-400 Practice Question: Design and implement build and release pipelines
Exhibit
##[debug]Evaluating condition for step: 'Publish Artifact' ##[debug]Evaluating: succeededOrFailed() ##[debug]Result: 'True' ##[debug]Starting: Publish Artifact ============================================================================== Task : PublishBuildArtifacts Description : Publish build artifacts to Azure Pipelines or a file share Version : 1.0.0 Author : Microsoft Corporation ============================================================================== ##[error]Artifact 'drop' already exists for build 20241120.1. ##[error]The artifact name 'drop' is already used by another artifact in this build.
Refer to the exhibit. A build pipeline fails at the 'Publish Artifact' step. The pipeline has two jobs: 'Build' and 'Test'. Both jobs have a 'PublishBuildArtifacts' task with artifact name 'drop'. What is the most likely cause?
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
✓
Two jobs are publishing artifacts with the same name.
Artifact names must be unique within a build. Both jobs publish with the same name 'drop', causing a conflict.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The artifact name 'drop' contains invalid characters.
Why it's wrong here
The artifact name 'drop' is a valid Azure DevOps artifact name; it consists entirely of lowercase letters, which are permitted. The actual failure is not due to invalid characters but because multiple jobs are publishing artifacts with the same name 'drop', causing a collision.
- ✗
The artifact is too large to publish.
Why it's wrong here
Azure Pipelines does enforce artifact upload size limits, but exceeding that limit produces a distinct error message explicitly stating the size limit was surpassed. The exhibited error about publishing 'drop' indicates a duplicate artifact name conflict, not a size-related failure.
- ✓
Two jobs are publishing artifacts with the same name.
Why this is correct
When two or more jobs in the same pipeline publish artifacts with an identical artifact name, the Azure DevOps PublishPipelineArtifact task fails because artifact names must be unique within the entire pipeline run. The second job's attempt to publish 'drop' conflicts with the first job's already published artifact, causing the build to fail.
- ✗
The pipeline does not have permission to publish artifacts.
Why it's wrong here
A permission failure when publishing artifacts would generate an authorization error, typically 'Access denied', 'Unauthorized', or a message about the security token or service connection lacking the 'PublishPipelineArtifact' permission. The illustrated error points to a naming collision rather than an authentication or authorization problem.
Go deeper
Related to this question
Learn chapter
Designing a Build Pipeline
Key term
Task
A Task in Azure DevOps is a predefined, reusable step that performs a specific action during a build or release pipeline, like compiling code or running tests.
Key term
Artifact
An artifact is any file or package produced during the software development process that is used to deploy, test, or run an application.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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-400 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-400 exam.