MicrosoftProfessional levelAZ-400

AZ-400 exam dumps: 306 free Azure DevOps Engineer Expert practice questions

Free AZ-400 practice questions for the Designing and Implementing Microsoft DevOps Solutions exam, with the correct answer and a full explanation for every option. Read the first 10 below, browse all 306 by number, or take a timed practice exam.

Question bank last updated May 2025

Start timed practice exam Browse all 306 questions

Free AZ-400 practice questions

Questions 1 to 10 of 306

Pick an answer before you open the explanation. Each question also has its own page with a permalink.

AZ-400 Question 1

Select 2

Your organization has recently adopted Azure DevOps for managing backlog items in Azure Boards and version control in Azure Repos. They want to ensure that every code commit is automatically associated with a relevant user story, so they can track the feature� progress from planning through to release. They also want to measure lead time and cycle time for each feature. Which two actions should you recommend to achieve end-to-end traceability between work items and code commits?

A
Instruct developers to include the work item ID in commit messages using the 'AB#' syntax to automatically link commits to user stories.
B
Enable branch policies to require a linked work item in each pull request before it can be merged.
C
Use multiple Git repositories, one per user story, so each repository can be directly tied to a specific backlog item.
D
Disable the Build Validation policy on pull requests to simplify linking between commits and user stories.

Show answer and explanation

Correct answers: A, B

Explanation

To design and implement end-to-end traceability in Azure DevOps, each code change should be tied to the corresponding backlog item. By instructing developers to reference work items in commit messages using 'AB#' and enforcing branch policies that require a linked work item before merging, teams can maintain a clear flow of work. These practices align with Microsoft� guidance on linking work items to commits (see Microsoft Documentation: https://learn.microsoft.com/azure/devops/boards/work-items/link-work-items-from-commits).

A. Correct.
Option 1 is correct. Including the work item ID in the commit message (e.g., 'AB#42') is the recommended approach to automatically link Azure Boards work items to commits in Azure Repos. This ensures you can trace changes from the user story to the actual code and gather metrics such as lead time and cycle time.
B. Correct.
Option 2 is correct. Enabling branch policies for pull requests that require referencing a work item helps enforce best practices and ensures that no code changes are merged without associating them to a specific user story. This enforces traceability.
C. Incorrect.
Option 3 is incorrect. Creating a separate Git repository for each user story would fragment the codebase and complicate overall flow. It does not inherently improve traceability or metrics gathering; instead, it introduces additional overhead in repository maintenance.
D. Incorrect.
Option 4 is incorrect. Disabling Build Validation does nothing to enhance traceability. Build Validation policies help ensure code quality and can be configured to enforce further requirements, but disabling them removes an important check without improving work-item linking.

AZ-400 Question 2

Single answer

Your organization is implementing a new feature in Azure DevOps and wants to ensure each code change is linked to the appropriate work items for complete traceability. The team decides to enforce references to work items in commit messages or pull request descriptions before merging changes. Which action should you implement to achieve this requirement?

A
Configure a branch policy in Azure Repos that requires linked work items in pull requests before allowing merges.
B
Enable the 'Enforce Commit Message Policy' in the Azure DevOps Project Settings under Boards > Process.
C
Create an Azure DevOps Pipeline task that automatically appends work item IDs to commit messages.
D
Use a Git hook on each developer's machine to insert work item references before the local commit is completed.

Show answer and explanation

Correct answer: A

Explanation

Designing and implementing traceability in Azure DevOps often involves enforcing references to work items in commits or pull requests. By configuring a branch policy within Azure Repos, you can ensure that changes referencing relevant tasks or user stories are merged only when they meet the traceability requirement. This approach aligns with best practices outlined in Microsoft Docs for maintaining end-to-end traceability (see https://docs.microsoft.com/azure/devops/repos/git/branch-policies for details).

A. Correct.
Correct. Configuring a branch policy in Azure Repos to enforce linked work items in PRs ensures that changes cannot be merged unless they reference the correct work items. This is the recommended approach since it centralizes the enforcement and provides an end-to-end traceability mechanism.
B. Incorrect.
Incorrect. There is no native 'Enforce Commit Message Policy' under Boards > Process in Azure DevOps. Process configurations do not provide commit message validation. This distractor could be believed if someone wrongly assumed boards process settings apply to commit messages.
C. Incorrect.
Incorrect. An Azure DevOps Pipeline task can be used to detect commit messages or annotate work items, but it does not strictly enforce that developers include the references in their local commits or PRs prior to entering the pipeline. It� not a reliable method of preventing merges without work item references.
D. Incorrect.
Incorrect. While Git hooks can enforce policies locally, they can be bypassed or incorrectly configured on each developer� machine. They are not a centralized or recommended approach for enterprise-level enforcement. Branch policies are more effective and consistent in Azure DevOps.

AZ-400 Question 3

Select 2

You are designing a solution in Azure DevOps for a cross-functional team. The team frequently commits and merges changes without linking them to the relevant work items, causing confusion about which user stories or bugs have been addressed. You want to enforce traceability so that every pull request references at least one relevant Azure Boards work item, and to streamline the flow of work from backlog item creation through deployment. Which two actions should you take to accomplish this goal?

A
Enable the 'Require a linked work item' branch policy in Azure Repos to prevent merges when no work items are linked.
B
Configure the build validation policy so that the branch cannot be merged unless the build is successful.
C
Use the '#' mention in commit messages or pull request titles to automatically link commits to their respective work items.
D
Apply a manual code review policy requiring at least two reviewers to check code quality and best practices.
E
Disable the auto-complete feature on pull requests to force developers to finalize merges manually.

Show answer and explanation

Correct answers: A, C

Explanation

To maintain traceability in Azure DevOps, you can enforce policies that require all code changes be associated with the relevant work items. The 'Require a linked work item' branch policy prevents merges lacking a linked work item, and using the '#' mention in commit messages or pull request titles ensures automatic linking. These measures address the root cause (unassociated work items) and establish an end-to-end flow of work. For more details, see the Microsoft documentation on branch policies (https://docs.microsoft.com/azure/devops/repos/git/branch-policies).

A. Correct.
Option 1 is correct. Enabling the 'Require a linked work item' policy in Azure Repos ensures that a pull request cannot be merged unless at least one work item is linked, thereby enforcing traceability and preventing unassociated changes.
B. Incorrect.
Option 2 is incorrect. While a build validation policy helps maintain code quality by ensuring builds pass before merging, it does not require or enforce linking changes to work items, so it does not solve the traceability issue.
C. Correct.
Option 3 is correct. Using the '#' mention in commits or pull requests automatically creates links to the appropriate work items in Azure Boards. This approach streamlines traceability without requiring manual linking each time.
D. Incorrect.
Option 4 is incorrect. A manual code review policy can improve the quality of the code, but it does not specifically enforce linking changes to work items. It addresses best practices in code review, not traceability.
E. Incorrect.
Option 5 is incorrect. Disabling the auto-complete feature may slow down merges and encourage manual oversight, but it does not inherently enforce linking to a work item. There is no mechanism in this setting that ties code changes to work items.

AZ-400 Question 4

Single answer

Your team is building a new cloud-native microservices application and wants to implement a simple, collaborative workflow using GitHub Flow. The team requires that each new feature or bug fix be developed and tested in isolation, with code reviews performed before merging changes into the main branch. Which approach best satisfies these requirements?

A
Allow all developers to commit directly into the main branch after local testing.
B
Create a short-lived branch for each feature or fix, push changes, open a pull request, and only merge it into the main branch after reviews pass and automated checks succeed.
C
Use separate branches for each environment (development, test, production) to isolate changes until they are deemed ready for production.
D
Adopt a single shared developer branch that merges into the main branch monthly to reduce merge conflicts.

Show answer and explanation

Correct answer: B

Explanation

GitHub Flow emphasizes a lightweight branching model with each change developed on a dedicated short-lived branch. Pull requests, reviews, and automated tests help ensure quality before merging into the main branch, supporting continuous integration and frequent deployments. This model is documented in GitHub's own workflow best practices: https://docs.github.com/en/get-started/quickstart/github-flow.

A. Incorrect.
Option 1 is incorrect because allowing developers to commit directly into main bypasses formal code reviews and can introduce broken changes without adequate checks.
B. Correct.
Option 2 is correct. This is the classic GitHub Flow approach: each feature or fix is worked on in its own branch, then merged back into main through a pull request once it passes review and testing.
C. Incorrect.
Option 3 is incorrect because juggling multiple long-lived environment branches is more aligned with GitFlow or release flow patterns, not simple GitHub Flow. GitHub Flow typically relies on a single main branch for deployment and uses short-lived branches for changes.
D. Incorrect.
Option 4 is incorrect because merging changes only once a month can block early feedback and continuous integration. It delays finding defects and complicates merges.

AZ-400 Question 5

Select 2

Your team has decided to adopt GitHub Flow to streamline feature development and ensure that your main branch is always in a deployable state. You want to enforce consistent workflows that both encourage collaboration and safeguard production-ready code. Which two actions should be included to align with GitHub Flow best practices?

A
Create a dedicated branch from the main branch for each new feature and work exclusively within that branch.
B
Merge the feature branch into the main branch via a Pull Request that includes code reviews before merging.
C
Force-push all feature branches directly to the main branch to keep commits linear and minimize merge commits.
D
Use a rebase-and-merge approach without requiring any peer review to reduce overhead in merging.

Show answer and explanation

Correct answers: A, B

Explanation

Under GitHub Flow, every feature or fix should be developed in its own branch, undergo code reviews via Pull Requests, and only then be merged into main. This approach ensures a clean commit history, fosters collaboration, and maintains production-ready code. For more information, refer to the official GitHub documentation on GitHub Flow best practices.

A. Correct.
Option A is correct. Creating a dedicated branch for each feature is a core principle of GitHub Flow, ensuring that work is isolated and can be independently tested or reviewed.
B. Correct.
Option B is correct. GitHub Flow recommends using Pull Requests with peer reviews before merging to catch issues early and maintain code quality in main.
C. Incorrect.
Option C is incorrect. Force-pushing directly to main bypasses the collaborative review process and can overwrite others� work, defeating a key objective of GitHub Flow.
D. Incorrect.
Option D is incorrect. Skipping code reviews removes critical checks. Although rebase-and-merge is a valid merge strategy, omitting peer review goes against best practices.

AZ-400 Question 6

Select 2

Your development team has recently adopted GitHub Flow for a new web application. Each developer creates feature branches from the main branch, and then opens a pull request to merge their changes back into main. However, the team has experienced issues with incomplete code accidentally merging into the main branch and wants to test changes in an ephemeral environment before merging. Which two actions should you recommend to improve the team� workflow according to GitHub Flow best practices?

A
Build a short-lived test environment for every pull request before merging
B
Merge incomplete code into the main branch and revert it later if issues are found
C
Enable branch protection rules requiring code reviews before merging
D
Push directly to the main branch whenever local tests pass

Show answer and explanation

Correct answers: A, C

Explanation

GitHub Flow emphasizes keeping the main branch stable and deployable by using feature branches, pull requests, and peer reviews. By requiring at least one reviewer and building short-lived test environments for each pull request, the team can validate changes thoroughly and maintain high code quality. Refer to GitHub� official documentation on 'Branch Protection Rules' and 'Pull Requests' for more details on these best practices.

A. Correct.
Correct. Creating ephemeral (short-lived) test environments for pull requests aligns with GitHub Flow best practices. It allows all stakeholders to test changes in isolation before merging.
B. Incorrect.
Incorrect. Merging incomplete code and reverting later can introduce delays and confusion. GitHub Flow encourages keeping the main branch in a deployable state at all times.
C. Correct.
Correct. Requiring code reviews aligns with GitHub Flow and helps catch issues before merging into the main branch. Branch protection rules enforce process consistency.
D. Incorrect.
Incorrect. Pushing directly to main bypasses essential steps like code review and automated testing, increasing the risk of merging incomplete or broken code.

AZ-400 Question 7

Select 2

You are building a feedback cycle for a web application that uses GitHub for source control and Azure DevOps for continuous integration and deployment. You want your development team to be quickly informed whenever a critical production issue arises, and you also want all feedback to be tracked in a central location. Which two actions should you take to design an effective feedback loop?

A
Configure a webhook from your monitoring system that automatically creates GitHub issues when production alerts are raised.
B
Deploy a GitHub Action that listens for newly opened issues and sends real-time notifications to the development team.
C
Ask developers to manually review production error logs each morning and create GitHub issues when they notice recurring patterns.
D
Set up an automatic rule to close issues older than 24 hours if no comments are added by users or developers.
E
Use GitHub Discussions as the primary mechanism to file bugs and urgent feedback from production.

Show answer and explanation

Correct answers: A, B

Explanation

To create a robust feedback pipeline, you should combine automated issue creation (e.g., via webhooks from your monitoring system) with real-time notifications (e.g., GitHub Actions that trigger Slack/Microsoft Teams messages). GitHub Issues is the recommended channel for tracking and triaging production issues. For more information, see GitHub documentation on webhooks (https://docs.github.com/en/developers/webhooks-and-events) and GitHub Actions (https://docs.github.com/en/actions).

A. Correct.
Correct: Webhooks allow you to automatically create a GitHub issue when an alert is triggered in your monitoring system. This ensures that any new production incidents have a corresponding issue without requiring manual intervention.
B. Correct.
Correct: A GitHub Action listening for newly opened issues can notify the development team via email, Slack, or Microsoft Teams. This approach ensures rapid visibility and a streamlined workflow.
C. Incorrect.
Incorrect: Relying on manual reviews of logs can delay feedback and increase the chance of missing critical issues. Automated creation of issues is more reliable for real-time alerts.
D. Incorrect.
Incorrect: Closing issues automatically after a short time (24 hours) can lead to unresolved or missed critical issues. While some auto-close policies exist, they typically allow more time and are based on inactivity, not strict timelines.
E. Incorrect.
Incorrect: GitHub Discussions is designed for broader conversations and community engagement. For production incidents and direct bug tracking, GitHub Issues provide better tooling, workflows, and integrations with CI/CD pipelines.

AZ-400 Question 8

Select 2

You are a DevOps Engineer at an organization that uses GitHub for version control and GitHub Actions for continuous integration. Developers have complained that they frequently miss critical build failures in pull requests and cannot easily track remediation work. You want to design a feedback mechanism that (1) sends immediate notifications when builds fail, and (2) automatically creates a new GitHub issue assigned to the correct developers when a failure occurs. Which two steps should you implement to meet these requirements?

A
Add a step in your GitHub Actions workflow to invoke the GitHub Issues API upon build failure, assigning it to the responsible team members.
B
Configure your repository� GitHub Actions settings to skip all notifications for failed builds in pull requests.
C
Enable email notifications in your GitHub repository settings, and use a workflow that listens for a 'workflow_run' event with a 'failure' status to auto-create and assign a new issue.
D
Install a third-party extension to automatically convert all build failures into Azure Boards work items, bypassing GitHub Issue creation.

Show answer and explanation

Correct answers: A, C

Explanation

To set up effective feedback loops, you can leverage GitHub Actions� ability to trigger events and call the GitHub REST API. By enabling email notifications (or other communication channels) and automatically creating a GitHub Issue upon build failure, development teams gain immediate visibility and an actionable way to track remediation. For more details, refer to GitHub� official documentation on GitHub Actions workflows and GitHub Issues APIs (https://docs.github.com/en/actions and https://docs.github.com/en/rest/issues).

A. Correct.
Option 1 is correct. GitHub Actions supports calling the GitHub REST API from within a workflow. You can check if a build step has failed and then use the 'issues' endpoint to create and assign a new issue, ensuring immediate tracking of failures.
B. Incorrect.
Option 2 is incorrect. This option disables notifications for failed builds, which contradicts the goal of creating an immediate feedback loop for developers.
C. Correct.
Option 3 is correct. GitHub� built-in email notifications can be integrated with a custom workflow triggered on 'workflow_run' (failure) to automate issue creation and assignment, providing immediate visibility into problems.
D. Incorrect.
Option 4 is incorrect. Bypassing GitHub Issues altogether does not match the requirement to track failures in GitHub Issues. Additionally, this approach delegates tracking responsibilities to Azure Boards, which was not part of the stated requirement.

AZ-400 Question 9

Select 2

You manage a CI/CD pipeline for a web application stored in a GitHub repository. The build process runs automated functional tests in a staging environment. The product owner requests immediate notifications whenever a test fails, and wants a new GitHub issue automatically created with relevant logs to streamline troubleshooting. Which two approaches should you recommend to implement an automated feedback cycle that meets these requirements? (Choose two options.)

A
1. Create a GitHub Actions workflow triggered on every push to the main branch. If tests fail, automatically generate a GitHub issue with detailed logs and assign it to the appropriate team. Provide an email notification to the product owner by configuring GitHub notifications.
B
1. Require manual issue creation by the QA team after reviewing test logs in the pipeline console. Configure pipeline notifications to alert only the engineering manager.
C
1. Use a GitHub Actions workflow triggered by the 'workflow_run' event that checks the status of the test job. If the job fails, parse the test results, generate a GitHub issue, and rely on GitHub� watch/notification settings to alert the product owner.
D
1. Set up a weekly scheduled workflow that amalgamates any test failures over the past week into a single GitHub issue, and forward the issue link to the product owner for review.

Show answer and explanation

Correct answers: A, C

Explanation

Implementing automated, immediate feedback involves leveraging GitHub Actions triggers that parse test results and create GitHub issues on failure, alongside configured notifications to key stakeholders. Options 1 and 3 use GitHub Actions appropriately for real-time alerts and issue creation. Refer to the official GitHub Actions documentation (https://docs.github.com/en/actions) for details on triggers, event types, and recommended best practices for integrating workflow_run events with issue creation.

A. Correct.
Option 1 is correct. A GitHub Actions workflow triggered on push can detect test failures, create a new issue for each failure, and provide immediate notifications if the product owner is watching the repository or email notifications are configured. This aligns with the requirement for automated and immediate feedback.
B. Incorrect.
Option 2 is incorrect. Relying on manual issue creation introduces delays. While pipeline notifications help, they do not automatically open GitHub issues or ensure immediate feedback to the product owner.
C. Correct.
Option 3 is correct. Using a 'workflow_run' event to check the status of a completed workflow is a practical way to parse final test results and automate GitHub issue creation. Configuring the product owner� GitHub account to watch the repository helps ensure they receive alerts.
D. Incorrect.
Option 4 is incorrect. Aggregating failures weekly does not meet the need for immediate notifications. Immediate feedback cycles require on-demand issue creation and real-time alerts when tests fail.

AZ-400 Question 10

Select 2

Your organization uses Azure DevOps for project tracking but stores its source code in GitHub. You want to ensure that when developers commit or create pull requests in GitHub, those changes are automatically linked to the corresponding Azure Boards work items. Which two actions should you perform to achieve this integration?

A
Install the Azure Boards app from the GitHub Marketplace and connect it to your Azure DevOps organization.
B
Use the AB# syntax in commit messages or pull request titles to link them to the corresponding work item in Azure Boards.
C
Create an Azure Pipeline that triggers on every GitHub commit to automatically update work items in Azure Boards.
D
Configure a YAML pipeline that references your repository and automatically assigns work items to new commits and pull requests.
E
Configure a GitHub repository-level setting to enforce referencing an Azure Boards work item in each commit.

Show answer and explanation

Correct answers: A, B

Explanation

To integrate GitHub commits and pull requests with Azure DevOps Boards, you must install and configure the Azure Boards GitHub app. Then, developers reference work items by including AB# followed by the work-item ID in their commit messages or PR titles (for example, 'AB#123'). This allows Azure Boards to automatically link source code changes to specific work items according to Microsoft� recommended best practices.

A. Correct.
Installing the Azure Boards app in GitHub is a key step. It enables you to connect your GitHub repository to Azure DevOps Boards so that commits and pull requests can be associated with work items.
B. Correct.
Using the AB# syntax (for example, AB#123) in commit messages or pull request titles is how Azure Boards recognizes which work item to link. This is crucial for automatic linkage.
C. Incorrect.
While creating an Azure Pipeline can be useful for continuous integration and deployment, it is not a required step for simply linking commits and pull requests to Azure Boards work items.
D. Incorrect.
Configuring a YAML pipeline is helpful for building and releasing code, but it does not automatically assign or link work items. Linking is handled by the Azure Boards integration and the AB# syntax.
E. Incorrect.
There is no direct GitHub repository-level setting to enforce referencing Azure Boards work items. Enforcing commit policies in Azure DevOps is possible, but it is not managed solely within GitHub settings.

Timed practice exam

Take a AZ-400 practice test under exam conditions

70 questions in 90 minutes, drawn from this bank, with a score report and a per-question review when you finish.

Start timed exam

What the AZ-400 exam covers

Official Designing and Implementing Microsoft DevOps Solutions exam domains and weightings.

Configure Processes and Communications
10% of exam
Design and Implement Source Control
15% of exam
Design and Implement Build and Release Pipelines
40% of exam
Develop a Security and Compliance Plan
10% of exam
Implement an Instrumentation Strategy
10% of exam

All 306 AZ-400 practice questions

Every question has a page with the answer and explanation. Numbers are stable, so you can bookmark or share them.

AZ-400 exam dumps FAQ

Are these AZ-400 dumps real exam questions?

No. These are original practice questions written to the Designing and Implementing Microsoft DevOps Solutions exam objectives, not questions copied from a live exam. Memorising leaked questions violates Microsoft's candidate agreement and stops working the moment the question pool rotates. Use this bank to check your understanding of each domain and to find the topics you still need to study.

How many AZ-400 practice questions are there?

306 questions, each with the correct answer, an explanation of the answer, and a note on why every other option is wrong. The first 10 are on this page and every question has its own page linked below.

Are the AZ-400 exam dumps free?

Yes. Every question, answer and explanation on this page and the linked question pages is free to read without an account. A free HydraNode account adds timed practice exams, scoring and progress tracking across attempts.

How do I take a timed AZ-400 practice test?

Sign in and start the Designing and Implementing Microsoft DevOps Solutions exam on HydraNode. A session gives you 70 questions drawn from this bank in 90 minutes, then a score report with a per-question review.

What topics does the AZ-400 exam cover?

The official exam domains are: Configure Processes and Communications; Design and Implement Source Control; Design and Implement Build and Release Pipelines; Develop a Security and Compliance Plan; Implement an Instrumentation Strategy.

More Microsoft exam dumps

All Microsoft exams

AZ-305243 questions

Azure Solutions Architect Expert exam dumps

Designing Microsoft Azure Infrastructure Solutions

AZ-700310 questions

Azure Network Engineer Associate exam dumps

Designing and Implementing Microsoft Azure Networking Solutions

AI-102493 questions

Azure AI Engineer Associate exam dumps

Designing and Implementing a Microsoft Azure AI Solution

AI-900286 questions

Azure AI Fundamentals exam dumps

Microsoft Azure AI Fundamentals

AZ-500273 questions

Azure Security Engineer Associate exam dumps

Microsoft Azure Security Technologies

AZ-104289 questions

Azure Administrator Associate exam dumps

Microsoft Certified: Azure Administrator Associate