Question 395 of 913
Design and implement a source control strategymediumMultiple ChoiceObjective-mapped

AZ-400 Practice Question: Design and implement a source control strategy

This AZ-400 practice question tests your understanding of design and implement a source control strategy. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Exhibit

Refer to the exhibit.
```json
{
  "status": "completed",
  "result": "failed",
  "ref": "refs/heads/feature/logging",
  "repository": {
    "name": "myapp",
    "url": "https://dev.azure.com/myorg/myapp/_apis/git/repositories/myapp"
  },
  "pipeline": {
    "name": "CI Pipeline",
    "id": 123
  }
}
```

You receive a webhook notification from Azure Pipelines with the above payload. The build for the 'feature/logging' branch failed. You want to automatically create a work item to track the fix. What should you configure in Azure DevOps?

Question 1mediummultiple choice
Full question →

Exhibit

Refer to the exhibit.
```json
{
  "status": "completed",
  "result": "failed",
  "ref": "refs/heads/feature/logging",
  "repository": {
    "name": "myapp",
    "url": "https://dev.azure.com/myorg/myapp/_apis/git/repositories/myapp"
  },
  "pipeline": {
    "name": "CI Pipeline",
    "id": 123
  }
}
```

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

Enable the 'Create work item on failure' option in the pipeline settings.

Option B is correct because Azure Pipelines provides a built-in setting called 'Create work item on failure' that automatically generates a work item (e.g., a bug or task) in Azure Boards whenever a pipeline run fails. This directly meets the requirement to track the fix for the failed build on the 'feature/logging' branch without requiring external integrations or manual steps.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • Add a branch policy on 'feature/logging' to require a successful build before merging.

    Why it's wrong here

    Policy does not create work items.

  • Enable the 'Create work item on failure' option in the pipeline settings.

    Why this is correct

    Automatically creates a work item when a build fails.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use a GitHub Actions workflow to create an issue on failure.

    Why it's wrong here

    GitHub Actions is for GitHub, not Azure Repos.

  • Create a service hook subscription to listen for build failures and call Azure Boards API.

    Why it's wrong here

    Possible but not the simplest option.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may overcomplicate the solution by choosing a manual or external integration (like service hooks or GitHub Actions) when Azure Pipelines already provides a simple, built-in configuration option for automatic work item creation on failure.

Detailed technical explanation

How to think about this question

The 'Create work item on failure' setting leverages the Azure Pipelines and Azure Boards integration, automatically mapping pipeline run failures to work items in the project's process (e.g., Agile, Scrum, CMMI). Under the hood, when a pipeline run fails, Azure DevOps triggers a system-defined service hook that creates a work item with details such as the failed stage, job, and task, linking it to the build run for traceability. In a real-world scenario, this ensures that every build break is immediately captured as a trackable item, preventing issues from being overlooked in fast-paced CI/CD workflows.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related AZ-400 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-400 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-400 question test?

Design and implement a source control strategy — This question tests Design and implement a source control strategy — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Enable the 'Create work item on failure' option in the pipeline settings. — Option B is correct because Azure Pipelines provides a built-in setting called 'Create work item on failure' that automatically generates a work item (e.g., a bug or task) in Azure Boards whenever a pipeline run fails. This directly meets the requirement to track the fix for the failed build on the 'feature/logging' branch without requiring external integrations or manual steps.

What should I do if I get this AZ-400 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.