In a bug tracking system, what is the purpose of assigning a severity level to a bug?

To specify the exact code change required to fix the bug.

To indicate the impact of the bug on the system or users, helping prioritize fixes.

To determine which developer will fix the bug.

To track the number of times the bug has been reported.

In GitHub Projects, what is the primary purpose of a project board?

To define the branching strategy for the repository.

To visualize and manage the flow of work using columns that represent different stages of progress.

To store the source code for the project in a structured folder hierarchy.

To automatically generate release notes for each version of the software.

What is the primary purpose of quality traceability in the software development process?

To automatically generate quality reports without any human involvement.

To replace the need for manual testing in the development lifecycle.

To link quality-related activities, such as tests and reviews, to specific requirements or work items.

To ensure that all code is written in a single programming language.

A team uses GitHub Issues for bug tracking and Azure Boards for feature work. They want to ensure that bugs are not lost and that they are linked to the feature work that introduced them. What should they implement?

Disable GitHub Issues and use only Azure Boards for all bug tracking.

Create a new Azure Boards work item for every GitHub issue and manually link them.

Use the Azure Boards app to link GitHub issues to work items and create a GitHub Project board for bug triage.

Use a label 'bug' on GitHub issues and rely on the team to check the Issues tab.

In GitHub Flow, what is the primary purpose of creating a feature branch from the main branch?

To permanently store completed work separately from the main branch to avoid any risk of conflicts.

To isolate work on a new feature or bug fix until it is ready to be merged back into main.

To create a snapshot of the entire codebase for release management purposes.

To allow multiple developers to work on the same branch simultaneously without coordination.

Microsoft Certified:DevOps Engineer Expert

Domain 1Objective 1

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

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 21–25

21foundation · easy
In a bug tracking system, what is the purpose of assigning a severity level to a bug?
Select an answer first
22foundation · easy
In GitHub Projects, what is the primary purpose of a project board?
Select an answer first
23foundation · easy
What is the primary purpose of quality traceability in the software development process?
Select an answer first
24expert · hard
A team uses GitHub Issues for bug tracking and Azure Boards for feature work. They want to ensure that bugs are not lost and that they are linked to the feature work that introduced them. What should they implement?
Select an answer first
25foundation · easy
In GitHub Flow, what is the primary purpose of creating a feature branch from the main branch?
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.