What is the primary purpose of using GitHub Issues in a feedback cycle strategy?

To store the final version of the codebase for each release.

To automatically deploy code changes to production when an issue is closed.

To replace all other forms of communication, such as email and chat, within the team.

To capture and track feedback, bugs, and feature requests in a structured and searchable way.

A company uses Azure Boards for planning and GitHub for code. They want to enforce that every pull request references a work item and that the work item is marked 'Done' only after the PR is merged and the build succeeds. What should they configure?

Use branch policies to require a linked work item and a GitHub Action to update the work item after a successful build.

Use a GitHub Action that automatically sets the work item to 'Done' when the PR is opened.

Use a webhook that updates the work item when the PR is merged, regardless of build status.

Rely on developers to manually link work items and update the status after merge.

A team using GitHub Flow wants to maintain a clean, linear history on main while still using pull requests. They also need to trace each merge to a work item. What should they configure?

Disable branch protection to allow fast-forward merges only.

Use 'Squash and merge' and rely on commit messages to reference work items.

Use 'Create a merge commit' as the merge method and require work items.

Enable 'Require linear history' in branch protection and require linked work items on PRs.

A company uses GitHub for code and Azure Boards for work tracking. They want to enforce that every PR is linked to a work item, but they also want to allow a small number of 'chore' PRs that do not require a work item. What should they implement?

Use a branch policy that requires a linked work item, but allow a specific label 'chore' to bypass the requirement.

Require a linked work item on all PRs and create a 'chore' work item type for such tasks.

Do not enforce the requirement and rely on developers to link work items when relevant.

Use a GitHub Action that fails the PR if no work item is linked, and manually override for chores.

A team using GitHub Flow wants to ensure that every feature branch is short-lived and that work items are updated when a branch is created and when it is merged. What should they implement?

Use a GitHub Project board and move cards manually.

Use a webhook that updates the work item when a branch is deleted.

Use a branch naming convention that includes the work item ID and manually update the work item.

Use a GitHub Action that creates a work item when a branch is created and updates it when the PR is merged.

Microsoft Certified:DevOps Engineer Expert

Domain 1Objective 1

Design and Implement Traceability and Flow of Work AZ-400 Practice Questions (Page 2)

Part of the Design and implement processes and communications domain, which makes up ~22% of our current practice bank. Microsoft does not publish an official question count, but from its 140-minute exam (~55–95 total, ~12–21 in this domain), expect 4–7 from this objective — we provide 31 practice questions to prepare you well beyond it. (estimate)

31questions here

7free pages

6concepts

Questions 6–10

6foundation · easy
What is the primary purpose of using GitHub Issues in a feedback cycle strategy?
Select an answer first
7application · medium
A company uses Azure Boards for planning and GitHub for code. They want to enforce that every pull request references a work item and that the work item is marked 'Done' only after the PR is merged and the build succeeds. What should they configure?
Select an answer first
8expert · hard
A team using GitHub Flow wants to maintain a clean, linear history on main while still using pull requests. They also need to trace each merge to a work item. What should they configure?
Select an answer first
9expert · hard
A company uses GitHub for code and Azure Boards for work tracking. They want to enforce that every PR is linked to a work item, but they also want to allow a small number of 'chore' PRs that do not require a work item. What should they implement?
Select an answer first
10expert · hard
A team using GitHub Flow wants to ensure that every feature branch is short-lived and that work items are updated when a branch is created and when it is merged. What should they implement?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AZ-400

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “AZ-400” is a trademark of its owner, used for identification only.